| Message ID | 20220918034415.74641-2-max@maxfierke.com |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
| Series | Introduce ClockworkPi CWD686 DRM panel driver | expand |
| Context | Check | Description |
|---|---|---|
| robh/checkpatch | success | |
| robh/patch-applied | success | |
| robh/dtbs-check | warning | build log |
| robh/dt-meta-schema | success |
Hi Max, On 9/17/22 22:44, Max Fierke wrote: > Add a prefix for Clockwork Tech LLC, known as ClockworkPi. They > produce a number of hobbyist devices, including the ClockworkPi > DevTerm and GameShell. > > Signed-off-by: Max Fierke <max@maxfierke.com> > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > --- > 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 2f0151e9f6be..64f4b899c40c 100644 > --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml > @@ -258,6 +258,8 @@ patternProperties: > description: Cirrus Logic, Inc. > "^cisco,.*": > description: Cisco Systems, Inc. > + "^clockworkpi,.*": > + description: Clockwork Tech LLC The vendor uses "clockwork" as the prefix in their downstream devicetrees[1][2][3], so I would suggest using the same here. I think there is a distinction between "Clockwork" the company and "ClockworkPi" the product. This is what I did for the board devicetree I sent[4]. Regards, Samuel [1]: https://github.com/clockworkpi/DevTerm/blob/main/Code/patch/armbian_build_a04/userpatches/kernel/sunxi-current/kernel_001_dts.patch#L31 [2]: https://github.com/clockworkpi/DevTerm/blob/main/Code/patch/armbian_build_a04/userpatches/kernel/sunxi-current/kernel_001_dts.patch#L127 [3]: https://github.com/clockworkpi/DevTerm/blob/main/Code/patch/armbian_build_a06/patch/kernel-001-a06-dts.patch#L37 [4]: https://lore.kernel.org/lkml/20220815050815.22340-12-samuel@sholland.org/ > "^cloudengines,.*": > description: Cloud Engines, Inc. > "^cnm,.*":
On Sat, Oct 29, 2022, at 1:17 PM, Samuel Holland wrote: > Hi Max, > > The vendor uses "clockwork" as the prefix in their downstream > devicetrees[1][2][3], so I would suggest using the same here. I think > there is a distinction between "Clockwork" the company and "ClockworkPi" > the product. This is what I did for the board devicetree I sent[4]. > > Regards, > Samuel > Hi Samuel, Ah yes, I struggled a bit with the distinction because the company itself seems to be a bit inconsistent here. I will follow your lead and post a v4 follow-up with that vendor prefix changed. Glad to see someone else working on support for this hardware! Thanks, Max
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml index 2f0151e9f6be..64f4b899c40c 100644 --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml @@ -258,6 +258,8 @@ patternProperties: description: Cirrus Logic, Inc. "^cisco,.*": description: Cisco Systems, Inc. + "^clockworkpi,.*": + description: Clockwork Tech LLC "^cloudengines,.*": description: Cloud Engines, Inc. "^cnm,.*":