devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rong Zhang <i@rong.moe>
To: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: Rong Zhang <i@rong.moe>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Icenowy Zheng <uwu@icenowy.me>
Subject: [PATCH 0/4] ARM: dts: qcom: msm8974: Add Samsung Galaxy S5 China support
Date: Sun, 21 Jan 2024 23:39:55 +0800	[thread overview]
Message-ID: <20240121154010.168440-1-i@rong.moe> (raw)

Samsung Galaxy S5 has some variants, currently, the only supported one
is klte. Samsung Galaxy S5 China (kltechn) is the China edition of
klte, and it has minor difference compared to klte. It can mostly work
with klte device tree, with only LEDs and WiFi not working.

This patchset adds support for kltechn by fixing up the GPIO pins for
the /i2c-gpio-led node (a corresponding label, "i2c_led_gpio", is also
added), and adding the brcm,board-type property in the wifi@1 node of
the klte device tree to allow loading the same firmware on all klte*
variants.

Rong Zhang (4):
  ARM: dts: qcom: msm8974-samsung-klte: Add label on /i2c-gpio-led
  ARM: dts: qcom: msm8974-samsung-klte: Pin brcm,board-type in wifi
  dt-bindings: arm: qcom: add Samsung Galaxy S5 China (kltechn)
  ARM: dts: qcom: msm8974: Add device tree for Samsung Galaxy S5 China

 Documentation/devicetree/bindings/arm/qcom.yaml  |  1 +
 arch/arm/boot/dts/qcom/Makefile                  |  1 +
 .../dts/qcom/qcom-msm8974pro-samsung-klte.dts    |  8 +++++++-
 .../dts/qcom/qcom-msm8974pro-samsung-kltechn.dts | 16 ++++++++++++++++
 4 files changed, 25 insertions(+), 1 deletion(-)
 create mode 100644 arch/arm/boot/dts/qcom/qcom-msm8974pro-samsung-kltechn.dts


base-commit: 7a396820222d6d4c02057f41658b162bdcdadd0e
-- 
2.43.0


             reply	other threads:[~2024-01-21 15:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21 15:39 Rong Zhang [this message]
2024-01-21 15:39 ` [PATCH 1/4] ARM: dts: qcom: msm8974-samsung-klte: Add label on /i2c-gpio-led Rong Zhang
2024-01-22  9:48   ` Krzysztof Kozlowski
2024-01-22 14:54     ` Rong Zhang
2024-01-21 15:39 ` [PATCH 2/4] ARM: dts: qcom: msm8974-samsung-klte: Pin brcm,board-type in wifi Rong Zhang
2024-01-21 15:39 ` [PATCH 3/4] dt-bindings: arm: qcom: add Samsung Galaxy S5 China (kltechn) Rong Zhang
2024-01-22  9:47   ` Krzysztof Kozlowski
2024-01-21 15:39 ` [PATCH 4/4] ARM: dts: qcom: msm8974: Add device tree for Samsung Galaxy S5 China Rong Zhang
2024-01-22  9:48   ` Krzysztof Kozlowski
2024-01-22 14:51     ` Rong Zhang
2024-01-22 15:17       ` Krzysztof Kozlowski
2024-01-22 15:27         ` Rong Zhang
2024-01-22 10:50   ` Konrad Dybcio
2024-01-22 14:01     ` Icenowy Zheng
2024-01-22 17:37     ` Rong Zhang

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=20240121154010.168440-1-i@rong.moe \
    --to=i@rong.moe \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=uwu@icenowy.me \
    /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).