From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Faraz Ata'" <faraz.ata@samsung.com>, <andi.shyti@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rosa.pila@samsung.com>,
<pritam.sutar@samsung.com>, <dev.tailor@samsung.com>
Subject: RE: [PATCH] dt-bindings: i2c: exynos5: add exynosautov920-hsi2c compatible
Date: Thu, 4 Sep 2025 15:39:25 +0530 [thread overview]
Message-ID: <435b01dc1d83$ff8bde30$fea39a90$@samsung.com> (raw)
In-Reply-To: <20250904072844.358759-1-faraz.ata@samsung.com>
Hi Faraz,
> -----Original Message-----
> From: Faraz Ata <faraz.ata@samsung.com>
> Sent: Thursday, September 4, 2025 12:59 PM
> To: andi.shyti@kernel.org; robh@kernel.org; krzk+dt@kernel.org;
> conor+dt@kernel.org; alim.akhtar@samsung.com
> Cc: linux-i2c@vger.kernel.org; devicetree@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org; linux-
> kernel@vger.kernel.org; rosa.pila@samsung.com;
> pritam.sutar@samsung.com; dev.tailor@samsung.com;
> faraz.ata@samsung.com
> Subject: [PATCH] dt-bindings: i2c: exynos5: add exynosautov920-hsi2c
> compatible
>
> Add "samsung,exynosautov920-hsi2c" dedicated compatible for HSI2C found
> in ExynosAutov920 SoC.
>
This is not complete; any new compatible should be complemented with driver changes
(User of the compatible) followed by dts change.
Always send a complete set, also mentioning how the patch was tested.
Best is to get patches reviewed internally before sending to community.
> Signed-off-by: Faraz Ata <faraz.ata@samsung.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 7ae8c7b1d006..207b95e392e5 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,exynosautov920-hsi2c
> - const: samsung,exynosautov9-hsi2c
> - const: samsung,exynos5-hsi2c # Exynos5250 and Exynos5420
> deprecated: true
> --
> 2.34.1
next prev parent reply other threads:[~2025-09-04 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250904071941epcas5p1ffa00f3f1cb69f7a10d08c1e96174cf1@epcas5p1.samsung.com>
2025-09-04 7:28 ` [PATCH] dt-bindings: i2c: exynos5: add exynosautov920-hsi2c compatible Faraz Ata
2025-09-04 8:04 ` Krzysztof Kozlowski
2025-09-04 13:15 ` Faraz Ata
2025-09-05 8:26 ` 'Krzysztof Kozlowski'
2025-09-04 10:09 ` Alim Akhtar [this message]
2026-01-06 17:47 ` Faraz Ata
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='435b01dc1d83$ff8bde30$fea39a90$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dev.tailor@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=faraz.ata@samsung.com \
--cc=krzk+dt@kernel.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=pritam.sutar@samsung.com \
--cc=robh@kernel.org \
--cc=rosa.pila@samsung.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;
as well as URLs for NNTP newsgroup(s).