alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	yoshii <takashi.yoshii.zj@renesas.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Magnus <magnus.damm@gmail.com>, Simon <horms@verge.net.au>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 0/9] ASoC: sh: fsi: tidyup and cleanup FSI
Date: Mon, 23 May 2011 15:43:08 +0100	[thread overview]
Message-ID: <4DDA727C.7000600@ti.com> (raw)
In-Reply-To: <w3pipt17i99.wl%kuninori.morimoto.gx@renesas.com>

On 23/05/11 12:45, Kuninori Morimoto wrote:
> 
> Dear Mark, Liam
> 
> Cc Simon, yoshii-san, Magnus
> 
> These are tidyup and cleanup patches for FSI
> 
> Kuninori Morimoto (9):
>       ASoC: sh: fsi: tidyup parameter of fsi_stream_push
>       ASoC: sh: fsi: tidyup unclear variable naming
>       ASoC: sh: fsi: remove pm_runtime from fsi_dai_set_fmt.
>       ASoC: sh: fsi: make sure fsi_stream_push/pop access by spin lock
>       ASoC: sh: fsi: Add fsi_set_master_clk
>       ASoC: sh: fsi: irq control moves to fsi_port_start/stop
>       ASoC: sh: fsi: Add fsi_hw_startup/shutdown
>       ASoC: sh: fsi: remove fsi_module_init/kill
>       ASoC: sh: fsi: cleanup suspend/resume
> 
> #1 and #2 are tidyup for fsi_fifo_data_ctrl.
> The variables and sub-functions were unclear nameing.
> So, it was difficult to understand the detail of calculation.
> Thank you for pointing it yoshii-san.
> 
> #3 - #9 are clean up for RuntimePM.
> Current FSI driver was wrong for RuntimePM.
> these patches fixup for RuntimePM and
> clean up for suspend/resume.
> last patch remove noisy saved_xxx variable.
> 

All

Acked-by: Liam Girdwood <lrg@ti.com>

  parent reply	other threads:[~2011-05-23 14:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 11:45 [PATCH 0/9] ASoC: sh: fsi: tidyup and cleanup FSI Kuninori Morimoto
2011-05-23 11:45 ` [PATCH 1/9] ASoC: sh: fsi: tidyup parameter of fsi_stream_push Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 2/9] ASoC: sh: fsi: tidyup unclear variable naming Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 3/9] ASoC: sh: fsi: remove pm_runtime from fsi_dai_set_fmt Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 4/9] ASoC: sh: fsi: make sure fsi_stream_push/pop access by spin lock Kuninori Morimoto
2011-05-24 10:39   ` Mark Brown
2011-05-25  0:32     ` Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 5/9] ASoC: sh: fsi: add fsi_set_master_clk Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 6/9] ASoC: sh: fsi: irq control moves to fsi_port_start/stop Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 7/9] ASoC: sh: fsi: add fsi_hw_startup/shutdown Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 8/9] ASoC: sh: fsi: remove fsi_module_init/kill Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 9/9] ASoC: sh: fsi: cleanup suspend/resume Kuninori Morimoto
2011-05-23 14:43 ` Liam Girdwood [this message]
2011-05-24 10:43 ` [PATCH 0/9] ASoC: sh: fsi: tidyup and cleanup 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=4DDA727C.7000600@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=magnus.damm@gmail.com \
    --cc=takashi.yoshii.zj@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 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).