* arc vendor prefix
@ 2018-09-19 1:05 Brian Dodge
2018-09-20 12:09 ` Alan Cox
0 siblings, 1 reply; 3+ messages in thread
From: Brian Dodge @ 2018-09-19 1:05 UTC (permalink / raw)
To: devicetree, linux-kernel
Hi,
In the linux kernel commit 91ab076e3a2f092254fe5231bbfa92b37fd52e38 the
vendor prefix "arctic" was added to vendor-prefixes.txt.
The original change I authored used "arc" not "arctic", and the device
tree bindings were added assuming that prefix in commit
ce9d22573d85341c987f997461ac712e4dbe47b1
Perhaps odeju changed the name to arctic in the patch after I created it
and before it was approved.
This pairing isn't really compatible is it? Either the prefix should be
reverted to "arc" or the bindings (and driver source) changed to use
"arctic", as in "arctic,arc2c0608" vs. "arc,arc2c0608"
The arcticsand company is now part of psemi (formerly peregrine
semiconductor) and they would like to keep using the arc prefix for
these chips and in the driver and I plan on changing the
vendor-prefix.txt to reflect that.
I am in the process of updating the driver code to support different and
new variants of the chip and would like to know what the preference is
for this prefix going forward.
Thank you
Brian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: arc vendor prefix
2018-09-19 1:05 arc vendor prefix Brian Dodge
@ 2018-09-20 12:09 ` Alan Cox
2018-09-25 15:23 ` Rob Herring
0 siblings, 1 reply; 3+ messages in thread
From: Alan Cox @ 2018-09-20 12:09 UTC (permalink / raw)
To: Brian Dodge; +Cc: devicetree, linux-kernel
On Tue, 18 Sep 2018 21:05:20 -0400
Brian Dodge <bdodge09@gmail.com> wrote:
> Hi,
>
> In the linux kernel commit 91ab076e3a2f092254fe5231bbfa92b37fd52e38 the
> vendor prefix "arctic" was added to vendor-prefixes.txt.
>
> The original change I authored used "arc" not "arctic", and the device
> tree bindings were added assuming that prefix in commit
> ce9d22573d85341c987f997461ac712e4dbe47b1
>
> Perhaps odeju changed the name to arctic in the patch after I created it
> and before it was approved.
>
> This pairing isn't really compatible is it? Either the prefix should be
> reverted to "arc" or the bindings (and driver source) changed to use
> "arctic", as in "arctic,arc2c0608" vs. "arc,arc2c0608"
ARC is a Synopsys registered trademark for the ARC processor line. I'm not
sure what the right answer is but I think it might be better to keep to
arctic to avoid confusion with arc based products.
Alan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: arc vendor prefix
2018-09-20 12:09 ` Alan Cox
@ 2018-09-25 15:23 ` Rob Herring
0 siblings, 0 replies; 3+ messages in thread
From: Rob Herring @ 2018-09-25 15:23 UTC (permalink / raw)
To: Alan Cox; +Cc: Brian Dodge, devicetree, linux-kernel
On Thu, Sep 20, 2018 at 01:09:52PM +0100, Alan Cox wrote:
> On Tue, 18 Sep 2018 21:05:20 -0400
> Brian Dodge <bdodge09@gmail.com> wrote:
>
> > Hi,
> >
> > In the linux kernel commit 91ab076e3a2f092254fe5231bbfa92b37fd52e38 the
> > vendor prefix "arctic" was added to vendor-prefixes.txt.
> >
> > The original change I authored used "arc" not "arctic", and the device
> > tree bindings were added assuming that prefix in commit
> > ce9d22573d85341c987f997461ac712e4dbe47b1
> >
> > Perhaps odeju changed the name to arctic in the patch after I created it
> > and before it was approved.
> >
> > This pairing isn't really compatible is it? Either the prefix should be
> > reverted to "arc" or the bindings (and driver source) changed to use
> > "arctic", as in "arctic,arc2c0608" vs. "arc,arc2c0608"
>
> ARC is a Synopsys registered trademark for the ARC processor line. I'm not
> sure what the right answer is but I think it might be better to keep to
> arctic to avoid confusion with arc based products.
Agreed.
Rob
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-09-25 15:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-09-19 1:05 arc vendor prefix Brian Dodge
2018-09-20 12:09 ` Alan Cox
2018-09-25 15:23 ` Rob Herring
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).