Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Troy Mitchell <troy.mitchell@linux.dev>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-hwmon@vger.kernel.org, linux-riscv@lists.infradead.org,
	spacemit@lists.linux.dev, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add Sensylink
Date: Wed, 22 Jul 2026 17:15:34 +0100	[thread overview]
Message-ID: <20260722-devious-seventh-9859bb3741b3@spud> (raw)
In-Reply-To: <673be23a-2a84-43b7-9be7-a661cf0e7935@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 3529 bytes --]

On Tue, Jul 21, 2026 at 10:56:36AM -0700, Guenter Roeck wrote:
> On 7/21/26 08:49, Conor Dooley wrote:
> > On Tue, Jul 21, 2026 at 02:48:27AM -0700, Troy Mitchell wrote:
> > > Add the vendor prefix for Sensylink Microelectronics.
> > > 
> > > Signed-off-by: Troy Mitchell <troy.mitchell@linux.dev>
> > > ---
> > >   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 396044f368e7..22d0d26f1bbd 100644
> > > --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > > @@ -1467,6 +1467,8 @@ patternProperties:
> > >       description: Sensirion AG
> > >     "^sensortek,.*":
> > >       description: Sensortek Technology Corporation
> > > +  "^sensylink,.*":
> > > +    description: Sensylink Microelectronics Technology Co., Ltd.
> > 
> > Googling the company to see what their website is, I seem to see a
> > different name for the company: Shanghai Sensylink Microelectronics Inc.
> > Their website has that with the Shanghai dropped.
> > 
> > Also, probably the commit message should contain
> > Link: https://en.sensylink.com/
> > 
> 
> Asking Google search: "Why the two names ? Did they rename themselves at some point ?"

The google search "AI" response was what showed me the different name,
sounds like I should have questioned it some more!

> 
> Response:
> 
> Understanding the Name Structure
> 
> 1. English Legal Name vs. Marketing Abbreviation
> 
> Sensylink Microelectronics Technology Co., Ltd.:
> This is the literal translation of their full, formal registered corporate name
> used for international trade, customs, and legal documentation.
> 
> Sensylink Microelectronics Inc.:
> This is a simplified, Westernized abbreviation used on their official
> English website and marketing materials for cleaner global branding.
> 
> 2. The Native Chinese Name
> 
> 上海申矽凌微电子科技股份有限公司 (Shanghai Shenxiling Microelectronics Technology
> Co., Ltd.): This is the company's sole, official legal name registered with
> the Chinese government.
> 
> "Sensylink" is a portmanteau created specifically for international markets,
> blending "Sensing" (their core technology) and "Link" (their interface and
> connectivity products).
> 
> Prodding further, asking if the previous response was complete, it tells
> me that there was a name change:
> 
> According to Chinese corporate registry data (via Tianyancha and Qcc),
> they did change their official Chinese legal name:
> 
> Old Name: 上海申矽凌微电子科技有限公司 (Shanghai Sensylink Microelectronics Technology
> Co., Ltd.)
> 
> New Name: 上海申矽凌微电子科技股份有限公司 (Shanghai Sensylink Microelectronics Technology
> Co., Ltd. by Shares / Joint-Stock Company)
> 
> I don't know if Linux has a policy about Legal vs. Marketing names. Personally
> I don't have an opinion. Your call, really.

I don't know what the policy is, or if there is one, but personally I
wouldn't use the westernised abbreviation since they may decide to rebrand
that etc and the vendor prefix information should remain static.

So this is probably fine as-is, just I'd like to see that link added to
their website.

Thanks (and thanks for doing the extra digging),
Conor.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-07-22 16:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  9:48 [PATCH v2 0/6] hwmon: (lm63) Add Sensylink CTF2301 support Troy Mitchell
2026-07-21  9:48 ` [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add Sensylink Troy Mitchell
2026-07-21  9:51   ` sashiko-bot
2026-07-21 15:49   ` Conor Dooley
2026-07-21 17:56     ` Guenter Roeck
2026-07-22 16:15       ` Conor Dooley [this message]
2026-07-22 17:09         ` Guenter Roeck
2026-07-21  9:48 ` [PATCH v2 2/6] dt-bindings: hwmon: Move LM63 family to a dedicated binding Troy Mitchell
2026-07-21  9:58   ` sashiko-bot
2026-07-21 11:38     ` Troy Mitchell
2026-07-21  9:48 ` [PATCH v2 3/6] dt-bindings: hwmon: Add Sensylink CTF2301 Troy Mitchell
2026-07-21  9:57   ` sashiko-bot
2026-07-21 15:46   ` Conor Dooley
2026-07-21  9:48 ` [PATCH v2 4/6] hwmon: (lm63) Add Sensylink CTF2301 support Troy Mitchell
2026-07-21 10:00   ` sashiko-bot
2026-07-21 11:52     ` Troy Mitchell
2026-07-21  9:48 ` [PATCH v2 5/6] riscv: dts: spacemit: Add K3 I2C6 pinctrl state Troy Mitchell
2026-07-21 10:00   ` sashiko-bot
2026-07-21 11:52     ` Troy Mitchell
2026-07-21  9:48 ` [PATCH v2 6/6] riscv: dts: spacemit: Add CTF2301 on K3 CoM260 Troy Mitchell
2026-07-21 10:00   ` sashiko-bot

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=20260722-devious-seventh-9859bb3741b3@spud \
    --to=conor@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=spacemit@lists.linux.dev \
    --cc=troy.mitchell@linux.dev \
    /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