scmi: fix struct scmi_clk_rate_set_in define error

According to the protocol of SCMI, struct scmi_clk_rate_set_in
should be as follows:
struct scmi_clk_rate_set_in {
u32 flags;
u32 clock_id;
u32

scmi: fix struct scmi_clk_rate_set_in define error

According to the protocol of SCMI, struct scmi_clk_rate_set_in
should be as follows:
struct scmi_clk_rate_set_in {
u32 flags;
u32 clock_id;
u32 rate_lsb;
u32 rate_msb;
};

Change-Id: I89955c13887034f5308dac2baa6b6bd53132c5ef
Signed-off-by: XiaoDong Huang <derrick.huang@rock-chips.com>

show more ...

UPSTREAM: reset: add reset controller driver for SCMI agents

This change introduces a reset controller driver for SCMI agent devices.
When SCMI agent and SCMI reset domain drivers are enabled, SCMI

UPSTREAM: reset: add reset controller driver for SCMI agents

This change introduces a reset controller driver for SCMI agent devices.
When SCMI agent and SCMI reset domain drivers are enabled, SCMI agent
binds a reset controller device for each SCMI reset domain protocol
devices enabled in the FDT.

SCMI reset driver is embedded upon CONFIG_RESET_SCMI=y. If enabled,
CONFIG_SCMI_AGENT is also enabled.

SCMI Reset Domain protocol is defined in the SCMI specification [1].

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>

Conflicts:
drivers/reset/Kconfig
drivers/reset/Makefile

(cherry picked from commit 34d76fefb2667d0ca138ff4fcf8bc8443032449f)
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I8c6dd9bb49e58cd9df9a67c1cd101d8da27f3691

show more ...

UPSTREAM: clk: add clock driver for SCMI agents

This change introduces a clock driver for SCMI agent devices. When
SCMI agent and SCMI clock drivers are enabled, SCMI agent binds a
clock device for

UPSTREAM: clk: add clock driver for SCMI agents

This change introduces a clock driver for SCMI agent devices. When
SCMI agent and SCMI clock drivers are enabled, SCMI agent binds a
clock device for each SCMI clock protocol devices enabled in the FDT.

SCMI clock driver is embedded upon CONFIG_CLK_SCMI=y. If enabled,
CONFIG_SCMI_AGENT is also enabled.

SCMI Clock protocol is defined in the SCMI specification [1].

Links: [1] https://developer.arm.com/architectures/system-architectures/software-standards/scmi
Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
Cc: Lukasz Majewski <lukma@denx.de>
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>

Conflics:
drivers/clk/Kconfig
drivers/clk/Makefile

(cherry picked from commit 60388844836f5639e6c9a4331335ff22298128da)
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I2063cff170f75be6edb169619c7321a07051583c

show more ...

UPSTREAM: firmware: add SCMI agent uclass

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

UPSTREAM: firmware: add SCMI agent uclass

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>

Conflicts:
arch/sandbox/dts/test.dts
configs/sandbox_defconfig
drivers/firmware/Kconfig
drivers/firmware/Makefile
test/dm/Makefile

(cherry picked from commit 358599efd827b0ee48af864537cc86facc9167c0)
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I251bf48c2bb60af041e71c5904e0eb73f0243439

show more ...