From: Conor Dooley <conor@kernel.org>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: tsbogend@alpha.franken.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-mips@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mips: lantiq: Document Lantiq Xway GPTU
Date: Thu, 14 Aug 2025 21:50:37 +0100 [thread overview]
Message-ID: <20250814-settling-hamstring-d6a6e957f6c6@spud> (raw)
In-Reply-To: <20250814093704.3197030-1-olek2@wp.pl>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
On Thu, Aug 14, 2025 at 11:36:59AM +0200, Aleksander Jan Bajkowski wrote:
> The Lantiq SoC has six built-in 16-bit general purpose timers (GPTU).
>
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
> .../mips/lantiq/lantiq,gptu-xway.yaml | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mips/lantiq/lantiq,gptu-xway.yaml
>
> diff --git a/Documentation/devicetree/bindings/mips/lantiq/lantiq,gptu-xway.yaml b/Documentation/devicetree/bindings/mips/lantiq/lantiq,gptu-xway.yaml
> new file mode 100644
> index 000000000000..fcfc634dd391
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/lantiq/lantiq,gptu-xway.yaml
> @@ -0,0 +1,39 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mips/lantiq/lantiq,gptu-xway.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Lantiq Xway SoC series General Purpose Timer Unit (GPTU)
"SoC series" implies that you're using the same compatible for multiple
devices. Why are you not using device-specific compatibles?
> +
> +maintainers:
> + - Aleksander Jan Bajkowski <olek2@wp.pl>
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - lantiq,gptu-xway
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + minItems: 6
> + maxItems: 6
And these interrupts are what exactly? I'd rather an items list
explaining what they are tbh.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + gptu@e100a00 {
> + compatible = "lantiq,gptu-xway";
> + reg = <0xe100a00 0x100>;
> + interrupt-parent = <&icu0>;
> + interrupts = <126>, <127>, <128>, <129> ,<130>, <131>;
> + };
> --
> 2.47.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-14 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 9:36 [PATCH 1/2] dt-bindings: mips: lantiq: Document Lantiq Xway GPTU Aleksander Jan Bajkowski
2025-08-14 9:37 ` [PATCH 2/2] mips: lantiq: danube: add missing timer interrupts Aleksander Jan Bajkowski
2025-08-14 20:50 ` Conor Dooley [this message]
2025-08-16 12:04 ` [PATCH 1/2] dt-bindings: mips: lantiq: Document Lantiq Xway GPTU Aleksander Jan Bajkowski
2025-08-18 15:14 ` Conor Dooley
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=20250814-settling-hamstring-d6a6e957f6c6@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).