From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>, Jonas Karlman <jonas@kwiboo.se>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 0/2] arm64: dts: rockchip: Add pwm nodes for RK3528
Date: Wed, 12 Mar 2025 20:38:31 +0100 [thread overview]
Message-ID: <7779050.EvYhyI6sBW@phil> (raw)
In-Reply-To: <b7d8d385-81ee-4947-ab8f-1da43843464b@kwiboo.se>
Am Mittwoch, 12. März 2025, 16:00:00 MEZ schrieb Jonas Karlman:
> Hi Chukun,
>
> On 2025-03-12 15:35, Chukun Pan wrote:
> > Hi,
> >
> >> The pinctrl-names should be changed to "default" and not "active",
> >> something you can fixup or do you want a patch?
so yes of course the pinctrl needs to be default - simply because
that's the only pinctrl state mainline supports.
But judging by the fact that you're discussing working vs. non-working
below, can you please check if we should drop the patch for 6.15 till
that is solved?
Thanks a lot
Heiko
> > Sorry I've been a bit busy this week and forgot to send the v2 patch.
> > In rk3528.dtsi, the uart and upcoming i2c nodes do not have pinctrl,
> > so I prefer to remove them.
> >
> >>> Unlike other SoCs, pinctrl-names need to be in "active" state,
> >>> I'm not sure about this, but otherwise the pwm-regulator will
> >>> not work properly.
> >
> > BTW, setting the pinctrl of pwm corresponding to pwm-regulator
> > to "default" will cause kernel boot suspended.
> > Sorry but do you know why?
>
> Not an issue I have seen, do you have any more logs or details? E.g.
> what board you use, full regulator node, do you have operating points
> defined etc.
>
> I have runtime tested a branch at [1], that use pinctrl-names = default,
> have vdd_arm and vdd_logic defined, also an opp table for cpu and gpu.
>
> For E20C there is a commit to enable the vdd_logic, however without gpu
> enabled and a mali-supply the pwm-regulator is initialized to
> max-microvolt by Linux. Have instead updated U-Boot to initialize the
> pwm-regulator's:
>
> ```
> &vdd_arm {
> regulator-init-microvolt = <953000>;
> };
>
> &vdd_logic {
> regulator-init-microvolt = <900000>;
> };
> ```
>
> [1] https://github.com/Kwiboo/linux-rockchip/commits/next-20250311-rk3528/
>
> Regards,
> Jonas
>
> >
> > e.g.
> > ```
> > vdd_arm: regulator-vdd-arm {
> > compatible = "pwm-regulator";
> > pwms = <&pwm1 0 5000 1>;
> > ...
> > };
> >
> > &pwm1 {
> > pinctrl-0 = <&pwm1m0_pins>;
> > pinctrl-names = "default";
> > status = "okay";
> > };
> > ```
> >
> > Thanks,
> > Chukun
> >
> > --
> > 2.25.1
> >
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>, Jonas Karlman <jonas@kwiboo.se>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 0/2] arm64: dts: rockchip: Add pwm nodes for RK3528
Date: Wed, 12 Mar 2025 20:38:31 +0100 [thread overview]
Message-ID: <7779050.EvYhyI6sBW@phil> (raw)
In-Reply-To: <b7d8d385-81ee-4947-ab8f-1da43843464b@kwiboo.se>
Am Mittwoch, 12. März 2025, 16:00:00 MEZ schrieb Jonas Karlman:
> Hi Chukun,
>
> On 2025-03-12 15:35, Chukun Pan wrote:
> > Hi,
> >
> >> The pinctrl-names should be changed to "default" and not "active",
> >> something you can fixup or do you want a patch?
so yes of course the pinctrl needs to be default - simply because
that's the only pinctrl state mainline supports.
But judging by the fact that you're discussing working vs. non-working
below, can you please check if we should drop the patch for 6.15 till
that is solved?
Thanks a lot
Heiko
> > Sorry I've been a bit busy this week and forgot to send the v2 patch.
> > In rk3528.dtsi, the uart and upcoming i2c nodes do not have pinctrl,
> > so I prefer to remove them.
> >
> >>> Unlike other SoCs, pinctrl-names need to be in "active" state,
> >>> I'm not sure about this, but otherwise the pwm-regulator will
> >>> not work properly.
> >
> > BTW, setting the pinctrl of pwm corresponding to pwm-regulator
> > to "default" will cause kernel boot suspended.
> > Sorry but do you know why?
>
> Not an issue I have seen, do you have any more logs or details? E.g.
> what board you use, full regulator node, do you have operating points
> defined etc.
>
> I have runtime tested a branch at [1], that use pinctrl-names = default,
> have vdd_arm and vdd_logic defined, also an opp table for cpu and gpu.
>
> For E20C there is a commit to enable the vdd_logic, however without gpu
> enabled and a mali-supply the pwm-regulator is initialized to
> max-microvolt by Linux. Have instead updated U-Boot to initialize the
> pwm-regulator's:
>
> ```
> &vdd_arm {
> regulator-init-microvolt = <953000>;
> };
>
> &vdd_logic {
> regulator-init-microvolt = <900000>;
> };
> ```
>
> [1] https://github.com/Kwiboo/linux-rockchip/commits/next-20250311-rk3528/
>
> Regards,
> Jonas
>
> >
> > e.g.
> > ```
> > vdd_arm: regulator-vdd-arm {
> > compatible = "pwm-regulator";
> > pwms = <&pwm1 0 5000 1>;
> > ...
> > };
> >
> > &pwm1 {
> > pinctrl-0 = <&pwm1m0_pins>;
> > pinctrl-names = "default";
> > status = "okay";
> > };
> > ```
> >
> > Thanks,
> > Chukun
> >
> > --
> > 2.25.1
> >
>
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-03-12 19:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 12:00 [PATCH 0/2] arm64: dts: rockchip: Add pwm nodes for RK3528 Chukun Pan
2025-03-07 12:00 ` Chukun Pan
2025-03-07 12:00 ` [PATCH 1/2] dt-bindings: pwm: rockchip: Add rockchip,rk3528-pwm Chukun Pan
2025-03-07 12:00 ` Chukun Pan
2025-03-07 15:35 ` Conor Dooley
2025-03-07 15:35 ` Conor Dooley
2025-03-07 17:07 ` Uwe Kleine-König
2025-03-07 17:07 ` Uwe Kleine-König
2025-03-08 16:25 ` Heiko Stuebner
2025-03-08 16:25 ` Heiko Stuebner
2025-03-09 0:24 ` Uwe Kleine-König
2025-03-09 0:24 ` Uwe Kleine-König
2025-03-07 12:00 ` [PATCH 2/2] arm64: dts: rockchip: Add pwm nodes for RK3528 Chukun Pan
2025-03-07 12:00 ` Chukun Pan
2025-03-09 18:28 ` Jonas Karlman
2025-03-09 18:28 ` Jonas Karlman
2025-03-12 7:45 ` (subset) [PATCH 0/2] " Heiko Stuebner
2025-03-12 7:45 ` Heiko Stuebner
2025-03-12 14:00 ` Jonas Karlman
2025-03-12 14:00 ` Jonas Karlman
2025-03-12 14:35 ` Chukun Pan
2025-03-12 14:35 ` Chukun Pan
2025-03-12 15:00 ` Jonas Karlman
2025-03-12 15:00 ` Jonas Karlman
2025-03-12 19:38 ` Heiko Stuebner [this message]
2025-03-12 19:38 ` Heiko Stuebner
2025-03-13 7:10 ` Chukun Pan
2025-03-13 7:10 ` Chukun Pan
2025-03-13 8:22 ` Jonas Karlman
2025-03-13 8:22 ` Jonas Karlman
2025-03-13 9:01 ` Chukun Pan
2025-03-13 9:01 ` Chukun Pan
2025-03-13 12:03 ` Jonas Karlman
2025-03-13 12:03 ` Jonas Karlman
2025-03-13 13:01 ` Chukun Pan
2025-03-13 13:01 ` Chukun Pan
2025-03-14 15:40 ` Chukun Pan
2025-03-14 15:40 ` Chukun Pan
2025-03-13 22:14 ` Heiko Stuebner
2025-03-13 22:14 ` Heiko Stuebner
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=7779050.EvYhyI6sBW@phil \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.