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. -- 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. -- 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. --- 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 email to rtc-linux+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
