From: Matthias Kaehlcke <mka@chromium.org>
To: Rajendra Nayak <quic_rjendra@quicinc.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
devicetree@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/4] arm64: dts: qcom: sc7280: Add 'piglin' to the crd-r3 compatible strings
Date: Mon, 21 Mar 2022 08:14:36 -0700 [thread overview]
Message-ID: <YjiWXA40Nh0jBPO9@google.com> (raw)
In-Reply-To: <c808dc08-09c8-bb08-6656-18dd649af036@quicinc.com>
On Mon, Mar 21, 2022 at 11:14:56AM +0530, Rajendra Nayak wrote:
>
> On 3/17/2022 5:58 AM, Matthias Kaehlcke wrote:
> > With newer bootloader versions the crd-r3 (aka CRD 1.0 and 2.0) is
> > identified as a 'piglin' board (like the IDP2 board), instead of 'hoglin'
> > Add the compatible strings 'google,piglin-rev{3,4}'. The hoglin entries
> > are kept to make sure the board keeps booting with older bootloader
> > versions.
>
> The older bootloaders really look for the google,hoglin-rev3/google,hoglin-rev4
> compatibles or just google,hoglin? If its just google,hoglin, won;t it pick the
> crd-rev5+ dtb now?
They look for the -revN compatible, I confirmed that on my CRD 2.0.
next prev parent reply other threads:[~2022-03-21 15:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 0:28 [PATCH v1 1/4] arm64: dts: qcom: sc7280: Rename crd to crd-r3 Matthias Kaehlcke
2022-03-17 0:28 ` [PATCH v1 2/4] arm64: dts: qcom: sc7280: Add 'piglin' to the crd-r3 compatible strings Matthias Kaehlcke
2022-03-17 17:08 ` Doug Anderson
2022-03-17 18:51 ` Stephen Boyd
2022-03-21 5:44 ` Rajendra Nayak
2022-03-21 15:14 ` Matthias Kaehlcke [this message]
2022-03-21 18:00 ` Doug Anderson
2022-03-22 4:16 ` Rajendra Nayak
2022-03-17 0:28 ` [PATCH v1 3/4] arm64: dts: qcom: sc7280: herobrine: disable some regulators by default Matthias Kaehlcke
2022-03-17 17:08 ` Doug Anderson
2022-03-17 19:03 ` Stephen Boyd
2022-03-24 4:57 ` Rajendra Nayak
2022-03-17 0:28 ` [PATCH v1 4/4] arm64: dts: qcom: sc7280: Add CRD rev5 Matthias Kaehlcke
2022-03-17 17:08 ` Doug Anderson
2022-03-17 19:04 ` Stephen Boyd
2022-03-24 4:58 ` Rajendra Nayak
2022-03-17 17:08 ` [PATCH v1 1/4] arm64: dts: qcom: sc7280: Rename crd to crd-r3 Doug Anderson
2022-03-17 18:51 ` Stephen Boyd
2022-03-22 4:18 ` Rajendra Nayak
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=YjiWXA40Nh0jBPO9@google.com \
--to=mka@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).