Skip to contentSkip to conversation

devicetree: Add a registry of vendor prefixes

PATCH In review Grant Likely 3 participants 6 messages Sep 21, 2011 – Sep 22, 2011 3 messages not in the archive Device tree bindings

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 devicetree: Add a registry of vendor prefixes

There is no centralized listing for the in-use vendor prefixes used in compatible strings and property names. This patch adds one. New prefixes should get added to this list to reduce the likelyhood of namespace collisions.

---
 .../devicetree/bindings/vendor-prefixes.txt        |   38 ++++++++++++++++++++
 1 files changed, 38 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/vendor-prefixes.txt
Documentation/devicetree/bindings/vendor-prefixes.txt new file +38 -0
new file mode 100644
index 0000000..81465c1
@@ -0,0 +1,38 @@
+Device tree binding vendor prefix registry.  Keep list in alphabetical order.
+
+This isn't an exhaustive list, but you should add new prefixes to it before
+using them to avoid name-space collisions.
+
+adi	Analog Devices, Inc.
+amcc	Applied Micro Circuits Corporation (APM, formally AMCC)
+apm	Applied Micro Circuits Corporation (APM)
+arm	ARM Ltd.
+chrp	Common Hardware Reference Platform
+dallas	Maxim Integrated Products (formerly Dallas Semiconductor)
+denx	Denx Software Engineering
+epson	Seiko Epson Corp.
+est	ESTeem Wireless Modems
+fsl	Freescale Semiconductor
+GEFanuc	GE Fanuc Intelligent Platforms Embedded Systems, Inc.
+gef	GE Fanuc Intelligent Platforms Embedded Systems, Inc.
+hp	Hewlett Packard
+ibm	International Business Machines (IBM)
+idt	Integrated Device Technologies, Inc.
+intercontrol	Inter Control Group
+linux	Linux-specific binding
+marvell	Marvell Technology Group Ltd.
+maxim	Maxim Integrated Products
+mosaixtech	Mosaix Technologies, Inc.
+national	National Semiconductor
+nintendo	Nintendo
+nvidia	NVIDIA
+nxp	NXP Semiconductors
+powervr	Imagination Technologies
+ramtron	Ramtron International
+samsung	Samsung Semiconductor
+schindler	Schindler
+simtek
+sirf	SiRF Technology, Inc.
+stericsson	ST-Ericsson
+ti	Texas Instruments
+xlnx	Xilinx
#1 lore raw

Documentation/devicetree/bindings/vendor-prefixes.txt line 31

Quoted 7 lines · Grant Likely

There is no centralized listing for the in-use vendor prefixes used in compatible strings and property names. This patch adds one. New prefixes should get added to this list to reduce the likelyhood of namespace collisions.

Documentation/devicetree/bindings/vendor-prefixes.txt new file +2 -0
+powervr	Imagination Technologies
+ramtron	Ramtron International

qcom is already used by the patches I sent out (and should be in the soc tree). I can make a patch for that, but I guess I first need to ask around here for what company name we should use.

David

Signature · 2 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

A message that is not in the archive (sent off-list or not yet received): 20110921203853.GA2824-AOX6H5vLt3Uj8izMo0bVsAC/[email protected]

#3 lore raw
Quoted 6 lines · David Brown
Quoted 5 lines · Grant Likely

There is no centralized listing for the in-use vendor prefixes used in compatible strings and property names. This patch adds one. New prefixes should get added to this list to reduce the likelyhood of namespace collisions.

Quoted 6 lines

Documentation/devicetree/bindings/vendor-prefixes.txt line 31

Quoted 2 lines
Documentation/devicetree/bindings/vendor-prefixes.txt new file +2 -0
+powervr	Imagination Technologies
+ramtron	Ramtron International

qcom is already used by the patches I sent out (and should be in the soc tree). I can make a patch for that, but I guess I first need to ask around here for what company name we should use.

This isn't any kind of "authoritative" list, and it represents who makes the components, not who writes the code. I'll use Qualcomm.

g.

A message that is not in the archive (sent off-list or not yet received): 20110921205336.GD17168-e0URQFbLeQY2iJbIjFUEsiwD8/[email protected]

#5 lore raw
Quoted 14 lines · Grant Likely
Quoted 6 lines · David Brown
Quoted 5 lines · Grant Likely

There is no centralized listing for the in-use vendor prefixes used in compatible strings and property names. This patch adds one. New prefixes should get added to this list to reduce the likelyhood of namespace collisions.

Quoted 6 lines

Documentation/devicetree/bindings/vendor-prefixes.txt line 31

Quoted 2 lines
Documentation/devicetree/bindings/vendor-prefixes.txt new file +2 -0
+powervr	Imagination Technologies
+ramtron	Ramtron International

qcom is already used by the patches I sent out (and should be in the soc tree). I can make a patch for that, but I guess I first need to ask around here for what company name we should use.

Quoted 2 lines

This isn't any kind of "authoritative" list, and it represents who makes the components, not who writes the code. I'll use Qualcomm.

Probably Qualcomm, Inc or Qualcomm Incorporated would be best, but if you make the change (rather than me) it matters less.

David

A message that is not in the archive (sent off-list or not yet received): 20110921225100.GA20726-AOX6H5vLt3Uj8izMo0bVsAC/[email protected]

#7 lore raw
Quoted 15 lines · David Brown
Quoted 14 lines · Grant Likely
Quoted 12 lines · David Brown

Review

Quoted 7 lines · Grant Likely

There is no centralized listing for the in-use vendor prefixes used in compatible strings and property names.  This patch adds one. New prefixes should get added to this list to reduce the likelyhood of namespace collisions.

(quoted diff) +2 -0
+powervr  Imagination Technologies
+ramtron  Ramtron International

qcom is already used by the patches I sent out (and should be in the soc tree).  I can make a patch for that, but I guess I first need to ask around here for what company name we should use.

Quoted 5 lines
Quoted 2 lines

This isn't any kind of "authoritative" list, and it represents who makes the components, not who writes the code.  I'll use Qualcomm.

Probably Qualcomm, Inc or Qualcomm Incorporated would be best, but if you make the change (rather than me) it matters less.

Done.

g.

#8 lore raw
In reply to Grant Likely

Hi Grant,

Le 21/09/2011 17:23, Grant Likely :

Quoted 17 lines

There is no centralized listing for the in-use vendor prefixes used in compatible strings and property names. This patch adds one. New prefixes should get added to this list to reduce the likelyhood of namespace collisions.

---
 .../devicetree/bindings/vendor-prefixes.txt        |   38 ++++++++++++++++++++
 1 files changed, 38 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/vendor-prefixes.txt
Documentation/devicetree/bindings/vendor-prefixes.txt new file +0 -0
new file mode 100644
index 0000000..81465c1

Documentation/devicetree/bindings/vendor-prefixes.txt line 9

Quoted 9 lines
Documentation/devicetree/bindings/vendor-prefixes.txt new file +9 -0
@@ -0,0 +1,38 @@
+Device tree binding vendor prefix registry.  Keep list in alphabetical order.
+
+This isn't an exhaustive list, but you should add new prefixes to it before
+using them to avoid name-space collisions.
+
+adi	Analog Devices, Inc.
+amcc	Applied Micro Circuits Corporation (APM, formally AMCC)
+apm	Applied Micro Circuits Corporation (APM)
+arm	ARM Ltd.

Can we add:
+atmel Atmel Corporation

I am working on a revival of patches that I have cooked at Linaro Connect for AT91...

Best regards,

Signature · 1 line
Nicolas Ferre