Re: [PATCH 0/6] GPIO character device skeleton

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

 



On Fri, Oct 30, 2015 at 2:55 AM, Alexandre Courbot <gnurou@xxxxxxxxx> wrote:
> On Sun, Oct 25, 2015 at 3:42 AM, Markus Pargmann <mpa@xxxxxxxxxxxxxx> wrote:

>> What happens if we have two I2C gpio expanders with the same I2C
>> addresses connected to different I2C busses? If I see this correctly
>> they would both show up with the same name. Is there an easy and
>> race-free way to see which GPIO chip is connected to which I2C bus?
>
> I suppose the bus path could be part of the GPIO chip name to avoid
> this ambiguity, something like: 7000c000.i2c/0-001c.gpio

For DT that is the simple solution.

Right now it used gpiochip->label if that is set, else the name of
the gpiochip device like gpiochip0, gpiochip1 etc.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux