mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@collabora.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: kernel@collabora.com, Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: add MSC Technologies
Date: Thu, 21 Jul 2022 09:03:56 +0100	[thread overview]
Message-ID: <86de8ba0157c451fcce4ca92b6cad835e3f1e4d9.camel@collabora.com> (raw)
In-Reply-To: <abd47815-c84b-115b-f6f2-b6ec0dbf1bef@linaro.org>

On Wed, 2022-07-20 at 19:07 +0200, Krzysztof Kozlowski wrote:
> On 20/07/2022 17:00, Martyn Welch wrote:
> > Add "msc" vendor prefix for MSC Technologies GmbH
> > (https://www.msc-technologies.eu).
> 
> Does not really work - leads to Avnet, so there is no MSC anymore?
> 

It still seems to be used as branding by Avnet.

> > 
> > Signed-off-by: Martyn Welch <martyn.welch@collabora.com>
> > ---
> > 
> > Changes in v2:
> >   - New addition
> > 
> >  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 0496773a3c4d..1658357bc1c4 100644
> > --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > @@ -816,6 +816,8 @@ patternProperties:
> >    "^mrvl,.*":
> >      description: Marvell Technology Group Ltd.
> >      deprecated: true
> > +  "^msc,.*":
> > +    description: MSC Technologies GmbH.
> 
> This should be rather msct or msctech, but anyway in fact you maybe
> should use avnet?
> 

My rationale for using MSC Technologies is that is how the device is
described on the website as being a MSC device. I think the
amalgamation of the MSC website into Avnet's has happened in the last
year or so. I assume a new device released in the near future would be
branded more directly as an Avnet device, or maybe not, I see that the
i.MX 9 is being described as "MSC SM2S-IMX93".

I'll switch to msctech unless there are objections to that.

Martyn

> >    "^mscc,.*":
> >      description: Microsemi Corporation
> >    "^msi,.*":
> 
> 
> Best regards,
> Krzysztof


  reply	other threads:[~2022-07-21  8:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 15:00 Martyn Welch
2022-07-20 15:00 ` [PATCH v2 2/3] dt-bindings: arm: fsl: Add MSC SM2S-IMX8PLUS SoM and SM2-MB-EP1 Carrier Martyn Welch
2022-07-20 20:32   ` Rob Herring
2022-07-20 15:00 ` [PATCH v2 3/3] arm64: dts: sm2s-imx8mp: Add device trees for MSC SM2S-IMX8PLUS SoM and carrier board Martyn Welch
2022-07-20 17:11   ` Krzysztof Kozlowski
2022-07-20 17:07 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: add MSC Technologies Krzysztof Kozlowski
2022-07-21  8:03   ` Martyn Welch [this message]
2022-07-21  8:46     ` Krzysztof Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86de8ba0157c451fcce4ca92b6cad835e3f1e4d9.camel@collabora.com \
    --to=martyn.welch@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®