From: Dragan Simic <dsimic@manjaro.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Lee Jones <lee@kernel.org>,
Dmitrii Osipenko <dmitry.osipenko@collabora.com>,
Mark Brown <broonie@kernel.org>, Urja <urja@urja.dev>,
Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com,
stable@vger.kernel.org
Subject: Re: [PATCH v1 1/1] mfd: rk8xx: Fix shutdown handler
Date: Sat, 03 Aug 2024 17:39:42 +0200 [thread overview]
Message-ID: <4637f562f327f7495ccfdd88590e07ef@manjaro.org> (raw)
In-Reply-To: <ih7hiojzuvqzpyipj66mgu5pmcderltabim7s5dnfzm6qpztbh@jqkst5tfw5ra>
Hello all,
On 2024-08-01 17:22, Sebastian Reichel wrote:
> On Thu, Aug 01, 2024 at 02:18:23PM GMT, Lee Jones wrote:
>> > + /*
>> > + * Currently the Rockchip SPI driver always sleeps when doing SPI
>> > + * transfers. This is not allowed in the SYS_OFF_MODE_POWER_OFF
>> > + * handler, so we are using the prepare handler as a workaround.
>> > + * This should be removed once the Rockchip SPI driver has been
>> > + * adapted.
>> > + */
>>
>> So why not just adapt the SPI driver now?
>
> This patch is simple and thus can easily be backported, so that the
> Acer Chromebook shutdown is fixed in the stable kernels. SPI based
> rkxx has been using SYS_OFF_MODE_POWER_OFF_PREPARE from the start,
> so it's not a regression.
>
> As far as I could see the SPI framework does not have something
> comparable to the I2C .xfer_atomic handler. So fixing up the
> Rockchip SPI driver probably involves creating some SPI core
> helpers. I'm not yet sure about the best way to deal with this.
> But I guess it will be better not having to backport all of the
> requires changes to stable.
>
> In any case I think the next step in this direction is discussing
> how to handle this in general for SPI.
I agree about accepting this (hot)fix first, and improving the SPI
drivers later. Having this fixed now provides clear benefits.
Also, please feel free to include:
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
>> What's the bet that if accepted, this hack is still here in 5 years
>> time?
>
> Even if I don't work on this now, I would expect somebody to have
> issues with broken shutdown on RK3588 boards before 5 years are
> over :)
next prev parent reply other threads:[~2024-08-03 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 18:05 [PATCH v1 1/1] mfd: rk8xx: Fix shutdown handler Sebastian Reichel
2024-07-30 19:07 ` Urja
2024-07-31 19:43 ` Heiko Stübner
2024-08-01 13:18 ` Lee Jones
2024-08-01 15:22 ` Sebastian Reichel
2024-08-03 15:39 ` Dragan Simic [this message]
2025-03-20 10:10 ` SPI transfers in atomic context [Was: Re: [PATCH v1 1/1] mfd: rk8xx: Fix shutdown handler] Uwe Kleine-König
2025-03-20 11:23 ` Mark Brown
2025-03-28 5:27 ` Dmitry Osipenko
2024-08-01 15:31 ` [PATCH v1 1/1] mfd: rk8xx: Fix shutdown handler Dmitry Osipenko
2024-08-01 17:41 ` Heiko Stübner
2024-08-01 17:52 ` Sebastian Reichel
2024-08-01 18:05 ` Dmitry Osipenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4637f562f327f7495ccfdd88590e07ef@manjaro.org \
--to=dsimic@manjaro.org \
--cc=broonie@kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=stable@vger.kernel.org \
--cc=urja@urja.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox