From: <jiada_wang@mentor.com>
To: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>, <kuninori.morimoto.gx@renesas.com>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH linux-next v2 0/9] ASoC: rsnd: support to use different BUSIF for GEN3
Date: Wed, 3 Oct 2018 17:58:46 +0900 [thread overview]
Message-ID: <20181003085855.4305-1-jiada_wang@mentor.com> (raw)
From: Jiada Wang <jiada_wang@mentor.com>
Rcar audio DMA/SSIU already support to use different BUSIF to transfer data,
but BUSIF is fixed at 0. This patchset adds busif property to dai stream,
GEN3 series can automatically select BUSIF to transfer data,
based on channel and SSI mode (currently only BUSIF0 is selected).
Device tree files are updated to use extended audio dmac register,
and add dma request number for busif0 ~ busif7 for GEN3.
---
v2:
- Instead of configure BUSIF by kctl interface "SSI Out/In BUSIF",
use rsnd_ssi_select_busif() to automatically select BUSIF.
- Keep 'rxu/txu' dma request, to keep compatibility with GEN2 series
- Re-order patch-set to satisfy git bisect
v1: initial version
Jiada Wang (9):
arm64: r8a7795: add dma request number for busif0 ~ busif7
arm64: r8a7796: add dma request number for busif0 ~ busif7
arm64: r8a774a1: add dma request number for busif0 ~ busif7
arm64: r8a7795: change to use extended audio dmac register
arm64: r8a7796: change to use extended audio dmac register
arm64: r8a774a1: change to use extended audio dmac register
arm64: r8a77965: change to use extended audio dmac register
ASoC: rsnd: ssi: Request dedicated dma channels for busif0 to 7
ASoC: rsnd: add busif property to dai stream
arch/arm64/boot/dts/renesas/r8a774a1.dtsi | 166 +++++++++++++++++++---
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 166 +++++++++++++++++++---
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 166 +++++++++++++++++++---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 2 +-
sound/soc/sh/rcar/core.c | 3 +
sound/soc/sh/rcar/dma.c | 31 ++++
sound/soc/sh/rcar/rsnd.h | 3 +
sound/soc/sh/rcar/ssi.c | 58 +++++++-
8 files changed, 525 insertions(+), 70 deletions(-)
--
2.17.0
next reply other threads:[~2018-10-03 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 8:58 jiada_wang [this message]
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
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=20181003085855.4305-1-jiada_wang@mentor.com \
--to=jiada_wang@mentor.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.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®