public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Botka <martin.botka@somainline.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	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:19:23 +0200	[thread overview]
Message-ID: <BSJ70S.HFFPUN9486BN2@somainline.org> (raw)
In-Reply-To: <CAPKp9ubXJbLQ_jOt3sp7Y8KXKyp42bzjHqbaa19LSqGMxE2yPg@mail.gmail.com>

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 :)

Cheers,
Martin

On Wed, Aug 30 2023 at 03:05:09 PM +01:00:00, Sudeep Holla 
<sudeep.holla@arm.com> wrote:
> 
> 
> On Wed, Aug 30, 2023 at 2:24 PM Martin Botka 
> <martin.botka@somainline.org> wrote:
>> arm_smccc_get_soc_id_version and arm_smccc_get_soc_id_revision
>>  need to be exported so they can be used by modules.
>>  Currently sun50i cpu freq driver is planning to use these functions.
> 
> I am not against exporting these but please post along with the 
> patches using these
> exported symbols so that no one complains about you exporting the 
> symbols mentioning
> some patches that may or may not appear in the future.
> 
> --
> Regards,
> Sudeep



  parent reply	other threads:[~2023-08-30 19:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 13:23 [PATCH] firmware: smccc: Export both soc_id functions Martin Botka
2023-08-30 14:00 ` Marc Zyngier
     [not found] ` <CAPKp9ubXJbLQ_jOt3sp7Y8KXKyp42bzjHqbaa19LSqGMxE2yPg@mail.gmail.com>
2023-08-30 14:19   ` Martin Botka [this message]
2023-08-30 15:43     ` Sudeep Holla
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=BSJ70S.HFFPUN9486BN2@somainline.org \
    --to=martin.botka@somainline.org \
    --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@biqu3d.com \
    --cc=sudeep.holla@arm.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