[RFC][2.6] Additional i2c adapter flags for i2c client isolation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 17, 2004 at 09:05:04PM +0100, Jean Delvare wrote:
> > > How would we export the value though? Numerical, with user-space
> > > headers to be included by user-space applications? Or converted to
> > > some explicit text strings so that no headers are needed?
> > 
> > A text string would be simple enough to use.
> 
> I'm not sure.  What about a chip driver that would belong to more than
> one class?  What about the eeprom driver which will belong to all
> classes?  With a numeric value, a simple binary operation handles all
> the cases.  With text strings we would end having to parse a possibly
> multi-valued string, and do string comparisons, with at least one
> exception to handle.  This is likely to require much more resources,
> don't you think?

Ok, I wasn't really awake when writing that, you are correct.  Other
devices export "values" that have to be looked up in tables in userspace
(think device ids).  We can just export a hex number that matches the
ones in i2c.h

Anyone want to write a patch?  :)

thanks,

greg k-h



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux