From: Rob Clark <robdclark@gmail.com>
To: linux-arm-msm@vger.kernel.org
Cc: Rob Clark <robdclark@chromium.org>
Subject: [RFC 0/3] arm64: dts: qcom: add cheza support
Date: Thu, 9 May 2019 11:44:10 -0700 [thread overview]
Message-ID: <20190509184415.11592-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
I cobbled together the dt for the cheza board (based on sdm845 SoC) from
the chromium kernel, mostly to simplify running an upstream kernel on
the device (it is a useful thing to be able to directly run an upstream
kernel when testing/debugging/implementing driver changes, rather than
having to cherry-pick everything back to an older kernel).
With this, and a few other fixes I've posted yesterday, plus sdm845.dtsi
patches for GPU and MDSS interconnect support which have been posted,
and a few other things which are making their way upstream, I can boot
to GUI on cheza. (So at least display and GPU work, plus a myriad of
other things required to get that far.)
In particular, the third patch depends on 'arm64: dts: sdm845: Add zap
shader region for GPU'
Douglas Anderson (1):
arm64: dts: qcom: sdm845-cheza: Re-add reserved memory
Rob Clark (2):
arm64: dts: qcom: sdm845-cheza: add initial cheza dt
arm64: dts: qcom: sdm845-cheza: delete zap-shader
arch/arm64/boot/dts/qcom/Makefile | 3 +
arch/arm64/boot/dts/qcom/sdm845-cheza-r1.dts | 238 +++
arch/arm64/boot/dts/qcom/sdm845-cheza-r2.dts | 238 +++
arch/arm64/boot/dts/qcom/sdm845-cheza-r3.dts | 180 +++
arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 1353 ++++++++++++++++++
arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 +-
6 files changed, 2013 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/qcom/sdm845-cheza-r1.dts
create mode 100644 arch/arm64/boot/dts/qcom/sdm845-cheza-r2.dts
create mode 100644 arch/arm64/boot/dts/qcom/sdm845-cheza-r3.dts
create mode 100644 arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi
--
2.20.1
next reply other threads:[~2019-05-09 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 18:44 Rob Clark [this message]
2019-05-09 18:44 ` [RFC 1/3] arm64: dts: qcom: sdm845-cheza: add initial cheza dt Rob Clark
2019-05-13 22:47 ` Doug Anderson
2019-05-09 18:44 ` [RFC 2/3] arm64: dts: qcom: sdm845-cheza: Re-add reserved memory Rob Clark
2019-05-13 22:48 ` Doug Anderson
2019-05-15 4:09 ` Rob Clark
2019-05-15 19:24 ` Jordan Crouse
2019-05-15 21:50 ` Doug Anderson
2019-05-15 23:41 ` Bjorn Andersson
2019-05-09 18:44 ` [RFC 3/3] arm64: dts: qcom: sdm845-cheza: delete zap-shader Rob Clark
2019-05-15 21:43 ` Doug Anderson
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=20190509184415.11592-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@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