[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vf+F3ArczHQ+nSmP4uFvRdMAQWufmR6xR0xtbHfVvFm-g@mail.gmail.com>
Date: Tue, 23 Apr 2024 13:34:21 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Thomas Richard <thomas.richard@...tlin.com>, Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>, Tony Lindgren <tony@...mide.com>, Aaro Koskinen <aaro.koskinen@....fi>,
Janusz Krzysztofik <jmkrzyszt@...il.com>, Vignesh R <vigneshr@...com>,
Andi Shyti <andi.shyti@...nel.org>, Peter Rosin <peda@...ntia.se>,
Lorenzo Pieralisi <lpieralisi@...nel.org>, Krzysztof Wilczyński <kw@...ux.com>,
Rob Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
Siddharth Vadapalli <s-vadapalli@...com>, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
linux-i2c@...r.kernel.org, linux-pci@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, gregory.clement@...tlin.com,
theo.lebrun@...tlin.com, thomas.petazzoni@...tlin.com, u-kumar1@...com,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH v5 01/11] gpio: pca953x: move suspend()/resume() to suspend_noirq()/resume_noirq()
On Tue, Apr 23, 2024 at 12:42 PM Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> On Tue, Apr 16, 2024 at 3:31 PM Thomas Richard
> <thomas.richard@...tlin.com> wrote:
..
> +i2c-rcar e66d8000.i2c: error -16 : 10000005
It probably means that I²C host controller is already in power off
mode and can't serve anymore.
> +pca953x 4-0020: Failed to sync GPIO dir registers: -16
> +pca953x 4-0020: Failed to restore register map: -16
> +pca953x 4-0020: PM: dpm_run_callback(): pca953x_resume_noirq
> returns -16
> +pca953x 4-0020: PM: failed to resume async noirq: error -16
Yeah, with this it's kinda forcing _every_ I²C host controller PM to
be moved also to noirq() or alike.
..
> All issues above are fixed by reverting this commit.
Let's revert as we close to the end of the cycle and this is not
something that can be fixed ASAP in my opinion.
..
Thanks for the report, It's a pity that it wasn't tested before from
the mailing list...
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists