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@xxxxxxxxxxxx>
> > 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@xxxxxxxxxxxx>
> > Cc: Ben Hutchings <bhutchings@xxxxxxxxxxxxxx>
> Acked-by: Ben Hutchings <bhutchings@xxxxxxxxxxxxxx>
>
> 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-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
