Re: i2c-mux-gpio platform device ID issue

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

 



On Wed, Jul 25, 2012 at 11:37:27PM +0200, Jean Delvare wrote:
> On Wed, 25 Jul 2012 20:32:43 +0100, Mark Brown wrote:
> > On Wed, Jul 25, 2012 at 04:39:13PM +0200, Jean Delvare wrote:

> > > I am using magic ID value -4 for this (I left -2 and -3 free in case
> > > we ever need a couple of other magic values.) The automatically

> > We could always add the new magic values starting at -3 instead...

> No, because my approach consumes _all_ negative values below the magic
> value. First mux will get -4, second will get -5 etc.

Oh, these are the values you're assigning not the value you use to
request this behaviour?  I see, that makes more sense.
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux