gpiolib and pinmux interaction

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

 



Hi Linus,
Have a small question.

In case where pinmux is used with gpiolibd, shouldn't the consumer be set to "used" or something if the pin was muxed and acquired by different driver ?

The example below refers to pinctrl driver with ability to mux every pin as a gpio. The output of gpioinfo is misleading, as it appears that all the gpio muxable pins are free to be used.

# gpioinfo
gpiochip0 - 29 lines:
        line   0:      unnamed       unused   input  active-high
        line   1:      unnamed       unused   input  active-high
        line   2:      unnamed       unused   input  active-high

# gpioset gpiochip0 2=1
[    6.642630] dum-pinctrl 1400000.pinctrl: pin PA2 already requested by a00000.uart; cannot claim for gpio-low:469
[    6.642668] dum-pinctrl 1400000.pinctrl: pin-2 (gpio-low:469) status -22
gpioset: error setting the GPIO line values: Invalid argument

Thanks,
Ramon.




[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