All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shankari Anand <shankari.ak0208@gmail.com>, devicetree@vger.kernel.org
Cc: "Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"William Zhang" <william.zhang@broadcom.com>,
	"Anand Gore" <anand.gore@broadcom.com>,
	"Kursad Oney" <kursad.oney@broadcom.com>,
	"Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"Broadcom internal kernel review list"
	<bcm-kernel-feedback-list@broadcom.com>,
	"Rob Herring" <robh@kernel.org>,
	skhan@linuxfoundation.org
Subject: Re: [PATCH] dt-bindings: arm/bcm: Fix and validate brcm,bcm63138 bindings with no errors
Date: Mon, 26 May 2025 06:01:52 +0200	[thread overview]
Message-ID: <fa348395-0526-4485-aea6-fd34f51a4cef@kernel.org> (raw)
In-Reply-To: <20250525194333.1729443-1-shankari.ak0208@gmail.com>

On 25/05/2025 21:43, Shankari Anand wrote:
> Fix and validate brcm,bcm63138 device tree bindings by correcting schema and example files.

Nothing like that is done here.

> This resolves previous schema validation errors and ensures compliance with devicetree core schema requirements.

Which errors?

> The patch passes dtbs check successfully, confirming the YAML bindings, example DTS, and generated DTB are error-free.

Drop, redundant.

Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597

> 
> Signed-off-by: Shankari Anand <shankari.ak0208@gmail.com>
> ---
>  .../bindings/arm/bcm/brcm,bcm63138.yaml       | 43 +++++++++++++++++++	
>  1 file changed, 43 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.yaml
> 
> diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.yaml b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.yaml
> new file mode 100644
> index 000000000000..5848f96128e1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.yaml
> @@ -0,0 +1,43 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/bcm/brcm,bcm63138.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom BCM63138 DSL SoC
> +
> +maintainers:
> +  - Shankari Anand <shankari.ak0208@gmail.com>
> +
> +description: |
> +  The Broadcom BCM63138 DSL System-on-a-Chip is designed for DSL platforms.
> +  It supports multi-core ARM Cortex-A9 CPUs, a boot lookup table (BootLUT),
> +  and software-controlled resets using a system timer.
> +
> +select:
> +  properties:
> +    compatible:
> +      contains:
> +        const: brcm,bcm63138
> +  required:
> +    - compatible
> +
> +properties:
> +  compatible:
> +    const: brcm,bcm63138

You are duplicating existing bindings - both TXT and schema. Maybe you
wanted to do the conversion, but that's still duplication.

> +
> +patternProperties:
> +  "^bootlut(@[0-9a-f]+)?$":
> +    type: object
> +    properties:
> +      compatible:
> +        const: brcm,bcm63138-bootlut
> +
> +      reg:
> +        maxItems: 1
> +
> +    required:
> +      - compatible
> +      - reg
> +
> +additionalProperties: true

No, this cannot be true. Look at other bindings... or is it soc/platform
file? I really do not understand what you want to achieve here.


Best regards,
Krzysztof

  reply	other threads:[~2025-05-26  4:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25 19:43 [PATCH] dt-bindings: arm/bcm: Fix and validate brcm,bcm63138 bindings with no errors Shankari Anand
2025-05-26  4:01 ` Krzysztof Kozlowski [this message]
2025-05-27 21:43   ` William Zhang
     [not found]     ` <CAPRMd3nyaV5fWYP_iY7XxgfzCDLUTpqHR0ebb0dSQ68tmEM62w@mail.gmail.com>
2025-06-08 18:40       ` Shankari Anand
     [not found]         ` <CAPRMd3n733TzxJMo1JooHBavSnjN=AWT_hKV38LOeZBpPHrnrw@mail.gmail.com>
2025-06-08 18:42           ` Shankari Anand
  -- strict thread matches above, loose matches on Subject: below --
2025-05-31 21:38 kernel test robot

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=fa348395-0526-4485-aea6-fd34f51a4cef@kernel.org \
    --to=krzk@kernel.org \
    --cc=anand.gore@broadcom.com \
    --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=kursad.oney@broadcom.com \
    --cc=rafal@milecki.pl \
    --cc=robh@kernel.org \
    --cc=shankari.ak0208@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=william.zhang@broadcom.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.