On 06/02/2016 02:30 PM, Linus Walleij wrote:
On Wed, Jun 1, 2016 at 1:03 PM, Helmut Grohne <h.grohne@xxxxxxxxxx> wrote:When the PM initialization was moved in the commit referenced below, the code enabling the clock was removed from the probe function. On CONFIG_PM=y kernels, this is not a problem as the pm resume hook enables the clock, but when power management is disabled, all those pm_* functions are noops and the clock is never enabled resulting in a dysfunctional gpio controller. Put the clock initialization back to support CONFIG_PM=n. Signed-off-by: Helmut Grohne <h.grohne@xxxxxxxxxx> Fixes: 3773c195d387 ("gpio: zynq: Do PM initialization earlier to support gpio hogs")This does not apply to my kernel tree, can you rebase it on v4.7-rc1? Sould it be tagged for stable and sent to fixes? 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
I just ran into that problem when using v4.7-rc1 for our Zynq-7015 based custom board running without CONFIG_PM. It relies on MIO based GPIO for hardware identification, which immediately ceased to work.
Rebasing Helmut's patch for v4.7-rc1 fixes this issue, so I can confirm it works!
Regards, Helmut Buchsbaum -- 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
