From: Mark Brown <broonie@kernel.org>
To: Miguel Aguilar <miguel.aguilar@ridgerun.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
alsa-devel@alsa-project.org, linaro-kernel@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Remove ASoC-level I/O functions from cq93vc
Date: Sat, 31 Aug 2013 14:07:41 +0100 [thread overview]
Message-ID: <20130831130741.GG18608@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
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.
Mark Brown (5):
mfd: davinci_voicecodec: Remove unused read and write functions
mfd: davinci_voicecodec: Provide a regmap for register I/O
ASoC: cq93vc: Use core I/O functions
ASoC: cq93vc: Don't use control data for core driver data
ASoC: cq93vc: Use regmap for I/O
drivers/mfd/davinci_voicecodec.c | 23 +++++++++++--------
include/linux/mfd/davinci_voicecodec.h | 3 +++
sound/soc/codecs/cq93vc.c | 42 +++++++++++-----------------------
3 files changed, 29 insertions(+), 39 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-08-31 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 13:07 Mark Brown [this message]
2013-09-01 14:48 ` [PATCH 0/5] Remove ASoC-level I/O functions from cq93vc Samuel Ortiz
2013-09-01 15:08 ` Mark Brown
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=20130831130741.GG18608@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.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 \
--cc=sameo@linux.intel.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