All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] am654 changes for v4.19 merge window
Date: Sat, 21 Jul 2018 15:07:22 -0700	[thread overview]
Message-ID: <20180721220722.43avzbs6ulpsem37@localhost> (raw)
In-Reply-To: <pull-1532152828-552759@atomide.com>

On Fri, Jul 20, 2018 at 11:05:16PM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
> 
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
> 
>   Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/am654-for-v4.19-signed
> 
> for you to fetch changes up to d0a064bec75e20a526c7bc0d626912f2660b6e81:
> 
>   arm64: dts: ti: Add support for AM654 EVM base board (2018-07-18 11:48:36 -0700)
> 
> ----------------------------------------------------------------
> TI AM654 support for v4.19 merge window
> 
> This branch adds initial support for new Texas Instruments AM654
> quad core A53 ARMv8 SoC. It's the first device for TI K3 multicore SoC
> architecture.
> 
> Initially only basic devices are configured, support for more devices
> will follow later on. And many of the internal devices familiar from
> earlier TI SoCs should work with existing kernel device drivers.

I squinted a bit and merged this into next/dt. Might have been a bit cleaner to
split it in a SoC and a DT branch, but either way it's pretty small changes.

Should the support be enabled in arm64's defconfig?


-Olof

  reply	other threads:[~2018-07-21 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-21  6:05 [GIT PULL] am654 changes for v4.19 merge window Tony Lindgren
2018-07-21 22:07 ` Olof Johansson [this message]
2018-07-22  6:40   ` Tony Lindgren
2018-07-23 13:06     ` Nishanth Menon
2018-07-23 16:18       ` Olof Johansson

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=20180721220722.43avzbs6ulpsem37@localhost \
    --to=olof@lixom.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.