* Peter Ujfalusi peter.ujfal...@ti.com [140124 00:21]:
Hi Benoit,
OMAP: Put the audio nodes to disabled styate by default and board dts files
should
enable the nodes which is used on the board.
am335x: correct the audio mclk clock. This patch has been marked to go to 3.13
stable
Hi Benoit,
OMAP: Put the audio nodes to disabled styate by default and board dts files
should
enable the nodes which is used on the board.
am335x: correct the audio mclk clock. This patch has been marked to go to 3.13
stable as well.
Regards,
Peter
---
Peter Ujfalusi (9):
ARM: DTS:
* Peter Ujfalusi peter.ujfal...@ti.com [130205 23:25]:
On 02/05/2013 07:40 PM, Tony Lindgren wrote:
For some reason the CONFIG_DEBUG_SECTION_MISMATCH got disabled in my
rolling
kernel config...
At least gcc version 4.3.5 (Debian 4.3.5-4) shows them. What's
the compiler you have?
Hi Tony,
On 02/04/2013 08:52 PM, Tony Lindgren wrote:
Looks like this now adds some new section warnings:
WARNING: vmlinux.o(.text+0x34124): Section mismatch in reference from the
function sdp3430_twl_gpio_setup() to the function
.init.text:omap_twl4030_audio_init()
The function
On Mon, Feb 04, 2013 at 11:52:51AM -0800, Tony Lindgren wrote:
@@ -245,7 +245,7 @@ static int sdp3430_twl_gpio_setup(struct device *dev,
return 0;
}
-static struct twl4030_gpio_platform_data sdp3430_gpio_data = {
+static struct twl4030_gpio_platform_data __initdata sdp3430_gpio_data
* Peter Ujfalusi peter.ujfal...@ti.com [130205 01:49]:
Hi Tony,
On 02/04/2013 08:52 PM, Tony Lindgren wrote:
Looks like this now adds some new section warnings:
WARNING: vmlinux.o(.text+0x34124): Section mismatch in reference from the
function sdp3430_twl_gpio_setup() to the function
* Russell King - ARM Linux li...@arm.linux.org.uk [130205 04:34]:
On Mon, Feb 04, 2013 at 11:52:51AM -0800, Tony Lindgren wrote:
@@ -245,7 +245,7 @@ static int sdp3430_twl_gpio_setup(struct device *dev,
return 0;
}
-static struct twl4030_gpio_platform_data sdp3430_gpio_data = {
On 02/05/2013 07:40 PM, Tony Lindgren wrote:
For some reason the CONFIG_DEBUG_SECTION_MISMATCH got disabled in my rolling
kernel config...
At least gcc version 4.3.5 (Debian 4.3.5-4) shows them. What's
the compiler you have?
It show for me as well now that I have enabled the
* Tony Lindgren t...@atomide.com [130130 14:09]:
* Peter Ujfalusi peter.ujfal...@ti.com [130129 00:34]:
Hi Tony,
On 01/22/2013 11:07 AM, Peter Ujfalusi wrote:
Hi Tony,
The content of this pull:
update for audio support via omap-twl4030 and pwm updates in board level:
* Peter Ujfalusi peter.ujfal...@ti.com [130129 00:34]:
Hi Tony,
On 01/22/2013 11:07 AM, Peter Ujfalusi wrote:
Hi Tony,
The content of this pull:
update for audio support via omap-twl4030 and pwm updates in board level:
http://www.spinics.net/lists/linux-omap/msg85085.html
-rc4 (2013-01-17 19:25:45 -0800)
are available in the git repository at:
git://gitorious.org/omap-audio/linux-audio.git peter/for-tony
for you to fetch changes up to e4f4e8bfa47431b91fbb21dd9b86d9bc2c15cbd7:
ARM: board-zoom: Do not request LCD panel enable GPIO from twl4030
(2013
of mainline v3.8-rc4 tag.
Regards,
Péter
---
The following changes since commit 7d1f9aeff1ee4a20b1aeb377dd0f579fe9647619:
Linux 3.8-rc4 (2013-01-17 19:25:45 -0800)
are available in the git repository at:
git://gitorious.org/omap-audio/linux-audio.git peter/for-tony
for you to fetch changes up
Hi,
I have combined the two previous series for easier handling.
audio via omap-twl4030 for Zoom2 and sdp3430:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/139128.html
PWM support for few boards:
Hi Peter,
On 08/29/2012 03:30 PM, Peter Ujfalusi wrote:
Hello,
I have extended and rebased the previous set:
'ARM/dts: omap McBSP and audio support for BeagleBoard'
Changes since v1:
- Rebased on current l-o:devel-dt branch
- Two new patch, one for OMAP4 to add reg-names for the mem
Hello,
I have extended and rebased the previous set:
'ARM/dts: omap McBSP and audio support for BeagleBoard'
Changes since v1:
- Rebased on current l-o:devel-dt branch
- Two new patch, one for OMAP4 to add reg-names for the mem areas, one for OMAP5
to add McPDM and DMIC section
The rest of
Gary Thomas:
I don't think it matters. The real problem is how to get 24 bits
of data aligned to the right place in the 32 bit frame. TRM implies
that the hardware can do this, I've just not figured out the magic...
Hi,
I asked a colleague, who worked on OMAP3 McBSP silicon validation. She
On Wednesday 17 February 2010 09:03:39 ext Jarkko Nikula wrote:
On Tue, 16 Feb 2010 11:19:25 -0700
Gary Thomas g...@mlbassoc.com wrote:
I need to connect the OMAP (3530) to a 24bit CODEC. So far
my attempts at getting this to go have not gone well. Then
I ran across this comment in
On 02/17/2010 03:26 AM, Peter Ujfalusi wrote:
On Wednesday 17 February 2010 09:03:39 ext Jarkko Nikula wrote:
On Tue, 16 Feb 2010 11:19:25 -0700
Gary Thomasg...@mlbassoc.com wrote:
I need to connect the OMAP (3530) to a 24bit CODEC. So far
my attempts at getting this to go have not gone
On 02/17/2010 04:17 AM, Peter Ujfalusi wrote:
On Wednesday 17 February 2010 12:43:56 ext Gary Thomas wrote:
On 02/17/2010 03:26 AM, Peter Ujfalusi wrote:
On Wednesday 17 February 2010 09:03:39 ext Jarkko Nikula wrote:
On Tue, 16 Feb 2010 11:19:25 -0700
Gary Thomasg...@mlbassoc.com wrote:
On Wed, 17 Feb 2010 05:01:53 -0700
Gary Thomas g...@mlbassoc.com wrote:
After looking at the TRM of OMAP, the sDMA has support for 8, 16 and 32 bit
data
types. So I'm not really sure how to configure McBSP and sDMA in case of 24
bit
packed format.
I would go with a trial and error
On 02/17/2010 10:45 AM, Jarkko Nikula wrote:
On Wed, 17 Feb 2010 05:01:53 -0700
Gary Thomasg...@mlbassoc.com wrote:
After looking at the TRM of OMAP, the sDMA has support for 8, 16 and 32 bit data
types. So I'm not really sure how to configure McBSP and sDMA in case of 24 bit
packed format.
I
On Wed, Feb 17, 2010 at 10:51:11AM -0700, Gary Thomas wrote:
Thanks. I'd really like to understand how to set things up to generate
the data I see in TRM:
Figure 21-11 shows an example with 24 bits data (MSB first) and 8 padding
bits at ?0?.
This matches my CODEC. Any clues?
Does your
On 02/17/2010 10:56 AM, Mark Brown wrote:
On Wed, Feb 17, 2010 at 10:51:11AM -0700, Gary Thomas wrote:
Thanks. I'd really like to understand how to set things up to generate
the data I see in TRM:
Figure 21-11 shows an example with 24 bits data (MSB first) and 8 padding
bits at ?0?.
This
I need to connect the OMAP (3530) to a 24bit CODEC. So far
my attempts at getting this to go have not gone well. Then
I ran across this comment in sound/soc/omap/omap-pcm.c:
/*
* Note: Regardless of interface data formats supported by OMAP McBSP
* or EAC blocks,
On Tue, 16 Feb 2010 11:19:25 -0700
Gary Thomas g...@mlbassoc.com wrote:
I need to connect the OMAP (3530) to a 24bit CODEC. So far
my attempts at getting this to go have not gone well. Then
I ran across this comment in sound/soc/omap/omap-pcm.c:
/*
* Note: Regardless of
25 matches
Mail list logo
