From: Denzeel Oliva <wachiturroxd150@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Sam Protsenko <semen.protsenko@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-serial@vger.kernel.org, linux-i2c@vger.kernel.org,
Denzeel Oliva <wachiturroxd150@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH 7/8] dt-bindings: i2c: exynos5: Add exynos990-hsi2c compatible
Date: Sun, 07 Sep 2025 21:34:03 +0000 [thread overview]
Message-ID: <20250907-perics-add-usinodes-v1-7-ae7600491a7f@gmail.com> (raw)
In-Reply-To: <20250907-perics-add-usinodes-v1-0-ae7600491a7f@gmail.com>
Add samsung,exynos990-hsi2c dedicated compatible for
representing I2C of Exynos990 SoC.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Denzeel Oliva <wachiturroxd150@gmail.com>
---
Documentation/devicetree/bindings/i2c/i2c-exynos5.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-exynos5.yaml b/Documentation/devicetree/bindings/i2c/i2c-exynos5.yaml
index 7ae8c7b1d0067e7e7a73a58e8bcb4aac71e87dd8..6fc03281a8f8440ba64df569f6c83ba2d9f6915e 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-exynos5.yaml
+++ b/Documentation/devicetree/bindings/i2c/i2c-exynos5.yaml
@@ -38,6 +38,7 @@ properties:
- google,gs101-hsi2c
- samsung,exynos2200-hsi2c
- samsung,exynos850-hsi2c
+ - samsung,exynos990-hsi2c
- const: samsung,exynosautov9-hsi2c
- const: samsung,exynos5-hsi2c # Exynos5250 and Exynos5420
deprecated: true
--
2.50.1
next prev parent reply other threads:[~2025-09-07 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 21:33 [PATCH 0/8] arm64: dts: exynos990: Add PERIC0/1 USI, UART and HSI2C support Denzeel Oliva
2025-09-07 21:33 ` [PATCH 1/8] dt-bindings: soc: samsung: exynos-sysreg: Add Exynos990 PERIC0/1 compatibles Denzeel Oliva
2025-09-07 21:33 ` [PATCH 2/8] arm64: dts: exynos990: Add sysreg nodes for PERIC0 and PERIC1 Denzeel Oliva
2025-09-07 21:33 ` [PATCH 3/8] dt-bindings: soc: samsung: Add Exynos990 USI compatible Denzeel Oliva
2025-09-07 21:34 ` [PATCH 4/8] arm64: dts: exynos990: Add USI nodes for PERIC0 and PERIC1 Denzeel Oliva
2025-09-07 21:34 ` [PATCH 5/8] dt-bindings: serial: samsung: Add Exynos990 UART compatible Denzeel Oliva
2025-09-07 21:34 ` [PATCH 6/8] arm64: dts: exynos990: Add UART nodes for PERIC0/1 Denzeel Oliva
2025-09-07 21:34 ` Denzeel Oliva [this message]
2025-09-07 21:34 ` [PATCH 8/8] arm64: dts: exynos990: Add HSI2C " Denzeel Oliva
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=20250907-perics-add-usinodes-v1-7-ae7600491a7f@gmail.com \
--to=wachiturroxd150@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.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).