From: Vivek Yadav <vivek.2311@samsung.com> To: rcsekar@samsung.com, krzysztof.kozlowski+dt@linaro.org, wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, pankaj.dubey@samsung.com, ravi.patel@samsung.com, alim.akhtar@samsung.com, linux-fsd@tesla.com, robh+dt@kernel.org Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org, aswani.reddy@samsung.com, sriranjani.p@samsung.com Subject: [PATCH v2 3/6] arm64: dts: fsd: add sysreg device node Date: Wed, 9 Nov 2022 15:39:25 +0530 [thread overview] Message-ID: <20221109100928.109478-4-vivek.2311@samsung.com> (raw) In-Reply-To: <20221109100928.109478-1-vivek.2311@samsung.com> From: Sriranjani P <sriranjani.p@samsung.com> Add SYSREG controller device node, which is available in PERIC and FSYS0 block of FSD SoC. Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com> Signed-off-by: Pankaj Kumar Dubey <pankaj.dubey@samsung.com> Cc: devicetree@vger.kernel.org Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: Rob Herring <robh+dt@kernel.org> Signed-off-by: Sriranjani P <sriranjani.p@samsung.com> --- arch/arm64/boot/dts/tesla/fsd.dtsi | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/tesla/fsd.dtsi b/arch/arm64/boot/dts/tesla/fsd.dtsi index f35bc5a288c2..3d8ebbfc27f4 100644 --- a/arch/arm64/boot/dts/tesla/fsd.dtsi +++ b/arch/arm64/boot/dts/tesla/fsd.dtsi @@ -518,6 +518,16 @@ "dout_cmu_fsys1_shared0div4"; }; + sysreg_peric: system-controller@14030000 { + compatible = "tesla,sysreg_peric", "syscon"; + reg = <0x0 0x14030000 0x0 0x1000>; + }; + + sysreg_fsys0: system-controller@15030000 { + compatible = "tesla,sysreg_fsys0", "syscon"; + reg = <0x0 0x15030000 0x0 0x1000>; + }; + mdma0: dma-controller@10100000 { compatible = "arm,pl330", "arm,primecell"; reg = <0x0 0x10100000 0x0 0x1000>; -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Yadav <vivek.2311@samsung.com> To: rcsekar@samsung.com, krzysztof.kozlowski+dt@linaro.org, wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, pankaj.dubey@samsung.com, ravi.patel@samsung.com, alim.akhtar@samsung.com, linux-fsd@tesla.com, robh+dt@kernel.org Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org, aswani.reddy@samsung.com, sriranjani.p@samsung.com Subject: [PATCH v2 3/6] arm64: dts: fsd: add sysreg device node Date: Wed, 9 Nov 2022 15:39:25 +0530 [thread overview] Message-ID: <20221109100928.109478-4-vivek.2311@samsung.com> (raw) In-Reply-To: <20221109100928.109478-1-vivek.2311@samsung.com> From: Sriranjani P <sriranjani.p@samsung.com> Add SYSREG controller device node, which is available in PERIC and FSYS0 block of FSD SoC. Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com> Signed-off-by: Pankaj Kumar Dubey <pankaj.dubey@samsung.com> Cc: devicetree@vger.kernel.org Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: Rob Herring <robh+dt@kernel.org> Signed-off-by: Sriranjani P <sriranjani.p@samsung.com> --- arch/arm64/boot/dts/tesla/fsd.dtsi | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/tesla/fsd.dtsi b/arch/arm64/boot/dts/tesla/fsd.dtsi index f35bc5a288c2..3d8ebbfc27f4 100644 --- a/arch/arm64/boot/dts/tesla/fsd.dtsi +++ b/arch/arm64/boot/dts/tesla/fsd.dtsi @@ -518,6 +518,16 @@ "dout_cmu_fsys1_shared0div4"; }; + sysreg_peric: system-controller@14030000 { + compatible = "tesla,sysreg_peric", "syscon"; + reg = <0x0 0x14030000 0x0 0x1000>; + }; + + sysreg_fsys0: system-controller@15030000 { + compatible = "tesla,sysreg_fsys0", "syscon"; + reg = <0x0 0x15030000 0x0 0x1000>; + }; + mdma0: dma-controller@10100000 { compatible = "arm,pl330", "arm,primecell"; reg = <0x0 0x10100000 0x0 0x1000>; -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-09 10:54 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20221109100240epcas5p2cdd73ae96d91a5e915f3ac9a42091620@epcas5p2.samsung.com> 2022-11-09 10:09 ` [PATCH v2 0/6] can: mcan: Add MCAN support for FSD SoC Vivek Yadav 2022-11-09 10:09 ` Vivek Yadav [not found] ` <CGME20221109100245epcas5p38a01aed025f491d39a09508ebcdcef84@epcas5p3.samsung.com> 2022-11-09 10:09 ` [PATCH v2 1/6] dt-bindings: Document the SYSREG specific compatibles found on " Vivek Yadav 2022-11-09 10:09 ` Vivek Yadav 2022-11-09 11:08 ` Krzysztof Kozlowski 2022-11-09 11:08 ` Krzysztof Kozlowski 2022-11-10 11:18 ` Vivek Yadav 2022-11-10 11:18 ` Vivek Yadav 2022-11-10 12:11 ` Krzysztof Kozlowski 2022-11-10 12:11 ` Krzysztof Kozlowski 2022-11-11 4:06 ` Vivek Yadav 2022-11-11 4:06 ` Vivek Yadav 2022-11-11 7:54 ` Krzysztof Kozlowski 2022-11-11 7:54 ` Krzysztof Kozlowski 2022-11-16 16:43 ` Rob Herring 2022-11-16 16:43 ` Rob Herring [not found] ` <CGME20221109100249epcas5p142a0a9f7e822c466f7ca778cd341e6d9@epcas5p1.samsung.com> 2022-11-09 10:09 ` [PATCH v2 2/6] dt-bindings: can: mcan: Add ECC functionality to message ram Vivek Yadav 2022-11-09 10:09 ` Vivek Yadav 2022-11-09 11:11 ` Krzysztof Kozlowski 2022-11-09 11:11 ` Krzysztof Kozlowski [not found] ` <CGME20221109100254epcas5p48c574876756f899875df8ac71464ce11@epcas5p4.samsung.com> 2022-11-09 10:09 ` Vivek Yadav [this message] 2022-11-09 10:09 ` [PATCH v2 3/6] arm64: dts: fsd: add sysreg device node Vivek Yadav 2022-11-09 11:16 ` Krzysztof Kozlowski 2022-11-09 11:16 ` Krzysztof Kozlowski 2022-11-09 11:17 ` Sam Protsenko 2022-11-09 11:17 ` Sam Protsenko 2022-11-10 12:54 ` Krzysztof Kozlowski 2022-11-10 12:54 ` Krzysztof Kozlowski [not found] ` <CGME20221109100258epcas5p2966d5e93e00d2a5b4e4a3096dc5a5ec6@epcas5p2.samsung.com> 2022-11-09 10:09 ` [PATCH v2 4/6] arm64: dts: fsd: Add MCAN " Vivek Yadav 2022-11-09 10:09 ` Vivek Yadav 2022-11-09 11:18 ` Krzysztof Kozlowski 2022-11-09 11:18 ` Krzysztof Kozlowski [not found] ` <CGME20221109100302epcas5p276282a3a320649661939dcb893765fbf@epcas5p2.samsung.com> 2022-11-09 10:09 ` [PATCH v2 5/6] can: m_can: Add ECC functionality for message RAM Vivek Yadav 2022-11-09 10:09 ` Vivek Yadav 2022-11-09 11:20 ` Krzysztof Kozlowski 2022-11-09 11:20 ` Krzysztof Kozlowski [not found] ` <CGME20221109100309epcas5p4bc1ddd62048098d681ba8af8d35e2e73@epcas5p4.samsung.com> 2022-11-09 10:09 ` [PATCH v2 6/6] arm64: dts: fsd: Add support for error correction code " Vivek Yadav 2022-11-09 10:09 ` Vivek Yadav 2022-11-09 11:21 ` Krzysztof Kozlowski 2022-11-09 11:21 ` 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=20221109100928.109478-4-vivek.2311@samsung.com \ --to=vivek.2311@samsung.com \ --cc=alim.akhtar@samsung.com \ --cc=aswani.reddy@samsung.com \ --cc=davem@davemloft.net \ --cc=devicetree@vger.kernel.org \ --cc=edumazet@google.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=kuba@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-can@vger.kernel.org \ --cc=linux-fsd@tesla.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=mkl@pengutronix.de \ --cc=netdev@vger.kernel.org \ --cc=pabeni@redhat.com \ --cc=pankaj.dubey@samsung.com \ --cc=ravi.patel@samsung.com \ --cc=rcsekar@samsung.com \ --cc=robh+dt@kernel.org \ --cc=sriranjani.p@samsung.com \ --cc=wg@grandegger.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.