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/scmiSigned-off-by: NEtienne 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: NSimon Glass <sjg@chromium.org>

Add tests for SCMI clocks. A test device driver sandbox-scmi_devices.c
is used to get clock resources, allowing further clock manipulation.

Change sandbox-smci_agent to emulate 3 clocks exposed through 2 agents.
Add DM test scmi_clocks to test these 3 clocks.
Update DM test sandbox_scmi_agent with load/remove test sequences
factorized by {load|remove}_sandbox_scmi_test_devices() helper functions.
Signed-off-by: NEtienne 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: NSimon Glass <sjg@chromium.org>

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/scmiSigned-off-by: NEtienne 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: NSimon Glass <sjg@chromium.org>

Dump SCMI DT bindings documentation from Linux kernel source
tree v5.8-rc1.
Signed-off-by: NEtienne Carriere <etienne.carriere@linaro.org>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NSimon Glass <sjg@chromium.org>

This change implements a SMCCC transport for SCMI exchanges. This
implementation follows the Linux kernel as references implementation
for SCMI message processing, using the SMT format for communication
channel meta-data.

Use of SMCCC transport in SCMI FDT bindings are defined in the Linux
kernel DT bindings since v5.8. SMCCC with SMT is implemented in OP-TEE
from tag 3.9.0 [2].

Links: [2] https://github.com/OP-TEE/optee_os/commit/a58c4d706d23Signed-off-by: NEtienne 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: NSimon Glass <sjg@chromium.org>

This change implements a mailbox transport using SMT format for SCMI
exchanges. This implementation follows the Linux kernel and
SCP-firmware [1] as references implementation for SCMI message
processing using SMT format for communication channel meta-data.

Use of mailboxes in SCMI FDT bindings are defined in the Linux kernel
DT bindings since v4.17.

Links: [1] https://github.com/ARM-software/SCP-firmwareSigned-off-by: NEtienne 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: NSimon Glass <sjg@chromium.org>

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/scmiSigned-off-by: NEtienne 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: NSimon Glass <sjg@chromium.org>

The tests rely on a dummy driver to allocate and initialize the regmaps
and the regmap fields using the managed API. The first test checks if
the regmap config fields like width, reg_offset_shift, range specifiers,
etc work. The second test checks if regmap fields behave properly (mask
and shift are ok) by peeking into the regmap.
Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com>
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

When more nodes are added for a uclass the index might go into two or
more digits. This means that there are less spaces printed because they
are used up by the extra digits. Update the regular expression to allow
variable-length spacing between the class name and and index.

This was discovered when adding a simple_bus node in test.dts made
test_bind_unbind_with_uclass() fail because the index went up to 10.
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>

A regmap field is an abstraction available in Linux. It provides to access
bitfields in a regmap without having to worry about shifts and masks.
Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>

Some devices need to calculate the regmap base address at runtime. This
makes it impossible to use device tree to get the regmap base. Instead,
allow devices to specify it in the regmap config. This will create a
regmap with a single range that corresponds to the start and size given
by the driver.
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Right now, the base of a regmap can only be obtained from the device
tree. This makes it impossible for devices which calculate the base at
runtime to use a regmap. An example of such a device is the Cadence
Sierra PHY.

Allow creating a regmap with one range whose start and size can be
specified by the driver based on calculations at runtime.
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Drivers can configure it to adjust the final read/write location.
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Right now, regmap_read() and regmap_write() read/write a 32-bit value
only. To write other lengths, regmap_raw_read() and regmap_raw_write()
need to be used.

This means that any driver ported from Linux that relies on
regmap_{read,write}() to know the size already has to be updated at each
callsite. This makes the port harder to maintain.

So, allow specifying the read/write width to make it easier to port the
drivers, since now the only change needed is when initializing the
regmap.
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Some fields will be introduced in the regmap structure that should be
set to 0 by default. So, once we allocate a regmap, make sure it is
zeroed out to avoid unexpected defaults for those values.
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Most of new linux drivers are using managed-API to allocate resources. To
ease porting drivers from linux to U-Boot, introduce devm_regmap_init() as
a managed API to get a regmap from the device tree.
Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>

Add a test to verify that GPIOs can be acquired/released using the managed
API. Also check that the GPIOs are released when the consumer device is
removed.
Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>

Add managed functions to get a gpio from the devce-tree, based on a
property name (minus the '-gpios' suffix) and optionally an index.

When the device is unbound, the GPIO is automatically released and the
data structure is freed.
Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>

The tests are basically the same as for the regular API. Except that
the reset are initialized using the managed API, and no freed manually.
Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>

Add managed functions to get a reset_ctl from the device-tree, based on a
name or an index.
Also add a managed functions to get a reset_ctl_bulk (array of reset_ctl)
from the device-tree.

When the device is unbound, the reset controllers are automatically
released and the data structure is freed.
Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NPratyush Yadav <p.yadav@ti.com>

- Disable CMD_IRQ for RISC-V.
- Update sipeed/maix doc
- Obtain reg of SiFive RAM via dev_read_addr_index() instead of regmap API.
- Cleans up RISC-V timer drivers and converts them to DM.
- Correctly handle IPIs already pending upon prior stage bootloader (on the K210)

- Improve our dev_xxx(..) wrappers to be generally used and available
  rather than discarded at link/compile time.

This adorns messages generated by dev_xxx with the device and driver
names. It also redirects dev_xxx to log when it is available. The names
of these functions very roughly take inspiration from Linux, but there is
no deeper correlation.

Both struct udevice and struct device are supported when logging, though
logging with struct device is no better than using log_xxx. The latter is
supported because of the large amount of existing code which logs with
struct device.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

This substitutes literal log levels with their symbolic constants.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

There is no member `dev` in dw_mipi_dsi, but there is one in mipi_dsi_host,
so use that.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NPatrick Delaunay <patrick.delaunay@st.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

This driver does not use DM, so we need to use a struct device instead of a
struct udevice. Not ideal, but it'll have to do for now.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

This can conflict with asm/io.h on some archs, and it isn't needed to build
dwc3-generic.c
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

This driver does not use DM, so use log_xxx instead.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

This logs with the device from struct dwc3. Some files also need to include
dm.h so fields in udevice can be accessed.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

This adds a dev argument to some functions so dev_xxx always has a device
to log with. In one instance we must use use a different log function when
we are compiled without DM_USB.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NPatrice Chotard <patrice.chotard@st.com>
Reviewed-by: NPatrick Delaunay <patrick.delaunay@st.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

ep0.c also need to include dm.h so dev_xxx can access udevice fields.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

The rst variable doesn't exist.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

Use `bus` instead of `dev`.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NMichal Simek <michal.simek@xilinx.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

Use `bus` and not `dev`.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

Remove the indirection.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

Pass a device to functions which log with one.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

Usually we can get a device from the current core, but some dev_dbg calls
have been converted to debug, since we are called on a cluster.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

This function is never used anywhere, and it also tries to log with a
nonexistant device.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

Use the phy's device.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NPatrice Chotard <patrice.chotard@st.com>
Reviewed-by: NPatrick Delaunay <patrick.delaunay@st.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>

`phy` doesn't exist; we need to use `x` instead.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Tested-by: NPatrick Delaunay <patrick.delaunay@st.com>