From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Miguel Aguilar <miguel.aguilar@ridgerun.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
davinci-linux-open-source@linux.davincidsp.com,
alsa-devel@alsa-project.org, linaro-kernel@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Remove ASoC-level I/O functions from cq93vc
Date: Sun, 1 Sep 2013 16:48:47 +0200 [thread overview]
Message-ID: <20130901144847.GM20329@zurbaran> (raw)
In-Reply-To: <20130831130741.GG18608@sirena.org.uk>
Hi Mark,
On Sat, Aug 31, 2013 at 02:07:41PM +0100, Mark Brown wrote:
> This patch series removes the use of the ASoC-level read and write
> functions from the cq93vc driver as part of a wider push to remove them
> completely and just use regmap for all register I/O. Since the driver
> is essentially doing what regmap-mmio is doing this is done by adding a
> MMIO regmap to the core device and using that. This is compile tested
> only, I don't have any hardware to run on.
>
> Since I anticipate doing more cleanups over the CODEC drivers during the
> next release cycle it'd be good to merge via ASoC, though there
> shouldn't be any overlap with the first patch.
As I'd prefer to carry the MFD ones (Including the twl6040 one) through
mfd-next, I can build a branch for you to pull from. Would that be fine
with you ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-09-01 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 13:07 [PATCH 0/5] Remove ASoC-level I/O functions from cq93vc Mark Brown
2013-08-31 13:08 ` [PATCH 1/5] mfd: davinci_voicecodec: Remove unused read and write functions Mark Brown
2013-08-31 13:08 ` [PATCH 2/5] mfd: davinci_voicecodec: Provide a regmap for register I/O Mark Brown
2013-08-31 13:08 ` [PATCH 4/5] ASoC: cq93vc: Don't use control data for core driver data Mark Brown
[not found] ` <1377954539-7532-1-git-send-email-broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2013-08-31 13:08 ` [PATCH 3/5] ASoC: cq93vc: Use core I/O functions Mark Brown
2013-08-31 13:08 ` [PATCH 5/5] ASoC: cq93vc: Use regmap for I/O Mark Brown
2013-09-01 14:48 ` Samuel Ortiz [this message]
2013-09-01 15:08 ` [PATCH 0/5] Remove ASoC-level I/O functions from cq93vc Mark Brown
[not found] ` <20130901150853.GG3084-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-09-02 8:55 ` Samuel Ortiz
2013-09-02 9:48 ` 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=20130901144847.GM20329@zurbaran \
--to=sameo@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.aguilar@ridgerun.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).