Re: Bug Report: Bus substitution causing a problem

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

 



On Mon, 8 Jul 2013 15:27:32 -0700, Guenter Roeck wrote:
> On Tue, Jul 09, 2013 at 12:00:13AM +0200, Jean Delvare wrote:
> > The problem here is that your i2c bus driver is evil and attributes the
> > same name to two different buses. It should not do that. This is a bug
> > in the i2c-omap driver. It should give each bus a distinct name, for
> > example by including the base I/O address in it.
>
> Unfortunately it is not the only such driver.
> 
> Same output on P2020:
> 
> i2c-0   i2c             MPC adapter                             I2C adapter
> i2c-1   i2c             MPC adapter                             I2C adapter
> 
> And on P5040:
> 
> i2c-0   i2c             MPC adapter                             I2C adapter
> i2c-1   i2c             MPC adapter                             I2C adapter
> i2c-2   i2c             MPC adapter                             I2C adapter
> i2c-3   i2c             MPC adapter                             I2C adapter
> 
> Question is ... would a patch to fix that be accepted by the i2c maintainers ?

I think it would, yes, as long as you explain why it is needed.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors




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

  Powered by Linux