From: Rudraksha Gupta <guptarud@gmail.com>
To: Andy Gross <agross@kernel.org>,
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>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
soc@kernel.org
Cc: Rudraksha Gupta <guptarud@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] Samsung Galaxy Express SGH-I437 Support
Date: Sun, 4 Jun 2023 02:30:17 -0400 [thread overview]
Message-ID: <20230604063032.365775-1-guptarud@gmail.com> (raw)
This patch series adds support for the Samsung Galaxy Express SGH-I437.
Currently the following things work on this phone: UART, eMMC, SD Card, and
USB.
version 3:
- Added Ack
- Fixed compatible in qcom,usb-hs-phy.yaml. `make dt_binding_check dtbs_check`
no longer complains about USB
- Fixed formatting in qcom-msm8960.dtsi and qcom-msm8960-samsung-expressatt.dts
- Fixed the spi1_default node in qcom-msm8960-samsung-expressatt.dts.
`make dt_binding_check dtbs_check` no longer complains
version 2:
- Combined patch 1 into patch 4, as the sleep_clk label is specifically needed
for the USB node.
- Reformatted the commit messages to align with the style used in other commit
messages that modify the same files.
- Included a cover letter to provide an overview of the patch series.
- Slight refactoring of the device tree source (DTS) file.
Rudraksha Gupta (4):
dt-bindings: arm: qcom: Add Samsung Galaxy Express
dt-bindings: phy: qcom,usb-hs-phy: Add compatible
ARM: dts: qcom: msm8960: Add USB node
ARM: dts: qcom: Add Samsung Galaxy Express support
.../devicetree/bindings/arm/qcom.yaml | 1 +
.../bindings/phy/qcom,usb-hs-phy.yaml | 5 +-
arch/arm/boot/dts/Makefile | 1 +
.../dts/qcom-msm8960-samsung-expressatt.dts | 331 ++++++++++++++++++
arch/arm/boot/dts/qcom-msm8960.dtsi | 34 +-
5 files changed, 370 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/boot/dts/qcom-msm8960-samsung-expressatt.dts
--
2.34.1
next reply other threads:[~2023-06-04 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 6:30 Rudraksha Gupta [this message]
2023-06-04 6:30 ` [PATCH v3 1/4] dt-bindings: arm: qcom: Add Samsung Galaxy Express Rudraksha Gupta
2023-06-04 6:30 ` [PATCH v3 2/4] dt-bindings: phy: qcom,usb-hs-phy: Add compatible Rudraksha Gupta
2023-06-04 7:23 ` Rob Herring
2023-06-06 2:06 ` Rudraksha Gupta
2023-06-04 10:30 ` Krzysztof Kozlowski
2023-06-06 2:48 ` Rudraksha Gupta
2023-06-06 6:20 ` Krzysztof Kozlowski
2023-06-04 6:30 ` [PATCH v3 3/4] ARM: dts: qcom: msm8960: Add USB node Rudraksha Gupta
2023-06-04 6:30 ` [PATCH v3 4/4] ARM: dts: qcom: Add Samsung Galaxy Express support Rudraksha Gupta
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=20230604063032.365775-1-guptarud@gmail.com \
--to=guptarud@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=vkoul@kernel.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).