Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753238AbbBYLIW (ORCPT ); Wed, 25 Feb 2015 06:08:22 -0500 Received: from mail-we0-f172.google.com ([74.125.82.172]:38883 "EHLO mail-we0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752646AbbBYLIU (ORCPT ); Wed, 25 Feb 2015 06:08:20 -0500 Date: Wed, 25 Feb 2015 11:08:09 +0000 From: Lee Jones To: Peter Griffin Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, kernel@stlinux.com, rtc-linux@googlegroups.com, wim@iguana.be, linux@roeck-us.net, linux-watchdog@vger.kernel.org Subject: Re: [STLinux Kernel] [PATCH v3 7/8] rtc: st: add new driver for ST's LPC RTC Message-ID: <20150225110809.GH21323@x1> References: <1424260154-12868-1-git-send-email-lee.jones@linaro.org> <1424260154-12868-8-git-send-email-lee.jones@linaro.org> <20150223101223.GA14142@griffinp-ThinkPad-X1-Carbon-2nd> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150223101223.GA14142@griffinp-ThinkPad-X1-Carbon-2nd> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1849 Lines: 56 On Mon, 23 Feb 2015, Peter Griffin wrote: > On Wed, 18 Feb 2015, Lee Jones wrote: > > > ST's Low Power Controller (LPC) controls two devices; watchdog and RTC. > > Only one of the devices can be used at any one time. This is enforced > > by the correlating MFD driver. This portion of the driver-set controls > > the Real Time Clock. > > > > > +{ > > + unsigned long flags; > > + > > + spin_lock_irqsave(&rtc->lock, flags); > > + > > + writel(1, rtc->ioaddr + LPC_WDT_OFF); > > + > > + writel(msb, rtc->ioaddr + LPC_LPA_MSB_OFF); > > + writel(lsb, rtc->ioaddr + LPC_LPA_LSB_OFF); > > + writel(1, rtc->ioaddr + LPC_LPA_START_OFF); > > + > > + writel(0, rtc->ioaddr + LPC_WDT_OFF); > > I think all the writel IO accessors in this driver can be replaced > with the *_relaxed variant. This will avoid the overhead of taking a > spinlock in the l2 outer cache part of writel. Yes, there is no technical reason why we can't use the relaxed variants. Will fix. > > +#ifdef CONFIG_PM_SLEEP > > +static int st_rtc_suspend(struct device *dev) > > +{ > > + struct st_rtc *rtc = dev_get_drvdata(dev); > > + > > + if (device_may_wakeup(dev)) > > + return 0; > > + > > + writel(1, rtc->ioaddr + LPC_WDT_OFF); > > + writel(0, rtc->ioaddr + LPC_LPA_START_OFF); > > + writel(0, rtc->ioaddr + LPC_WDT_OFF); > > Is there a reason for not disabling the IP clock in suspend / resume functions? There is. It will stop the alarm timer, which is undesirable. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- 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/