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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y3bepmgb.wl-kuninori.morimoto.gx@renesas.com>
Date:   Thu, 4 Oct 2018 00:55:10 +0000
From:   Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To:     <jiada_wang@...tor.com>
Cc:     <lgirdwood@...il.com>, <broonie@...nel.org>, <perex@...ex.cz>,
        <tiwai@...e.com>, <alsa-devel@...a-project.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH linux-next v2 1/9] arm64: r8a7795: add dma request number for busif0 ~ busif7


Hi Jiada

Thank you for your patch

> From: Jiada Wang <jiada_wang@...tor.com>
> 
> This patch adds dma request number for busif0 ~ busif7
> to be used by GEN3 series. GEN2 continues to use rxu/txu
> for busif data transfer.
> 
> Signed-off-by: Jiada Wang <jiada_wang@...tor.com>
> ---
>  arch/arm64/boot/dts/renesas/r8a7795.dtsi | 164 ++++++++++++++++++++---
>  1 file changed, 144 insertions(+), 20 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> index b5f2273caca4..fc6100eddfed 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> @@ -1923,53 +1923,177 @@
>  			rcar_sound,ssi {
>  				ssi0: ssi-0 {
>  					interrupts = <GIC_SPI 370 IRQ_TYPE_LEVEL_HIGH>;
> -					dmas = <&audma0 0x01>, <&audma1 0x02>, <&audma0 0x15>, <&audma1 0x16>;
> -					dma-names = "rx", "tx", "rxu", "txu";
> +					dmas = <&audma0 0x01>, <&audma1 0x02>,
> +					       <&audma0 0x15>, <&audma1 0x16>,
> +					       <&audma0 0x15>, <&audma1 0x16>,
> +					       <&audma0 0x35>, <&audma1 0x36>,
> +					       <&audma0 0x37>, <&audma1 0x38>,
> +					       <&audma0 0x47>, <&audma1 0x48>,
> +					       <&audma0 0x3f>, <&audma1 0x40>,
> +					       <&audma0 0x43>, <&audma1 0x44>,
> +					       <&audma0 0x4f>, <&audma1 0x50>,
> +					       <&audma0 0x53>, <&audma1 0x54>;
> +					dma-names = "rx", "tx",
> +						    "rxu", "txu",
> +						    "rxu0", "txu0",
> +						    "rxu1", "txu1",
> +						    "rxu2", "txu2",
> +						    "rxu3", "txu3",
> +						    "rxu4", "txu4",
> +						    "rxu5", "txu5",
> +						    "rxu6", "txu6",
> +						    "rxu7", "txu7";

In theory, I think DT side patch should be posted/applied
if driver side patch was accepted.
And, Gen3 side DT doesn't need "rxu/txu" I think.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ