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 17:45:21 +0200 [thread overview]
Message-ID: <LRN70S.BVS224FBSYMM3@somainline.org> (raw)
In-Reply-To: <20230830154312.zferm3it7mj4nwsy@bogus>
Got it.
Cheers,
Martin
On Wed, Aug 30 2023 at 04:43:12 PM +01:00:00, Sudeep Holla
<sudeep.holla@arm.com> wrote:
> 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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
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 17:45:21 +0200 [thread overview]
Message-ID: <LRN70S.BVS224FBSYMM3@somainline.org> (raw)
In-Reply-To: <20230830154312.zferm3it7mj4nwsy@bogus>
Got it.
Cheers,
Martin
On Wed, Aug 30 2023 at 04:43:12 PM +01:00:00, Sudeep Holla
<sudeep.holla@arm.com> wrote:
> 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 15:46 UTC|newest]
Thread overview: 10+ 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 13:23 ` Martin Botka
2023-08-30 14:00 ` Marc Zyngier
2023-08-30 14:00 ` Marc Zyngier
[not found] ` <CAPKp9ubXJbLQ_jOt3sp7Y8KXKyp42bzjHqbaa19LSqGMxE2yPg@mail.gmail.com>
2023-08-30 14:19 ` Martin Botka
2023-08-30 14:19 ` Martin Botka
2023-08-30 15:43 ` Sudeep Holla
2023-08-30 15:43 ` Sudeep Holla
2023-08-30 15:45 ` Martin Botka [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=LRN70S.BVS224FBSYMM3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.