From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: keerthy <j-keerthy@ti.com>
Cc: linux-rtc@vger.kernel.org, a.zummo@towertech.it,
alexandre.belloni@bootlin.com, d-gerlach@ti.com,
tony@atomide.com, t-kristo@ti.com, ssantosh@kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] AM437x: Add rtc-only + DDR mode support
Date: Mon, 25 Mar 2019 10:59:20 +0000 [thread overview]
Message-ID: <20190325105920.4se5hjul2srkzre7@shell.armlinux.org.uk> (raw)
In-Reply-To: <1fadeed8-b091-43c8-e7ec-f29ad0fff82c@ti.com>
On Mon, Mar 25, 2019 at 07:13:53AM +0530, keerthy wrote:
>
>
> On 3/23/2019 12:02 AM, Russell King - ARM Linux admin wrote:
> > On Fri, Mar 22, 2019 at 10:46:14PM +0530, Keerthy wrote:
> > > RTC plus DDR in self-refresh is power a saving mode where in the entire
> > "a power" ?
>
> Will correct the above typo.
>
> >
> > > system including the different voltage rails from PMIC are shutdown except
> > > the ones feeding on to RTC and DDR. DDR is kept in self-refresh hence the
>
> As explained above All the voltage rails of PMIC are shut off except for RTC
> and DDR Rails.
You seem to be replying to yourself there - the quote above your reply
there is what you wrote.
>
> > > contents are preserved. RTC ALARM2 is connected to PMIC_EN line once
> > > we the ALARM2 is triggered we enter the mode with DDR in self-refresh
> >
> > Doesn't make sense.
> >
> > > and RTC Ticking. After a predetermined time an RTC ALARM1 triggers waking
> > > up the system.
> >
> > Huh, you start off explaining the wiring above... how does RTC ALARM1
> > trigger waking up the system if RTC ALARM2 is connected to the PMIC
> > and all other power is shut down?
> The entire PMIC is shutdown but for RTC rail. RTC is a separate voltage
> domain and is powered up during this power save mode.
>
> http://www.ti.com/lit/ug/spruhl7h/spruhl7h.pdf Page 2884.
I'm not asking for a reference, I'm asking for your cover letter to
make sense and actually be useful. Right now, it's far from that.
Thanks.
>
> >
> > > The control goes to bootloader. The bootloader then checks
> > > RTC scratchpad registers to confirm it was an rtc_only wakeup and follows
> > > a different path, configure bare minimal clocks for ddr and then jumps to
> > > the resume address in another RTC scratchpad registers and transfers the
> > > control to Kernel. Kernel then restores the saved context.
> > >
> > > The patch series adds rtc-only + DDR mode support am am437x
> > > Tested DS0, rtc+ddr back and forth on am437x-gp-evm board.
> > >
> > > This mode works only with u-boot built with am43xx_evm_rtconly_defconfig
> > >
> > > Additional patch is needed for omap-gpio save restore which will
> > > come as fixes later.
> > >
> > > Keerthy (5):
> > > rtc: OMAP: Add support for rtc-only mode
> > > rtc: interface: Add power_off_program to rtc_class_ops
> > > arm: mach-omap2: pm33xx: Add support for rtc+ddr in self refresh mode
> > > soc: ti: pm33xx: Push the am33xx_push_sram_idle to the top
> > > soc: ti: pm33xx: AM437X: Add rtc_only with ddr in self-refresh support
> > >
> > > arch/arm/mach-omap2/pm33xx-core.c | 76 +++++++-
> > > drivers/rtc/interface.c | 12 ++
> > > drivers/rtc/rtc-omap.c | 49 ++++-
> > > drivers/soc/ti/Kconfig | 5 +-
> > > drivers/soc/ti/pm33xx.c | 272 ++++++++++++++++++++++-----
> > > include/linux/platform_data/pm33xx.h | 5 +
> > > include/linux/rtc.h | 2 +
> > > 7 files changed, 360 insertions(+), 61 deletions(-)
> > >
> > > --
> > > 2.17.1
> > >
> > >
> > > _______________________________________________
> > > linux-arm-kernel mailing list
> > > linux-arm-kernel@lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> > >
> >
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-25 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 17:16 [PATCH 0/5] AM437x: Add rtc-only + DDR mode support Keerthy
2019-03-22 17:16 ` [PATCH 1/5] rtc: OMAP: Add support for rtc-only mode Keerthy
2019-04-01 5:58 ` Keerthy
2019-03-22 17:16 ` [PATCH 2/5] rtc: interface: Add power_off_program to rtc_class_ops Keerthy
2019-03-22 17:16 ` [PATCH 3/5] arm: mach-omap2: pm33xx: Add support for rtc+ddr in self refresh mode Keerthy
2019-04-01 17:52 ` Tony Lindgren
2019-04-01 18:38 ` Andreas Kemnade
2019-04-01 20:40 ` Tony Lindgren
2019-04-04 10:51 ` Andreas Kemnade
2019-04-04 14:11 ` Tony Lindgren
2019-03-22 17:16 ` [PATCH 4/5] soc: ti: pm33xx: Push the am33xx_push_sram_idle to the top Keerthy
2019-03-22 17:16 ` [PATCH 5/5] soc: ti: pm33xx: AM437X: Add rtc_only with ddr in self-refresh support Keerthy
2019-03-22 18:32 ` [PATCH 0/5] AM437x: Add rtc-only + DDR mode support Russell King - ARM Linux admin
2019-03-25 1:43 ` keerthy
2019-03-25 10:59 ` Russell King - ARM Linux admin [this message]
2019-03-26 4:34 ` keerthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190325105920.4se5hjul2srkzre7@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=d-gerlach@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).