From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Kuninori Morimoto <morimoto.kuninori@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 0/4] ASoC: fsi: FSI2 device support
Date: Wed, 24 Mar 2010 09:33:12 +0000 [thread overview]
Message-ID: <1269423192.3798.17.camel@odin> (raw)
In-Reply-To: <u1vfa44ls.wl%morimoto.kuninori@renesas.com>
On Wed, 2010-03-24 at 15:26 +0900, Kuninori Morimoto wrote:
> Dear Mark
>
> These patches are FSI2 support
>
> Kuninori Morimoto (4):
> ASoC: fsi: ensures process inside master lock
> ASoC: fsi: Add FIFO size calculate
> ASoC: fsi: IRQ related process had be united
> ASoC: fsi: Add FSI2 device support
>
> ARM SH-MOBILE series have FSI2/FMSI device which are
> advance version of FSI.
> Above patches add simple FSI2 support.
> These patches are tested on AP4 board
Btw, your clock appears to be a bit broken, patch 2/4 has a time stamp
from 7 days ago...
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-03-24 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 6:26 [PATCH 0/4] ASoC: fsi: FSI2 device support Kuninori Morimoto
2010-03-17 5:26 ` [PATCH 2/4] ASoC: fsi: Add FIFO size calculate Kuninori Morimoto
2010-03-24 9:46 ` Liam Girdwood
2010-03-25 2:39 ` Kuninori Morimoto
2010-03-25 8:56 ` Liam Girdwood
2010-03-23 2:47 ` [PATCH 3/4] ASoC: fsi: IRQ related process had be united Kuninori Morimoto
2010-03-24 9:48 ` Liam Girdwood
2010-03-24 6:27 ` [PATCH 1/4] ASoC: fsi: ensures process inside master lock Kuninori Morimoto
2010-03-24 9:49 ` Liam Girdwood
2010-03-24 6:27 ` [PATCH 4/4] ASoC: fsi: Add FSI2 device support Kuninori Morimoto
2010-03-24 9:50 ` Liam Girdwood
2010-03-24 9:33 ` Liam Girdwood [this message]
2010-03-24 11:19 ` [PATCH 0/4] ASoC: fsi: " Mark Brown
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=1269423192.3798.17.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=morimoto.kuninori@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.