From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932694AbcAHSdF (ORCPT ); Fri, 8 Jan 2016 13:33:05 -0500 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.220]:29924 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754140AbcAHSdC convert rfc822-to-8bit (ORCPT ); Fri, 8 Jan 2016 13:33:02 -0500 X-RZG-AUTH: :JGIXVUS7cutRB/49FwqZ7WcKdUCnXG6JabOfSXKWrat+hdPnz40= X-RZG-CLASS-ID: mo00 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [PATCH 1/3] ARM: dts: omap5-board-common: enable rtc and charging of backup battery From: "H. Nikolaus Schaller" In-Reply-To: <20160108181551.GX12777@atomide.com> Date: Fri, 8 Jan 2016 19:32:54 +0100 Cc: Laxman Dewangan , Nishanth Menon , =?iso-8859-1?Q?Beno=EEt_Cousson?= , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , linux-omap , devicetree@vger.kernel.org, LKML , Marek Belisko Content-Transfer-Encoding: 8BIT Message-Id: <832803EE-E4CB-46B1-BF39-2DC0BB695A5D@goldelico.com> References: <568C5451.8070709@ti.com> <20160106010011.GG12777@atomide.com> <8FE6954B-6411-4593-9CE5-717A469A6AA8@goldelico.com> <20160106164136.GI12777@atomide.com> <2AC46952-3758-458A-B0A5-1794C207BD4C@goldelico.com> <20160106170925.GK12777@atomide.com> <66F37918-EA7F-4D83-8B5F-A6B5C0CD7623@goldelico.com> <20160108181551.GX12777@atomide.com> To: Tony Lindgren X-Mailer: Apple Mail (2.1878.6) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 08.01.2016 um 19:15 schrieb Tony Lindgren : > * H. Nikolaus Schaller [160108 09:50]: >> Tony, >> it is strange. It now works under unknown conditions - without any obvoius change. >> >> Am 06.01.2016 um 18:09 schrieb Tony Lindgren : >>> >>> OK. It could be also some .config change with something built-in? >> >> I have compared /proc/config.gz from both systems and /sys/firmware/fdt >> with no significant and obvious change. >> >> Then I booted the 4.4-rc8 again and this time it worked. >> >> To verify, I have checked out linux-next this morning, cherry-picked this palmas >> rtc patch, compiled with omap2plus defconfig, and used the omap5-uevm.dtb. And >> hwclock works after doing a modprobe rtc_palmas. > > Weird. No luck here with current linux next or anything. > >> Then I did the same with official v4.4-rc8 and hwclock hangs. And now our >> 4.4-rc8 production kernel hangs again as well. Even if I use the >> DTB from the 4.3 kernel. > > I'm not seeing the RTC second increase in u-boot either, this > should show it: > > # i2c md 0x48 0x100 > > Of course the rtc may not be enabled in u-boot unlike for x15. > >> So I think it is something which is unstable in 4.4-rc8 that is (probably) fixed in >> linux-next and unrelated to this DT patch. >> >> But I have no hint or idea what it is. > > Or something hangs the RTC? And the back-up battery has to drain to > reset the RTC somehow? Indeed it could be something like this. I already suspected that it depends on boot order of some components. But you get the /dev/rtc and /sys/class/rtc nodes? This is what this patch should enable (and not fix potential driver issues). BR, Nikolaus From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Nikolaus Schaller" Subject: Re: [PATCH 1/3] ARM: dts: omap5-board-common: enable rtc and charging of backup battery Date: Fri, 8 Jan 2016 19:32:54 +0100 Message-ID: <832803EE-E4CB-46B1-BF39-2DC0BB695A5D@goldelico.com> References: <568C5451.8070709@ti.com> <20160106010011.GG12777@atomide.com> <8FE6954B-6411-4593-9CE5-717A469A6AA8@goldelico.com> <20160106164136.GI12777@atomide.com> <2AC46952-3758-458A-B0A5-1794C207BD4C@goldelico.com> <20160106170925.GK12777@atomide.com> <66F37918-EA7F-4D83-8B5F-A6B5C0CD7623@goldelico.com> <20160108181551.GX12777@atomide.com> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <20160108181551.GX12777-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Tony Lindgren Cc: Laxman Dewangan , Nishanth Menon , =?iso-8859-1?Q?Beno=EEt_Cousson?= , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , linux-omap , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, LKML , Marek Belisko List-Id: devicetree@vger.kernel.org Am 08.01.2016 um 19:15 schrieb Tony Lindgren : > * H. Nikolaus Schaller [160108 09:50]: >> Tony, >> it is strange. It now works under unknown conditions - without any obvoius change. >> >> Am 06.01.2016 um 18:09 schrieb Tony Lindgren : >>> >>> OK. It could be also some .config change with something built-in? >> >> I have compared /proc/config.gz from both systems and /sys/firmware/fdt >> with no significant and obvious change. >> >> Then I booted the 4.4-rc8 again and this time it worked. >> >> To verify, I have checked out linux-next this morning, cherry-picked this palmas >> rtc patch, compiled with omap2plus defconfig, and used the omap5-uevm.dtb. And >> hwclock works after doing a modprobe rtc_palmas. > > Weird. No luck here with current linux next or anything. > >> Then I did the same with official v4.4-rc8 and hwclock hangs. And now our >> 4.4-rc8 production kernel hangs again as well. Even if I use the >> DTB from the 4.3 kernel. > > I'm not seeing the RTC second increase in u-boot either, this > should show it: > > # i2c md 0x48 0x100 > > Of course the rtc may not be enabled in u-boot unlike for x15. > >> So I think it is something which is unstable in 4.4-rc8 that is (probably) fixed in >> linux-next and unrelated to this DT patch. >> >> But I have no hint or idea what it is. > > Or something hangs the RTC? And the back-up battery has to drain to > reset the RTC somehow? Indeed it could be something like this. I already suspected that it depends on boot order of some components. But you get the /dev/rtc and /sys/class/rtc nodes? This is what this patch should enable (and not fix potential driver issues). BR, Nikolaus -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html