From: Lech Perczak <lech.perczak@gmail.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH] ARM: dts: nxp: imx7d-pico: add cpu-supply nodes
Date: Mon, 11 Dec 2023 23:41:35 +0100 [thread overview]
Message-ID: <5b285fdd-9d69-400c-978f-234665fca73e@gmail.com> (raw)
In-Reply-To: <20231206013247.GY236001@dragon>
W dniu 2023-12-06 o 02:32, Shawn Guo pisze:
> On Sat, Nov 18, 2023 at 12:23:52AM +0100, Lech Perczak wrote:
>> The PICO-IMX7D SoM has the usual power supply configuration using
>> output sw1a of PF3000 PMIC, which was defined in downstream derivative
>> of linux-imx (see link) in the sources for "Android Things" devkit.
>> It is required to support CPU frequency scaling.
>>
>> Map the respective "cpu-supply" nodes of each core to sw1a of the PMIC.
>>
>> Enabling them causes cpufreq-dt, and imx-thermal drivers to probe
>> successfully, and CPU frequency scaling to function.
>>
>> Link: https://android.googlesource.com/platform/hardware/bsp/kernel/nxp/imx-v4.1/+/o-iot-preview-5/arch/arm/boot/dts/imx7d-pico.dtsi#849
>>
>> Cc: Fabio Estevam <festevam@gmail.com>
>> Cc: Shawn Guo <shawnguo@kernel.org>
>> Cc: Sascha Hauer <s.hauer@pengutronix.de>
>>
>> Signed-off-by: Lech Perczak <lech.perczak@gmail.com>
> Applied, thanks!
Hi Shawn,
Do you think this could be backported to stable later?
OpenWrt and Debian could then pick this change up - I have a pull
request open in OpenWrt backporting this.
--
Pozdrawiam/With kind regards,
Lech Perczak
next prev parent reply other threads:[~2023-12-11 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 23:23 [PATCH] ARM: dts: nxp: imx7d-pico: add cpu-supply nodes Lech Perczak
2023-11-17 23:29 ` Fabio Estevam
2023-12-06 1:32 ` Shawn Guo
2023-12-11 22:41 ` Lech Perczak [this message]
2023-12-12 13:44 ` Fabio Estevam
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=5b285fdd-9d69-400c-978f-234665fca73e@gmail.com \
--to=lech.perczak@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).