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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK9=C2WutH5+3eNvMpD89WhXdNaJAJVz=h5r6c_Jc39nBx9NEw@mail.gmail.com>
Date: Mon, 23 Jun 2025 09:15:59 +0530
From: Anup Patel <apatel@...tanamicro.com>
To: Stephen Boyd <sboyd@...nel.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, Bartosz Golaszewski <brgl@...ev.pl>, 
	Conor Dooley <conor+dt@...nel.org>, Jassi Brar <jassisinghbrar@...il.com>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Linus Walleij <linus.walleij@...aro.org>, 
	Michael Turquette <mturquette@...libre.com>, Mika Westerberg <mika.westerberg@...ux.intel.com>, 
	"Rafael J . Wysocki" <rafael@...nel.org>, Rob Herring <robh@...nel.org>, 
	Thomas Gleixner <tglx@...utronix.de>, Uwe Kleine-König <ukleinek@...nel.org>, 
	Palmer Dabbelt <palmer@...belt.com>, Paul Walmsley <paul.walmsley@...ive.com>, 
	Len Brown <lenb@...nel.org>, Sunil V L <sunilvl@...tanamicro.com>, 
	Rahul Pathak <rpathak@...tanamicro.com>, Leyfoon Tan <leyfoon.tan@...rfivetech.com>, 
	Atish Patra <atish.patra@...ux.dev>, Andrew Jones <ajones@...tanamicro.com>, 
	Samuel Holland <samuel.holland@...ive.com>, Anup Patel <anup@...infault.org>, 
	linux-clk@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org, 
	Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v6 07/23] dt-bindings: clock: Add RPMI clock service
 message proxy bindings

On Sun, Jun 22, 2025 at 2:30 AM Stephen Boyd <sboyd@...nel.org> 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