On Sat, 2020-11-07 at 09:03 -0500, Sean Anderson wrote: > On 11/7/20 3:14 AM, Damien Le Moal wrote: > > Update Documentation/devicetree/bindings/vendor-prefixes.yaml to include > > "Kendryte" and "canaan" as a vendor prefix for "Canaan Inc." > > > > Signed-off-by: Damien Le Moal <damien.lemoal@xxxxxxx> > > --- > > 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 2735be1a8470..f53d4d8e7f2a 100644 > > --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml > > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml > > @@ -179,6 +179,8 @@ patternProperties: > > description: CALAO Systems SAS > > "^calxeda,.*": > > description: Calxeda > > + "^canaan,.*": > > + description: Canaan, Inc. > > "^caninos,.*": > > description: Caninos Loucos Program > > "^capella,.*": > > @@ -537,6 +539,8 @@ patternProperties: > > description: Ka-Ro electronics GmbH > > "^keithkoep,.*": > > description: Keith & Koep GmbH > > + "^kendryte,.*": > > + description: Canaan, Inc. > > "^keymile,.*": > > description: Keymile GmbH > > "^khadas,.*": > > > > So AFAIK Canaan is the company, and Kendryte is the brand. However, I > was unaware of this when I did my initial porting work. So all the > compatible strings like "kendryte,k210-foo" should really be > "canaan,kendryte-k210-foo". These _should_ all get fixed in the device > tree, but no one has done it yet. I fixed everything using "canaan,k210-foo", a little shorter than "canaan,kendryte-k210-foo" (The "k" in k210 already probably standing for Kendryte...). But I can use the longer version too. Will I was at it, I also changed directory names and config option names to also use canaan/CANAAN instead of kendryte/KENDRYTE. > > --Sean -- Damien Le Moal Western Digital
