From: Jagan Teki <jagan@edgeble.ai>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>
Cc: devicetree@vger.kernel.org, Jagan Teki <jagan@edgeble.ai>
Subject: [PATCH 2/4] dt-bindings: vendor-prefixes: Document Jadard
Date: Wed, 24 Aug 2022 00:12:40 +0530 [thread overview]
Message-ID: <20220823184242.3554472-2-jagan@edgeble.ai> (raw)
In-Reply-To: <20220823184242.3554472-1-jagan@edgeble.ai>
Jadard Technology Inc. manufactures and distributes chips
from Shenzhen.
Add vendor prefix for it.
Signed-off-by: Jagan Teki <jagan@edgeble.ai>
---
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 e8ee5084cb89..6ac4c1fc09c4 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -637,6 +637,8 @@ patternProperties:
description: ITian Corporation
"^iwave,.*":
description: iWave Systems Technologies Pvt. Ltd.
+ "^jadard,.*":
+ description: Jadard Technology Inc.
"^jdi,.*":
description: Japan Display Inc.
"^jedec,.*":
--
2.25.1
next prev parent reply other threads:[~2022-08-23 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 18:42 [PATCH 1/4] dt-bindings: vendor-prefixes: Document Chongzhou Jagan Teki
2022-08-23 18:42 ` Jagan Teki [this message]
2022-08-24 13:30 ` [PATCH 2/4] dt-bindings: vendor-prefixes: Document Jadard Krzysztof Kozlowski
2022-08-23 18:42 ` [PATCH 3/4] dt-bindings: display: Document Jadard JD9365DA-H3 DSI panel Jagan Teki
2022-08-24 13:32 ` Krzysztof Kozlowski
2022-08-23 18:42 ` [PATCH 4/4] drm: panel: Add " Jagan Teki
2022-08-24 13:39 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Document Chongzhou Krzysztof Kozlowski
2022-08-25 19:40 ` Jagan Teki
2022-08-26 6:00 ` Krzysztof Kozlowski
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=20220823184242.3554472-2-jagan@edgeble.ai \
--to=jagan@edgeble.ai \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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).