On Mon, May 05, 2014 at 12:17:23PM -0700, Mark Brown wrote: > On Sun, May 04, 2014 at 11:21:47PM -0500, Maxime Ripard wrote: > > On Fri, May 02, 2014 at 10:40:48AM -0700, Mark Brown wrote: > > > > i2c-dev works great in these cases, because you always have access to > > > > all the bus, and all the devices, except if the device is already used > > > > by someone. The patch I suggested is an attempt to mimic this. > > > > It seems better to implement something like this at the device model > > > level, provide a way to have a default UIO driver for anything on a > > > given bus. I don't see anything bus specific apart from saying what the > > > default driver to use is and it avoids the icky code fiddling about with > > > what devices are bound and the races that might be involved duplicated > > > in individual buses. > > > Hmmm, yes, that's probably a great long-term way of dealing with this, > > but I don't see it happening soon. > > Isn't the code in the patch that started this thread roughly what's > needed, just done in a SPI specific way instead of a generic way? Hmmm, I think I get your point now. Yes, we could do it. Let me find some time to actually write something :) Thanks, Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Attachment:
signature.asc
Description: Digital signature
