On 5/24/2011 8:12 PM, Steve Calfee wrote:
On 05/23/11 20:39, Ricardo Neri wrote:
Hi Steve,
Le mercredi 18 mai 2011 à 12:07 -0500, Steve Calfee a écrit :
On 05/17/11 22:41, Peter Ujfalusi wrote:
On Tuesday 17 May 2011 22:35:09 Steve Calfee wrote:
I think the generally accepted method of
On 05/23/11 20:39, Ricardo Neri wrote:
Hi Steve,
Le mercredi 18 mai 2011 à 12:07 -0500, Steve Calfee a écrit :
On 05/17/11 22:41, Peter Ujfalusi wrote:
On Tuesday 17 May 2011 22:35:09 Steve Calfee wrote:
I think the generally accepted method of doing stuff like this is to
have the
Hi Steve,
Le mercredi 18 mai 2011 à 12:07 -0500, Steve Calfee a écrit :
On 05/17/11 22:41, Peter Ujfalusi wrote:
On Tuesday 17 May 2011 22:35:09 Steve Calfee wrote:
I think the generally accepted method of doing stuff like this is to
have the ifdeffery in a header file where a inline code
On 05/17/11 22:41, Peter Ujfalusi wrote:
On Tuesday 17 May 2011 22:35:09 Steve Calfee wrote:
I think the generally accepted method of doing stuff like this is to
have the ifdeffery in a header file where a inline code segment is
defined if it applies to the processor being built. If the code
On 05/16/11 20:14, Ricardo Neri wrote:
+++ b/arch/arm/mach-omap2/devices.c
@@ -313,6 +313,22 @@ OMAP_MCBSP_PLATFORM_DEVICE(5);
static void omap_init_audio(void)
{
+ struct omap_hwmod *oh_hdmi;
+ struct omap_device *od_hdmi;
+ char *oh_hdmi_name = dss_hdmi;
+ char
On Tuesday 17 May 2011 22:35:09 Steve Calfee wrote:
I think the generally accepted method of doing stuff like this is to
have the ifdeffery in a header file where a inline code segment is
defined if it applies to the processor being built. If the code does not
apply to the model being built, a
Add device for HDMI audio. This device uses hwmod data from
dss_hdmi. This device is to be used by the ASoC HDMI CPU DAI to
obtain base memory address and DMA request number.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
---
arch/arm/mach-omap2/devices.c | 16
1 files
