On Thu, Oct 30, 2008 at 4:45 AM, Mark Brown [EMAIL PROTECTED] wrote:
On Wed, Oct 22, 2008 at 09:44:48PM +0100, Mark Brown wrote:
On Wed, Oct 22, 2008 at 01:30:26PM -0700, Steve Sakoman wrote:
I am happy to resubmit the patches, if that is what folks want. I'm
copying alsa-devel so they can
* David Brownell [EMAIL PROTECTED] [081022 12:14]:
On Wednesday 22 October 2008, Felipe Contreras wrote:
+
+ printk(KERN_INFO OMAP3 Beagle SoC init\n);
+ if (!machine_is_omap3_beagle()) {
+ printk(KERN_ERR Not OMAP3 Beagle!\n);
+ return -ENODEV;
This is exactly the same as the overo configuration.
Signed-off-by: Felipe Contreras [EMAIL PROTECTED]
---
I'm resending this patch since it hasn't been applied yet.
I have only tested this with alsa-oss emulation.
sound/soc/omap/Kconfig |8 ++
sound/soc/omap/Makefile |2 +
* Felipe Contreras [EMAIL PROTECTED] [081022 09:31]:
This is exactly the same as the overo configuration.
This should go to alsa-devel list with l-o list cc'd. AFAIK, all
the omap ASoC stuff is in mainline already. I will not push it
to l-o until we have an ack from alsa-devel.
Cheers,
Tony
On Wednesday 22 October 2008, Felipe Contreras wrote:
+
+ printk(KERN_INFO OMAP3 Beagle SoC init\n);
+ if (!machine_is_omap3_beagle()) {
+ printk(KERN_ERR Not OMAP3 Beagle!\n);
+ return -ENODEV;
+ }
+
Note that the version I (re)posted fixed
On Wed, Oct 22, 2008 at 12:36 PM, David Brownell [EMAIL PROTECTED] wrote:
On Wednesday 22 October 2008, Tony Lindgren wrote:
This should go to alsa-devel list with l-o list cc'd. AFAIK, all
the omap ASoC stuff is in mainline already. I will not push it
to l-o until we have an ack from
On Wed, Oct 22, 2008 at 01:30:26PM -0700, Steve Sakoman wrote:
At the time, the feedback from the alsa-devel list was that they were
OK with these patches living in linux-omap until the twl4030 driver
was mainline ready.
Indeed. The only blocker was that TWL4030 codec support breaks the
Hi David,
On Fri, 3 Oct 2008, David Brownell wrote:
On Tuesday 16 September 2008, Felipe Contreras wrote:
This is exactly the same as the overo configuration. It might make sense
to have them in a single one.
I got a hard lockup (no timer ticking), no blinkenlights, etc ...
doesn't look
On Monday 06 October 2008, Paul Walmsley wrote:
[ INFO: possible recursive locking detected ]
2.6.27-rc8-omap1 #174
-
aplay/1816 is trying to acquire lock:
(clockfw_lock){}, at: [c0036be4] clk_enable+0x24/0x70
but task is already
On Mon, Oct 06, 2008 at 11:01:53AM -0700, David Brownell wrote:
On Monday 06 October 2008, Paul Walmsley wrote:
[ INFO: possible recursive locking detected ]
2.6.27-rc8-omap1 #174
-
aplay/1816 is trying to acquire lock:
On Tuesday 16 September 2008, Felipe Contreras wrote:
This is exactly the same as the overo configuration. It might make sense
to have them in a single one.
I got a hard lockup (no timer ticking), no blinkenlights, etc ...
doesn't look like the issue is *this* driver.
% aplay dedodedo.wav
On Tue, 16 Sep 2008 23:51:35 +0300
ext Felipe Contreras [EMAIL PROTECTED] wrote:
This is exactly the same as the overo configuration. It might make
sense to have them in a single one.
Signed-off-by: Felipe Contreras [EMAIL PROTECTED]
---
This was suggested by Koen Kooi.
This is exactly the same as the overo configuration. It might make sense
to have them in a single one.
Signed-off-by: Felipe Contreras [EMAIL PROTECTED]
---
This was suggested by Koen Kooi.
sound/soc/omap/Kconfig |8 ++
sound/soc/omap/Makefile |2 +
13 matches
Mail list logo
