| Message ID | 20240216025839.902288-1-robh@kernel.org |
|---|---|
| State | Accepted |
| Headers | show |
| Series | dt-bindings: vendor-prefixes: Add missing prefixes used in compatibles | expand |
| Context | Check | Description |
|---|---|---|
| robh/checkpatch | success | |
| robh/patch-applied | success | |
| robh/dtbs-check | warning | build log |
| robh/dt-meta-schema | success |
On 16/02/2024 03:58, Rob Herring wrote: > A new check for vendor-prefixes used in compatibles finds some missing > ones. Add the missing ones already in use. > > This omits some ancient prefixes in powerpc and arm32 as there are a > bunch of out of business one-offs that take too much time to track down > who they were. > > Signed-off-by: Rob Herring <robh@kernel.org> > --- Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
On Thu, Feb 15, 2024 at 08:58:29PM -0600, Rob Herring wrote: > + "^calao,.*": > + description: CALAO Systems SAS > "^calaosystems,.*": > description: CALAO Systems SAS > + "^IBM,.*": > + description: International Business Machines (IBM) > "^ibm,.*": > description: International Business Machines (IBM) These ones add duplicates with no indication of which one is to be used going forward. Why not mark one as deprecated?
On Fri, Feb 16, 2024 at 08:59:56AM +0000, Conor Dooley wrote: > On Thu, Feb 15, 2024 at 08:58:29PM -0600, Rob Herring wrote: > > + "^calao,.*": > > + description: CALAO Systems SAS > > "^calaosystems,.*": > > description: CALAO Systems SAS > > > + "^IBM,.*": > > + description: International Business Machines (IBM) > > "^ibm,.*": > > description: International Business Machines (IBM) > > These ones add duplicates with no indication of which one is to be used > going forward. Why not mark one as deprecated? Because I couldn't decide which... It's a mixture with no clear pattern of on what or when each one is used. Power is kind of special. Rob
On Tue, Feb 20, 2024 at 09:38:45AM -0700, Rob Herring wrote: > On Fri, Feb 16, 2024 at 08:59:56AM +0000, Conor Dooley wrote: > > On Thu, Feb 15, 2024 at 08:58:29PM -0600, Rob Herring wrote: > > > + "^calao,.*": > > > + description: CALAO Systems SAS > > > "^calaosystems,.*": > > > description: CALAO Systems SAS > > > > > + "^IBM,.*": > > > + description: International Business Machines (IBM) > > > "^ibm,.*": > > > description: International Business Machines (IBM) > > > > These ones add duplicates with no indication of which one is to be used > > going forward. Why not mark one as deprecated? > > Because I couldn't decide which... It's a mixture with no clear pattern > of on what or when each one is used. Power is kind of special. That might be true for ibm, but is it true for calao systems? The website appears to now be something to do with Korean gambling, but the twitter remains and looks to have produced arm sbcs: https://twitter.com/calaosystems?lang=en
On Tue, Feb 20, 2024 at 05:51:37PM +0000, Conor Dooley wrote: > On Tue, Feb 20, 2024 at 09:38:45AM -0700, Rob Herring wrote: > > On Fri, Feb 16, 2024 at 08:59:56AM +0000, Conor Dooley wrote: > > > On Thu, Feb 15, 2024 at 08:58:29PM -0600, Rob Herring wrote: > > > > + "^calao,.*": > > > > + description: CALAO Systems SAS > > > > "^calaosystems,.*": > > > > description: CALAO Systems SAS > > > > > > > + "^IBM,.*": > > > > + description: International Business Machines (IBM) > > > > "^ibm,.*": > > > > description: International Business Machines (IBM) > > > > > > These ones add duplicates with no indication of which one is to be used > > > going forward. Why not mark one as deprecated? > > > > Because I couldn't decide which... It's a mixture with no clear pattern > > of on what or when each one is used. Power is kind of special. > > That might be true for ibm, but is it true for calao systems? > The website appears to now be something to do with Korean gambling, but > the twitter remains and looks to have produced arm sbcs: > https://twitter.com/calaosystems?lang=en I used this: https://en.wikipedia.org/wiki/Calao_Systems The company went bankrupt in 2016. ST based systems used one prefix and Atmel based systems used the other. Which do I pick to deprecate? I'm not expecting any new boards either. Rob
On Wed, Feb 21, 2024 at 08:03:03AM -0700, Rob Herring wrote: > On Tue, Feb 20, 2024 at 05:51:37PM +0000, Conor Dooley wrote: > > On Tue, Feb 20, 2024 at 09:38:45AM -0700, Rob Herring wrote: > > > On Fri, Feb 16, 2024 at 08:59:56AM +0000, Conor Dooley wrote: > > > > On Thu, Feb 15, 2024 at 08:58:29PM -0600, Rob Herring wrote: > > > > > + "^calao,.*": > > > > > + description: CALAO Systems SAS > > > > > "^calaosystems,.*": > > > > > description: CALAO Systems SAS > > > > > > > > > + "^IBM,.*": > > > > > + description: International Business Machines (IBM) > > > > > "^ibm,.*": > > > > > description: International Business Machines (IBM) > > > > > > > > These ones add duplicates with no indication of which one is to be used > > > > going forward. Why not mark one as deprecated? > > > > > > Because I couldn't decide which... It's a mixture with no clear pattern > > > of on what or when each one is used. Power is kind of special. > > > > That might be true for ibm, but is it true for calao systems? > > The website appears to now be something to do with Korean gambling, but > > the twitter remains and looks to have produced arm sbcs: > > https://twitter.com/calaosystems?lang=en > > I used this: > > https://en.wikipedia.org/wiki/Calao_Systems > > The company went bankrupt in 2016. Yah. I found the twitter to provide more info about the type of chips they used than wikipedia though, since I was trying to confirm whether or not they were power. > ST based systems used one prefix and > Atmel based systems used the other. Which do I pick to deprecate? I'm > not expecting any new boards either. I guess, if nothing new will show up since the company itself got deprecated, it doesn;t really matter.
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml index 1a0dc04f1db4..08d5d63cb646 100644 --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml @@ -230,6 +230,8 @@ patternProperties: description: ByteDance Ltd. "^calamp,.*": description: CalAmp Corp. + "^calao,.*": + description: CALAO Systems SAS "^calaosystems,.*": description: CALAO Systems SAS "^calxeda,.*": @@ -478,6 +480,9 @@ patternProperties: description: EZchip Semiconductor "^facebook,.*": description: Facebook + "^fairchild,.*": + description: Fairchild Semiconductor (deprecated, use 'onnn') + deprecated: true "^fairphone,.*": description: Fairphone B.V. "^faraday,.*": @@ -542,6 +547,8 @@ patternProperties: description: Giantec Semiconductor, Inc. "^giantplus,.*": description: Giantplus Technology Co., Ltd. + "^glinet,.*": + description: GL Intelligence, Inc. "^globalscale,.*": description: Globalscale Technologies, Inc. "^globaltop,.*": @@ -601,6 +608,8 @@ patternProperties: description: Honestar Technologies Co., Ltd. "^honeywell,.*": description: Honeywell + "^hoperf,.*": + description: Shenzhen Hope Microelectronics Co., Ltd. "^hoperun,.*": description: Jiangsu HopeRun Software Co., Ltd. "^hp,.*": @@ -631,12 +640,16 @@ patternProperties: description: Hyundai Technology "^i2se,.*": description: I2SE GmbH + "^IBM,.*": + description: International Business Machines (IBM) "^ibm,.*": description: International Business Machines (IBM) "^icplus,.*": description: IC Plus Corp. "^idt,.*": description: Integrated Device Technologies, Inc. + "^iei,.*": + description: IEI Integration Corp. "^ifi,.*": description: Ingenieurburo Fur Ic-Technologie (I/F/I) "^ilitek,.*": @@ -821,6 +834,8 @@ patternProperties: description: LSI Corp. (LSI Logic) "^lunzn,.*": description: Shenzhen Lunzn Technology Co., Ltd. + "^luxul,.*": + description: Lagrand | AV "^lwn,.*": description: Liebherr-Werk Nenzing GmbH "^lxa,.*": @@ -899,6 +914,9 @@ patternProperties: description: Miniand Tech "^minix,.*": description: MINIX Technology Ltd. + "^mips,.*": + description: MIPS Technology (deprecated, use 'mti' or 'img') + deprecated: true "^miramems,.*": description: MiraMEMS Sensing Technology Co., Ltd. "^mitsubishi,.*": @@ -993,6 +1011,9 @@ patternProperties: description: Novatek "^novtech,.*": description: NovTech, Inc. + "^numonyx,.*": + description: Numonyx (deprecated, use micron) + deprecated: true "^nutsboard,.*": description: NutsBoard "^nuvoton,.*": @@ -1536,8 +1557,12 @@ patternProperties: description: Voipac Technologies s.r.o. "^vot,.*": description: Vision Optical Technology Co., Ltd. + "^vscom,.*": + description: VS Visions Systems GmbH "^vxt,.*": description: VXT Ltd + "^wacom,.*": + description: Wacom "^wanchanglong,.*": description: Wanchanglong Electronics Technology（SHENZHEN）Co.，Ltd. "^wand,.*":
A new check for vendor-prefixes used in compatibles finds some missing ones. Add the missing ones already in use. This omits some ancient prefixes in powerpc and arm32 as there are a bunch of out of business one-offs that take too much time to track down who they were. Signed-off-by: Rob Herring <robh@kernel.org> --- .../devicetree/bindings/vendor-prefixes.yaml | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+)