From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Liam Girdwood <lrg@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: ams-delta: fix card initalization failure
Date: Thu, 6 Sep 2012 15:36:35 +0800 [thread overview]
Message-ID: <20120906073633.GC22330@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1939338.OUN9Uq58XY@vclass>
On Sat, Sep 01, 2012 at 11:09:18AM +0200, Janusz Krzysztofik wrote:
> I see your point, however for now I can see no better way of referencing
> the data (of type struct snd_soc_card) then passing it to
> snd_soc_register_card(). But for this to work, I would have to register
> successfully an ams-delta specific platform device first, not the soc-
> audio. This, even if still done from the sound/soc/omap/ams-delta.c, not
> from an arch board file, would require now not existing ams-delta ASoC
> platform driver probe/remove callbacks at least. I'm still not convinced
> if such modification would be acceptable in the middle of the rc cycle.
> If there is a simpler, less intrusive way to do this, then sorry, I
> still can't see it.
Like I already said just make it a static variable.
next prev parent reply other threads:[~2012-09-06 7:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 21:28 [PATCH] ASoC: ams-delta: fix card initalization failure Janusz Krzysztofik
2012-08-27 21:38 ` Mark Brown
2012-08-28 15:13 ` Janusz Krzysztofik
2012-08-28 18:13 ` Mark Brown
2012-08-29 5:04 ` [alsa-devel] " Janusz Krzysztofik
2012-08-31 21:31 ` Mark Brown
2012-09-01 9:09 ` Janusz Krzysztofik
2012-09-06 7:36 ` Mark Brown [this message]
2012-09-16 19:17 ` [PATCH] ASoC: ams-delta: Convert to use snd_soc_register_card() Janusz Krzysztofik
2012-09-16 20:44 ` Tony Lindgren
2012-10-02 21:07 ` Janusz Krzysztofik
2012-10-03 10:38 ` Mark Brown
2012-10-03 10:46 ` [RESEND][PATCH] " Janusz Krzysztofik
2012-10-03 13:51 ` Janusz Krzysztofik
2012-10-04 17:50 ` 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=20120906073633.GC22330@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.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).