From: Dhruva Gole <d-gole@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Bryan Brattlof <bb@ti.com>, Nishanth Menon <nm@ti.com>,
Andrew Davis <afd@ti.com>, Lee Jones <lee@kernel.org>,
<linux-arm-msm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 0/2] ti-cpufreq: AM62: Backward compatibility for syscon and update offsets
Date: Thu, 3 Oct 2024 14:43:41 +0530 [thread overview]
Message-ID: <20241003091341.elvgzscchqngmgod@lcpd911> (raw)
In-Reply-To: <20241001080400.diqfgbkje77pjby7@vireshk-i7>
Viresh,
On Oct 01, 2024 at 13:34:00 +0530, Viresh Kumar wrote:
> On 01-10-24, 13:27, Dhruva Gole wrote:
> > On Sep 30, 2024 at 15:02:08 +0530, Dhruva Gole wrote:
> > > With the Silicon revision being taken directly from socinfo, there's no
> > > longer any need for reading any SOC register for revision from this driver.
> > > Hence, we do not require any rev_offset for AM62 family of devices.
> > >
> > > Also, maintain the backward compatibility with old devicetree, and hence
> > > add condition to handle the case where we have the zero offset such that we
> > > don't end up reading the wrong register offset in new AM625 DTs whenever we fix
> > > them up.
> > >
> > > These patches have been in discussion as part of another series, which is now
> > > being split up as per discussions with Nishanth. Ref. the following link for
> > > more context on the same:
> > > https://lore.kernel.org/all/20240926-ti-cpufreq-fixes-v5-v7-0-3c94c398fe8f@ti.com/
> > >
> > > **DEPENDS ON:**
> > > "mfd: syscon: Use regmap max_register_is_0 as needed"
> > > https://lore.kernel.org/linux-arm-kernel/20240903184710.1552067-1-nm@ti.com/
> >
> > Just an update, the above dependency patch is now taken in by Lee Jones [1].
> > Waiting for it to finally appear in -next.
> >
> > + Lee just because we are users of that patch.
> >
> > [1]
> > https://lore.kernel.org/linux-arm-kernel/172770742318.523866.16912261914335612487.b4-ty@kernel.org/
>
> Ping me once this series is ready to be applied and all dependencies
> are merged somewhere I can rebase.
I can see the dependency is part of next-20241003, please feel free to pick the
series now if it looks ok to you.
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
prev parent reply other threads:[~2024-10-03 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240930-b4-ti-cpufreq-am62-quirk-v1-0-b5e04f0f899b@ti.com>
2024-10-01 7:57 ` [PATCH 0/2] ti-cpufreq: AM62: Backward compatibility for syscon and update offsets Dhruva Gole
2024-10-01 8:04 ` Viresh Kumar
2024-10-03 9:13 ` 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=20241003091341.elvgzscchqngmgod@lcpd911 \
--to=d-gole@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=broonie@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--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