From: Dhruva Gole <d-gole@ti.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
<bb@ti.com>, <vibhore@ti.com>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Dhruva Gole <d-gole@ti.com>
Subject: [PATCH 0/2] dts: ti: k3-am62: Use opp_efuse_table for opp-table
Date: Mon, 2 Sep 2024 15:02:20 +0530 [thread overview]
Message-ID: <20240902093222.2828345-1-d-gole@ti.com> (raw)
Hi,
In this series, I add another entry in the wkup_conf for the syscon node,
and then use that for the syscon in opp-table. Then, since the driver
can now pick the efuse reg directly, we no longer need the old offset, hence
make it 0 here itself.
This series has 2 patches that need to go in at the same time, hence
preferrably via your tree Viresh if that's fine by all the concerned
maintainers.
It also depends on the series previously sent [1]
[1] Message-Id: <20240902092135.2826470-1-d-gole@ti.com>
Cc: Bryan Brattlof <bb@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Vibhore Vardhan <vibhore@ti.com>
Cc: Nishanth Menon <nm@ti.com>
Dhruva Gole (2):
arm64: dts: ti: k3-am62: use opp_efuse_table for opp-table syscon
cpufreq: ti-cpufreq: Make the AM625 efuse_offset 0
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 7 ++++++-
arch/arm64/boot/dts/ti/k3-am625.dtsi | 2 +-
drivers/cpufreq/ti-cpufreq.c | 2 +-
3 files changed, 8 insertions(+), 3 deletions(-)
base-commit: ecc768a84f0b8e631986f9ade3118fa37852fef0
--
2.34.1
next reply other threads:[~2024-09-02 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 9:32 Dhruva Gole [this message]
2024-09-02 9:32 ` [PATCH 1/2] arm64: dts: ti: k3-am62: use opp_efuse_table for opp-table syscon Dhruva Gole
2024-09-02 9:32 ` [PATCH 2/2] cpufreq: ti-cpufreq: Make the AM625 efuse_offset 0 Dhruva Gole
2024-09-02 23:34 ` Bryan Brattlof
2024-09-03 6:07 ` Dhruva Gole
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=20240902093222.2828345-1-d-gole@ti.com \
--to=d-gole@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=vibhore@ti.com \
--cc=vigneshr@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
all inboxes | Powered by JetHome®