From: Doug Anderson <dianders@chromium.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/4] arm64: dts: qcom: sc7280: Rename crd to crd-r3
Date: Thu, 17 Mar 2022 10:08:19 -0700 [thread overview]
Message-ID: <CAD=FV=XeVGjGJVOx6OXBuMahjEsNQfrbYb_dZxJSBvQim0EjgA@mail.gmail.com> (raw)
In-Reply-To: <20220316172814.v1.1.I2deda8f2cd6adfbb525a97d8fee008a8477b7b0e@changeid>
Hi,
On Wed, Mar 16, 2022 at 5:28 PM Matthias Kaehlcke <mka@chromium.org> wrote:
>
> There are multiple revisions of CRD boards. The current sc7280-crd.dts
> describes revision 3 and 4 (aka CRD 1.0 and 2.0). Support for a newer
> version will be added by another patch. Add the revision number to
> distinguish it from the versionn. Also add the revision numbers to
> the compatible string.
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> ---
>
> arch/arm64/boot/dts/qcom/Makefile | 2 +-
> .../arm64/boot/dts/qcom/{sc7280-crd.dts => sc7280-crd-r3.dts} | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Douglas Anderson <dianders@chromium.org>
next prev parent reply other threads:[~2022-03-17 17:08 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
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 ` Doug Anderson [this message]
2022-03-17 18:51 ` [PATCH v1 1/4] arm64: dts: qcom: sc7280: Rename crd to crd-r3 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='CAD=FV=XeVGjGJVOx6OXBuMahjEsNQfrbYb_dZxJSBvQim0EjgA@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--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).