Messages in this thread | | | Subject | Re: Shared i2c adapter locking | From | Ben Hutchings <> | Date | Thu, 05 Nov 2009 13:57:24 +0000 |
| |
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 i2c_{lock,unlock}_adapter() using rt_mutex in your i2c tree?
Ben.
-- Ben Hutchings, Senior Software Engineer, Solarflare Communications Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked.
-- 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/
| |