From: Lubomir Rintel <lkundrak@v3.sk>
To: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@siol.net>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Lubomir Rintel <lkundrak@v3.sk>, Rob Herring <robh@kernel.org>
Subject: [PATCH v4 1/3] dt-bindings: Add vendor prefix for Chrontel, Inc.
Date: Tue, 24 Mar 2020 16:19:29 +0100 [thread overview]
Message-ID: <20200324151931.449985-2-lkundrak@v3.sk> (raw)
In-Reply-To: <20200324151931.449985-1-lkundrak@v3.sk>
Chrontel makes encoders for video displays and perhaps other stuff.
Their web site is http://www.chrontel.com/.
Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
Acked-by: Rob Herring <robh@kernel.org>
---
Changes since v1:
- Collect Rob's ack
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 a2da166df1bc7..0ab86d876f4d2 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -185,6 +185,8 @@ patternProperties:
description: ChipOne
"^chipspark,.*":
description: ChipSPARK
+ "^chrontel,.*":
+ description: Chrontel, Inc.
"^chrp,.*":
description: Common Hardware Reference Platform
"^chunghwa,.*":
--
2.26.0.rc2
next prev parent reply other threads:[~2020-03-24 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 15:19 [PATCH v4 0/3] drm: Add support for Chrontel CH7033 VGA/DVI Encoder Lubomir Rintel
2020-03-24 15:19 ` Lubomir Rintel [this message]
2020-03-24 15:19 ` [PATCH v4 2/3] dt-bindings: display: Add Chrontel CH7033 Video Encoder binding Lubomir Rintel
2020-03-24 15:19 ` [PATCH v4 3/3] drm/bridge: chrontel-ch7033: Add a new driver Lubomir Rintel
2020-04-21 12:54 ` Daniel Vetter
2020-04-21 12:57 ` Daniel Vetter
2020-04-23 21:18 ` Lubomir Rintel
2020-04-28 10:09 ` Daniel Vetter
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=20200324151931.449985-2-lkundrak@v3.sk \
--to=lkundrak@v3.sk \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh@kernel.org \
/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).