Re: i2c-mux-gpio platform device ID issue

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

 



Yeah, replying to myself once again...

On Thu, 26 Jul 2012 09:28:14 +0200, Jean Delvare wrote:
> I slept on it and came up with what I think is an easier and more
> elegant solution. We could simply agree on using GPIO pin numbers as
> platform device IDs, as two i2c-gpio-mux instances can't control the
> same GPIO pin.

Unfortunately this simple and elegant solution is not compatible with a
feature I want to add to the i2c-mux-gpio driver (deferred probing.)
I'll post that other patch later today. Unless someone sees a solution
I missed, I'm afraid we'll have to choose which one of these two
patches we want to take in, and discard the other one.

-- 
Jean Delvare
--
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