Skip to contentSkip to conversation

DaVinci ASoC updates

PATCH Applied David Brownell 3 participants 7 messages May 14, 2009 – May 15, 2009

lore
Share & tools
lore
#0 lore raw

cover DaVinci ASoC updates

The 2.6.30-rc5 merges included a bunch of DaVinci platform updates, including EDMA support. Which means that finally the ASoC stuff can be made to build in mainline ... it was probably sent to mainline before its time. ;)

Following are three patches which resync mainline ASoC code with what's in the DaVinci tree. I'd like to suggest they all merge before 2.6.30-final ... two are build fixes, and the third is needed to make it work.

(I'm cc'ing all interested parties -- except alsa-devel, which is members-only -- on this note, but will only cc the DaVinci list on the three patches.)

#1 lore raw

At Thu, 14 May 2009 12:35:35 -0700,

Quoted 10 lines · David Brownell

The 2.6.30-rc5 merges included a bunch of DaVinci platform updates, including EDMA support. Which means that finally the ASoC stuff can be made to build in mainline ... it was probably sent to mainline before its time. ;)

Following are three patches which resync mainline ASoC code with what's in the DaVinci tree. I'd like to suggest they all merge before 2.6.30-final ... two are build fixes, and the third is needed to make it work.

The patches haven't been sent yet?

thanks,

Takashi

#2 lore raw
Quoted 8 lines · Takashi Iwai

At Thu, 14 May 2009 12:35:35 -0700,

Quoted 6 lines · David Brownell

The 2.6.30-rc5 merges included a bunch of DaVinci platform updates, including EDMA support. Which means that finally the ASoC stuff can be made to build in mainline ... it was probably sent to mainline before its time. ;)

Quoted 6 lines
Quoted 4 lines

Following are three patches which resync mainline ASoC code with what's in the DaVinci tree. I'd like to suggest they all merge before 2.6.30-final ... two are build fixes, and the third is needed to make it work.

The patches haven't been sent yet?

I just cc'd Mark and Liam, maintainers of the ASoC stuff, and the DaVinci list ...

http://linux.omap.com/pipermail/davinci-linux-open-source/2009-May/013339.html
http://linux.omap.com/pipermail/davinci-linux-open-source/2009-May/013338.html
http://linux.omap.com/pipermail/davinci-linux-open-source/2009-May/013340.html

If you want to merge them I'll forward those to you.

Applied
#3 lore raw
Quoted 1 line · David Brownell

If you want to merge them I'll forward those to you.

I've applied them all, a pull request will be going to Takashi in the next couple of minutes.

#4 lore raw

At Fri, 15 May 2009 09:22:27 +0100,

Quoted 7 lines · Mark Brown
Quoted 1 line · David Brownell

If you want to merge them I'll forward those to you.

I've applied them all, a pull request will be going to Takashi in the next couple of minutes.

Thanks. I'm going to send a pull request to Linus today later together with other fixes.

Takashi

#5 lore raw
In reply to David Brownell
Quoted 4 lines · David Brownell

The 2.6.30-rc5 merges included a bunch of DaVinci platform updates, including EDMA support. Which means that finally the ASoC stuff can be made to build in mainline ... it was probably sent to mainline before its time. ;)

I've applied all three patches. Obviously they should all have been merged much earlier but given that the code didn't even build there's no risk of making the situation worse and they look fine.

Quoted 3 lines

(I'm cc'ing all interested parties -- except alsa-devel, which is members-only -- on this note, but will only cc the DaVinci list on the three patches.)

In future I'd suggest not sending the cover letter to more recipients than the actual patches, it just creates confusion.

#6 lore raw
Quoted 8 lines · Mark Brown
Quoted 4 lines · David Brownell

The 2.6.30-rc5 merges included a bunch of DaVinci platform updates, including EDMA support. Which means that finally the ASoC stuff can be made to build in mainline ... it was probably sent to mainline before its time. ;)

I've applied all three patches.

Thanks.

Quoted 3 lines

Obviously they should all have been
merged much earlier but given that the code didn't even build there's no risk of making the situation worse and they look fine.

Yeah; I'm glad those updates managed to get into RC5. Until they did, there wasn't much point in sending what would likely have been an incomplete synch.