From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V8 0/3] soc: imx: add scu firmware api support
Date: Sun, 30 Sep 2018 21:28:03 +0800 [thread overview]
Message-ID: <20180930132759.GP26692@dragon> (raw)
In-Reply-To: <20180930072628.GN26692@dragon>
On Sun, Sep 30, 2018 at 03:26:30PM +0800, Shawn Guo wrote:
> On Sun, Sep 30, 2018 at 08:48:33AM +0800, Dong Aisheng wrote:
> > Unlike the former i.MX Architectures, the new generation i.MX8 SoCs
> > (e.g. MX8QXP and MX8QM) contain a system controller which runs on a
> > dedicated Cortex-M core to provide power, clock, Pad, and resource
> > management. Communication between the host processor running
> > an OS and the system controller happens through a SCU protocol.
> > This patchset adds the SCU APIs which is implemented based on MU
> > and will be used by different system components.
> >
> > It mainly consists of below parts:
> > 1) SCU IPC
> > Basic IPC mechanism implemention based on mailbox which is used
> > for communication between AP and SCU firmware.
> > 2) SCU IPC Service API
> >
> > Dong Aisheng (3):
> > dt-bindings: arm: fsl: add scu binding doc
> > firmware: imx: add SCU firmware driver support
> > firmware: imx: add misc svc support
>
> Applied all, thanks.
I dropped the series for now because ...
>
> >
> > .../devicetree/bindings/arm/freescale/fsl,scu.txt | 183 ++++++
> > drivers/firmware/Kconfig | 1 +
> > drivers/firmware/Makefile | 1 +
> > drivers/firmware/imx/Kconfig | 11 +
> > drivers/firmware/imx/Makefile | 2 +
> > drivers/firmware/imx/imx-scu.c | 270 +++++++++
> > drivers/firmware/imx/misc.c | 99 ++++
> > include/soc/imx/scu/ipc.h | 59 ++
> > include/soc/imx/scu/sci.h | 17 +
> > include/soc/imx/scu/svc/misc.h | 55 ++
> > include/soc/imx/scu/types.h | 617 +++++++++++++++++++++
... I'm not sure the scu folder should be created under include/soc/imx/
or include/linux/firmware/imx/ like meson platform. I would like to
hear more opinions.
Shawn
next prev parent reply other threads:[~2018-09-30 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 0:48 [PATCH V8 0/3] soc: imx: add scu firmware api support Dong Aisheng
2018-09-30 0:48 ` [PATCH V8 1/3] dt-bindings: arm: fsl: add scu binding doc Dong Aisheng
2018-09-30 0:48 ` [PATCH V8 2/3] firmware: imx: add SCU firmware driver support Dong Aisheng
2018-09-30 0:48 ` [PATCH V8 3/3] firmware: imx: add misc svc support Dong Aisheng
2018-09-30 7:26 ` [PATCH V8 0/3] soc: imx: add scu firmware api support Shawn Guo
2018-09-30 13:28 ` Shawn Guo [this message]
2018-10-07 12:36 ` A.s. Dong
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=20180930132759.GP26692@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).