mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: <jiada_wang@mentor.com>
Cc: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
	<tiwai@suse.com>, <alsa-devel@alsa-project.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH linux-next v2 1/9] arm64: r8a7795: add dma request number for busif0 ~ busif7
Date: Thu, 4 Oct 2018 00:55:10 +0000	[thread overview]
Message-ID: <87y3bepmgb.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20181003085855.4305-2-jiada_wang@mentor.com>


Hi Jiada

Thank you for your patch

> From: Jiada Wang <jiada_wang@mentor.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@mentor.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.

  reply	other threads:[~2018-10-04  0:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03  8:58 [PATCH linux-next v2 0/9] ASoC: rsnd: support to use different BUSIF for GEN3 jiada_wang
2018-10-03  8:58 ` [PATCH linux-next v2 1/9] arm64: r8a7795: add dma request number for busif0 ~ busif7 jiada_wang
2018-10-04  0:55   ` Kuninori Morimoto [this message]
2018-10-04  3:15     ` Jiada Wang
2018-10-03  8:58 ` [PATCH linux-next v2 2/9] arm64: r8a7796: " jiada_wang
2018-10-03  8:58 ` [PATCH linux-next v2 3/9] arm64: r8a774a1: " jiada_wang
2018-10-03  8:58 ` [PATCH linux-next v2 4/9] arm64: r8a7795: change to use extended audio dmac register jiada_wang

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=87y3bepmgb.wl-kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jiada_wang@mentor.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®