From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] arm64: Initial support Texas Instrument's AM654 Platform
Date: Wed, 20 Jun 2018 22:40:10 -0700 [thread overview]
Message-ID: <20180621054010.GE112168@atomide.com> (raw)
In-Reply-To: <20180619194253.27288-1-nm@ti.com>
* Nishanth Menon <nm@ti.com> [180619 19:46]:
> Hi,
> This is an update from RFC posted earlier:
> https://marc.info/?l=linux-arm-kernel&m=152817866312732&w=2
>
> The following series enables support for newest addition in TI's SoC
> portfolio - AM654 SoC.
>
> The series is based off v4.18-rc1, also available here:
> https://github.com/nmenon/linux-2.6-playground/tree/upstream/v4.18-rc1/k3-1-am6-base
>
> Key changes since RFC are indicated in respective patches:
> * dt bindings updates (from review comments)
> * device tree is split up to incorporate ranges and bus segments
> * Cosmetic fixes including renaming the base dts to prevent confusion
> * UART has been split out
Other than the cbass to interrconnect naming, looks good to me now:
Reviewed-by: Tony Lindgren <tony@atomide.com>
prev parent reply other threads:[~2018-06-21 5:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 19:42 [PATCH 0/5] arm64: Initial support Texas Instrument's AM654 Platform Nishanth Menon
2018-06-19 19:42 ` [PATCH 1/5] dt-bindings: arm: ti: Add bindings for AM654 SoC Nishanth Menon
2018-06-19 19:42 ` [PATCH 2/5] arm64: Add support for TI's K3 Multicore SoC architecture Nishanth Menon
2018-06-19 19:42 ` [PATCH 3/5] arm64: dts: ti: Add Support for AM654 SoC Nishanth Menon
2018-06-21 5:37 ` Tony Lindgren
2018-06-21 11:36 ` Nishanth Menon
2018-06-19 19:42 ` [PATCH 4/5] soc: ti: Add Support for AM654 SoC config option Nishanth Menon
2018-06-19 19:42 ` [PATCH 5/5] arm64: dts: ti: Add support for AM654 EVM base board Nishanth Menon
2018-06-21 5:40 ` Tony Lindgren [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=20180621054010.GE112168@atomide.com \
--to=tony@atomide.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).