From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCHv3 0/9] ARM: OMAP2+: AM33XX: Add suspend-resume support Date: Wed, 4 Sep 2013 08:18:09 -0700 Message-ID: References: <1375811376-49985-1-git-send-email-d-gerlach@ti.com> <5211E3F6.6090108@ti.com> <52125A39.3010008@ti.com> <87vc2qyjao.fsf@linaro.org> <521FBD6B.3020208@ti.com> <87mwo0rvf8.fsf@linaro.org> <52261B34.60206@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-we0-f175.google.com ([74.125.82.175]:49392 "EHLO mail-we0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934783Ab3IDPSK (ORCPT ); Wed, 4 Sep 2013 11:18:10 -0400 Received: by mail-we0-f175.google.com with SMTP id q59so513539wes.34 for ; Wed, 04 Sep 2013 08:18:09 -0700 (PDT) In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Russ Dill Cc: Dave Gerlach , Paul Walmsley , "linux-omap@vger.kernel.org" , Linux ARM Kernel List , Gururaja Hebbar On Wed, Sep 4, 2013 at 8:12 AM, Russ Dill wrote: > On Wed, Sep 4, 2013 at 8:01 AM, Kevin Hilman wrote: >> Hi Dave, >> >>> Thanks for taking the time to try this out, it does seem there are a few >>> kinks with BeagleBone Black but we'll get those worked out. >> >> I also just noticed that wake from RTC isn't working, but wake from >> serial console does. Does RTC wake work for you? (I use rtcwake -m >> mem -s4) >> >> Kevin > > On Beaglebone white or black? White. > For PG 1.0 (Beaglebone white) there is > the following errata: > > "RTC: 32.768-kHZ Clock is Gating Off" > > Details The RTC has a clock gating issue that stops the internal > 32.768-kHz clock when the VDD_CORE voltage domain drops below the > recommended operating range or the PWRONRSTn input terminal is held > low. This issue has the following side effects: > > - The RTC counters stop incrementing when the 32.768-kHz clock is > gated. This causes the RTC to lose time while the clock is gated. > > - A wakeup event applied to the EXT_WAKEUP input terminal is masked if > the EXT_WAKEUP_DB_EN bit in the RTC PMIC register (0x98) is set to 1 > which enables the de-bounce function for the EXT_WAKEUP input. This > occurs because the 32.768-kHz clock is being used to clock the > de-bounce circuit. I'm not using your VDD_CORE scaling series (or maybe the firmware is scaling VDD_CORE?) Anyways, thanks for the info on the errata, that must be what's causing it. Kevin From mboxrd@z Thu Jan 1 00:00:00 1970 From: khilman@linaro.org (Kevin Hilman) Date: Wed, 4 Sep 2013 08:18:09 -0700 Subject: [PATCHv3 0/9] ARM: OMAP2+: AM33XX: Add suspend-resume support In-Reply-To: References: <1375811376-49985-1-git-send-email-d-gerlach@ti.com> <5211E3F6.6090108@ti.com> <52125A39.3010008@ti.com> <87vc2qyjao.fsf@linaro.org> <521FBD6B.3020208@ti.com> <87mwo0rvf8.fsf@linaro.org> <52261B34.60206@ti.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Sep 4, 2013 at 8:12 AM, Russ Dill wrote: > On Wed, Sep 4, 2013 at 8:01 AM, Kevin Hilman wrote: >> Hi Dave, >> >>> Thanks for taking the time to try this out, it does seem there are a few >>> kinks with BeagleBone Black but we'll get those worked out. >> >> I also just noticed that wake from RTC isn't working, but wake from >> serial console does. Does RTC wake work for you? (I use rtcwake -m >> mem -s4) >> >> Kevin > > On Beaglebone white or black? White. > For PG 1.0 (Beaglebone white) there is > the following errata: > > "RTC: 32.768-kHZ Clock is Gating Off" > > Details The RTC has a clock gating issue that stops the internal > 32.768-kHz clock when the VDD_CORE voltage domain drops below the > recommended operating range or the PWRONRSTn input terminal is held > low. This issue has the following side effects: > > - The RTC counters stop incrementing when the 32.768-kHz clock is > gated. This causes the RTC to lose time while the clock is gated. > > - A wakeup event applied to the EXT_WAKEUP input terminal is masked if > the EXT_WAKEUP_DB_EN bit in the RTC PMIC register (0x98) is set to 1 > which enables the de-bounce function for the EXT_WAKEUP input. This > occurs because the 32.768-kHz clock is being used to clock the > de-bounce circuit. I'm not using your VDD_CORE scaling series (or maybe the firmware is scaling VDD_CORE?) Anyways, thanks for the info on the errata, that must be what's causing it. Kevin