[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141015165452.GB15770@saruman>
Date: Wed, 15 Oct 2014 11:55:02 -0500
From: Felipe Balbi <balbi@...com>
To: Johan Hovold <johan@...nel.org>
CC: Alessandro Zummo <a.zummo@...ertech.it>,
Tony Lindgren <tony@...mide.com>,
BenoƮt Cousson <bcousson@...libre.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Felipe Balbi <balbi@...com>, Lokesh Vutla <lokeshvutla@...com>,
Guenter Roeck <linux@...ck-us.net>,
Colin Foe-Parker <colin.foeparker@...icpd.com>,
<nsekhar@...com>, <t-kristo@...com>, <j-keerthy@...com>,
<linux-omap@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <rtc-linux@...glegroups.com>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/12] rtc: omap: fixes and power-off feature
Hi,
On Thu, Oct 09, 2014 at 09:06:22PM +0200, Johan Hovold wrote:
> This series fixes a few issues with the omap rtc-driver, cleans up a bit
> and finally adds support for the PMIC control feature found in some
> revisions of this RTC IP block.
>
> Ultimately, this allows for powering off the Beaglebone and waking it up
> again on RTC alarms.
>
> I noticed yesterday that Lokesh Vutla recently posted some patches to
> add regulator support to this driver. [1] While that series has some
> issues that needs to be addressed, I still think it could be a good idea
> to rebase my pmic_power_en patch on top of it as it adds some long
> overdue device abstraction. That would be needed anyway in order to
> support the new power-off infrastructure that's in the pipe in a clean
> way. [2]
>
> So my suggestion is to merge the first seven patches, rebase Lokesh
> series on top of that, and then I rebase my final five patches on top
> of that in turn. Hopefully, the new power-off handler call chain will
> have stabilised by then.
BTW, how do you test this series ?
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists