devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <conor.dooley@microchip.com>
To: <robh+dt@kernel.org>, <jassisinghbrar@gmail.com>,
	<aou@eecs.berkeley.edu>, <paul.walmsley@sifive.com>,
	<palmer@dabbelt.com>, <devicetree@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>
Cc: <lewis.hanly@microchip.com>, <cyril.jean@microchip.com>,
	<daire.mcnamara@microchip.com>, <atish.patra@wdc.com>,
	<anup.patel@wdc.com>, <david.abdurachmanov@gmail.com>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH 0/6] Add support for the PolarFire Soc system controller
Date: Thu, 19 Nov 2020 17:04:04 +0000	[thread overview]
Message-ID: <20201119170404.18151-1-conor.dooley@microchip.com> (raw)

From: Conor Dooley <conor.dooley@microchip.com>

This patch series adds support for the system controller on
the PolarFire SoC, using the mailbox framework. A Microchip directory
in the SoC subsystem has been created to hold the mailbox client
driver and will be used for future service drivers.

This directory is included by the kconfig option: 
CONFIG_SOC_MICROCHIP_POLARFIRE, so this patch series depends on Atish 
Patra's PolarFire SoC support patches which introduce that option.

Conor Dooley (6):
  mbox: add polarfire soc system controller mailbox
  soc: add polarfire soc header file
  dt-bindings: add bindings for polarfire soc mailbox
  soc: add polarfire soc system controller
  dt-bindings: add bindings for polarfire soc system controller
  MAINTAINERS: add microchip polarfire soc support

 .../mailbox/microchip,mpfs-mailbox.yaml       |  46 +++
 .../microchip,mpfs_sys_controller.yaml        |  50 +++
 MAINTAINERS                                   |   9 +
 drivers/mailbox/Kconfig                       |  12 +
 drivers/mailbox/Makefile                      |   2 +
 drivers/mailbox/mailbox-mpfs.c                | 296 ++++++++++++++++++
 drivers/soc/Kconfig                           |   1 +
 drivers/soc/Makefile                          |   1 +
 drivers/soc/microchip/Kconfig                 |  10 +
 drivers/soc/microchip/Makefile                |   1 +
 drivers/soc/microchip/mpfs_sys_controller.c   | 136 ++++++++
 include/soc/microchip/mpfs.h                  |  50 +++
 12 files changed, 614 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mailbox/microchip,mpfs-mailbox.yaml
 create mode 100644 Documentation/devicetree/bindings/soc/microchip/microchip,mpfs_sys_controller.yaml
 create mode 100644 drivers/mailbox/mailbox-mpfs.c
 create mode 100644 drivers/soc/microchip/Kconfig
 create mode 100644 drivers/soc/microchip/Makefile
 create mode 100644 drivers/soc/microchip/mpfs_sys_controller.c
 create mode 100644 include/soc/microchip/mpfs.h


base-commit: f8394f232b1eab649ce2df5c5f15b0e528c92091
-- 
2.17.1


                 reply	other threads:[~2020-11-19 17:04 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=20201119170404.18151-1-conor.dooley@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=anup.patel@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@wdc.com \
    --cc=cyril.jean@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=david.abdurachmanov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=lewis.hanly@microchip.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@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).