From: Dragan Simic <dsimic@manjaro.org>
To: Vicente Bergas <vicencb@gmail.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-spi@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Rockchip SPI: Runtime PM usage count underflow!
Date: Sun, 18 Aug 2024 20:26:38 +0200 [thread overview]
Message-ID: <d35a5c5216ee3d0321c725aea61e0326@manjaro.org> (raw)
In-Reply-To: <CAAMcf8Dts3=6CxNCLZBvXsdFHpaOs9mL2NJ8TMPU5+duray6-g@mail.gmail.com>
Hello Vincente,
On 2024-08-18 20:13, Vicente Bergas 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!
I'm working on a related patch. Could you, please, describe your
use case for the spidev driver, i.e. what board are you using it on,
and for what purpose?
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-08-18 18:27 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 [this message]
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
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=d35a5c5216ee3d0321c725aea61e0326@manjaro.org \
--to=dsimic@manjaro.org \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--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=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