linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 0/5] soc: imx: add scu firmware api support
Date: Wed, 11 Jul 2018 17:49:02 +0100	[thread overview]
Message-ID: <24505e51-3a5d-4f34-7ba6-262e118d070e@arm.com> (raw)
In-Reply-To: <1531061817-1980-1-git-send-email-aisheng.dong@nxp.com>



On 08/07/18 15:56, 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) MU mailbox driver
> 1) Implementation of the IPC functions based on MUs (client side).
> 
> 

I do understand the firmware might be already released for the current
generation of platforms, but instead of adding to the fragmentation, it
would be good to migrated to ARM SCMI for future platforms.

This system controller communication protocol is already so fragmented
(we have TI SCI, QCOM RPM, Nvidia Tegra BPMP, ARM SCPI and so on..
and now this i.MX specific one added to that), the main intention of ARM
SCMI is to stop that. The idea is for any Power Control System
Architecture(PCSA) compliant systems or any similar systems, SCMI should
be the standard communication protocol.

-- 
Regards,
Sudeep

  parent reply	other threads:[~2018-07-11 16:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-08 14:56 [PATCH V4 0/5] soc: imx: add scu firmware api support Dong Aisheng
2018-07-08 14:56 ` [PATCH V4 1/5] dt-bindings: mailbox: allow mbox-cells to be equal to 0 Dong Aisheng
2018-07-08 14:56 ` [PATCH V4 2/5] dt-bindings: arm: fsl: add mu binding doc Dong Aisheng
2018-07-11 15:09   ` Rob Herring
2018-07-08 14:56 ` [PATCH V4 3/5] mailbox: imx: add imx mu support Dong Aisheng
2018-07-10 14:19   ` Sascha Hauer
2018-07-11  7:29     ` A.s. Dong
2018-07-11  7:54       ` Sascha Hauer
2018-07-11 10:37         ` A.s. Dong
2018-07-11 10:44           ` Jassi Brar
2018-07-11 12:58             ` A.s. Dong
2018-07-11 16:31               ` Jassi Brar
2018-07-11 16:41                 ` A.s. Dong
2018-07-11 17:00                   ` Jassi Brar
2018-07-12  4:06                     ` A.s. Dong
2018-07-11 13:30       ` Peng Fan
2018-07-08 14:56 ` [PATCH V4 4/5] dt-bindings: arm: fsl: add scu binding doc Dong Aisheng
2018-07-11 15:08   ` Rob Herring
2018-07-12 11:04     ` A.s. Dong
2018-07-08 14:56 ` [PATCH V4 5/5] soc: imx: add SC firmware IPC and APIs Dong Aisheng
2018-07-10 14:44   ` Sascha Hauer
2018-07-11  9:18     ` A.s. Dong
2018-07-11 10:31       ` Sascha Hauer
2018-07-11 11:27         ` A.s. Dong
2018-07-11 16:49 ` Sudeep Holla [this message]
2018-07-12  3:46   ` [PATCH V4 0/5] soc: imx: add scu firmware api support A.s. Dong
2018-07-12 10:32     ` Sudeep Holla
2018-07-12 12:29       ` Leonard Crestez

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=24505e51-3a5d-4f34-7ba6-262e118d070e@arm.com \
    --to=sudeep.holla@arm.com \
    --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).