On Thursday 07 November 2013 11:07 PM, Daniel Mack wrote:
> Hi Joel,
>
> On 11/07/2013 05:34 PM, Joel Fernandes wrote:
>> Thanks for your followup patch on this. It looks much better now using
>> existing
>> functions to save/restore the state.
>
> Yes, thanks for the suggesting it in the first
On Wednesday 06 November 2013 11:06 PM, Joel Fernandes wrote:
> Hi Vaibhav,
>
> On 10/31/2013 05:25 PM, Vaibhav Bedia wrote:
>> Hi Daniel,
>>
>> On Wed, Oct 30, 2013 at 4:21 PM, Daniel Mack wrote:
>> [...]
>>> +
>>> +static SIMPLE_DEV_PM_OPS(edma_pm_ops, edma_pm_suspend, edma_pm_resume);
>>> +
>>
On Wednesday 09 October 2013 11:33 AM, Fernandes, Joel wrote:
> Some temporary issues with my mua so forgive any artifacts in this email.
>
> On Oct 9, 2013, at 12:14 AM, "Hebbar, Gururaja"
> wrote:
>
>> On Wednesday 09 October 2013 09:58 AM, Joel Fernandes wrote:
>>> On 10/01/2013 10:04 AM, Da
On Wednesday 09 October 2013 09:58 AM, Joel Fernandes wrote:
> On 10/01/2013 10:04 AM, Daniel Mack wrote:
>> This patch makes the edma driver resume correctly after suspend. Tested
>> on an AM33xx platform with cyclic audio streams.
>>
>> The code was shamelessly taken from an ancient BSP tree.
>>
On Tuesday 01 October 2013 07:21 PM, Daniel Mack wrote:
> This patch makes the edma driver resume correctly after suspend. Tested
> on an AM33xx platform with cyclic audio streams.
I believe you have confirmed below are the only registers/fields which
will lose context across suspend/resume
>
>
On 8/20/2013 10:03 PM, Russ Dill wrote:
> On Sun, Aug 18, 2013 at 10:49 PM, Gururaja Hebbar
> wrote:
>>
>> On 8/15/2013 4:04 AM, Russ Dill wrote:
>>> On Wed, Aug 14, 2013 at 3:18 AM, Gururaja Hebbar
>>> wrote:
>>>> On 8/14/2013 3:50 AM, Russ Dil
Hi,
On 8/6/2013 11:19 PM, Dave Gerlach wrote:
> From: Vaibhav Bedia
>
> In preparation for suspend-resume support for AM33XX, add
> the assembly file with the code which is copied to internal
> memory (OCMC RAM) during bootup and runs from there.
>
> As part of the low power entry (DeepSleep0 m
On 8/6/2013 11:19 PM, Dave Gerlach wrote:
> Hi,
>
> This is the third version of the patch series for adding basic suspend-resume
> support for AM33XX, previously submitted by Vaibhav Bedia. This patchset
> is based on 3.11-rc4 and depends on a forthcoming patchset from Suman Anna
> that adds mai
On 8/15/2013 4:04 AM, Russ Dill wrote:
> On Wed, Aug 14, 2013 at 3:18 AM, Gururaja Hebbar
> wrote:
>> On 8/14/2013 3:50 AM, Russ Dill wrote:
>>> Changes since v1:
>>> * Rebased onto new am335x PM branch
>>> * Changed to u
Hi All,
Kindly ignore this series. there is mistake/typo because of which it
will not directly apply. I will resend the patch-set.
sorry for the trouble.
regards
Gururaja
On 8/16/2013 5:06 PM, Hebbar, Gururaja wrote:
> The syntax of compatible property in DT is to mention the Most specific
> ma
On 8/15/2013 4:04 AM, Russ Dill wrote:
> On Wed, Aug 14, 2013 at 3:18 AM, Gururaja Hebbar
> wrote:
>> On 8/14/2013 3:50 AM, Russ Dill wrote:
>>> Changes since v1:
>>> * Rebased onto new am335x PM branch
>>> * Changed to use 5th param register
>>>
On 8/14/2013 3:50 AM, Russ Dill wrote:
> Changes since v1:
> * Rebased onto new am335x PM branch
> * Changed to use 5th param register
>
> Changes since v2:
> * Passes I2C bus speed in kHz to M3 firmware
>
> Changes since v3:
> * Rebased to 3.11-rc3, moves some functionality to wkup_m3.c
> * Addi
On 8/14/2013 3:50 AM, Russ Dill wrote:
> Changes since v1:
> * Rebased onto new am335x PM branch
>
> This adds a sleep and wake sequence to set the VDD core voltage to the
> OPP50 level, 0.950V. This saves power during suspend. The sequences are
> specific to the Beaglebone layout and PMIC, the TP
On 8/2/2013 4:50 PM, Mark Rutland wrote:
On Fri, Aug 02, 2013 at 12:07:36PM +0100, Gururaja Hebbar wrote:
On 8/1/2013 10:35 PM, Mark Rutland wrote:
On Tue, Jul 30, 2013 at 05:21:14PM +0100, Sekhar Nori wrote:
On 7/30/2013 8:25 PM, Mark Rutland wrote:
On Tue, Jul 30, 2013 at 06:05:52AM +0100
On 8/1/2013 10:35 PM, Mark Rutland wrote:
On Tue, Jul 30, 2013 at 05:21:14PM +0100, Sekhar Nori wrote:
On 7/30/2013 8:25 PM, Mark Rutland wrote:
On Tue, Jul 30, 2013 at 06:05:52AM +0100, Gururaja Hebbar wrote:
Hi,
On 7/3/2013 2:17 PM, Hebbar Gururaja wrote:
Since AM33xx RTC IP has
Hi,
On 7/3/2013 2:17 PM, Hebbar Gururaja wrote:
Since AM33xx RTC IP has RTC_IRQWAKEEN to support Alarm Wake-up.
Update the rtc compatible property to "ti,am3352-rtc" to enable handling
of this feature inside rtc-omap driver.
The other 2 rtc driver related patches have been pulled up. If you
Hi Andrew,
On 7/3/2013 2:17 PM, Hebbar Gururaja wrote:
On some platforms (like AM33xx), a special register (RTC_IRQWAKEEN)
is available to enable Alarm Wakeup feature. This register needs to be
properly handled for the rtcwake to work properly.
Platforms using such IP should set "ti,am3352-rtc"
On 10/31/2012 3:34 PM, Felipe Balbi wrote:
Hi,
On Wed, Oct 31, 2012 at 01:58:35PM +0530, Hebbar, Gururaja wrote:
HSMMC IP on AM33xx need a special setting to handle High-speed cards.
Other platforms like TI81xx, OMAP4 may need this as-well. This depends
on the HSMMC IP timing closure done for t
18 matches
Mail list logo
