From: Frank.Li@oss.nxp.com
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Primoz Fiser <primoz.fiser@norik.com>
Cc: Frank Li <Frank.Li@nxp.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, upstream@lists.phytec.de,
Yunus Bas <y.bas@phytec.de>
Subject: Re: [PATCH 0/2] ARM: dts: phyCORE-i.MX6 custom OPP table
Date: Thu, 1 Oct 2026 10:57:36 -0400 [thread overview]
Message-ID: <179086665044.2214513.936581075433795034.b4-ty@b4> (raw)
In-Reply-To: <20260923070505.494949-1-primoz.fiser@norik.com>
From: Frank Li <Frank.Li@nxp.com>
On Wed, 23 Sep 2026 09:05:03 +0200, Primoz Fiser wrote:
> This is a revival of a series originally posted by Yunus Bas in
> February 2022 [1][2]. It adds a label to the imx6dl cpu1 node and
> introduces phyCORE-i.MX6 SOM specific operating-points tables, since
> the phyCORE modules run at slightly different voltage/frequency values
> than the generic i.MX6Q/DL tables.
>
> [1] https://lore.kernel.org/all/20220209223258.1672425-1-y.bas@phytec.de/
> [2] https://lore.kernel.org/all/20220209223258.1672425-2-y.bas@phytec.de/
>
> [...]
Applied, thanks!
[1/2] ARM: dts: imx6dl: Add a label to cpu1 node
commit: dcbe9b512afacb9a6ee8966b8129861e02256a8f
[2/2] ARM: dts: imx6qdl: phycore-som: Add custom volt/freq table
commit: bf2f5dba1ff19d575eb9917c7722bf095724f4a6
Best regards,
--
Frank Li <Frank.Li@nxp.com>
prev parent reply other threads:[~2026-10-01 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 7:05 Primoz Fiser
2026-09-23 7:05 ` [PATCH 1/2] ARM: dts: imx6dl: Add a label to cpu1 node Primoz Fiser
2026-09-23 7:05 ` [PATCH 2/2] ARM: dts: imx6qdl: phycore-som: Add custom volt/freq table Primoz Fiser
2026-10-01 14:57 ` Frank.Li [this message]
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=179086665044.2214513.936581075433795034.b4-ty@b4 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=primoz.fiser@norik.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=upstream@lists.phytec.de \
--cc=y.bas@phytec.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
all inboxes | Powered by JetHome®