Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	tsbogend@alpha.franken.de, john@phrozen.org,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: mips: lantiq: Document Lantiq Xway GPTU
Date: Mon, 18 Aug 2025 18:38:24 +0100	[thread overview]
Message-ID: <20250818-departure-gloss-b99cacb9401e@spud> (raw)
In-Reply-To: <20250816132002.3632343-2-olek2@wp.pl>

[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]

On Sat, Aug 16, 2025 at 03:16:22PM +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         | 67 +++++++++++++++++++
>  1 file changed, 67 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..fcbcd98def46
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/lantiq/lantiq,gptu-xway.yaml
> @@ -0,0 +1,67 @@
> +# 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)
> +
> +maintainers:
> +  - Aleksander Jan Bajkowski <olek2@wp.pl>
> +
> +description:
> +  The Lantiq SoC has six built-in 16-bit general purpose timers. The voice
> +  firmware needs these timers as a reference.
> +
> +properties:
> +  $nodename:
> +    pattern: "^gptu@[0-9a-f]+$"

This is a timer, why are you not using "timer" as the prefix?
Otherwise, this looks okay to me other than...

> +
> +  compatible:
> +    items:
> +      - enum:
> +          - lantiq,ase-gptu
> +          - lantiq,danube-gptu
> +          - lantiq,xrx100-gptu
> +          - lantiq,xrx200-gptu
> +      - const: lantiq,gptu-xway

..the fact that my OCD hates how the fallback inverts the position of
gptu in the compatible!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-08-18 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 13:16 [PATCH v2 0/3] dt-bindings: mips: lantiq: Document Lantiq Xway GPTU Aleksander Jan Bajkowski
2025-08-16 13:16 ` [PATCH v2 1/3] " Aleksander Jan Bajkowski
2025-08-18 17:38   ` Conor Dooley [this message]
2025-08-19  9:15     ` Krzysztof Kozlowski
2025-08-16 13:16 ` [PATCH v2 2/3] mips: lantiq: danube: add missing timer interrupts Aleksander Jan Bajkowski
2025-08-16 13:16 ` [PATCH v2 3/3] mips: lantiq: danube: add device-specified compatible in GPTU node Aleksander Jan Bajkowski

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=20250818-departure-gloss-b99cacb9401e@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=john@phrozen.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