From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: Luca Weiss <luca@z3ntu.xyz>,
linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Andy Gross <agross@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] soc: qcom: socinfo: import PMIC IDs from pmic-spmi
Date: Tue, 25 May 2021 22:58:17 -0500 [thread overview]
Message-ID: <YK3HWaAaM3PRWZ4l@builder.lan> (raw)
In-Reply-To: <08fde8a5-1d9f-4676-41c2-133b7a9a1c75@somainline.org>
On Wed 05 May 14:14 CDT 2021, Konrad Dybcio wrote:
> Hi,
>
>
> > The driver in drivers/mfd/qcom-spmi-pmic.c has a more complete and more
> > up-to-date list of PMICs with the respective IDs. Use those names for
> > socinfo.
> >
> > Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> > ---
> > I'm sending this as RFC because I'm not sure what names are correct for
> > the IDs that I've replaced (13, 16, 17, 20, 21, 24).
> > For PM8941, PM8841, PM8226 and PMA8084 I'm quite sure that the IDs are
> > correct, but I don't have devices with the other PMICs. Please advise
> > what to do.
> >
> As far as I'm aware, qcom did the lazy and ugly thing (as they usually do) and
>
> decided to reuse previously-occupied IDs on newer kernel releases, where the legacy
>
> PMICs weren't supported anymore. That's why some IDs have multiple candidates and unless
>
> a better suggestion than "let's check if this 2013 PMIC+ 2019 SoC combo is sane" pops up, we
>
> will probably just have to deal with ambiguity (for example `[20] PM8015/PM8998`).
>
I like this suggestion, even though I think it's only PM8058 we at all
care about upstream (as of now).
Luca, can you please respin the patch accordingly?
Thanks,
Bjorn
prev parent reply other threads:[~2021-05-26 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 20:37 [RFC PATCH] soc: qcom: socinfo: import PMIC IDs from pmic-spmi Luca Weiss
2021-05-05 19:14 ` Konrad Dybcio
2021-05-26 3:58 ` Bjorn Andersson [this message]
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=YK3HWaAaM3PRWZ4l@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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