Re: GPIO regression on mvebu and/or max310x since 2ab73c6d8323

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

 



On Tue, Jun 23, 2020 at 11:11 PM Jan Kundrát <jan.kundrat@xxxxxxxxx> wrote:

> > Unfortunately I'm largely ignorant of the relation between
> > gpio, pinctrl and pinmux, so I'm afraid I cannot dig much
> > further. Should I try to blindly add the "gpio-ranges" into the
> > DTS, for example?
>
> Hi Thierry, Linus,
> can you help me with this, please? As it is now, my GPIO-based I2C no
> longer works since 2ab73c6d8323 on this Solidrun Clearfog Base. I suspect
> that this is because of no gpio-ranges property in the DTS files, but I
> don't know how the mvebu gpio/pinctrl/pinmux drivers work internally to
> debug this.

I have as little clue as you, who maintains this driver? Who wrote it?

Can you just send a patch to the Armada DTS file adding these ranges?

Yours,
Linus Walleij




[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