From: "Ravi Patel" <ravi.patel@samsung.com>
To: "'Sriranjani P'" <sriranjani.p@samsung.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <devicetree@vger.kernel.org>,
<alim.akhtar@samsung.com>, <pankaj.dubey@samsung.com>,
<sathya@samsung.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-samsung-soc@vger.kernel.org>
Subject: RE: [PATCH v4 1/2] dt-bindings: soc: samsung: exynos-sysreg: Add tesla FSD sysreg compatibles
Date: Tue, 6 Dec 2022 14:36:41 +0530 [thread overview]
Message-ID: <000f01d90952$0f8df4b0$2ea9de10$@samsung.com> (raw)
In-Reply-To: <20221129115531.102932-2-sriranjani.p@samsung.com>
>-----Original Message-----
>From: Sriranjani P [mailto:sriranjani.p@samsung.com]
>Sent: 29 November 2022 17:26
>To: robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
>devicetree@vger.kernel.org; alim.akhtar@samsung.com;
>pankaj.dubey@samsung.com; ravi.patel@samsung.com;
>sathya@samsung.com
>Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org; linux-
>samsung-soc@vger.kernel.org; Sriranjani P <sriranjani.p@samsung.com>
>Subject: [PATCH v4 1/2] dt-bindings: soc: samsung: exynos-sysreg: Add tesla
>FSD sysreg compatibles
>
>Add compatible for Tesla SYSREG controllers found on FSD SoC.
>
>Signed-off-by: Sriranjani P <sriranjani.p@samsung.com>
>---
> .../bindings/soc/samsung/samsung,exynos-sysreg.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
>diff --git
>a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-
>sysreg.yaml
>b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-
>sysreg.yaml
>index e7c80dd73081..4954790eda6c 100644
>--- a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-
>sysreg.yaml
>+++ b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-
>sysreg.yaml
>@@ -19,6 +19,10 @@ properties:
> - samsung,exynos5-sysreg
> - samsung,exynos850-sysreg
> - samsung,exynosautov9-sysreg
>+ - tesla,fsd-cam-sysreg
>+ - tesla,fsd-fsys0-sysreg
>+ - tesla,fsd-fsys1-sysreg
>+ - tesla,fsd-peric-sysreg
> - const: syscon
> - items:
> - enum:
>--
>2.17.1
Reviewed-by: Ravi Patel <ravi.patel@samsung.com>
next prev parent reply other threads:[~2022-12-06 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221129115540epcas5p370eb47c404a8d2c08ab4f264ae983481@epcas5p3.samsung.com>
2022-11-29 11:55 ` [PATCH v4 0/2] arm64: dts: Add SYSREG nodes for FSD SoC Sriranjani P
[not found] ` <CGME20221129115543epcas5p3638987bf61777f9cc1b54b980c98c25b@epcas5p3.samsung.com>
2022-11-29 11:55 ` [PATCH v4 1/2] dt-bindings: soc: samsung: exynos-sysreg: Add tesla FSD sysreg compatibles Sriranjani P
2022-12-06 9:06 ` Ravi Patel [this message]
[not found] ` <CGME20221129115546epcas5p3d5ef247af122c4041f50337ed2ec148c@epcas5p3.samsung.com>
2022-11-29 11:55 ` [PATCH v4 2/2] arm64: dts: fsd: add sysreg device node Sriranjani P
2022-12-06 9:07 ` Ravi Patel
2022-12-06 8:57 ` [PATCH v4 0/2] arm64: dts: Add SYSREG nodes for FSD SoC Sriranjani P
2022-12-06 10:07 ` Krzysztof Kozlowski
2022-12-26 15:17 ` 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='000f01d90952$0f8df4b0$2ea9de10$@samsung.com' \
--to=ravi.patel@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=robh+dt@kernel.org \
--cc=sathya@samsung.com \
--cc=sriranjani.p@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).