mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bhargav Joshi <j.bhargav.u@gmail.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	 Andreas Kemnade <andreas@kemnade.info>,
	Kevin Hilman <khilman@baylibre.com>,
	 Roger Quadros <rogerq@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	 Mark Jackson <mpfj@newflow.co.uk>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-omap@vger.kernel.org,
	Bhargav Joshi <j.bhargav.u@gmail.com>
Subject: [PATCH 1/7] dt-bindings: vendor-prefixes: add eets and newflow
Date: Wed, 11 Nov 2026 01:22:31 +0530	[thread overview]
Message-ID: <20261111-ti-omap-dts-fix-v1-1-19022d1ff4b4@gmail.com> (raw)
In-Reply-To: <20261111-ti-omap-dts-fix-v1-0-19022d1ff4b4@gmail.com>

Add vendor prefixes for EETS GmbH ("eets") and Newflow Ltd ("newflow").
These prefixes are needed to document the compatibles for the in-tree
AM335x PDU001 and AM335x NanoBone boards.

Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
 Documentation/devicetree/bindings/vendor-prefixes.yaml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
index 5471a06f93f10..447f1424bf9c8 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -505,6 +505,8 @@ patternProperties:
     description: Emtop Embedded Solutions
   "^eeti,.*":
     description: eGalax_eMPIA Technology Inc
+  "^eets,.*":
+    description: EETS GmbH
   "^efinix,.*":
     description: Efinix, Inc.
   "^egnite,.*":
@@ -1198,6 +1200,8 @@ patternProperties:
     description: Shenzhen Netxeon Technology CO., LTD
   "^neweast,.*":
     description: Guangdong Neweast Optoelectronics CO., LTD
+  "^newflow,.*":
+    description: Newflow Ltd
   "^newhaven,.*":
     description: Newhaven Display International
   "^newvision,.*":

-- 
2.56.0


  reply	other threads:[~2026-11-10 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 19:52 [PATCH 0/7] ARM: dts: ti: omap: fix dtbs_check warnings for omap binding Bhargav Joshi
2026-11-10 19:52 ` Bhargav Joshi [this message]
2026-11-10 19:52 ` [PATCH 2/7] dt-bindings: arm: omap: document missing AM33xx boards and SoMs Bhargav Joshi
2026-11-10 19:52 ` [PATCH 3/7] dt-bindings: arm: omap: document BeagleBone family board compatibles Bhargav Joshi
2026-11-10 19:52 ` [PATCH 4/7] dt-bindings: arm: omap: document missing OMAP3, AM35, and OMAP5 boards Bhargav Joshi
2026-11-10 19:52 ` [PATCH 5/7] ARM: dts: ti: omap: am335x: add board compatibles for nano and pdu001 Bhargav Joshi
2026-11-10 19:52 ` [PATCH 6/7] ARM: dts: ti: omap: omap4-panda-es: drop redundant fallback compatibles Bhargav Joshi
2026-11-10 19:52 ` [PATCH 7/7] ARM: dts: ti: omap: omap3: drop redundant ti,omap34xx compatible Bhargav Joshi

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=20261111-ti-omap-dts-fix-v1-1-19022d1ff4b4@gmail.com \
    --to=j.bhargav.u@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mpfj@newflow.co.uk \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.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

all inboxes | Powered by JetHome®