linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Philip Chen <philipchen@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v3 3/4] arm64: dts: sc7180: Support Lazor/Limozeen rev9
Date: Mon, 1 Nov 2021 10:09:44 -0700	[thread overview]
Message-ID: <CAD=FV=XCGAFd1-h9FbeToRPpJSbVRU8AuvWUw2yyOt6KMwy_uQ@mail.gmail.com> (raw)
In-Reply-To: <20211029152647.v3.3.Ie56f55924f5c7706fe3194e710bbef6fdb8b5bc6@changeid>

Hi,

On Fri, Oct 29, 2021 at 3:27 PM Philip Chen <philipchen@chromium.org> wrote:
>
> Support Lazor/Limozeen rev9 board where Parade ps8640 is added as the
> second source edp bridge.
>
> To support different edp bridge chips in different board revisions,
> now we move the #incldue line of the edp bridge dts fragment (e.g.
> sc7180-trogdor-ti-sn65dsi86.dtsi) from "sc7180-trogdor-lazor.dtsi" to
> per-board-rev dts files.
>
> Since the edp bridge dts fragment overrides 'dsi0_out', which is
> defined in "sc7180.dtsi", move the #incldue line of "sc7180.dtsi" from
> "sc7180-trogdor-lazor.dtsi" to per-board-rev dts files too, before
> the #include line of the edp bridge dts fragment.
>
> Signed-off-by: Philip Chen <philipchen@chromium.org>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> ---
> Retroactively edit the v2 change log slightly
>
> (no changes since v2)
>
> Changes in v2:
> - Explain why "sc7180.dtsi" is moved out of "sc7180-trogdor-lazor.dtsi"
>   in the commit message.
> - In limozeen (nots) r5 dts, replace "google,rev5-sku5" with
>   "google,lazor-rev5-sku5" and sort it
> - In limozeen (nots) r9 dts, drop the support for "sku5".
> - In limozeen r4 dts, remove the redundant "google,lazor-rev6-sku4" and
>   add "google,lazor-rev7-sku4".
> - Do not add panel compatible in -r9 dts files.
> - Move the #include line of gpio.h from sc7180.dtsi to the bridge dts
>   fragments, and factor out this change to patch 1/3.
>
>  arch/arm64/boot/dts/qcom/Makefile             |  9 +++-
>  .../sc7180-trogdor-lazor-limozeen-nots-r4.dts |  2 +-
>  .../sc7180-trogdor-lazor-limozeen-nots-r5.dts | 31 +++++++++++++
>  ...sc7180-trogdor-lazor-limozeen-nots-r9.dts} |  8 ++--
>  .../qcom/sc7180-trogdor-lazor-limozeen-r4.dts | 46 +++++++++++++++++++
>  ...s => sc7180-trogdor-lazor-limozeen-r9.dts} |  6 ++-
>  .../boot/dts/qcom/sc7180-trogdor-lazor-r0.dts |  2 +
>  .../boot/dts/qcom/sc7180-trogdor-lazor-r1.dts |  2 +
>  .../dts/qcom/sc7180-trogdor-lazor-r3-kb.dts   |  9 +++-
>  .../dts/qcom/sc7180-trogdor-lazor-r3-lte.dts  |  9 +++-
>  .../boot/dts/qcom/sc7180-trogdor-lazor-r3.dts |  8 +++-
>  .../dts/qcom/sc7180-trogdor-lazor-r9-kb.dts   | 22 +++++++++
>  .../dts/qcom/sc7180-trogdor-lazor-r9-lte.dts  | 30 ++++++++++++
>  .../boot/dts/qcom/sc7180-trogdor-lazor-r9.dts | 18 ++++++++
>  .../boot/dts/qcom/sc7180-trogdor-lazor.dtsi   |  3 --
>  15 files changed, 188 insertions(+), 17 deletions(-)
>  create mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-limozeen-nots-r5.dts
>  rename arch/arm64/boot/dts/qcom/{sc7180-trogdor-lazor-limozeen-nots.dts => sc7180-trogdor-lazor-limozeen-nots-r9.dts} (60%)
>  create mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-limozeen-r4.dts
>  rename arch/arm64/boot/dts/qcom/{sc7180-trogdor-lazor-limozeen.dts => sc7180-trogdor-lazor-limozeen-r9.dts} (82%)
>  create mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r9-kb.dts
>  create mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r9-lte.dts
>  create mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r9.dts

Reviewed-by: Douglas Anderson <dianders@chromium.org>

  reply	other threads:[~2021-11-01 17:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 22:27 [PATCH v3 1/4] arm64: dts: sc7180: Include gpio.h in edp bridge dts Philip Chen
2021-10-29 22:27 ` [PATCH v3 2/4] arm64: dts: sc7180: Specify "data-lanes" for DSI host output Philip Chen
2021-10-29 23:16   ` Stephen Boyd
2021-10-29 23:24     ` Philip Chen
2021-10-29 23:35       ` Stephen Boyd
     [not found]       ` <e91a6134-c2ce-6112-0818-ffd9483feeeb@quicinc.com>
     [not found]         ` <55f951c1-1713-ad55-4ca3-b83d4f3763f6@quicinc.com>
2021-11-01 16:39           ` Philip Chen
2021-11-01 17:09   ` Doug Anderson
2021-11-01 18:09   ` Stephen Boyd
2021-10-29 22:27 ` [PATCH v3 3/4] arm64: dts: sc7180: Support Lazor/Limozeen rev9 Philip Chen
2021-11-01 17:09   ` Doug Anderson [this message]
2021-10-29 22:27 ` [PATCH v3 4/4] arm64: dts: sc7180: Support Homestar rev4 Philip Chen
2021-11-20 23:55 ` [PATCH v3 1/4] arm64: dts: sc7180: Include gpio.h in edp bridge dts 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='CAD=FV=XCGAFd1-h9FbeToRPpJSbVRU8AuvWUw2yyOt6KMwy_uQ@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=philipchen@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).