From: Krzysztof Kozlowski <krzk@kernel.org>
To: V.Yurkov.EXT@bruker.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Vyacheslav Yurkov <uvv.mail@gmail.com>
Subject: Re: [PATCH 1/2] dt-bindings: bus: Add binding for Altera AXI Timeout Bridge
Date: Sat, 3 Oct 2026 23:18:27 +0200 [thread overview]
Message-ID: <eeb7c9d4-ed3e-4b94-a590-0fcff1998971@kernel.org> (raw)
In-Reply-To: <20261003-feature-timeout-ip-v1-1-8837c311d571@bruker.com>
On 03/10/2026 22:19, Vyacheslav Yurkov via B4 Relay wrote:
> From: Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
>
> Add a device tree binding for the Altera timeout bridge, which connects
> an Avalon bus to the HPS and provides an address space for child
> devices with a fall back to a simple bus.
>
> Signed-off-by: Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
> ---
> .../bindings/bus/altera-timeout-bridge.yaml | 82 ++++++++++++++++++++++
Filename must match compatible and compatible has completely broken
format. Please look at DT spec or any other examples how compatibles are
created.
> 1 file changed, 82 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/bus/altera-timeout-bridge.yaml b/Documentation/devicetree/bindings/bus/altera-timeout-bridge.yaml
> new file mode 100644
> index 000000000000..b57a0966ba6e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/altera-timeout-bridge.yaml
> @@ -0,0 +1,82 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/bus/altera-timeout-bridge.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Altera Timeout Bridge
> +
> +maintainers:
> + - Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
> +
> +description: |
> + Altera timeout bridge bus.
Useless description. You keep repeating the same.
> +
> +properties:
> + compatible:
> + items:
> + - const: altera-timeout-bridge
> + - const: simple-bus
Why the fallback?
Your commit msg is also useless here, you just wrote what you did, not why.
I see no reason why generic "bus" like that should stay generic,
although you have entire commit msg to explain why this is different or
what is the versioning of this IP block.
Missing blank line.
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + ranges: true
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - interrupt-parent
> + - ranges
> + - "#address-cells"
> + - "#size-cells"
> +
> +patternProperties:
This follows properties.
> + "^[a-zA-Z][a-zA-Z0-9,+._-]*@[0-9a-f]+$":
> + type: object
> + description: |
> + Device connected to the timeout bridge.
> +
> + required:
> + - compatible
> + - reg
> +
> + additionalProperties: true
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + intc: interrupt-controller {
> + interrupt-controller;
> + #interrupt-cells = <3>;
> + };
Drop, irrelevant
> +
> + timeout_bridge_hps@10000 {
Really, this is the style you send? So the toolset - dt-check-style - or
the Coding style mean nothing and you keep sending what you have in
downstream.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-03 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 20:19 [PATCH 0/2] Add Altera timeout bridge driver Vyacheslav Yurkov via B4 Relay
2026-10-03 20:19 ` [PATCH 1/2] dt-bindings: bus: Add binding for Altera AXI Timeout Bridge Vyacheslav Yurkov via B4 Relay
2026-10-03 21:18 ` Krzysztof Kozlowski [this message]
2026-10-03 20:19 ` [PATCH 2/2] bus: add Altera timeout bridge driver Vyacheslav Yurkov via B4 Relay
2026-10-03 21:24 ` Krzysztof Kozlowski
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=eeb7c9d4-ed3e-4b94-a590-0fcff1998971@kernel.org \
--to=krzk@kernel.org \
--cc=V.Yurkov.EXT@bruker.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=uvv.mail@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®