linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: ARM-SoC Maintainers <arm@kernel.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	nsekhar@ti.com,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL 1/4] DaVinci SoC updates for v5.4
Date: Wed, 28 Aug 2019 20:47:51 +0530	[thread overview]
Message-ID: <20190828151754.21023-1-nsekhar@ti.com> (raw)

The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:

  Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-for-v5.4/soc

for you to fetch changes up to 93eae12c9f3e3bf423b308b341d380b0b4291bf8:

  ARM: davinci: dm646x: Fix a typo in the comment (2019-08-26 17:51:28 +0530)

----------------------------------------------------------------
This converts all DaVinci SoCs except DM365 to use new clocksource
driver. DM365 conversion is still under debug and will be part of a
future pull request.

----------------------------------------------------------------
Bartosz Golaszewski (8):
      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: dm644x: switch to using the clocksource driver
      ARM: davinci: dm646x: switch to using the clocksource driver

Christophe JAILLET (1):
      ARM: davinci: dm646x: Fix a typo in the comment

 arch/arm/Kconfig                          |  1 +
 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/dm355.c             | 28 ++++++++++-------
 arch/arm/mach-davinci/dm365.c             |  4 +++
 arch/arm/mach-davinci/dm644x.c            | 28 ++++++++++-------
 arch/arm/mach-davinci/dm646x.c            | 30 +++++++++++--------
 arch/arm/mach-davinci/include/mach/time.h |  2 --
 arch/arm/mach-davinci/time.c              | 14 ---------
 10 files changed, 95 insertions(+), 110 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-08-28 15:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 15:17 Sekhar Nori [this message]
2019-08-28 15:17 ` [GIT PULL 2/4] DaVinci defconfig updates for v5.4 Sekhar Nori
2019-09-04 14:51   ` Arnd Bergmann
2019-09-05  6:17     ` Sekhar Nori
2019-09-05  9:15       ` Arnd Bergmann
2019-09-06  6:31     ` Peter Ujfalusi
2019-09-06  8:46       ` Arnd Bergmann
2019-08-28 15:17 ` [GIT PULL 3/4] DaVinci fbdev driver " Sekhar Nori
2019-09-04 14:56   ` Arnd Bergmann
2019-08-28 15:17 ` [GIT PULL 4/4] DaVinci DT " Sekhar Nori
2019-09-04 14:57   ` Arnd Bergmann
2019-09-04 13:24 ` [GIT PULL 1/4] DaVinci SoC " Arnd Bergmann

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=20190828151754.21023-1-nsekhar@ti.com \
    --to=nsekhar@ti.com \
    --cc=arm@kernel.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.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).