From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: core: Fix snd_soc_add_card_controls to pass correct data
Date: Tue, 14 Feb 2012 15:17:03 -0800 [thread overview]
Message-ID: <20120214231702.GD3152@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1329260193-9757-1-git-send-email-swarren@nvidia.com>
[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]
On Tue, Feb 14, 2012 at 03:56:33PM -0700, Stephen Warren wrote:
> Commit 022658b "ASoC: core: Add support for DAI and machine kcontrols."
> created new functions to create controls for cards, codecs, platforms,
> and DAIs. The new snd_soc_add_card_controls() passed the wrong "data" to
> utility function snd_soc_add_controls(); it should be passing a codec,
> but instead ended up passing the soc_card. Fix this.
Well, sort of. The idea with Liam's commit was to split things out so
that card operations got given a card so the argument change was
intentional. What's gone wrong is that things like PIN_SWITCH() (which
is only ever used by cards) weren't updated to match so they still
expect to find a CODEC there. This'll quite probably have broken some
other machine specific controls too.
I'll send a patch for PIN_SWITCH later today but it looks like we need
an audit of all the drivers using non-CODEC adds to make sure they don't
assume a CODEC in the callbacks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-02-14 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 22:56 [PATCH] ASoC: core: Fix snd_soc_add_card_controls to pass correct data Stephen Warren
2012-02-14 23:17 ` Mark Brown [this message]
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=20120214231702.GD3152@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=swarren@nvidia.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.