lkml.org 
[lkml]   [2009]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Shared i2c adapter locking
    On Thu, 05 Nov 2009 13:57:24 +0000, Ben Hutchings wrote:
    > On Thu, 2009-11-05 at 14:11 +0100, Jean Delvare wrote:
    > [...]
    > > What about the following patch?
    > >
    > > From: Jean Delvare <khali@linux-fr.org>
    > > Subject: i2c: Add an interface to lock/unlock I2C bus segment
    > >
    > > Some drivers need to be able to prevent access to an I2C bus segment
    > > for a specific period of time. Add an interface for them to do so
    > > without twiddling with i2c-core internals.
    > >
    > > Signed-off-by: Jean Delvare <khali@linux-fr.org>
    > > Cc: Ben Hutchings <bhutchings@solarflare.com>
    > Acked-by: Ben Hutchings <bhutchings@solarflare.com>
    >
    > Presumably this is meant for net-next-2.6, and you'll implement

    Actually I meant to push this to Linus immediately, through my i2c
    tree. This is essentially a no-op: the binary code will be the same as
    before the patch, so guaranteed to be safe, and this will solve
    conflicts in linux-next.

    > i2c_{lock,unlock}_adapter() using rt_mutex in your i2c tree?

    Correct.

    --
    Jean Delvare
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2009-11-05 15:09    [W:0.022 / U:61.180 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site