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] dt-bindings: mips: lantiq: Document Lantiq Xway VMMC
Date: Thu, 14 Aug 2025 21:53:14 +0100 [thread overview]
Message-ID: <20250814-extended-collector-8335abee820d@spud> (raw)
In-Reply-To: <20250814161748.3230278-1-olek2@wp.pl>
[-- Attachment #1: Type: text/plain, Size: 2562 bytes --]
On Thu, Aug 14, 2025 at 06:17:45PM +0200, Aleksander Jan Bajkowski wrote:
> The Lantiq SoCs have a 2nd mips core called "voice mips macro core (vmmc)"
> which is used to run the voice firmware.
>
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
> .../mips/lantiq/lantiq,vmmc-xway.yaml | 51 +++++++++++++++++++
> 1 file changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mips/lantiq/lantiq,vmmc-xway.yaml
>
> diff --git a/Documentation/devicetree/bindings/mips/lantiq/lantiq,vmmc-xway.yaml b/Documentation/devicetree/bindings/mips/lantiq/lantiq,vmmc-xway.yaml
> new file mode 100644
> index 000000000000..bee64f6d0e97
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/lantiq/lantiq,vmmc-xway.yaml
> @@ -0,0 +1,51 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mips/lantiq/lantiq,vmmc-xway.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Lantiq VMMC (Voice MIPS Macro Core)
> +
> +maintainers:
> + - Aleksander Jan Bajkowski <olek2@wp.pl>
> +
> +description:
> + The Lantiq SoCs have a 2nd mips core called "Voice MIPS Macro Core (VMMC)"
> + which is used to run the voice firmware. The firmware handles analog
> + telephone lines.
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - lantiq,vmmc-xway
Same comment here as elsewhere, the commit message seems to suggest that
you're trying to use one compatible for multiple devices. Not using
soc-specific compatibles requires justification if that's what you're
doing as they are the norm.
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + minItems: 6
> + maxItems: 6
Same comment here as elsewhere re: items list explaining each item.
> +
> + gpios: true
What are these gpios? You've got 3 below, what portion of those three
are required? How many mix/max?
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + vmmc@107000 {
> + compatible = "lantiq,vmmc-xway";
> + reg = <0x107000 0x300>;
> + interrupt-parent = <&icu0>;
> + interrupts = <150>, <151>, <152>, <153>, <154>, <155>;
> + gpios = <&gpio 30 GPIO_ACTIVE_HIGH
> + &gpio 31 GPIO_ACTIVE_HIGH
> + &gpio 3 GPIO_ACTIVE_HIGH>;
> +
> + };
> --
> 2.47.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-08-14 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 16:17 [PATCH] dt-bindings: mips: lantiq: Document Lantiq Xway VMMC Aleksander Jan Bajkowski
2025-08-14 20:53 ` Conor Dooley [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=20250814-extended-collector-8335abee820d@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