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

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

 



Adrian Cox wrote:

>On Sat, 2004-04-03 at 15:30, Jean Delvare wrote:
>
>  
>
>>I'm not sure that the function you propose would be really useful. I
>>guess that most people don't load i2c chip drivers they don't need. The
>>class filter you propose, added to the different I2C addresses, should
>>do the rest.
>>    
>>
>
>What about using two DVB cards of different models to record off one
>multiplex while watching another?
>
>Only an explicit list of which chips should be probed on each I2C bus is
>safe for this sort of system.
>
>  
>
You might be able to use the ignore= and force=  parameters to the i2c 
drivers to accomplish this.  With ignore you can prevent a driver from 
scanning an address (specify -1 as the bus to ignore that address on all 
busses) and with force you can specify which bus/address to find the 
specific chip.

I haven't read the code in detail yet, but if force doesn't already 
override ignore, it probably should.  I can't think of reason why you 
would want ignore to override a force directive.

:v)



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

  Powered by Linux