From: Max Fierke <max@maxfierke.com>
To: thierry.reding@gmail.com, sam@ravnborg.org, airlied@linux.ie,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Max Fierke <max@maxfierke.com>
Subject: [PATCH 1/3] dt-bindings: vendor-prefixes: Add prefix for ClockworkPi
Date: Wed, 1 Jun 2022 00:17:46 -0500 [thread overview]
Message-ID: <20220601051748.1305450-2-max@maxfierke.com> (raw)
In-Reply-To: <20220601051748.1305450-1-max@maxfierke.com>
Add a prefix for Clockwork Tech LLC, known as ClockworkPi. They
produce a number of hobbyist devices, including the ClockworkPi
DevTerm and GameShell.
Signed-off-by: Max Fierke <max@maxfierke.com>
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
index 79b72e370ade..9546d8320224 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -251,6 +251,8 @@ patternProperties:
description: Cirrus Logic, Inc.
"^cisco,.*":
description: Cisco Systems, Inc.
+ "^clockworkpi,.*":
+ description: Clockwork Tech LLC
"^cloudengines,.*":
description: Cloud Engines, Inc.
"^cnm,.*":
--
2.36.1
next prev parent reply other threads:[~2022-06-01 5:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 5:17 [PATCH 0/3] Introduce ClockworkPi CWD686 DRM panel driver Max Fierke
2022-06-01 5:17 ` Max Fierke [this message]
2022-06-01 7:46 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add prefix for ClockworkPi Krzysztof Kozlowski
2022-06-01 5:17 ` [PATCH 2/3] dt-bindings: display: Add bindings for ClockworkPi CWD686 Max Fierke
2022-06-01 7:49 ` Krzysztof Kozlowski
2022-06-01 18:47 ` Rob Herring
2022-06-02 3:51 ` Max Fierke
2022-06-01 5:17 ` [PATCH 3/3] drm: panel: Add driver for ClockworkPi cwd686 panel Max Fierke
2022-06-24 20:57 ` Sam Ravnborg
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=20220601051748.1305450-2-max@maxfierke.com \
--to=max@maxfierke.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).