devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Skladowski <a39.skl@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	Adam Skladowski <a39.skl@gmail.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/1] Add MSM8976 Device tree
Date: Tue,  1 Nov 2022 20:16:19 +0100	[thread overview]
Message-ID: <20221101191659.172416-1-a39.skl@gmail.com> (raw)

This patch introduce devicetree for MSM8976 SoC,
most of already supported hardware should be described there.
Note about v2:
Based on advice from Bjorn i decided to keep clocks container,
this format appears in every other qcom dts.

Changes since v1
================
1. Dropped l1 i/d cache from cpu nodes.
2. Replaced xo_board with rpmcc where possible.
3. Added base address to memory node.
4. Padded addresses to 8 digits.
5. Moved imem to mmio range.
6. Adjusted mdss te pin name.
7. Reorganized reg positions per Konrad's request.

Adam Skladowski (1):
  arm64: dts: qcom: Add MSM8976 device tree

 arch/arm64/boot/dts/qcom/msm8976.dtsi | 1310 +++++++++++++++++++++++++
 1 file changed, 1310 insertions(+)
 create mode 100644 arch/arm64/boot/dts/qcom/msm8976.dtsi

-- 
2.25.1


             reply	other threads:[~2022-11-01 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 19:16 Adam Skladowski [this message]
2022-11-01 19:16 ` [PATCH v2 1/1] arm64: dts: qcom: Add MSM8976 device tree Adam Skladowski
2022-11-02  3:01   ` Bjorn Andersson
2022-11-02 20:03   ` Krzysztof Kozlowski
2022-11-02 20:11   ` Krzysztof Kozlowski

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=20221101191659.172416-1-a39.skl@gmail.com \
    --to=a39.skl@gmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).