lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <LRN70S.BVS224FBSYMM3@somainline.org>
Date:   Wed, 30 Aug 2023 17:45:21 +0200
From:   Martin Botka <martin.botka@...ainline.org>
To:     Sudeep Holla <sudeep.holla@....com>
Cc:     Mark Rutland <mark.rutland@....com>,
        Lorenzo Pieralisi <lpieralisi@...nel.org>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Andre Przywara <andre.przywara@....com>,
        Alan Ma <tech@...u3d.com>,
        Luke Harrison <bttuniversity@...u3d.com>,
        Marijn Suijten <marijn.suijten@...ainline.org>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...ainline.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>,
        Martin Botka <martin@...u3d.com>
Subject: Re: [PATCH] firmware: smccc: Export both soc_id functions

Got it.

Cheers,
Martin

On Wed, Aug 30 2023 at 04:43:12 PM +01:00:00, Sudeep Holla 
<sudeep.holla@....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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ