From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 1/8] firmware: add SCMI agent uclass
Date: Thu, 1 Oct 2020 10:07:24 -0400 [thread overview]
Message-ID: <20201001140724.GM14816@bill-the-cat> (raw)
In-Reply-To: <20200909164407.14327-1-etienne.carriere@linaro.org>
On Wed, Sep 09, 2020 at 06:44:00PM +0200, Etienne Carriere wrote:
> This change introduces SCMI agent uclass to interact with a firmware
> using the SCMI protocols [1].
>
> SCMI agent uclass currently supports a single method to request
> processing of the SCMI message by an identified server. A SCMI message
> is made of a byte payload associated to a protocol ID and a message ID,
> all defined by the SCMI specification [1]. On return from process_msg()
> method, the caller gets the service response.
>
> SCMI agent uclass defines a post bind generic sequence for all devices.
> The sequence binds all the SCMI protocols listed in the FDT for that
> SCMI agent device. Currently none, but later change will introduce
> protocols.
>
> This change implements a simple sandbox device for the SCMI agent uclass.
> The sandbox nicely answers SCMI_NOT_SUPPORTED to SCMI messages.
> To prepare for further test support, the sandbox exposes a architecture
> function for test application to read the sandbox emulated devices state.
> Currently supports 2 SCMI agents, identified by an ID in the FDT device
> name. The simplistic DM test does nothing yet.
>
> SCMI agent uclass is designed for platforms that embed a SCMI server in
> a firmware hosted somewhere, for example in a companion co-processor or
> in the secure world of the executing processor. SCMI protocols allow an
> SCMI agent to discover and access external resources as clock, reset
> controllers and more. SCMI agent and server communicate following the
> SCMI specification [1]. This SCMI agent implementation complies with
> the DT bindings defined in the Linux kernel source tree regarding
> SCMI agent description since v5.8.
>
> Links: [1] https://developer.arm.com/architectures/system-architectures/software-standards/scmi
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
> Cc: Simon Glass <sjg@chromium.org>
> Cc: Peng Fan <peng.fan@nxp.com>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/next, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201001/5063fe28/attachment.sig>
prev parent reply other threads:[~2020-10-01 14:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 16:44 [PATCH v4 1/8] firmware: add SCMI agent uclass Etienne Carriere
2020-09-09 16:44 ` [PATCH v4 2/8] firmware: scmi: mailbox/smt agent device Etienne Carriere
2020-09-10 13:38 ` Simon Glass
2020-10-01 14:07 ` Tom Rini
2020-09-09 16:44 ` [PATCH v4 3/8] firmware: scmi: support Arm SMCCC transport Etienne Carriere
2020-09-10 13:38 ` Simon Glass
2020-10-01 14:07 ` Tom Rini
2020-09-09 16:44 ` [PATCH v4 4/8] dt-bindings: arm: SCMI bindings documentation Etienne Carriere
2020-09-10 13:38 ` Simon Glass
2020-10-01 14:07 ` Tom Rini
2020-09-09 16:44 ` [PATCH v4 5/8] clk: add clock driver for SCMI agents Etienne Carriere
2020-09-10 13:38 ` Simon Glass
2020-10-01 14:07 ` Tom Rini
2020-09-09 16:44 ` [PATCH v4 6/8] firmware: scmi: sandbox test for SCMI clocks Etienne Carriere
2020-09-10 13:38 ` Simon Glass
2020-10-01 14:07 ` Tom Rini
2020-09-09 16:44 ` [PATCH v4 7/8] reset: add reset controller driver for SCMI agents Etienne Carriere
2020-09-10 13:38 ` Simon Glass
2020-10-01 14:08 ` Tom Rini
2020-09-09 16:44 ` [PATCH v4 8/8] firmware: smci: sandbox test for SCMI reset controllers Etienne Carriere
2020-09-10 13:38 ` Simon Glass
2020-10-01 14:08 ` Tom Rini
2020-10-01 14:07 ` Tom Rini [this message]
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=20201001140724.GM14816@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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