Linux SOC development
 help / color / mirror / Atom feed
From: <nicolas.ferre@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	<arm@kernel.org>, <soc@kernel.org>
Cc: <kavyasree.kotagiri@microchip.com>, <clement.leger@bootlin.com>,
	"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>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: [GIT PULL] ARM: at91: soc for 5.19
Date: Fri, 13 May 2022 14:17:01 +0200	[thread overview]
Message-ID: <20220513121701.77683-1-nicolas.ferre@microchip.com> (raw)

From: Nicolas Ferre <nicolas.ferre@microchip.com>

Arnd, Olof,

Here are the at91 and Polarfire soc changes for 5.19.
Thanks to Claudiu who did most of the work collecting the patches for this
pull-request!

Please pull.

Thanks, best regards,
  Nicolas

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git tags/at91-soc-5.19

for you to fetch changes up to 6041558ebf1fc87d1e0bdeb51e985807dab06bed:

  ARM: at91: debug: add lan966 support (2022-05-13 13:42:03 +0200)

----------------------------------------------------------------
AT91 & POLARFIRE SoC #1 for 5.19:

- Power Management: add possibility to implement
  specific pm quirks for some SoCs
- Kconfig update for AT91 PIT64 and LAN966 low-level debugging
- sama5d2: add secure calls to OP-TEE and secure suspend

----------------------------------------------------------------
Claudiu Beznea (5):
      ARM: at91: pm: keep documentation inline with structure members
      ARM: at91: pm: introduce macros for pm mode replacement
      ARM: at91: pm: use kernel documentation style
      ARM: at91: pm: add quirks for pm
      ARM: at91: Kconfig: implement PIT64B selection

Clément Léger (2):
      ARM: at91: add code to handle secure calls
      ARM: at91: pm: add support for sama5d2 secure suspend

Kavyasree Kotagiri (1):
      ARM: at91: debug: add lan966 support

 arch/arm/Kconfig.debug          |  22 ++
 arch/arm/mach-at91/Kconfig      |  20 +-
 arch/arm/mach-at91/Makefile     |   2 +-
 arch/arm/mach-at91/pm.c         | 431 ++++++++++++++++++++++++++++++++---
 arch/arm/mach-at91/sam_secure.c |  46 ++++
 arch/arm/mach-at91/sam_secure.h |  18 ++
 arch/arm/mach-at91/sama5.c      |   2 +
 7 files changed, 506 insertions(+), 35 deletions(-)
 create mode 100644 arch/arm/mach-at91/sam_secure.c
 create mode 100644 arch/arm/mach-at91/sam_secure.h

-- 
Nicolas Ferre

             reply	other threads:[~2022-05-13 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 12:17 nicolas.ferre [this message]
2022-05-13 14:40 ` [GIT PULL] ARM: at91: soc for 5.19 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=20220513121701.77683-1-nicolas.ferre@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=claudiu.beznea@microchip.com \
    --cc=clement.leger@bootlin.com \
    --cc=kavyasree.kotagiri@microchip.com \
    --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