From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: peter.griffin@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: andi.shyti@kernel.org, alim.akhtar@samsung.com,
s.nawrocki@samsung.com, tomasz.figa@gmail.com,
cw00.choi@samsung.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, andre.draszik@linaro.org,
semen.protsenko@linaro.org, willmcvicker@google.com,
kernel-team@android.com, Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: [PATCH v4 7/8] arm64: dts: exynos: gs101: define USI8 with I2C configuration
Date: Fri, 19 Jan 2024 11:11:31 +0000 [thread overview]
Message-ID: <20240119111132.1290455-8-tudor.ambarus@linaro.org> (raw)
In-Reply-To: <20240119111132.1290455-1-tudor.ambarus@linaro.org>
USI8 I2C is used to communicate with an eeprom found on the battery
connector. Define USI8 in I2C configuration.
USI8 CONFIG register comes with a 0x0 reset value, meaning that USI8
doesn't have a default protocol (I2C, SPI, UART) at reset. Thus the
selection of the protocol is intentionally left for the board dts file.
Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org>
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
---
arch/arm64/boot/dts/exynos/google/gs101.dtsi | 29 ++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/arch/arm64/boot/dts/exynos/google/gs101.dtsi b/arch/arm64/boot/dts/exynos/google/gs101.dtsi
index 6aa25cc4676e..f14a24628d04 100644
--- a/arch/arm64/boot/dts/exynos/google/gs101.dtsi
+++ b/arch/arm64/boot/dts/exynos/google/gs101.dtsi
@@ -352,6 +352,35 @@ pinctrl_peric0: pinctrl@10840000 {
interrupts = <GIC_SPI 625 IRQ_TYPE_LEVEL_HIGH 0>;
};
+ usi8: usi@109700c0 {
+ compatible = "google,gs101-usi",
+ "samsung,exynos850-usi";
+ reg = <0x109700c0 0x20>;
+ ranges;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ clocks = <&cmu_peric0 CLK_GOUT_PERIC0_CLK_PERIC0_USI8_USI_CLK>,
+ <&cmu_peric0 CLK_GOUT_PERIC0_PERIC0_TOP0_IPCLK_7>;
+ clock-names = "pclk", "ipclk";
+ samsung,sysreg = <&sysreg_peric0 0x101c>;
+ status = "disabled";
+
+ hsi2c_8: i2c@10970000 {
+ compatible = "google,gs101-hsi2c",
+ "samsung,exynosautov9-hsi2c";
+ reg = <0x10970000 0xc0>;
+ interrupts = <GIC_SPI 642 IRQ_TYPE_LEVEL_HIGH 0>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&hsi2c8_bus>;
+ clocks = <&cmu_peric0 CLK_GOUT_PERIC0_PERIC0_TOP0_IPCLK_7>,
+ <&cmu_peric0 CLK_GOUT_PERIC0_CLK_PERIC0_USI8_USI_CLK>;
+ clock-names = "hsi2c", "hsi2c_pclk";
+ status = "disabled";
+ };
+ };
+
usi_uart: usi@10a000c0 {
compatible = "google,gs101-usi",
"samsung,exynos850-usi";
--
2.43.0.429.g432eaa2c6b-goog
next prev parent reply other threads:[~2024-01-19 11:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 11:11 [PATCH v4 0/8] GS101 Oriole: CMU_PERIC0 support and USI updates Tudor Ambarus
2024-01-19 11:11 ` [PATCH v4 1/8] dt-bindings: clock: google,gs101-clock: add PERIC0 clock management unit Tudor Ambarus
2024-01-22 11:15 ` (subset) " Krzysztof Kozlowski
2024-01-19 11:11 ` [PATCH v4 2/8] dt-bindings: i2c: exynos5: add google,gs101-hsi2c compatible Tudor Ambarus
2024-01-22 11:15 ` (subset) " Krzysztof Kozlowski
2024-01-19 11:11 ` [PATCH v4 3/8] clk: samsung: gs101: add support for cmu_peric0 Tudor Ambarus
2024-01-22 11:13 ` Krzysztof Kozlowski
2024-01-22 11:45 ` Tudor Ambarus
2024-01-19 11:11 ` [PATCH v4 4/8] arm64: dts: exynos: gs101: remove reg-io-width from serial Tudor Ambarus
2024-01-22 11:15 ` (subset) " Krzysztof Kozlowski
2024-01-19 11:11 ` [PATCH v4 5/8] arm64: dts: exynos: gs101: enable cmu-peric0 clock controller Tudor Ambarus
2024-01-22 11:15 ` (subset) " Krzysztof Kozlowski
2024-01-19 11:11 ` [PATCH v4 6/8] arm64: dts: exynos: gs101: update USI UART to use peric0 clocks Tudor Ambarus
2024-01-22 11:15 ` (subset) " Krzysztof Kozlowski
2024-01-23 7:54 ` Krzysztof Kozlowski
2024-01-23 9:54 ` (subset) " Krzysztof Kozlowski
2024-01-19 11:11 ` Tudor Ambarus [this message]
2024-01-22 11:15 ` (subset) [PATCH v4 7/8] arm64: dts: exynos: gs101: define USI8 with I2C configuration Krzysztof Kozlowski
2024-01-23 7:52 ` Krzysztof Kozlowski
2024-01-23 8:34 ` Tudor Ambarus
2024-01-23 8:39 ` Krzysztof Kozlowski
2024-01-23 8:44 ` Tudor Ambarus
2024-01-23 8:57 ` Tudor Ambarus
2024-01-23 8:59 ` Krzysztof Kozlowski
2024-01-23 9:09 ` Tudor Ambarus
2024-01-23 9:54 ` (subset) " Krzysztof Kozlowski
2024-01-19 11:11 ` [PATCH v4 8/8] arm64: dts: exynos: gs101: enable eeprom on gs101-oriole Tudor Ambarus
2024-01-22 11:15 ` (subset) " Krzysztof Kozlowski
2024-01-23 9:54 ` 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=20240119111132.1290455-8-tudor.ambarus@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tomasz.figa@gmail.com \
--cc=willmcvicker@google.com \
/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