From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: linux-arm-msm@vger.kernel.org, andersson@kernel.org,
agross@kernel.org, krzysztof.kozlowski@linaro.org
Cc: marijn.suijten@somainline.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/9] arm64: dts: qcom: ipq6018: Use lowercase hex
Date: Mon, 12 Dec 2022 12:10:29 +0100 [thread overview]
Message-ID: <20221212111037.98160-2-konrad.dybcio@linaro.org> (raw)
In-Reply-To: <20221212111037.98160-1-konrad.dybcio@linaro.org>
Use lowercase hex, as that's the preferred and overwhermingly present
style.
Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
---
arch/arm64/boot/dts/qcom/ipq6018.dtsi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/ipq6018.dtsi b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
index 5d453f11acd9..2ceae73a6069 100644
--- a/arch/arm64/boot/dts/qcom/ipq6018.dtsi
+++ b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
@@ -679,7 +679,7 @@ dwc_1: usb@7000000 {
ssphy_0: ssphy@78000 {
compatible = "qcom,ipq6018-qmp-usb3-phy";
- reg = <0x0 0x78000 0x0 0x1C4>;
+ reg = <0x0 0x78000 0x0 0x1c4>;
#address-cells = <2>;
#size-cells = <2>;
ranges;
@@ -696,7 +696,7 @@ ssphy_0: ssphy@78000 {
usb0_ssphy: phy@78200 {
reg = <0x0 0x00078200 0x0 0x130>, /* Tx */
<0x0 0x00078400 0x0 0x200>, /* Rx */
- <0x0 0x00078800 0x0 0x1F8>, /* PCS */
+ <0x0 0x00078800 0x0 0x1f8>, /* PCS */
<0x0 0x00078600 0x0 0x044>; /* PCS misc */
#phy-cells = <0>;
#clock-cells = <0>;
@@ -721,7 +721,7 @@ qusb_phy_0: qusb@79000 {
usb3: usb@8af8800 {
compatible = "qcom,ipq6018-dwc3", "qcom,dwc3";
- reg = <0x0 0x8AF8800 0x0 0x400>;
+ reg = <0x0 0x8af8800 0x0 0x400>;
#address-cells = <2>;
#size-cells = <2>;
ranges;
@@ -747,7 +747,7 @@ usb3: usb@8af8800 {
dwc_0: usb@8a00000 {
compatible = "snps,dwc3";
- reg = <0x0 0x8A00000 0x0 0xcd00>;
+ reg = <0x0 0x8a00000 0x0 0xcd00>;
interrupts = <GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>;
phys = <&qusb_phy_0>, <&usb0_ssphy>;
phy-names = "usb2-phy", "usb3-phy";
--
2.38.1
next parent reply other threads:[~2022-12-12 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221212111037.98160-1-konrad.dybcio@linaro.org>
2022-12-12 11:10 ` Konrad Dybcio [this message]
2022-12-12 11:10 ` [PATCH 2/9] arm64: dts: qcom: msm8996: Use lowercase hex Konrad Dybcio
2022-12-12 11:10 ` [PATCH 3/9] arm64: dts: qcom: msm8998: " Konrad Dybcio
2022-12-12 11:10 ` [PATCH 4/9] arm64: dts: qcom: sdm630: " Konrad Dybcio
2022-12-12 11:10 ` [PATCH 5/9] arm64: dts: qcom: sdm660: " Konrad Dybcio
2022-12-12 11:10 ` [PATCH 6/9] arm64: dts: qcom: sdm845: " Konrad Dybcio
2022-12-12 11:10 ` [PATCH 7/9] arm64: dts: qcom: sm8250: " Konrad Dybcio
2022-12-12 11:10 ` [PATCH 8/9] arm64: dts: qcom: sm8150: " Konrad Dybcio
2022-12-12 11:10 ` [PATCH 9/9] arm64: dts: qcom: sdm845: Fix some whitespace/newlines Konrad Dybcio
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=20221212111037.98160-2-konrad.dybcio@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robh+dt@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).