From: Stefan Wahren <wahrenst@gmx.net>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: soc: bcm: document brcm,bcm2711-avs-monitor
Date: Thu, 23 May 2024 09:24:04 +0200 [thread overview]
Message-ID: <be9cc413-6780-45f9-913c-056238be2451@gmx.net> (raw)
In-Reply-To: <20240517125138.53441-1-krzysztof.kozlowski@linaro.org>
Hi,
Am 17.05.24 um 14:51 schrieb Krzysztof Kozlowski:
> Document alreasdy used binding for Syscon / AVS monitor:
s/alreasdy/already excepted of that: Reviewed-by: Stefan Wahren
<wahrenst@gmx.net> Thanks
> brcm,bcm2711-avs-monitor to fix dt_binding_check and dtbs_check warnings
> like:
>
> brcm,avs-ro-thermal.example.dtb: /example-0/avs-monitor@7d5d2000: failed to match any schema with compatible: ['brcm,bcm2711-avs-monitor', 'syscon', 'simple-mfd']
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../soc/bcm/brcm,bcm2711-avs-monitor.yaml | 44 +++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2711-avs-monitor.yaml
>
> diff --git a/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2711-avs-monitor.yaml b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2711-avs-monitor.yaml
> new file mode 100644
> index 000000000000..e02d9d7e7d9a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2711-avs-monitor.yaml
> @@ -0,0 +1,44 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/bcm/brcm,bcm2711-avs-monitor.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom AVS Monitor
> +
> +maintainers:
> + - Stefan Wahren <wahrenst@gmx.net>
> +
> +properties:
> + compatible:
> + items:
> + - const: brcm,bcm2711-avs-monitor
> + - const: syscon
> + - const: simple-mfd
> +
> + reg:
> + maxItems: 1
> +
> + thermal:
> + $ref: /schemas/thermal/brcm,avs-ro-thermal.yaml
> + description: Broadcom AVS ring oscillator thermal
> +
> +required:
> + - compatible
> + - reg
> + - thermal
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + avs-monitor@7d5d2000 {
> + compatible = "brcm,bcm2711-avs-monitor", "syscon", "simple-mfd";
> + reg = <0x7d5d2000 0xf00>;
> +
> + thermal: thermal {
> + compatible = "brcm,bcm2711-thermal";
> + #thermal-sensor-cells = <0>;
> + };
> + };
> +...
prev parent reply other threads:[~2024-05-23 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 12:51 [PATCH] dt-bindings: soc: bcm: document brcm,bcm2711-avs-monitor Krzysztof Kozlowski
2024-05-17 21:27 ` Rob Herring
2024-05-17 22:00 ` Florian Fainelli
2024-05-23 7:24 ` Stefan Wahren [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=be9cc413-6780-45f9-913c-056238be2451@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=robh@kernel.org \
/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