[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69033de7.050a0220.34ea6.780b@mx.google.com>
Date: Thu, 30 Oct 2025 11:28:53 +0100
From: Christian Marangi <ansuelsmth@...il.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: Ilia Lin <ilia.lin@...nel.org>, "Rafael J. Wysocki" <rafael@...nel.org>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	Bjorn Andersson <andersson@...nel.org>,
	Konrad Dybcio <konradybcio@...nel.org>,
	Raag Jadav <raag.jadav@...el.com>, Arnd Bergmann <arnd@...db.de>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] cpufreq: qcom-nvmem: add compatible fallback for
 ipq806x for no SMEM
On Thu, Oct 30, 2025 at 09:56:24AM +0100, Konrad Dybcio wrote:
> On 10/29/25 2:33 PM, Christian Marangi wrote:
> > On some IPQ806x SoC SMEM might be not initialized by SBL. This is the
> > case for some Google devices (the OnHub family) that can't make use of
> > SMEM to detect the SoC ID.
> 
> Oh this is (the unpleasant kind of ) interesting.. Is there any sort
> of uboot/kernel tree for these machines available?
>
There is some sort of source but quite confusing. From the info they use
coreboot and chromeos.
Looking at the source they comment everything related to SMEM
(confirming the fact that they actually don't init it)
[1] https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/refs/heads/firmware-storm-6315.B/src/board/storm
[2] https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/firmware-storm-6315.B
-- 
	Ansuel
Powered by blists - more mailing lists
 
