From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Sai Prakash Ranjan <quic_saipraka@quicinc.com>,
matvore@chromium.org, Andy Gross <agross@kernel.org>,
"Reviewed-by : Stephen Boyd" <swboyd@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: (subset) [PATCH] soc: qcom: socinfo: Add another ID for sc7180
Date: Wed, 4 May 2022 11:30:25 -0700 [thread overview]
Message-ID: <YnLGQWPmcJo73vtu@ripper> (raw)
In-Reply-To: <CAD=FV=WkJu8s5EmwJke49TPZ8CU8kD-CMcQi-9a3oUMqz9yBrQ@mail.gmail.com>
On Wed 04 May 10:51 PDT 2022, Doug Anderson wrote:
> Hi,
>
> On Wed, May 4, 2022 at 10:21 AM Bjorn Andersson
> <bjorn.andersson@linaro.org> wrote:
> >
> > On Mon, 2 May 2022 17:33:45 -0700, Douglas Anderson wrote:
> > > It appears the some sc7180 devices, like the one in my
> > > sc7180-trogdor-homestar, report an ID of 407 instead of 425. Add
> > > another ID into the list.
> > >
> > >
> >
> > Applied, thanks!
> >
> > [1/1] soc: qcom: socinfo: Add another ID for sc7180
> > commit: c35886d605604e0b03cdd835ae3249dc1fe0cc2a
>
> Hmm. Did you see the responses from Sai [1] about this? He seemed to
> indicate that there might be some issue here because he thought 407
> was supposed to be a different SoC. Are we sure we want to land this
> patch while we're sorting it out?
>
I stared at the thread but didn't see his reply for some reason.
Congrats on the getting the random SoC in your device ;) As this was the
top patch on drivers-for-5.19, I just popped that off and pushed the
branch again.
Let me know when you've figured the numbering out (and if it turns out
to be the mobile id I wouldn't mind carrying that in the table)
Regards,
Bjorn
> [1] https://lore.kernel.org/r/13819b2d-26f0-14f4-9cb9-affb6b18f13d@quicinc.com/
prev parent reply other threads:[~2022-05-04 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 0:33 [PATCH] soc: qcom: socinfo: Add another ID for sc7180 Douglas Anderson
2022-05-04 2:14 ` Sai Prakash Ranjan
2022-05-04 3:30 ` Doug Anderson
2022-05-04 10:52 ` Sai Prakash Ranjan
2022-05-04 17:20 ` patchwork-bot+linux-arm-msm
2022-05-04 17:21 ` (subset) " Bjorn Andersson
2022-05-04 17:51 ` Doug Anderson
2022-05-04 18:30 ` 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=YnLGQWPmcJo73vtu@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matvore@chromium.org \
--cc=quic_saipraka@quicinc.com \
--cc=swboyd@chromium.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