From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: rtc-linux@googlegroups.com Received: from mail.free-electrons.com (mail.free-electrons.com. [62.4.15.54]) by gmr-mx.google.com with ESMTP id v70si894498wmf.0.2017.02.20.09.36.43 for ; Mon, 20 Feb 2017 09:36:43 -0800 (PST) From: Gregory CLEMENT To: Russell King - ARM Linux Cc: Alessandro Zummo , Thomas Petazzoni , Andrew Lunn , Jason Cooper , rtc-linux@googlegroups.com, Haim Boot , Alexandre Belloni , linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth Subject: [rtc-linux] Re: [PATCH v2 0/3] Extend rtc-armada38x support for Armada 7K/8K References: <20170217101907.8963-1-gregory.clement@free-electrons.com> <87tw7oaj24.fsf@free-electrons.com> <20170220172739.GN21222@n2100.armlinux.org.uk> Date: Mon, 20 Feb 2017 18:36:33 +0100 In-Reply-To: <20170220172739.GN21222@n2100.armlinux.org.uk> (Russell King's message of "Mon, 20 Feb 2017 17:27:39 +0000") Message-ID: <87mvdgahni.fsf@free-electrons.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Hi Russell King, =20 On lun., f=C3=A9vr. 20 2017, Russell King - ARM Linux wrote: > On Mon, Feb 20, 2017 at 06:06:11PM +0100, Gregory CLEMENT wrote: >> I saw on IRC than Russell managed to have a more coherent date with this >> series on his 8040 based board. For the record, as the U-Boot on this >> board didn't provide a "date reset" command for the RTC located on CP >> slave, then Russell needed to do the following: >>=20 >> devmem2 0xf428401c w 0 >> devmem2 0xf4284018 w 0x2000 >> followed by: >> date 021612342017; ntpdate ...; hwclock -uw >>=20 >> But this issue was related to the bootloader not to the kernel. The >> other potential issue seen by Russell was about the GIC mapping for the >> interrupt, but here again this mapping was done by the 1st stage >> bootloader. >>=20 >> Given this information would it be OK to applied this series? > > No it is not. As I already pointed out, the interrupt for the 8040 is > GIC_SPI 71 _not_ GIC_SPI 77 as you have it in this series. > > Both CP110's on Armada 8040 have a default mapping of ICU 77 to GIC > 71. OK so I am sending a v2 with this fix. Thanks, Gregory > > --=20 > RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ > FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up > according to speedtest.net. --=20 Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com --=20 You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. ---=20 You received this message because you are subscribed to the Google Groups "= rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to rtc-linux+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout. From mboxrd@z Thu Jan 1 00:00:00 1970 From: gregory.clement@free-electrons.com (Gregory CLEMENT) Date: Mon, 20 Feb 2017 18:36:33 +0100 Subject: [PATCH v2 0/3] Extend rtc-armada38x support for Armada 7K/8K In-Reply-To: <20170220172739.GN21222@n2100.armlinux.org.uk> (Russell King's message of "Mon, 20 Feb 2017 17:27:39 +0000") References: <20170217101907.8963-1-gregory.clement@free-electrons.com> <87tw7oaj24.fsf@free-electrons.com> <20170220172739.GN21222@n2100.armlinux.org.uk> Message-ID: <87mvdgahni.fsf@free-electrons.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Russell King, On lun., f?vr. 20 2017, Russell King - ARM Linux wrote: > On Mon, Feb 20, 2017 at 06:06:11PM +0100, Gregory CLEMENT wrote: >> I saw on IRC than Russell managed to have a more coherent date with this >> series on his 8040 based board. For the record, as the U-Boot on this >> board didn't provide a "date reset" command for the RTC located on CP >> slave, then Russell needed to do the following: >> >> devmem2 0xf428401c w 0 >> devmem2 0xf4284018 w 0x2000 >> followed by: >> date 021612342017; ntpdate ...; hwclock -uw >> >> But this issue was related to the bootloader not to the kernel. The >> other potential issue seen by Russell was about the GIC mapping for the >> interrupt, but here again this mapping was done by the 1st stage >> bootloader. >> >> Given this information would it be OK to applied this series? > > No it is not. As I already pointed out, the interrupt for the 8040 is > GIC_SPI 71 _not_ GIC_SPI 77 as you have it in this series. > > Both CP110's on Armada 8040 have a default mapping of ICU 77 to GIC > 71. OK so I am sending a v2 with this fix. Thanks, Gregory > > -- > RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ > FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up > according to speedtest.net. -- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com