From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Vicente Bergas" <vicencb@gmail.com>,
"Huang-Huang Bao" <i@eh5.me>,
"Rockchip SoC..." <linux-rockchip@lists.infradead.org>,
<linux-spi@vger.kernel.org>, "Heiko Stuebner" <heiko@sntech.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Sasha Levin" <sashal@kernel.org>
Cc: "linux-arm-kernel" <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Mark Brown" <broonie@kernel.org>
Subject: Re: [BUG] Rockchip SPI: Runtime PM usage count underflow!
Date: Mon, 19 Aug 2024 15:33:12 +0200 [thread overview]
Message-ID: <D3JXD607339U.2F1IAKUSM59UP@cknow.org> (raw)
In-Reply-To: <CAAMcf8Ctr9rOZ2oOzk48haakJOO2bzyNURb2oZTRxJ3tnafXUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On Mon Aug 19, 2024 at 3:14 PM CEST, Vicente Bergas wrote:
> On Mon, Aug 19, 2024 at 2:49 PM Vicente Bergas <vicencb@gmail.com> wrote:
> > On Mon, Aug 19, 2024 at 4:12 AM Vicente Bergas <vicencb@gmail.com> wrote:
> > > > i am a user of the CONFIG_SPI_SPIDEV device.
> > > > It stopped working between 6.8 and 6.10.5.
> > > > The SPI bus itself reports no errors to userspace, but no devices
> > > > appear connected to the bus.
> > > > The platform used is RK3328.
> > > > The only spi-related message in dmesg is:
> > > > rockchip-spi ff190000.spi: Runtime PM usage count underflow!
FWIW: I've seen this issue as well.
> > Added:
> > Huang-Huang Bao <i@eh5.me>
> > Linus Walleij <linus.walleij@linaro.org>
> > Sasha Levin <sashal@kernel.org>
> >
> > The first offending commit is:
> > 29d8101fb9442544077e68e27839a1979f85633d pinctrl: rockchip: fix pinmux
> > bits for RK3328 GPIO2-B pins
> >
> > I've also tested 6.10.6 with it reverted (and
> > 456447ff1fe3c28e2fd7b57a79650f62245c6428 and
> > 7127c68c76f120367b9a5053f524df0b603d4a48 as dependencies) and SPI
> > works fine.
>
> Sorry for the noise:
> reverting only 29d8101fb9442544077e68e27839a1979f85633d makes it work on 6.10.6.
> Ignore what i said about 456447ff1fe3c28e2fd7b57a79650f62245c6428 and
> 7127c68c76f120367b9a5053f524df0b603d4a48.
Please try if unreverting that commit and adding the following:
https://lore.kernel.org/linux-rockchip/20240709105428.1176375-1-i@eh5.me/
fixes the issue as well.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-08-19 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 18:13 [BUG] Rockchip SPI: Runtime PM usage count underflow! Vicente Bergas
2024-08-18 18:26 ` Dragan Simic
2024-08-18 18:55 ` Vicente Bergas
2024-08-18 19:20 ` Dragan Simic
2024-08-18 20:10 ` Vicente Bergas
2024-08-18 20:26 ` Dragan Simic
2024-08-19 2:12 ` Vicente Bergas
2024-08-19 12:49 ` Vicente Bergas
2024-08-19 13:14 ` Vicente Bergas
2024-08-19 13:33 ` Diederik de Haas [this message]
2024-08-19 14:37 ` Vicente Bergas
2024-08-19 14:51 ` Diederik de Haas
2024-08-19 20:14 ` Dragan Simic
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=D3JXD607339U.2F1IAKUSM59UP@cknow.org \
--to=didi.debian@cknow.org \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=i@eh5.me \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=vicencb@gmail.com \
/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