linux-kernel - Re: [RESEND PATCH 00/10] ARM: davinci: use the new clocksource driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 8 Aug 2019 09:41:11 +0200
From:   Bartosz Golaszewski <brgl@...ev.pl>
To:     Sekhar Nori <nsekhar@...com>
Cc:     Kevin Hilman <khilman@...nel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [RESEND PATCH 00/10] ARM: davinci: use the new clocksource driver

śr., 7 sie 2019 o 21:28 Sekhar Nori <nsekhar@...com> napisał(a):
>
> On 05/08/19 1:59 PM, Bartosz Golaszewski wrote:
> > pon., 22 lip 2019 o 15:17 Bartosz Golaszewski <brgl@...ev.pl> napisał(a):
> >>
> >> From: Bartosz Golaszewski <bgolaszewski@...libre.com>
> >>
> >> Sekhar,
> >>
> >> the following patches switch DaVinci to using the new clocksource driver which
> >> is now upstream. They are rebased on top of v5.3-rc1. Additionally the
> >> following two patches were reverted locally due to a regression in v5.3-rc1
> >> about which the relevant maintainers have been already notified:
> >>
> >>   2eef1399a866 modules: fix BUG when load module with rodata=n
> >>   93651f80dcb6 modules: fix compile error if don't have strict module rwx
> >>
> >> Bartosz Golaszewski (10):
> >>   ARM: davinci: enable the clocksource driver for DT mode
> >>   ARM: davinci: WARN_ON() if clk_get() fails
> >>   ARM: davinci: da850: switch to using the clocksource driver
> >>   ARM: davinci: da830: switch to using the clocksource driver
> >>   ARM: davinci: move timer definitions to davinci.h
> >>   ARM: davinci: dm355: switch to using the clocksource driver
> >>   ARM: davinci: dm365: switch to using the clocksource driver
> >>   ARM: davinci: dm644x: switch to using the clocksource driver
> >>   ARM: davinci: dm646x: switch to using the clocksource driver
> >>   ARM: davinci: remove legacy timer support
> >>
> >>  arch/arm/Kconfig                            |   1 +
> >>  arch/arm/mach-davinci/Makefile              |   3 +-
> >>  arch/arm/mach-davinci/da830.c               |  45 +--
> >>  arch/arm/mach-davinci/da850.c               |  50 +--
> >>  arch/arm/mach-davinci/davinci.h             |   3 +
> >>  arch/arm/mach-davinci/devices-da8xx.c       |   1 -
> >>  arch/arm/mach-davinci/devices.c             |  19 -
> >>  arch/arm/mach-davinci/dm355.c               |  28 +-
> >>  arch/arm/mach-davinci/dm365.c               |  26 +-
> >>  arch/arm/mach-davinci/dm644x.c              |  28 +-
> >>  arch/arm/mach-davinci/dm646x.c              |  28 +-
> >>  arch/arm/mach-davinci/include/mach/common.h |  17 -
> >>  arch/arm/mach-davinci/include/mach/time.h   |  35 --
> >>  arch/arm/mach-davinci/time.c                | 414 --------------------
> >>  14 files changed, 110 insertions(+), 588 deletions(-)
> >>  delete mode 100644 arch/arm/mach-davinci/include/mach/time.h
> >>  delete mode 100644 arch/arm/mach-davinci/time.c
> >>
> >> --
> >> 2.21.0
> >>
> >
> > Hi Sekhar,
> >
> > a gentle ping. Is this series good to go in for v5.4?
>
> Hi Bartosz, a quick test shows that DM365 fails to boot after this. Can
> you please see if there is anything obviously wrong for that SoC. Rest
> seems to be okay.
>
> Thanks,
> Sekhar

Hi Sekhar,

just verified on Kevin's dm365-evm rebased on top of v5.3-rc3 and it
boots fine. I know that davinci failed to boot at v5.3-rc1.

Let me know if I can help with debugging.

Bart