| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <5eeac2a0-4293-675e-9dc2-25ed8ab3fb8f@samsung.com>
Date: Thu, 28 Apr 2022 11:50:24 +0200
From: Marek Szyprowski <m.szyprowski@...sung.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Lee Jones <lee.jones@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Dinh Nguyen <dinguyen@...nel.org>,
Michal Simek <michal.simek@...inx.com>,
Liviu Dudau <liviu.dudau@....com>,
Sudeep Holla <sudeep.holla@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
Broadcom Kernel Team <bcm-kernel-feedback-list@...adcom.com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Rob Herring <robh@...nel.org>
Subject: Re: [PATCH 08/10] ARM: dts: exynos: use proper
'dma-channels/requests' properties
Hi Krzysztof,
On 27.04.2022 17:58, Krzysztof Kozlowski wrote:
> pl330 DMA controller bindings documented 'dma-channels' and
> 'dma-requests' properties (without leading hash sign), so fix the DTS to
> match the bindings.
>
> Reported-by: Rob Herring <robh@...nel.org>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Are those properties really needed for PL330 driver on Exynos SoCs? I've
removed them and I still see the proper values read from registers and
reported in the log (Exynos4210):
dma-pl330 12680000.dma-controller: Loaded driver for PL330 DMAC-141330
dma-pl330 12680000.dma-controller: DBUFF-32x4bytes Num_Chans-8
Num_Peri-32 Num_Events-32
dma-pl330 12690000.dma-controller: Loaded driver for PL330 DMAC-141330
dma-pl330 12690000.dma-controller: DBUFF-32x4bytes Num_Chans-8
Num_Peri-32 Num_Events-32
dma-pl330 12850000.dma-controller: Loaded driver for PL330 DMAC-141330
dma-pl330 12850000.dma-controller: DBUFF-64x8bytes Num_Chans-8
Num_Peri-1 Num_Events-32
I also don't see any code that would read those properties. IMHO they
should be simply removed at all, at least for the PL330 related nodes.
> ---
> arch/arm/boot/dts/exynos3250.dtsi | 8 ++++----
> arch/arm/boot/dts/exynos4.dtsi | 12 +++++------
> .../boot/dts/exynos4210-universal_c210.dts | 4 ++--
> arch/arm/boot/dts/exynos5250.dtsi | 16 +++++++--------
> arch/arm/boot/dts/exynos5410.dtsi | 8 ++++----
> arch/arm/boot/dts/exynos5420.dtsi | 20 +++++++++----------
> 6 files changed, 34 insertions(+), 34 deletions(-)
>
> diff --git a/arch/arm/boot/dts/exynos3250.dtsi b/arch/arm/boot/dts/exynos3250.dtsi
> index 41bb421e67c2..7bdd4f0782c3 100644
> --- a/arch/arm/boot/dts/exynos3250.dtsi
> +++ b/arch/arm/boot/dts/exynos3250.dtsi
> @@ -429,8 +429,8 @@ pdma0: dma-controller@...80000 {
> clocks = <&cmu CLK_PDMA0>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> pdma1: dma-controller@...90000 {
> @@ -440,8 +440,8 @@ pdma1: dma-controller@...90000 {
> clocks = <&cmu CLK_PDMA1>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> adc: adc@...c0000 {
> diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi
> index 5fd17bc52321..2a244aaf84b4 100644
> --- a/arch/arm/boot/dts/exynos4.dtsi
> +++ b/arch/arm/boot/dts/exynos4.dtsi
> @@ -676,8 +676,8 @@ pdma0: dma-controller@...80000 {
> clocks = <&clock CLK_PDMA0>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> pdma1: dma-controller@...90000 {
> @@ -687,8 +687,8 @@ pdma1: dma-controller@...90000 {
> clocks = <&clock CLK_PDMA1>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> mdma1: dma-controller@...50000 {
> @@ -698,8 +698,8 @@ mdma1: dma-controller@...50000 {
> clocks = <&clock CLK_MDMA>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <1>;
> + dma-channels = <8>;
> + dma-requests = <1>;
> };
>
> fimd: fimd@...00000 {
> diff --git a/arch/arm/boot/dts/exynos4210-universal_c210.dts b/arch/arm/boot/dts/exynos4210-universal_c210.dts
> index 138d606d58a5..c1b11704b8ee 100644
> --- a/arch/arm/boot/dts/exynos4210-universal_c210.dts
> +++ b/arch/arm/boot/dts/exynos4210-universal_c210.dts
> @@ -666,8 +666,8 @@ mdma0: dma-controller@...40000 {
> clocks = <&clock CLK_MDMA>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <1>;
> + dma-channels = <8>;
> + dma-requests = <1>;
> power-domains = <&pd_lcd0>;
> };
> };
> diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi
> index df80ddfada2d..c4c0b4c08094 100644
> --- a/arch/arm/boot/dts/exynos5250.dtsi
> +++ b/arch/arm/boot/dts/exynos5250.dtsi
> @@ -700,8 +700,8 @@ pdma0: dma-controller@...a0000 {
> clocks = <&clock CLK_PDMA0>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> pdma1: dma-controller@...b0000 {
> @@ -711,8 +711,8 @@ pdma1: dma-controller@...b0000 {
> clocks = <&clock CLK_PDMA1>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> mdma0: dma-controller@...00000 {
> @@ -722,8 +722,8 @@ mdma0: dma-controller@...00000 {
> clocks = <&clock CLK_MDMA0>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <1>;
> + dma-channels = <8>;
> + dma-requests = <1>;
> };
>
> mdma1: dma-controller@...10000 {
> @@ -733,8 +733,8 @@ mdma1: dma-controller@...10000 {
> clocks = <&clock CLK_MDMA1>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <1>;
> + dma-channels = <8>;
> + dma-requests = <1>;
> };
>
> gsc_0: gsc@...00000 {
> diff --git a/arch/arm/boot/dts/exynos5410.dtsi b/arch/arm/boot/dts/exynos5410.dtsi
> index 4d797a9abba4..6dc08cb0622c 100644
> --- a/arch/arm/boot/dts/exynos5410.dtsi
> +++ b/arch/arm/boot/dts/exynos5410.dtsi
> @@ -196,8 +196,8 @@ pdma0: dma-controller@...a0000 {
> clocks = <&clock CLK_PDMA0>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> pdma1: dma-controller@...b0000 {
> @@ -207,8 +207,8 @@ pdma1: dma-controller@...b0000 {
> clocks = <&clock CLK_PDMA1>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> audi2s0: i2s@...0000 {
> diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi
> index 21b608705049..08198d82ce8d 100644
> --- a/arch/arm/boot/dts/exynos5420.dtsi
> +++ b/arch/arm/boot/dts/exynos5420.dtsi
> @@ -437,8 +437,8 @@ adma: dma-controller@...0000 {
> clocks = <&clock_audss EXYNOS_ADMA>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <6>;
> - #dma-requests = <16>;
> + dma-channels = <6>;
> + dma-requests = <16>;
> power-domains = <&mau_pd>;
> };
>
> @@ -449,8 +449,8 @@ pdma0: dma-controller@...a0000 {
> clocks = <&clock CLK_PDMA0>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> pdma1: dma-controller@...b0000 {
> @@ -460,8 +460,8 @@ pdma1: dma-controller@...b0000 {
> clocks = <&clock CLK_PDMA1>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <32>;
> + dma-channels = <8>;
> + dma-requests = <32>;
> };
>
> mdma0: dma-controller@...00000 {
> @@ -471,8 +471,8 @@ mdma0: dma-controller@...00000 {
> clocks = <&clock CLK_MDMA0>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <1>;
> + dma-channels = <8>;
> + dma-requests = <1>;
> };
>
> mdma1: dma-controller@...10000 {
> @@ -482,8 +482,8 @@ mdma1: dma-controller@...10000 {
> clocks = <&clock CLK_MDMA1>;
> clock-names = "apb_pclk";
> #dma-cells = <1>;
> - #dma-channels = <8>;
> - #dma-requests = <1>;
> + dma-channels = <8>;
> + dma-requests = <1>;
> /*
> * MDMA1 can support both secure and non-secure
> * AXI transactions. When this is enabled in
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
Powered by blists - more mailing lists