linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org, lee.jones@linaro.org
Cc: lgirdwood@gmail.com, sameo@linux.intel.com,
	patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] *** SUBJECT HERE ***
Date: Tue, 19 Nov 2013 16:03:59 +0000	[thread overview]
Message-ID: <1384877043-5640-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)

Hi,

Small patch series adding some missing functionality on
the WM5110. Given most of the changes are in ASoC I have
generated the patches against Mark's tree but let me know
if we want to push them through MFD instead and I can
regenerate, but I suspect they will cause less conflicts
going through ASoC.

Thanks,
Charles

Charles Keepax (3):
  mfd: wm5110: Make DSP memories readable
  ASoC: wm5110: Add basic support for ISRCs
  ASoC: wm5110: Expose input high pass filter controls

Mark Brown (1):
  ASoC: wm5110: Hook up ADSP2 cores

 drivers/mfd/wm5110-tables.c           |   73 +++++++-
 include/linux/mfd/arizona/registers.h |   37 ++++
 sound/soc/codecs/Kconfig              |    2 +
 sound/soc/codecs/arizona.c            |   10 +
 sound/soc/codecs/arizona.h            |    1 +
 sound/soc/codecs/wm5110.c             |  316 ++++++++++++++++++++++++++++++++-
 6 files changed, 433 insertions(+), 6 deletions(-)

-- 
1.7.2.5


             reply	other threads:[~2013-11-19 16:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19 16:03 Charles Keepax [this message]
2013-11-19 16:04 ` [PATCH 1/4] mfd: wm5110: Make DSP memories readable Charles Keepax
2013-11-20  9:17   ` Lee Jones
2013-11-19 16:04 ` [PATCH 2/4] ASoC: wm5110: Hook up ADSP2 cores Charles Keepax
2013-11-24 13:38   ` Mark Brown
2013-11-19 16:04 ` [PATCH 3/4] ASoC: wm5110: Add basic support for ISRCs Charles Keepax
2013-11-24 13:38   ` Mark Brown
2013-11-19 16:04 ` [PATCH 4/4] ASoC: wm5110: Expose input high pass filter controls Charles Keepax
2013-11-20  9:16   ` Lee Jones
2013-11-20 10:20     ` Mark Brown
2013-11-20 10:45       ` Lee Jones
2013-11-20 11:34         ` Mark Brown
2013-11-21  9:07           ` [GIT PULL] mfd: Immutable branch for ASoC Lee Jones
2013-11-21 11:41             ` Mark Brown
2013-11-21 12:21               ` Lee Jones
2013-11-21 12:27               ` Lee Jones
2013-11-21 12:59                 ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2025-12-12  3:13 [PATCH 0/4] *** SUBJECT HERE *** Xiaoshun Xu
2025-12-12 11:30 ` Xiaoshun Xu (徐晓顺)
2020-08-18  9:17 Tomer Samara
2020-08-18  9:50 ` Greg Kroah-Hartman
2020-08-18  9:52   ` Tomer Samara
2020-08-18  8:52 Tomer Samara
2020-08-18  8:48 Tomer Samara
2020-08-18  8:47 Tomer Samara
2014-08-20  4:30 Valentina Manea
2014-08-25 17:43 ` Greg KH
2013-11-19 16:03 Charles Keepax
2011-02-09  9:51 Tobias Klauser
2011-02-09  9:53 ` Tobias Klauser

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=1384877043-5640-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).