From: Dhruva Gole <d-gole@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Nishanth Menon <nm@ti.com>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Bryan Brattlof <bb@ti.com>, Wadim Egorov <w.egorov@phytec.de>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am62: use opp_efuse_table for opp-table syscon
Date: Mon, 4 Nov 2024 10:22:27 +0530 [thread overview]
Message-ID: <20241104045227.2tzm2lcwi7kqee5r@lcpd911> (raw)
In-Reply-To: <e3c4f895-71a1-481f-86d4-dfab1b61715c@ti.com>
On Oct 30, 2024 at 11:17:16 +0530, Vignesh Raghavendra wrote:
> Hi
>
> On 30/10/24 10:15, Dhruva Gole wrote:
> > Add another entry in the wkup_conf for the syscon node, and then use
> > that for the syscon in opp-table.
> >
> > Marking entire wkup_conf as "syscon", "simple-mfd" is wrong and needs to
> > be addressed similar to how other child-nodes in wkup_conf are implemented
> > in the same file.
> >
> > Signed-off-by: Dhruva Gole <d-gole@ti.com>
> > ---
> >
> > Since the driver fixes for ti-cpufreq.c have made it in -next [1],
> > The DT fixes for SK-AM62x can be supported with support for legacy
> > style DT as well. This has been tested on SK-AM62x [2]
> >
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/cpufreq/ti-cpufreq.c?id=1724ae88efcbcd0daeb203ffeb4a2c0e59f2ddf7
> > [2] https://gist.github.com/DhruvaG2000/40b80cc04a9ac90c86445d6e67ece4cb
> >
> > Changelog:
> >
> > Changes in v2:
> > - Deleted PATCH to Make the AM625 efuse_offset 0, because with [1] we no
> > longer break backward compatibility and hence need to preserve the old
> > offset.
> > - Link to v1:
> > https://lore.kernel.org/linux-arm-kernel/20240902093222.2828345-3-d-gole@ti.com/
> >
> > ---
> > arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 7 ++++++-
> > arch/arm64/boot/dts/ti/k3-am625.dtsi | 2 +-
> > 2 files changed, 7 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> > index e0afafd532a5..b2b65e31c7cf 100644
> > --- a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> > +++ b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> > @@ -10,7 +10,7 @@
> > &cbass_wakeup {
> > wkup_conf: syscon@43000000 {
>
> Now that the compatible is updated, this needs to be bus@addr
> dtbs_check should catch such errors.
Oh yes, I'll update this. Good catch.
>
> > bootph-all;
> > - compatible = "syscon", "simple-mfd";
> > + compatible = "simple-bus";
>
> Did you also check U-Boot and make sure no regression/update needed?
>
No, I can do a quick sanity boot till kernel with this DTB in U-boot to
check for regressions.
Thanks for the review.
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
prev parent reply other threads:[~2024-11-04 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 4:45 [PATCH v2] arm64: dts: ti: k3-am62: use opp_efuse_table for opp-table syscon Dhruva Gole
2024-10-30 5:47 ` Vignesh Raghavendra
2024-11-04 4:52 ` Dhruva Gole [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=20241104045227.2tzm2lcwi7kqee5r@lcpd911 \
--to=d-gole@ti.com \
--cc=bb@ti.com \
--cc=devicetree@vger.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=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=w.egorov@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