Re: [PATCH v6 07/23] dt-bindings: clock: Add RPMI clock service message proxy bindings

[Anup Patel]

On Sun, Jun 22, 2025 at 2:30 AM Stephen Boyd <sboyd@xxxxxxxxxx> wrote:
>
> Quoting Anup Patel (2025-06-18 05:13:42)
> > diff --git a/Documentation/devicetree/bindings/clock/riscv,rpmi-mpxy-clock.yaml b/Documentation/devicetree/bindings/clock/riscv,rpmi-mpxy-clock.yaml
> > new file mode 100644
> > index 000000000000..70ffc88d0110
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/clock/riscv,rpmi-mpxy-clock.yaml
> > @@ -0,0 +1,64 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/clock/riscv,rpmi-mpxy-clock.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> [...]
> > +
> > +examples:
> > +  - |
> > +    clock-controller {
> > +        compatible = "riscv,rpmi-mpxy-clock";
> > +        mboxes = <&rpmi_shmem_mbox 0x8>;
> > +        riscv,sbi-mpxy-channel-id = <0x1000>;
>
> Why aren't there any #clock-cells in this clock controller node?

This binding is intended for M-mode firmware (OpenSBI) and not
for S-mode OS (Linux) where the firmware will use this binding to
probe a message proxy driver which in-turn will allows the Linux
RPMI clock driver to access RPMI clocks via SBI calls.

Regards,
Anup