Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754498Ab3G3QV4 (ORCPT ); Tue, 30 Jul 2013 12:21:56 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:56172 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750895Ab3G3QVz (ORCPT ); Tue, 30 Jul 2013 12:21:55 -0400 Message-ID: <51F7E7FA.3080702@ti.com> Date: Tue, 30 Jul 2013 21:51:14 +0530 From: Sekhar Nori User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Mark Rutland CC: Gururaja Hebbar , "davinci-linux-open-source@linux.davincidsp.com" , "tony@atomide.com" , "benoit.cousson@gmail.com" , "linux-kernel@vger.kernel.org" , "vaibhav.bedia@ti.com" , "benoit.cousson@linaro.org" , "linux-omap@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [Patch V2 4/4] ARM: dts: AM33XX: update rtc node compatibility References: <1372841225-18813-1-git-send-email-gururaja.hebbar@ti.com> <1372841225-18813-5-git-send-email-gururaja.hebbar@ti.com> <51F749B0.7020802@ti.com> <20130730145501.GA29859@e106331-lin.cambridge.arm.com> In-Reply-To: <20130730145501.GA29859@e106331-lin.cambridge.arm.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1972 Lines: 57 On 7/30/2013 8:25 PM, Mark Rutland wrote: > On Tue, Jul 30, 2013 at 06:05:52AM +0100, Gururaja Hebbar wrote: >> Hi, >> >> On 7/3/2013 2:17 PM, Hebbar Gururaja wrote: >>> Since AM33xx RTC IP has RTC_IRQWAKEEN to support Alarm Wake-up. >>> >>> Update the rtc compatible property to "ti,am3352-rtc" to enable handling >>> of this feature inside rtc-omap driver. >> >> The other 2 rtc driver related patches have been pulled up. If you have >> no comments, can you please pull this up. >> >> Regards >> Gururaja >> >>> >>> Signed-off-by: Hebbar Gururaja >>> --- >>> :100644 100644 77aa1b0... dde180a... M arch/arm/boot/dts/am33xx.dtsi >>> arch/arm/boot/dts/am33xx.dtsi | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi >>> index 77aa1b0..dde180a 100644 >>> --- a/arch/arm/boot/dts/am33xx.dtsi >>> +++ b/arch/arm/boot/dts/am33xx.dtsi >>> @@ -297,7 +297,7 @@ >>> }; >>> >>> rtc@44e3e000 { >>> - compatible = "ti,da830-rtc"; >>> + compatible = "ti,am3352-rtc"; > > Given that this is backwards compatible with the old binding, it would > be nicer to have this as: > > compatible = "ti,am3352-rtc", "ti,da830-rtc"; > > We must get into the habit of changing dts files in a > backwards-compatible fashion. Right, I suggested this when v1 was posted. It turns out the current kernel does not handle the compatilble list correctly and the string selected actually depends on the order in which it appears in match table in driver instead. I saw there were patches being discussed to fix this issue, but until that is fixed, we cannot really use what you (and I before) suggested. Thanks, Sekhar -- 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/