From: Sudeep Holla <sudeep.holla@arm.com>
To: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Arnd Bergmann <arnd@arndb.de>, Arnd Bergmann <arnd@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Olof Johansson <olof@lixom.net>
Subject: [GIT PULL] firmware: arm_scmi: updates for v5.14
Date: Fri, 11 Jun 2021 08:57:22 +0100 [thread overview]
Message-ID: <20210611075722.2813550-1-sudeep.holla@arm.com> (raw)
Message-ID: <20210611075722.XxIRmtB2pmVUMgNSgddsVnghUzjWHEac96mluma_8gc@z> (raw)
Hi ARM SoC Team,
Please pull !
Regards,
Sudeep
-->8
The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/scmi-updates-5.14
for you to fetch changes up to 61832b35b4d953b2b4f6c668a3ad2a3013f40532:
firmware: arm_scmi: Avoid multiple initialisations of hdr->protocol_id (2021-06-08 16:06:12 +0100)
----------------------------------------------------------------
ARM SCMI updates for v5.14
- Support for SCMI clocks from the SCMI power domains
- Addition of checks for correct compatibles for shmem devicetree nodes
that were found missing in the process of YAML schema conversion
- Kconfig and associated build fix found when optee transport are being
worked on
- Couple of fixes and cleanups found as with work-in-progress virtio
transport support
The new transports(optee and virtio) themselves are still being worked on
with ongoing reviews, they are not part of this yet
----------------------------------------------------------------
Cristian Marussi (3):
firmware: arm_scmi: Reset Rx buffer to max size during async commands
firmware: arm_scmi: Add delayed response status check
firmware: arm_scmi: Move reinit_completion from scmi_xfer_get to do_xfer
Etienne Carriere (1):
firmware: arm_scmi: Add SMCCC discovery dependency in Kconfig
Nicolas Pitre (1):
firmware: arm_scmi: Add clock management to the SCMI power domain
Sudeep Holla (4):
firmware: arm_scmi: Fix the build when CONFIG_MAILBOX is not selected
firmware: arm_scpi: Add compatibility checks for shmem node
firmware: arm_scmi: Add compatibility checks for shmem node
firmware: arm_scmi: Avoid multiple initialisations of hdr->protocol_id
drivers/firmware/Kconfig | 2 +-
drivers/firmware/arm_scmi/common.h | 2 +-
drivers/firmware/arm_scmi/driver.c | 24 +++++++++++++++---------
drivers/firmware/arm_scmi/mailbox.c | 3 +++
drivers/firmware/arm_scmi/scmi_pm_domain.c | 26 ++++++++++++++++++++++++++
drivers/firmware/arm_scmi/smc.c | 3 +++
drivers/firmware/arm_scpi.c | 11 +++++++++++
7 files changed, 60 insertions(+), 11 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-06-11 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 7:57 Sudeep Holla [this message]
2021-06-11 7:57 ` [GIT PULL] firmware: arm_scmi: updates for v5.14 Sudeep Holla
2021-06-12 16:10 ` 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=20210611075722.2813550-1-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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).