From: Simon Horman <horms@verge.net.au>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Laurent <laurent.pinchart@ideasonboard.com>,
Magnus <magnus.damm@gmail.com>,
Linux-SH <linux-sh@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 4/5 v2] ARM: shmobile: bockw: add R-Car sound support (PIO)
Date: Thu, 05 Sep 2013 07:19:50 +0000 [thread overview]
Message-ID: <20130905071946.GA8334@verge.net.au> (raw)
In-Reply-To: <20130905055749.GF14960@verge.net.au>
[ CC Mark Brown, alsa-devel ]
On Thu, Sep 05, 2013 at 02:57:51PM +0900, Simon Horman wrote:
> On Mon, Aug 26, 2013 at 01:52:35AM -0700, Kuninori Morimoto wrote:
> > This patch enables R-Car sound,
> > AK4643 (CN19) and AK4554 (CN20/CN21) codec chip
> > on Bock-W.
> >
> > But, it supports PIO transfer only at this point.
> > User can check sound settings (Dip-switch/PFC etc)
> > via this patch, but will get under/over flow error
> > when playback/capture.
> > Because PIO transfer via SSI will be interrupted
> > "sampling rate" times per 1 second.
> >
> > DMA transfer will be supported when HPB-DMAC was
> > enabled on r8a7778.
> >
> > You will notice strange ALSA sound card HW
> > numbering on Bock-W board.
> > This came from AK4554 strange format on playback/capture.
> > The format on playback/capture is same on "normal" codec chip,
> > but AK4554 was different.
> > Because of that, AK4554 playback/capture are
> > registered as a different sound card.
> >
> > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > ---
> > v1 -> v2
>
> Thanks, I have queued this up for v3.13.
>
> There was a bit of diff-noise, please make sure I have applied it
> correctly. The patch I applied is below:
Unfortunately I didn't read your cover email carefully before queuing this up.
I now see that it has dependencies that aren't present in v3.11-rc and
thus I have temporarily dropped it.
It seems to me that the dependencies could be provided by
the topic/car branch of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git.
Morimoto-san, is this correct?
If so, Mark, would it be possible for you to provide topic/car
or similar as stable branch for me to use as a base?
My intention is to queue these up for v3.13.
next prev parent reply other threads:[~2013-09-05 7:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 4:05 [PATCH 0/5] ARM: shmobile: bockw: add Sound support Kuninori Morimoto
2013-08-21 8:50 ` Simon Horman
2013-08-26 8:50 ` [PATCH 0/5 v2] " Kuninori Morimoto
2013-08-26 8:52 ` [PATCH 4/5 v2] ARM: shmobile: bockw: add R-Car sound support (PIO) Kuninori Morimoto
2013-09-04 18:38 ` Sergei Shtylyov
2013-09-05 5:57 ` Simon Horman
2013-09-05 7:19 ` Simon Horman [this message]
2013-09-05 7:31 ` Simon Horman
2013-09-05 7:40 ` Kuninori Morimoto
2013-09-05 13:53 ` Mark Brown
2013-09-06 2:16 ` Simon Horman
2013-08-30 0:42 ` [PATCH 0/5 v2] ARM: shmobile: bockw: add Sound support Kuninori Morimoto
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=20130905071946.GA8334@verge.net.au \
--to=horms@verge.net.au \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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