From: Andre Przywara <andre.przywara@arm.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: <u-boot@lists.denx.de>, Jagan Teki <jagan@amarulasolutions.com>,
Cody Eksal <masterr3c0rd@epochal.quest>,
Philippe Simons <simons.philippe@gmail.com>,
Sumit Garg <sumit.garg@kernel.org>, <linux-sunxi@lists.linux.dev>,
Tom Rini <trini@konsulko.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: Re: [PATCH v2 3/6] arm64: dts: allwinner: a100: Add CPU Operating Performance Points table
Date: Mon, 12 May 2025 11:46:45 +0100 [thread overview]
Message-ID: <20250512114645.60bff4cb@donnerap.manchester.arm.com> (raw)
In-Reply-To: <ab250c1b-d227-404d-b834-300b82b925a9@cherry.de>
On Mon, 12 May 2025 11:24:07 +0200
Quentin Schulz <quentin.schulz@cherry.de> wrote:
> Hi Andre,
>
> On 5/11/25 3:10 AM, Andre Przywara wrote:
> > Add an Operating Performance Points table for the CPU cores to
> > enable Dynamic Voltage & Frequency Scaling on the A100.
> >
> > Signed-off-by: Shuosheng Huang <huangshuosheng@allwinnertech.com>
> > [masterr3c0rd@epochal.quest: fix typos in -cpu-opp, use compatible]
> > Signed-off-by: Cody Eksal <masterr3c0rd@epochal.quest>
> > Link: https://patch.msgid.link/20241031070232.1793078-14-masterr3c0rd@epochal.quest
> > Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >
> > [ upstream commit: a8181e6861fec3068f393d77ff81b2aaf4ea4203 ]
>
> Did you use tools/update-subtree.sh to cherry-pick those commits? The
No, I didn't, just remembered that afterwards. This would only work for
this patch anyways, since the other two DT patches are not yet merged in a
tagged release (the last one isn't even reviewed yet), so I just added them
here for completeness, to give people an idea of how the defconfig would
look like and to allow compile testing.
The plan was to maybe merge the first two patches (the DRAM code and
Kconfig bits), then wait for the DT bits to trickle in.
Thanks!
Andre
> changelog seems odd to me compared to what we usually get when using
> that tool. Modifications of dts/upstream should only be done via this tool.
>
> Same remark for the other DTS changes in this series.
>
> Cheers,
> Quentin
next prev parent reply other threads:[~2025-05-12 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 1:09 [PATCH v2 0/6] sunxi: Allwinner A133 SoC support Andre Przywara
2025-05-11 1:09 ` [PATCH v2 1/6] sunxi: A133: add DRAM init code Andre Przywara
2025-05-11 9:23 ` Andre Przywara
2025-05-12 9:21 ` Quentin Schulz
2025-05-12 10:49 ` Andre Przywara
2025-05-12 15:12 ` Cody Eksal
2025-05-26 13:45 ` Parthiban
2025-05-11 1:09 ` [PATCH v2 2/6] sunxi: add support for the Allwinner A100/A133 SoC Andre Przywara
2025-05-11 1:10 ` [PATCH v2 3/6] arm64: dts: allwinner: a100: Add CPU Operating Performance Points table Andre Przywara
2025-05-12 9:24 ` Quentin Schulz
2025-05-12 10:46 ` Andre Przywara [this message]
2025-05-12 15:58 ` Quentin Schulz
2025-05-11 1:10 ` [PATCH v2 4/6] arm64: dts: allwinner: a100: set maximum MMC frequency Andre Przywara
2025-05-11 1:10 ` [PATCH v2 5/6] arm64: dts: allwinner: a100: add Liontron H-A133L board support Andre Przywara
2025-05-11 1:10 ` [PATCH v2 6/6] sunxi: add support for Liontron H-A133L board Andre Przywara
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=20250512114645.60bff4cb@donnerap.manchester.arm.com \
--to=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=masterr3c0rd@epochal.quest \
--cc=quentin.schulz@cherry.de \
--cc=simons.philippe@gmail.com \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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