Re: [Regression?] Removed regulator support in ehci-omap

2011-04-11 Thread Steve Calfee
On 04/11/11 02:32, Dmitry Artamonow wrote: Hi, guys! Can anyone explain why regulator support has been removed from ehci-omap driver in commit 19403165 (usb: host: omap: ehci and ohci simplification)[1]? In 2.6.37/2.6.38 it was enough to apply simple patch[2] adding regulators description

Re: [Regression?] Removed regulator support in ehci-omap

2011-04-25 Thread Steve Calfee
On 04/25/11 09:41, Keshava Munegowda wrote: -Original Message- From: Steve Sakoman [mailto:sako...@gmail.com] Sent: Monday, April 25, 2011 7:46 PM To: Alan Ott Cc: Keshava Munegowda; Dmitry Artamonow; Steve Calfee; Felipe Balbi; linux-...@vger.kernel.org; linux-omap@vger.kernel.org

Re: [Regression?] Removed regulator support in ehci-omap

2011-04-25 Thread Steve Calfee
On 04/25/11 10:23, Steve Calfee wrote: On 04/25/11 09:41, Keshava Munegowda wrote: -Original Message- From: Steve Sakoman [mailto:sako...@gmail.com] Sent: Monday, April 25, 2011 7:46 PM To: Alan Ott Cc: Keshava Munegowda; Dmitry Artamonow; Steve Calfee; Felipe Balbi; linux

Re: [PATCH] mfd: Fix usbhs_enable error handling

2011-04-26 Thread Steve Calfee
am sure I will get nfs working shortly. I am using the 2.6.39-rc4 with your 3 patches. So from the Beagleboard XM perspective it works and you can include my Tested-by: Steve Calfee stevecal...@gmail.com -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body

Re: [PATCH] mfd: Fix usbhs_enable error handling

2011-04-26 Thread Steve Calfee
-by: Steve Calfee stevecal...@gmail.com -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [alsa-devel] [PATCH] ASoC: omap-mcbsp: Remove restrictive checks for cpu type

2011-05-11 Thread Steve Calfee
On 05/11/11 06:55, Sanjeev Premi wrote: Current checks for cpu type were too restrictive leading to failures for other silicons in same family. The problem was found while testing audio playback on AM37x and AM35x processors. But should exist on OMAP36xx as well. Signed-off-by: Sanjeev

Re: beagleboardxm 2.6.39rc4 mcbsp problems.

2011-05-12 Thread Steve Calfee
On 05/12/11 04:01, Peter Ujfalusi wrote: On Thursday 12 May 2011 09:25:55 Jarkko Nikula wrote: Of course for this you need to use omap as a master and codec as a slave. One example for this is sound/soc/omap/omap3pandora.c. static struct omap_board_mux board_mux[] __initdata = { +

Re: beagleboardxm 2.6.39rc4 mcbsp problems.

2011-05-13 Thread Steve Calfee
On Thu, May 12, 2011 at 10:59 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote: On Thursday 12 May 2011 21:43:20 Steve Calfee wrote: Since it is set to 0xF0F, doesn't this set it as master? Sorry, that is correct, McBSP is configured as msater. Also, spelunking the kernel sources, I cannot

Re: beagleboardxm 2.6.39rc4 mcbsp problems.

2011-05-16 Thread Steve Calfee
On 05/16/11 01:54, Peter Ujfalusi wrote: On Saturday 14 May 2011 05:47:33 Steve Calfee wrote: I put in a few debug statements. It appears that my DMA never gets started. I know it can work with a different machine and codec driver, but not mine. I don't see any explicit DMA init, but that must

Re: [PATCH 1/2] OMAP4: HDMI: Add OMAP device for HDMI audio CPU DAI

2011-05-17 Thread Steve Calfee
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

Re: [PATCH 1/2] OMAP4: HDMI: Add OMAP device for HDMI audio CPU DAI

2011-05-18 Thread Steve Calfee
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

Re: beagleboardxm 2.6.39rc4 mcbsp problems.

2011-05-18 Thread Steve Calfee
On 05/17/11 03:42, Peter Ujfalusi wrote: Hi, On Monday 16 May 2011 21:07:40 Steve Calfee wrote: No, they get called. I just don't get the clock on the bclk pin. OK. Could you try to disconnect the CLKX, and FSX lines from OMAP, and see that you have the clocks on the codec side

Re: beagleboardxm 2.6.39rc4 mcbsp problems.

2011-05-18 Thread Steve Calfee
On 05/16/11 23:37, Jarkko Nikula wrote: Hi On Mon, 16 May 2011 11:07:40 -0700 Steve Calfee stevecal...@gmail.com wrote: On 05/16/11 01:54, Peter Ujfalusi wrote: On Saturday 14 May 2011 05:47:33 Steve Calfee wrote: I put in a few debug statements. It appears that my DMA never gets

Re: beagleboardxm 2.6.39rc4 mcbsp problems.

2011-05-19 Thread Steve Calfee
On 05/19/11 04:28, Peter Ujfalusi wrote: ... My codec cannot be set to use only 16 bits per phase. Is there a way to setup the omap so that data is sent to both channels? As you can see above the xphase bit is one saying dual channels. Is this a dma setup problem? I can not find datasheet

Re: beagleboardxm 2.6.39rc4 mcbsp problems.

2011-05-19 Thread Steve Calfee
On 05/18/11 18:06, Steve Calfee wrote: On 05/16/11 23:37, Jarkko Nikula wrote: Did you try to run OMAP as an I2S master like what omap3pandora.c is doing? Missing clock in codec master configuration suggests that reason is in codec side and reversed roles during development makes easier

Re: beagleboardxm 2.6.39rc4 mcbsp problems.

2011-05-20 Thread Steve Calfee
On 05/19/11 23:29, Jarkko Nikula wrote: On Thu, 19 May 2011 17:58:56 -0700 Steve Calfee stevecal...@gmail.com wrote: ... This very likely sounds that in master mode the master clock to McBSP is missing if there is no DMA running. Did you try to use internal 96 MHz from my example or did

Re: [PATCH 1/2] OMAP4: HDMI: Add OMAP device for HDMI audio CPU DAI

2011-05-24 Thread Steve Calfee
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

Re: [RFC][PATCH 3/9] OMAP4460: HWMOD: DO not reset GPIO1 during HWMOD init

2011-05-29 Thread Steve Calfee
On Fri, May 27, 2011 at 12:38 PM, Kevin Hilman khil...@ti.com wrote: Cousson, Benoit b-cous...@ti.com writes: [...] In general we do not want to reset nor idle an IP that was potentially already properly configured by bootloader or early Linux boot code. Actually, the opposite is true.

beagleboard xm alsa in mcbsp3. 2.6.39-rc4

2011-06-09 Thread Steve Calfee
Hi, I have mcbsp1 working on an external codec. I moved the wires to the mcbsp3 pins. The codec is master, using tdm mode. I use the same codec i2s bus, and it gets the same setup (I change the dai-link stuff in my alsa machine driver to use the other omap i2s bus for my tests). If I pull the clk