From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jiada Wang <jiada_wang@mentor.com>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 2/2] arm64: dts: renesas: r8a7796: use extended audio dmac register
Date: Wed, 20 Feb 2019 09:05:02 +0100 [thread overview]
Message-ID: <CAMuHMdVVo7LkYu6taKBndssmHMHS5U=nw+FnBoUXuF-r19Yuiw@mail.gmail.com> (raw)
In-Reply-To: <20190220052435.20508-3-jiada_wang@mentor.com>
On Wed, Feb 20, 2019 at 6:25 AM Jiada Wang <jiada_wang@mentor.com> wrote:
> Basic audio dmac register only supports busif from 0 to 3,
> in order to use busif4 ~ busif7, extended audio dmac register
> need to be used
>
> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
but please consider my comments to the cover letter.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2019-02-20 8:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 5:24 [PATCH v1 0/2] rsnd: dts: change to use extended audio dmac register Jiada Wang
2019-02-20 5:24 ` [PATCH v1 1/2] arm64: dts: renesas: r8a7795: " Jiada Wang
2019-02-20 8:04 ` Geert Uytterhoeven
2019-02-20 5:24 ` [PATCH v1 2/2] arm64: dts: renesas: r8a7796: " Jiada Wang
2019-02-20 8:05 ` Geert Uytterhoeven [this message]
2019-02-20 8:04 ` [PATCH v1 0/2] rsnd: dts: change to " Geert Uytterhoeven
2019-02-20 8:10 ` Kuninori Morimoto
2019-02-22 3:05 ` jiada
2019-02-25 9:23 ` Simon Horman
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='CAMuHMdVVo7LkYu6taKBndssmHMHS5U=nw+FnBoUXuF-r19Yuiw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=jiada_wang@mentor.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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).