Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753552AbaJVQpI (ORCPT ); Wed, 22 Oct 2014 12:45:08 -0400 Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:28028 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750930AbaJVQpF (ORCPT ); Wed, 22 Oct 2014 12:45:05 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 104.193.169.186 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/go2WisEh8PyIAzeYdGp4y Date: Wed, 22 Oct 2014 09:43:26 -0700 From: Tony Lindgren To: Johan Hovold Cc: Felipe Balbi , Alessandro Zummo , =?utf-8?Q?Beno=C3=AEt?= Cousson , Andrew Morton , Lokesh Vutla , Guenter Roeck , nsekhar@ti.com, t-kristo@ti.com, j-keerthy@ti.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/12] rtc: omap: fixes and power-off feature Message-ID: <20141022164326.GJ2542@atomide.com> References: <1412881594-25678-1-git-send-email-johan@kernel.org> <20141010175409.GL31348@saruman> <20141011093819.GA18988@localhost> <20141011190817.GA20644@atomide.com> <20141022110758.GO2113@localhost> <20141022152956.GI2542@atomide.com> <20141022162104.GB2381@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141022162104.GB2381@localhost> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Johan Hovold [141022 09:25]: > On Wed, Oct 22, 2014 at 08:29:56AM -0700, Tony Lindgren wrote: > > * Johan Hovold [141022 04:12]: > > > On Sat, Oct 11, 2014 at 12:08:18PM -0700, Tony Lindgren wrote: > > > > * Johan Hovold [141011 02:42]: > > > > > On Fri, Oct 10, 2014 at 12:54:22PM -0500, Felipe Balbi wrote: > > > > > > > > > > > > is this power-off feature "RTC-only mode" ? > > > > > > > > > > Yes, I believe so, at least as long as RTC power is maintained. The > > > > > pmic_power_en pin can otherwise still be used to power off. > > > > > > > > > > On the BeagleBone the PMIC can be configured to enter OFF or SLEEP mode > > > > > on power off, where the latter (and default) mode keeps the RTC power > > > > > supply enabled. > > > > > > > > > > Thanks for the fast review, Felipe. > > > > > > > > Great :) I assume adding the regulator support to this driver should > > > > also help in the 35xx case? > > > > > > If I remember correctly both OMAP and Sitara 35xx have no on-chip RTC so > > > they won't be using this driver. > > > > Sorry I made a typo.. I meanto to ask if adding the regulator > > helps in your 335x case (not 35xx case)? > > Ah, sorry, that's what I first read before I noticed you wrote "35xx" > twice. :) Yes sorry my nerves are doing things on their own for some stuff it seems like :) > Yes, RTC power can be configured as a regulator on am33xx (e.g. provided > by LDO1 of the PMIC on BBB). I guess you would still need to configure > it as always-on to be able to use the RTC-only mode, though. OK great. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/