linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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: Olof Johansson <olof@lixom.net>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>
Subject: [GIT PULL] firmware: arm_scmi: updates for v5.7-rc1
Date: Wed, 4 Mar 2020 17:52:47 +0000	[thread overview]
Message-ID: <20200304175247.GA5402@bogus> (raw)

Hi ARM SoC Team,

Please pull !

Note that I have pulled in one vexpress syscfg fix in this pull request
itself instead of a separate one as I think it also falls under 'driver'
category in your pull requests. Let me know if you prefer to keep it
separate.

Regards,
Sudeep

-->8

The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:

  Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/scmi-updates-5.7

for you to fetch changes up to 57c45d4d8a9d78c962e9ddfc4fb2d3210f34f966:

  misc: vexpress: Replace zero-length array with flexible-array member (2020-02-20 17:15:04 +0000)

----------------------------------------------------------------
ARM SCMI/SCPI updates for v5.7

1. Abstraction of the scmi transport type from the core protocol driver
   which enables addition of other transports like SMC/HVC, SPCI and
   virtio apart from the existing mailbox
2. Miscellaneous fix for minor formatting issues with the kernel-doc
   style comments
3. Replacement of zero-length array with flexible-array member which is
   part of tree-wide cleanup

----------------------------------------------------------------
Gustavo A. R. Silva (4):
      firmware: arm_scmi: Replace zero-length array with flexible-array member
      firmware: arm_scmi/perf: Replace zero-length array with flexible-array member
      firmware: arm_scpi: Replace zero-length array with flexible-array member
      misc: vexpress: Replace zero-length array with flexible-array member

Viresh Kumar (3):
      firmware: arm_scmi: Update doc style comments
      firmware: arm_scmi: Move macros and helpers to common.h
      firmware: arm_scmi: Make scmi core independent of the transport type

 drivers/firmware/arm_scmi/Makefile  |   3 +-
 drivers/firmware/arm_scmi/common.h  | 115 +++++++++++++-
 drivers/firmware/arm_scmi/driver.c  | 293 +++++-------------------------------
 drivers/firmware/arm_scmi/mailbox.c | 184 ++++++++++++++++++++++
 drivers/firmware/arm_scmi/perf.c    |   2 +-
 drivers/firmware/arm_scmi/shmem.c   |  83 ++++++++++
 drivers/firmware/arm_scpi.c         |   4 +-
 drivers/misc/vexpress-syscfg.c      |   2 +-
 8 files changed, 420 insertions(+), 266 deletions(-)
 create mode 100644 drivers/firmware/arm_scmi/mailbox.c
 create mode 100644 drivers/firmware/arm_scmi/shmem.c

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2020-03-04 17:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200304175247.GA5402@bogus \
    --to=sudeep.holla@arm.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --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).