From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: tsbogend@alpha.franken.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, olek2@wp.pl, linux-mips@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] dt-bindings: mips: lantiq: Document Lantiq Xway VMMC
Date: Thu, 14 Aug 2025 18:17:45 +0200 [thread overview]
Message-ID: <20250814161748.3230278-1-olek2@wp.pl> (raw)
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
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ minItems: 6
+ maxItems: 6
+
+ gpios: true
+
+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
next reply other threads:[~2025-08-14 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 16:17 Aleksander Jan Bajkowski [this message]
2025-08-14 20:53 ` [PATCH] dt-bindings: mips: lantiq: Document Lantiq Xway VMMC 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=20250814161748.3230278-1-olek2@wp.pl \
--to=olek2@wp.pl \
--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=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 read-only IMAP folder(s) and NNTP newsgroup(s).