From: "Sriranjani P" <sriranjani.p@samsung.com>
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>
Subject: RE: [PATCH v4 0/2] arm64: dts: Add SYSREG nodes for FSD SoC
Date: Tue, 6 Dec 2022 14:27:28 +0530 [thread overview]
Message-ID: <01ff01d90950$c7768fd0$5663af70$@samsung.com> (raw)
In-Reply-To: <20221129115531.102932-1-sriranjani.p@samsung.com>
Hi all,
Gentle Reminder to review this patch series.
Thanks,
Sriranjani P.
> -----Original Message-----
> From: Sriranjani P [mailto:sriranjani.p@samsung.com]
> Sent: 29 November 2022 17:25
> 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 0/2] arm64: dts: Add SYSREG nodes for FSD SoC
>
> FSD has few system controller register blocks. This patch series intends to
> add support of device node for system controller registers group that resides
> in PERIC, FSYS0, FSYS1 and CAM blocks of FSD SoC. As these will be used by
> PCIE, EQoS and CSI module. Patches for adding support for PCIE, EQoS and
> CSI are already under review at [1], [2] and [3].
>
> Also this patch series add required DT bindings for such system controller of
> FSD SoC.
>
> [1]: https://lkml.org/lkml/2022/11/21/463
> [2]: https://lkml.org/lkml/2022/11/4/420
> [3]: https://lkml.org/lkml/2022/11/20/363
>
> These changes are made on top of Krzysztof's patches [4] posted as part of
> splitting Samsung Exynos SoC SYSREG bindings to own file.
>
> [4]: https://lkml.org/lkml/2022/11/25/370
>
> Changes since v3:
> 1. As per update from Krzysztof, add dedicated compatibles for sysreg found
> on FSD SoC in the exynos-sysreg.yaml file.
> 2. Add CAM block sysreg changes in the dtsi file and respective compatible in
> binding document.
>
> Changes since v2:
> 1. Updated compatibles as per improvements suggested by Krzysztof.
>
> Changes since v1:
> 1. Fixed SoB in [PATCH 1/2] dt-bindings: mfd: syscon: Add tesla compatible
> found on FSD SoC.
> 2. Address review comments from Krzysztof on [PATCH 2/2] and aligned
> sysreg node near to respective blocks sorted in order of unit address.
>
> Sriranjani P (2):
> dt-bindings: soc: samsung: exynos-sysreg: Add tesla FSD sysreg
> compatibles
> arm64: dts: fsd: add sysreg device node
>
> .../soc/samsung/samsung,exynos-sysreg.yaml | 4 ++++
> arch/arm64/boot/dts/tesla/fsd.dtsi | 20 +++++++++++++++++++
> 2 files changed, 24 insertions(+)
>
> --
> 2.17.1
next prev parent reply other threads:[~2022-12-06 9:30 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
[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 ` Sriranjani P [this message]
2022-12-06 10:07 ` [PATCH v4 0/2] arm64: dts: Add SYSREG nodes for FSD SoC 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='01ff01d90950$c7768fd0$5663af70$@samsung.com' \
--to=sriranjani.p@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=ravi.patel@samsung.com \
--cc=robh+dt@kernel.org \
--cc=sathya@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).