linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Kevin Hilman <khilman@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [RESEND PATCH 00/10] ARM: davinci: use the new clocksource driver
Date: Mon, 26 Aug 2019 19:03:00 +0530	[thread overview]
Message-ID: <5bcac6b1-0377-4a0f-0aea-bcc6c5e34c9a@ti.com> (raw)
In-Reply-To: <CAMRc=MeTgNf5Xsv6dSY0LJbsAOuoHcfB-x1riMwQkWtVc7wddQ@mail.gmail.com>

On 08/08/19 1:11 PM, Bartosz Golaszewski wrote:
> śr., 7 sie 2019 o 21:28 Sekhar Nori <nsekhar@ti.com> napisał(a):
>>
>> On 05/08/19 1:59 PM, Bartosz Golaszewski wrote:
>>> pon., 22 lip 2019 o 15:17 Bartosz Golaszewski <brgl@bgdev.pl> napisał(a):
>>>>
>>>> From: Bartosz Golaszewski <bgolaszewski@baylibre.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.

Added series except 7/10 and 10/10 to v5.4/soc. Debug of DM365 issue is
still going on offline. DM365 migration is postponed pending conclusion
of that debug.

Thanks,
Sekhar

      reply	other threads:[~2019-08-26 13:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 13:17 [RESEND PATCH 00/10] ARM: davinci: use the new clocksource driver Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 01/10] ARM: davinci: enable the clocksource driver for DT mode Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 02/10] ARM: davinci: WARN_ON() if clk_get() fails Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 03/10] ARM: davinci: da850: switch to using the clocksource driver Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 04/10] ARM: davinci: da830: " Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 05/10] ARM: davinci: move timer definitions to davinci.h Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 06/10] ARM: davinci: dm355: switch to using the clocksource driver Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 07/10] ARM: davinci: dm365: " Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 08/10] ARM: davinci: dm644x: " Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 09/10] ARM: davinci: dm646x: " Bartosz Golaszewski
2019-07-22 13:17 ` [RESEND PATCH 10/10] ARM: davinci: remove legacy timer support Bartosz Golaszewski
2019-08-05  8:29 ` [RESEND PATCH 00/10] ARM: davinci: use the new clocksource driver Bartosz Golaszewski
2019-08-07 19:28   ` Sekhar Nori
2019-08-08  7:41     ` Bartosz Golaszewski
2019-08-26 13:33       ` Sekhar Nori [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bcac6b1-0377-4a0f-0aea-bcc6c5e34c9a@ti.com \
    --to=nsekhar@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).