From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
Misael Lopez Cruz <misael.lopez@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: Re: Re: [PATCH 06/10] ASoC: omap-abe-twl6040: Convert to platform deriver
Date: Thu, 15 Dec 2011 10:17:38 +0200 [thread overview]
Message-ID: <5238231.U46jV2XvpL@barack> (raw)
In-Reply-To: <20111214112710.GI3072@opensource.wolfsonmicro.com>
Hi Mark,
On Wednesday 14 December 2011 19:27:11 Mark Brown wrote:
> This seems like we need a better system for doing this, we can't go
> changing the machine name every time there's a kernel space change that
> affects a UCM file, that's going to get crazy.
As of know we do not have UCM for the driver in upstream. In fact it is not
recommended at the moment to use the upstream driver since we do not have the
ABE/dynamic PCM upstream.
There are UCM files shipped with distributions (like Linaro, ubuntu), but
those UCM files will not work with the upstream kernel (due to the missing
parts).
It can be also confusing to have the same card name for fundamentally
different sound cards.
We do support the kernel shipped with distributions (with patched up ASoC),
but we also need to support clean upstream version. Having to deal with
mismatching UCM files does not really help here.
I have not planned to change the card names in the future.
Having said that I can revert back to use the names used by Linaro for example
(even if the cards are different):
SPD4430/Panda/PandaES
If I write the UCM file it will be for the vanilla upstream sound, so we will
have UCM files upstream, which does not work on the Distributions - I think
this is even more confusing than having different card names initially untill
we get everything upstream.
--
Péter
PS:
Liam: what is your take on this?
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-15 8:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 9:46 [PATCH 00/10] OMAP4: ASoC: Support for PandaBoard family Peter Ujfalusi
2011-12-14 9:46 ` [PATCH 01/10] ASoC: sdp4430: Correct author e-mail address Peter Ujfalusi
2011-12-14 10:06 ` Mark Brown
2011-12-14 9:46 ` [PATCH 02/10] ASoC: OMAP4: Rename the sdp4430 machine driver Peter Ujfalusi
2011-12-14 10:22 ` Mark Brown
2011-12-14 9:46 ` [PATCH 03/10] ASoC: omap-abe-twl6040: Correct internal prefix, Kconfig entry Peter Ujfalusi
2011-12-14 10:23 ` Mark Brown
2011-12-14 9:46 ` [PATCH 04/10] include: platform_data: Platform data header for OMAP4 ASoC audio Peter Ujfalusi
2011-12-14 9:57 ` Mark Brown
2011-12-15 13:02 ` Péter Ujfalusi
2011-12-17 9:36 ` Mark Brown
2011-12-19 14:04 ` Peter Ujfalusi
2011-12-19 19:20 ` Tony Lindgren
2011-12-20 0:47 ` Mark Brown
2011-12-20 0:24 ` Mark Brown
2011-12-14 9:46 ` [PATCH 05/10] OMAP4: 4430sdp: Register platform device for OMAP4 audio Peter Ujfalusi
2011-12-14 18:00 ` Tony Lindgren
2011-12-14 9:46 ` [PATCH 06/10] ASoC: omap-abe-twl6040: Convert to platform deriver Peter Ujfalusi
2011-12-14 10:01 ` Mark Brown
2011-12-14 10:15 ` Péter Ujfalusi
2011-12-14 11:27 ` Mark Brown
2011-12-15 8:17 ` Péter Ujfalusi [this message]
2011-12-15 13:01 ` Re: " Péter Ujfalusi
2011-12-14 9:47 ` [PATCH 07/10] ASoC: omap-abe-twl6040: Add support for PandaBoard Peter Ujfalusi
2011-12-14 9:47 ` [PATCH 08/10] OMAP4: omap4panda: Enable audio support Peter Ujfalusi
2011-12-14 18:02 ` Tony Lindgren
2011-12-14 9:47 ` [PATCH 09/10] ASoC: omap-abe-twl6040: Add missing audio route information Peter Ujfalusi
2011-12-14 10:14 ` [alsa-devel] " Mark Brown
2011-12-21 18:26 ` [PATCH 00/10] OMAP4: ASoC: Support for PandaBoard family Liam Girdwood
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=5238231.U46jV2XvpL@barack \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.com \
--cc=tony@atomide.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.