From: "Raghavendra, Vignesh" <vigneshr@ti.com>
To: Paresh Bhagat <p-bhagat@ti.com>, <nm@ti.com>, <praneeth@ti.com>
Cc: <kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <rafael@kernel.org>,
<viresh.kumar@linaro.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pm@vger.kernel.org>, <khasim@ti.com>, <v-singh1@ti.com>,
<afd@ti.com>, <bb@ti.com>, <s-vadapalli@ti.com>
Subject: Re: [PATCH 0/4] Add cpufreq and USB support for AM62D2
Date: Thu, 21 Aug 2025 12:02:25 +0530 [thread overview]
Message-ID: <77ed674f-8667-4c51-a2f5-0f8545bdc610@ti.com> (raw)
In-Reply-To: <20250820083331.3412378-1-p-bhagat@ti.com>
On 8/20/2025 2:03 PM, Paresh Bhagat wrote:
> This patch series introduces following changes:
>
> * Patch 1 fixes the register length in main_pmx/padconfig for AM62D
> and AM62A.
>
> * Patch 2 enables USB support for AM62D2-EVM by adding pinmux and device
> tree nodes.
>
> * Patch 3 adds AM62D2 SoC to cpufreq-dt-platdev blacklist so that
> cpufreq is handled by the ti-cpufreq driver instead of the
> generic cpufreq-dt driver.
>
> * Patch 4 extends ti-cpufreq to register AM62D2 SoC support by
> reusing the am62a7_soc_data.
Please don't randomly mix patches into single series. Here patches 1/4
and 2/4 have no bearing on cpufreq driver changes in 3/4 and 4/4. They
even go through different trees.
>
> Boot Logs-
> https://gist.github.com/paresh-bhagat12/e29d33c3fd92ff17580edf1441ece9f9
>
> Tech Ref Manual-https://www.ti.com/lit/pdf/sprujd4
> Schematics Link-https://www.ti.com/lit/zip/sprcal5
>
> Paresh Bhagat (3):
> arm64: dts: ti: k3-am62d2-evm: Enable USB support
> cpufreq: dt-platdev: Blacklist ti,am62d2 SoC
> cpufreq: ti: Add support for AM62D2
>
> Vibhore Vardhan (1):
> arm64: dts: ti: k3-am62a-main: Fix pinctrl properties
>
> arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 2 +-
> arch/arm64/boot/dts/ti/k3-am62d2-evm.dts | 21 +++++++++++++++++++++
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> drivers/cpufreq/ti-cpufreq.c | 2 ++
> 4 files changed, 25 insertions(+), 1 deletion(-)
>
next prev parent reply other threads:[~2025-08-21 6:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 8:33 [PATCH 0/4] Add cpufreq and USB support for AM62D2 Paresh Bhagat
2025-08-20 8:33 ` [PATCH 1/4] arm64: dts: ti: k3-am62a-main: Fix pinctrl properties Paresh Bhagat
2025-08-21 6:35 ` Raghavendra, Vignesh
2025-08-20 8:33 ` [PATCH 2/4] arm64: dts: ti: k3-am62d2-evm: Enable USB support Paresh Bhagat
2025-08-20 8:33 ` [PATCH 3/4] cpufreq: dt-platdev: Blacklist ti,am62d2 SoC Paresh Bhagat
2025-08-20 8:33 ` [PATCH 4/4] cpufreq: ti: Add support for AM62D2 Paresh Bhagat
2025-08-20 8:37 ` [PATCH 0/4] Add cpufreq and USB " Viresh Kumar
2025-08-21 6:32 ` Raghavendra, Vignesh [this message]
2025-08-21 12:27 ` Nishanth Menon
2025-08-22 6:21 ` Paresh Bhagat
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=77ed674f-8667-4c51-a2f5-0f8545bdc610@ti.com \
--to=vigneshr@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khasim@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=p-bhagat@ti.com \
--cc=praneeth@ti.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=v-singh1@ti.com \
--cc=viresh.kumar@linaro.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).