From: Dragan Simic <dsimic@manjaro.org>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Alexey Charkov <alchark@gmail.com>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org,
Sebastian Reichel <sebastian.reichel@collabora.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: Fix broken tsadc pinctrl binding for rk3588
Date: Tue, 28 Jan 2025 10:24:33 +0100 [thread overview]
Message-ID: <b57d8a834f5c07e37e0e7ee74346c700@manjaro.org> (raw)
In-Reply-To: <CAP1tNvTRER=QzC29Udw4ffOetVECWV+MfZ2o-mbUFvuZ0_i-Kw@mail.gmail.com>
Hello Alexander,
On 2025-01-26 15:25, Alexander Shiyan wrote:
>> > > I think it's actually better to accept the approach in Alexander's
>> > > patch, because the whole thing applies to other Rockchip SoCs as well,
>> > > not just to the RK3588(S).
>> >
>> > Anyway, I've just tried it after including the changes below, and
>> > while /sys/kernel/debug/pinctrl/pinctrl-handles shows the expected
>> > pinctrls under tsadc, the driver still doesn't seem to be triggering a
>> > PMIC reset. Weird. Any thoughts welcome.
>>
>> I found the culprit. "otpout" (or "default" if we follow Alexander's
>> suggested approach) pinctrl state should refer to the &tsadc_shut_org
>> config instead of &tsadc_shut - then the PMIC reset works.
>
> Great, I'll use this in v2.
Please, let's wait with the v2 until I go through the whole thing again,
which I expected to have done already, but had some other "IRL stuff"
that
introduced a delay.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-01-28 9:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 5:26 [PATCH] arm64: dts: rockchip: Fix broken tsadc pinctrl binding for rk3588 Alexander Shiyan
2025-01-24 8:33 ` Alexey Charkov
2025-01-24 10:06 ` Dragan Simic
2025-01-24 10:25 ` Alexey Charkov
2025-01-24 10:37 ` Dragan Simic
2025-01-24 10:45 ` Dragan Simic
2025-01-24 17:23 ` Alexey Charkov
2025-01-24 19:44 ` Alexey Charkov
2025-01-26 6:10 ` Dragan Simic
2025-01-26 14:25 ` Alexander Shiyan
2025-01-28 9:24 ` Dragan Simic [this message]
2025-01-28 10:30 ` Alexey Charkov
2025-01-28 10:44 ` Dragan Simic
2025-10-03 13:33 ` Laurent Pinchart
2025-10-03 14:13 ` Alexey Charkov
2025-10-03 14:55 ` Alexey Charkov
2025-10-03 23:28 ` Laurent Pinchart
2025-10-04 11:41 ` Alexey Charkov
2025-10-04 22:03 ` Laurent Pinchart
2025-10-05 10:55 ` Alexey Charkov
2025-10-05 18:29 ` Laurent Pinchart
2025-10-03 23:52 ` Laurent Pinchart
2025-01-26 6:09 ` Dragan Simic
2025-01-24 10:38 ` 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=b57d8a834f5c07e37e0e7ee74346c700@manjaro.org \
--to=dsimic@manjaro.org \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eagle.alexander923@gmail.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=stable@vger.kernel.org \
/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