From: Andrew Halaney <ahalaney@redhat.com>
To: andersson@kernel.org
Cc: agross@kernel.org, konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bmasney@redhat.com, quic_shazhuss@quicinc.com,
Andrew Halaney <ahalaney@redhat.com>
Subject: [PATCH v2 2/2] arm64: dts: qcom: sa8540p-ride: Document i2c busses
Date: Mon, 30 Jan 2023 09:48:23 -0600 [thread overview]
Message-ID: <20230130154823.117542-2-ahalaney@redhat.com> (raw)
In-Reply-To: <20230130154823.117542-1-ahalaney@redhat.com>
It isn't obvious in the current devicetree what is connected. Go ahead
and document what's on the other end.
Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
---
Changes since v1:
* Document i2c12 having a max20411 (Shazad)
In v1 I said i2c12 was not connected, that's not true though (I just
have a board schematic which shows it not connected, but it _is_
connected on the SIP/SOM, which I verified with series [0]).
I debated waiting for Bjorn to sort out appropriate label names over at
[0] (and follow suit in a third patch here), but decided to get this
series out again to clean up the current warnings while that's worked
out. Once [0] is resubmitted I'll submit a separate patch to enable the
max20411 on this board as well!
[0] https://lore.kernel.org/linux-arm-msm/20230130035642.GA464800@hu-bjorande-lv.qualcomm.com/
Thanks,
Andrew
arch/arm64/boot/dts/qcom/sa8540p-ride.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sa8540p-ride.dts b/arch/arm64/boot/dts/qcom/sa8540p-ride.dts
index 6ab4b435c49e..8b7555f22528 100644
--- a/arch/arm64/boot/dts/qcom/sa8540p-ride.dts
+++ b/arch/arm64/boot/dts/qcom/sa8540p-ride.dts
@@ -317,6 +317,7 @@ &xo_board_clk {
&tlmm {
i2c0_default: i2c0-default-state {
+ /* To USB7002T-I/KDXVA0 USB hub (SIP1 only) */
pins = "gpio135", "gpio136";
function = "qup0";
drive-strength = <2>;
@@ -324,6 +325,7 @@ i2c0_default: i2c0-default-state {
};
i2c1_default: i2c1-default-state {
+ /* To PM40028B-F3EI PCIe switch */
pins = "gpio158", "gpio159";
function = "qup1";
drive-strength = <2>;
@@ -331,6 +333,7 @@ i2c1_default: i2c1-default-state {
};
i2c12_default: i2c12-default-state {
+ /* To Maxim max20411 */
pins = "gpio0", "gpio1";
function = "qup12";
drive-strength = <2>;
@@ -338,6 +341,7 @@ i2c12_default: i2c12-default-state {
};
i2c15_default: i2c15-default-state {
+ /* To display connector (SIP1 only) */
pins = "gpio36", "gpio37";
function = "qup15";
drive-strength = <2>;
@@ -345,6 +349,7 @@ i2c15_default: i2c15-default-state {
};
i2c18_default: i2c18-default-state {
+ /* To ASM330LHH IMU (SIP1 only) */
pins = "gpio66", "gpio67";
function = "qup18";
drive-strength = <2>;
--
2.39.1
next prev parent reply other threads:[~2023-01-30 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:48 [PATCH v2 1/2] arm64: dts: qcom: sa8540p-ride: Fix some i2c pinctrl settings Andrew Halaney
2023-01-30 15:48 ` Andrew Halaney [this message]
2023-01-31 21:34 ` [PATCH v2 2/2] arm64: dts: qcom: sa8540p-ride: Document i2c busses Eric Chanudet
2023-02-09 4:22 ` (subset) [PATCH v2 1/2] arm64: dts: qcom: sa8540p-ride: Fix some i2c pinctrl settings Bjorn Andersson
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=20230130154823.117542-2-ahalaney@redhat.com \
--to=ahalaney@redhat.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--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=quic_shazhuss@quicinc.com \
--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