RE: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-12-24 Thread Aggarwal, Anuj
: RE: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix Looking at the very original patch, I don't know how things could get into deep sleep by disabling the fclk only... need to disable the iclk also. In threshold mode, HW autogates the iclk, so you may be just lucky

RE: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-11-30 Thread Aggarwal, Anuj
Looking at the very original patch, I don't know how things could get into deep sleep by disabling the fclk only... need to disable the iclk also. In threshold mode, HW autogates the iclk, so you may be just lucky. [Anuj] No, I am not :(. I had to modify the original patch to include the

Re: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-11-20 Thread Jarkko Nikula
On Fri, 20 Nov 2009 09:51:13 +0200 Peter Ujfalusi peter.ujfal...@nokia.com wrote: My question is: is sysfs the only way to choose threshold or can it be made as default? I could not see that happening in the code so thinking of the possible reason of choosing not to do so. Because the

Re: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-11-20 Thread Eero Nurkkala
On Fri, 2009-11-20 at 14:53 +0100, ext Jarkko Nikula wrote: On Fri, 20 Nov 2009 09:51:13 +0200 Peter Ujfalusi peter.ujfal...@nokia.com wrote: My question is: is sysfs the only way to choose threshold or can it be made as default? I could not see that happening in the code so

Re: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-11-20 Thread Anuj Aggarwal
On Fri, Nov 20, 2009 at 7:39 PM, Eero Nurkkala ext-eero.nurkk...@nokia.com wrote: On Fri, 2009-11-20 at 14:53 +0100, ext Jarkko Nikula wrote: On Fri, 20 Nov 2009 09:51:13 +0200 Peter Ujfalusi peter.ujfal...@nokia.com wrote: My question is: is sysfs the only way to choose threshold or can it

Re: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-11-19 Thread Anuj Aggarwal
On Thu, Nov 19, 2009 at 1:04 PM, Jarkko Nikula jhnik...@gmail.com wrote: On Wed, Nov 18, 2009 at 8:28 PM, Aggarwal, Anuj anuj.aggar...@ti.comwrote: If no API or feature would require active McBSP block before the omap_mcbsp_start call, then the clock management could be done inside the

Re: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-11-19 Thread Peter Ujfalusi
On Thursday 19 November 2009 21:48:26 ext Anuj Aggarwal wrote: [Anuj] Yes, w/o audio, it goes into suspend neatly. After going through the entire patch series [PATCHv5 00/20] OMAP ASoC changes in DMA utilization, which I missed earlier, I found that the sysfs entry dma_op_mode can be toggled

RE: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-11-13 Thread Wang, Jane
, Jane Subject: Re: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix On 13 Nov 2009, at 17:39, Jane Wang jw...@ti.com wrote: McBSP fucntional clock is not disabled when suspend is triggerd which prevents PER domain entering target low-power state. To fix the problem: 1

Re: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix

2009-11-13 Thread Mark Brown
; linux-omap@vger.kernel.org; peter.ujfal...@nokia.com; Wang, Jane Subject: Re: [alsa-devel] [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix On 13 Nov 2009, at 17:39, Jane Wang jw...@ti.com wrote: McBSP fucntional clock is not disabled when suspend is triggerd which prevents PER domain