From: Sudeep Holla <sudeep.holla@arm.com>
To: Martin Botka <martin.botka@somainline.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
Alan Ma <tech@biqu3d.com>,
Luke Harrison <bttuniversity@biqu3d.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Martin Botka <martin@biqu3d.com>
Subject: Re: [PATCH] firmware: smccc: Export both soc_id functions
Date: Wed, 30 Aug 2023 16:43:12 +0100 [thread overview]
Message-ID: <20230830154312.zferm3it7mj4nwsy@bogus> (raw)
In-Reply-To: <BSJ70S.HFFPUN9486BN2@somainline.org>
On Wed, Aug 30, 2023 at 04:19:23PM +0200, Martin Botka wrote:
> The patches using this are still WIP but the basic point is that H616 has 2
> die revisions (And those have
> couple of other versions themselves) that require different uV and some
> frequencies are blacklisted on those
> versions.
>
> The driver is using these functions to read the revision (Not the version.
> It just looked like the logical
> thing to export both and Andre confirmed. We can ofc drop the version symbol
> export if need be) and reads
> trough the OPP table and selects the supported frequencies and uV for the
> chip its running on :)
>
> I will try to get the cpufreq patches in order in the upcoming days and I
> will Cc you in those as well +
> post a link to them in this thread :)
>
For simplicity, just make this patch part of the series that adds cpufreq
support on this platform/soc. Cross referencing won't give any more confidence
that the user is also getting merged at the same time as this patch.
--
Regards,
Sudeep
next prev parent reply other threads:[~2023-08-30 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 13:23 Martin Botka
2023-08-30 14:00 ` Marc Zyngier
[not found] ` <CAPKp9ubXJbLQ_jOt3sp7Y8KXKyp42bzjHqbaa19LSqGMxE2yPg@mail.gmail.com>
2023-08-30 14:19 ` Martin Botka
2023-08-30 15:43 ` Sudeep Holla [this message]
2023-08-30 15:45 ` Martin Botka
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=20230830154312.zferm3it7mj4nwsy@bogus \
--to=sudeep.holla@arm.com \
--cc=andre.przywara@arm.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bttuniversity@biqu3d.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mark.rutland@arm.com \
--cc=martin.botka@somainline.org \
--cc=martin@biqu3d.com \
--cc=tech@biqu3d.com \
/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®