From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: broonie@kernel.org, cw00.choi@samsung.com, dmitry.torokhov@gmail.com
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
patches@opensource.wolfsonmicro.com, myungjoo.ham@samsung.com,
linux-input@vger.kernel.org
Subject: [PATCH V2 0/5] ASoC/arizona: Ensure pin searches use widget name prefix
Date: Tue, 29 Nov 2016 15:44:37 +0000 [thread overview]
Message-ID: <1480434282-26389-1-git-send-email-rf@opensource.wolfsonmicro.com> (raw)
The name of a codec pin can have an optional prefix string, which is
defined by the audio machine driver. The snd_soc_dapm_x_pin functions
take the fully-specified name including the prefix and so the existing
code would fail to find the pin if the audio machine driver had added
a prefix.
This patch chain adds new helper functions that take a non-prefixed name
for a specific ASoC component and internally add that component's prefix.
The other patches update the arizona drivers to use these new functions.
Richard Fitzgerald (5):
ASoC: core: Add component pin control functions
ASoC: arizona: Use component pin control functions
regulator: arizona-micsupp: Use SoC component pin control functions
extcon: arizona: Use SoC component pin control functions
Input: arizona-haptics - Use SoC component pin control functions
drivers/extcon/extcon-arizona.c | 8 +-
drivers/input/misc/arizona-haptics.c | 13 ++-
drivers/regulator/arizona-micsupp.c | 6 +-
include/sound/soc.h | 20 ++++
sound/soc/codecs/arizona.c | 12 ++-
sound/soc/codecs/cs47l24.c | 3 +-
sound/soc/codecs/wm5102.c | 3 +-
sound/soc/codecs/wm5110.c | 3 +-
sound/soc/codecs/wm8997.c | 3 +-
sound/soc/codecs/wm8998.c | 3 +-
sound/soc/soc-utils.c | 199 +++++++++++++++++++++++++++++++++++
11 files changed, 255 insertions(+), 18 deletions(-)
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: <broonie@kernel.org>, <cw00.choi@samsung.com>,
<dmitry.torokhov@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<patches@opensource.wolfsonmicro.com>, <myungjoo.ham@samsung.com>,
<linux-input@vger.kernel.org>
Subject: [PATCH V2 0/5] ASoC/arizona: Ensure pin searches use widget name prefix
Date: Tue, 29 Nov 2016 15:44:37 +0000 [thread overview]
Message-ID: <1480434282-26389-1-git-send-email-rf@opensource.wolfsonmicro.com> (raw)
The name of a codec pin can have an optional prefix string, which is
defined by the audio machine driver. The snd_soc_dapm_x_pin functions
take the fully-specified name including the prefix and so the existing
code would fail to find the pin if the audio machine driver had added
a prefix.
This patch chain adds new helper functions that take a non-prefixed name
for a specific ASoC component and internally add that component's prefix.
The other patches update the arizona drivers to use these new functions.
Richard Fitzgerald (5):
ASoC: core: Add component pin control functions
ASoC: arizona: Use component pin control functions
regulator: arizona-micsupp: Use SoC component pin control functions
extcon: arizona: Use SoC component pin control functions
Input: arizona-haptics - Use SoC component pin control functions
drivers/extcon/extcon-arizona.c | 8 +-
drivers/input/misc/arizona-haptics.c | 13 ++-
drivers/regulator/arizona-micsupp.c | 6 +-
include/sound/soc.h | 20 ++++
sound/soc/codecs/arizona.c | 12 ++-
sound/soc/codecs/cs47l24.c | 3 +-
sound/soc/codecs/wm5102.c | 3 +-
sound/soc/codecs/wm5110.c | 3 +-
sound/soc/codecs/wm8997.c | 3 +-
sound/soc/codecs/wm8998.c | 3 +-
sound/soc/soc-utils.c | 199 +++++++++++++++++++++++++++++++++++
11 files changed, 255 insertions(+), 18 deletions(-)
--
1.9.1
next reply other threads:[~2016-11-29 15:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 15:44 Richard Fitzgerald [this message]
2016-11-29 15:44 ` [PATCH V2 0/5] ASoC/arizona: Ensure pin searches use widget name prefix Richard Fitzgerald
2016-11-29 15:44 ` [PATCH V2 1/5] ASoC: core: Add component pin control functions Richard Fitzgerald
2016-11-29 15:44 ` Richard Fitzgerald
2016-11-30 17:16 ` Applied "ASoC: core: Add component pin control functions" to the asoc tree Mark Brown
2016-11-30 17:16 ` Mark Brown
2016-11-29 15:44 ` [PATCH V2 2/5] ASoC: arizona: Use component pin control functions Richard Fitzgerald
2016-11-29 15:44 ` Richard Fitzgerald
2016-11-30 18:07 ` Applied "ASoC: arizona: Use component pin control functions" to the asoc tree Mark Brown
2016-11-30 18:07 ` Mark Brown
2016-11-29 15:44 ` [PATCH V2 3/5] regulator: arizona-micsupp: Use SoC component pin control functions Richard Fitzgerald
2016-11-29 15:44 ` Richard Fitzgerald
2016-11-29 15:44 ` [PATCH V2 4/5] extcon: arizona: " Richard Fitzgerald
2016-11-29 15:44 ` Richard Fitzgerald
2016-11-30 0:19 ` Chanwoo Choi
2016-11-30 17:27 ` Mark Brown
2016-12-01 1:56 ` Chanwoo Choi
2016-11-29 15:44 ` [PATCH V2 5/5] Input: arizona-haptics - " Richard Fitzgerald
2016-11-29 15:44 ` Richard Fitzgerald
2016-11-30 1:41 ` Dmitry Torokhov
2016-11-30 17:28 ` Mark Brown
2016-11-30 18:30 ` Dmitry Torokhov
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=1480434282-26389-1-git-send-email-rf@opensource.wolfsonmicro.com \
--to=rf@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.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.