Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Ilia Lin <ilia.lin@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Raag Jadav <raag.jadav@intel.com>,
	linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] cpufreq: qcom-nvmem: add compatible fallback for ipq806x for no SMEM
Date: Fri, 31 Oct 2025 15:19:12 +0100	[thread overview]
Message-ID: <6904c563.050a0220.a13ee.0212@mx.google.com> (raw)
In-Reply-To: <aQS5FpuOWk1bWnQd@smile.fi.intel.com>

On Fri, Oct 31, 2025 at 03:26:46PM +0200, Andy Shevchenko wrote:
> On Fri, Oct 31, 2025 at 02:08:34PM +0100, 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.
> > 
> > To handle these specific case, check if the SMEM is not initialized (by
> > checking if the qcom_smem_get_soc_id returns -ENODEV) and fallback to
> > OF machine compatible checking to identify the SoC variant.
> > 
> > Notice that the checking order is important as the machine compatible
> > are normally defined with the specific one following the generic SoC
> > (for example compatible = "qcom,ipq8065", "qcom,ipq8064").
> 
> ...
> 
> > +		if (of_machine_is_compatible("qcom,ipq8062"))
> > +			msm_id = QCOM_ID_IPQ8062;
> > +		else if (of_machine_is_compatible("qcom,ipq8065") ||
> > +			 of_machine_is_compatible("qcom,ipq8069"))
> > +			msm_id = QCOM_ID_IPQ8065;
> > +		else if (of_machine_is_compatible("qcom,ipq8064") ||
> > +			 of_machine_is_compatible("qcom,ipq8066") ||
> > +			 of_machine_is_compatible("qcom,ipq8068"))
> > +			msm_id = QCOM_ID_IPQ8064;
> 
> A nit-pick (in case you need a new version of the series): I would expect
> the conditionals be sorted by assigned value.
> 
> 		if (of_machine_is_compatible("qcom,ipq8062"))
> 			msm_id = QCOM_ID_IPQ8062;
> 		else if (of_machine_is_compatible("qcom,ipq8064") ||
> 			 of_machine_is_compatible("qcom,ipq8066") ||
> 			 of_machine_is_compatible("qcom,ipq8068"))
> 			msm_id = QCOM_ID_IPQ8064;
> 		else if (of_machine_is_compatible("qcom,ipq8065") ||
> 			 of_machine_is_compatible("qcom,ipq8069"))
> 			msm_id = QCOM_ID_IPQ8065;
>

Hi as said in the commit, parsing 65/69 before 64 is needed as we might
have compatible like

"qcom,ipq8065","qcom,ipq8064" so we might incorrectly parse msm_id
ipq8064.

> -- 
> With Best Regards,
> Andy Shevchenko
> 
> 

-- 
	Ansuel

  reply	other threads:[~2025-10-31 14:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 13:08 [PATCH v2 0/3] cpufreq: qcom: handle ipq806x with no SMEM Christian Marangi
2025-10-31 13:08 ` [PATCH v2 1/3] err.h: add INIT_ERR_PTR macro Christian Marangi
2025-10-31 13:23   ` Andy Shevchenko
2025-10-31 13:08 ` [PATCH v2 2/3] soc: qcom: smem: better track SMEM uninitialized state Christian Marangi
2025-10-31 13:08 ` [PATCH v2 3/3] cpufreq: qcom-nvmem: add compatible fallback for ipq806x for no SMEM Christian Marangi
2025-10-31 13:26   ` Andy Shevchenko
2025-10-31 14:19     ` Christian Marangi [this message]
2025-10-31 14:34       ` Andy Shevchenko
2025-11-01 11:50         ` Christian Marangi
2025-11-02 20:23           ` Dmitry Baryshkov
2025-10-31 13:27   ` Andy Shevchenko
2025-11-01 17:42   ` Bjorn Andersson
2025-11-04 11:59     ` Christian Marangi
2025-11-04 12:13       ` Konrad Dybcio
2025-11-02 18:09 ` (subset) [PATCH v2 0/3] cpufreq: qcom: handle ipq806x with " Bjorn Andersson

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=6904c563.050a0220.a13ee.0212@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=andersson@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=ilia.lin@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=raag.jadav@intel.com \
    --cc=rafael@kernel.org \
    --cc=viresh.kumar@linaro.org \
    /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