From: Olof Johansson <olof@lixom.net>
To: Tero Kristo <t-kristo@ti.com>
Cc: Nishanth Menon <nm@ti.com>, "tony@atomide.com" <tony@atomide.com>,
"J, Keerthy" <j-keerthy@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
arm@kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Roger Quadros <rogerq@ti.com>
Subject: Re: [GIT PULL] Texas Instruments K3 SoC changes for 5.3
Date: Wed, 19 Jun 2019 09:03:55 -0700 [thread overview]
Message-ID: <20190619160355.w35g64mxbzqx7zq7@localhost> (raw)
In-Reply-To: <479002be-d9cf-38d6-e7a7-82e71d439ff7@ti.com>
On Wed, Jun 19, 2019 at 03:06:45PM +0300, Tero Kristo wrote:
> Hello arm-soc maintainers,
>
> Please pull the changes for Texas Instruments K3 SoC family changes for 5.3.
>
> Thanks,
> Tero
>
> ---
>
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
>
> Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kristo/linux
> tags/ti-k3-soc-for-v5.3
>
> for you to fetch changes up to 78eccc2ac98e4166def294f02283f21cefd89591:
>
> arm64: dts: ti: k3-j721e: Add the MCU SRAM node (2019-06-19 11:59:49
> +0300)
>
> ----------------------------------------------------------------
> Texas Instruments K3 SoC family changes for 5.3
>
> - Add support for the new J721e SoC, includes basic peripherals needed for
> booting up the device
> - New peripheral support added for AM654x:
> * TI SCI irqchip
> * GPIO
> * MCU SRAM
> * R5Fs
> * MSMC RAM
> * SERDES and PCIe
Merged, thanks!
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-19 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 12:06 [GIT PULL] Texas Instruments K3 SoC changes for 5.3 Tero Kristo
2019-06-19 16:03 ` Olof Johansson [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=20190619160355.w35g64mxbzqx7zq7@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=j-keerthy@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=rogerq@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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