From: <nicolas.ferre@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
<arm@kernel.org>, <soc@kernel.org>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Kavyasree Kotagiri - I30978 <Kavyasree.Kotagiri@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: [GIT PULL] ARM: at91: soc for 5.16
Date: Mon, 11 Oct 2021 14:46:50 +0200 [thread overview]
Message-ID: <20211011124650.17218-1-nicolas.ferre@microchip.com> (raw)
Message-ID: <20211011124650.BrhXsy_lGJgpNvUCwJIM2NL8vI-zvcviZ-LvQ6ElWEU@z> (raw)
From: Nicolas Ferre <nicolas.ferre@microchip.com>
Arnd, Olof,
Here are the at91 soc changes for 5.16. We are really at the beginning for
lan966 family with an ongoing activity in the clock sub-system, for instance.
Thanks, best regards,
Nicolas
The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git tags/at91-soc-5.16
for you to fetch changes up to 3efc443121180c2acc987929b3b7b86ca83e3ee5:
ARM: at91: add basic support for new SoC family lan966 (2021-10-04 14:50:18 +0200)
----------------------------------------------------------------
AT91 SoC #1 for 5.16:
- Documentation for sama7g5 and lan966 families
- Kconfig entry for lan966 new SoC.
----------------------------------------------------------------
Kavyasree Kotagiri (3):
ARM: at91: Documentation: add lan966 family
dt-bindings: arm: at91: Document lan966 pcb8291 and pcb8290 boards
ARM: at91: add basic support for new SoC family lan966
Nicolas Ferre (1):
ARM: at91: Documentation: add sama7g5 family
Documentation/arm/microchip.rst | 20 ++++++++++++++++++++
.../devicetree/bindings/arm/atmel-at91.yaml | 12 ++++++++++++
arch/arm/mach-at91/Kconfig | 9 +++++++++
3 files changed, 41 insertions(+)
--
Nicolas Ferre
next reply other threads:[~2021-10-11 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211011124650.Xm4D9MXOvGMaU2u7Qp5RrsjOeEd9i5ab-2wH1MEyeQM@z>
2021-10-11 12:46 ` nicolas.ferre [this message]
2021-10-11 12:46 ` [GIT PULL] ARM: at91: soc for 5.16 nicolas.ferre
2021-10-11 22:50 ` patchwork-bot+linux-soc
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=20211011124650.17218-1-nicolas.ferre@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=olof@lixom.net \
--cc=soc@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).