From: Xilin Wu <wuxilin123@gmail.com>

Add an entry for AYN Technologies (https://www.ayntec.com/)

Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
This was originally submitted as part of the original Odin 2 submission
[0], but that series stalled, so submitting this separately. The prefix
was renamed to ayntec as per the review comment on that patch.

[0] https://lore.kernel.org/linux-arm-msm/20240424-ayn-odin2-initial-v1-8-e0aa05c991fd@gmail.com/
---
 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 ee7fd3cfe203936d4aa42d4ce6f2efee951b4023..4d08af7b6ceb98ffb330a6e71a8f908d9cb37c4b 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -221,6 +221,8 @@ patternProperties:
     description: Axiado Corporation
   "^axis,.*":
     description: Axis Communications AB
+  "^ayntec,.*":
+    description: AYN Technologies Co., Ltd.
   "^azoteq,.*":
     description: Azoteq (Pty) Ltd
   "^azw,.*":

---
base-commit: fe9e3edb6a215515d1148d32a5c445c5bdd7916f
change-id: 20260220-ayn-vendor-a153168c29b2

Best regards,
-- 
Aaron Kling <webgeek1234@gmail.com>

On Fri, Feb 20, 2026 at 04:11:11PM -0600, Aaron Kling wrote:
> From: Xilin Wu <wuxilin123@gmail.com>
> 
> Add an entry for AYN Technologies (https://www.ayntec.com/)
> 
> Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> This was originally submitted as part of the original Odin 2 submission
> [0], but that series stalled, so submitting this separately. The prefix
> was renamed to ayntec as per the review comment on that patch.

And why do we want it without the rest? Answering: we don't want unused
binding and nothing in the commit msg explains other options.

Best regards,
Krzysztof

On Sat, Feb 21, 2026 at 4:55 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On Fri, Feb 20, 2026 at 04:11:11PM -0600, Aaron Kling wrote:
> > From: Xilin Wu <wuxilin123@gmail.com>
> >
> > Add an entry for AYN Technologies (https://www.ayntec.com/)
> >
> > Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
> > Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> > ---
> > This was originally submitted as part of the original Odin 2 submission
> > [0], but that series stalled, so submitting this separately. The prefix
> > was renamed to ayntec as per the review comment on that patch.
>
> And why do we want it without the rest? Answering: we don't want unused
> binding and nothing in the commit msg explains other options.

You have told me repeatedly to not do monolithic series that cross
subsystems. So I am working through support for the AYN qcs8550
devices and splitting that into a bunch of different series. Several
of those independently reference this vendor prefix and may progress
in any order, so this needs submitted separately. I am submitting it
early to try to get it in before the rest are ready, so I don't have
to list this as a dependency to all of them.

Aaron

On 21/02/2026 17:31, Aaron Kling wrote:
> On Sat, Feb 21, 2026 at 4:55 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Fri, Feb 20, 2026 at 04:11:11PM -0600, Aaron Kling wrote:
>>> From: Xilin Wu <wuxilin123@gmail.com>
>>>
>>> Add an entry for AYN Technologies (https://www.ayntec.com/)
>>>
>>> Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
>>> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
>>> ---
>>> This was originally submitted as part of the original Odin 2 submission
>>> [0], but that series stalled, so submitting this separately. The prefix
>>> was renamed to ayntec as per the review comment on that patch.
>>
>> And why do we want it without the rest? Answering: we don't want unused
>> binding and nothing in the commit msg explains other options.
> 
> You have told me repeatedly to not do monolithic series that cross
> subsystems. So I am working through support for the AYN qcs8550

So why is this patch not with the rest for the same subsystem?

> devices and splitting that into a bunch of different series. Several
> of those independently reference this vendor prefix and may progress

Which one? I see only one in the patchset pointed by [0]. I really do
not understand why you are doing it completely different than every
other upstreaming which you can find on lore.

> in any order, so this needs submitted separately. I am submitting it
> early to try to get it in before the rest are ready, so I don't have
> to list this as a dependency to all of them.




Best regards,
Krzysztof

On Sat, Feb 21, 2026 at 10:56 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On 21/02/2026 17:31, Aaron Kling wrote:
> > On Sat, Feb 21, 2026 at 4:55 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >>
> >> On Fri, Feb 20, 2026 at 04:11:11PM -0600, Aaron Kling wrote:
> >>> From: Xilin Wu <wuxilin123@gmail.com>
> >>>
> >>> Add an entry for AYN Technologies (https://www.ayntec.com/)
> >>>
> >>> Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
> >>> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> >>> ---
> >>> This was originally submitted as part of the original Odin 2 submission
> >>> [0], but that series stalled, so submitting this separately. The prefix
> >>> was renamed to ayntec as per the review comment on that patch.
> >>
> >> And why do we want it without the rest? Answering: we don't want unused
> >> binding and nothing in the commit msg explains other options.
> >
> > You have told me repeatedly to not do monolithic series that cross
> > subsystems. So I am working through support for the AYN qcs8550
>
> So why is this patch not with the rest for the same subsystem?
>
> > devices and splitting that into a bunch of different series. Several
> > of those independently reference this vendor prefix and may progress
>
> Which one? I see only one in the patchset pointed by [0]. I really do
> not understand why you are doing it completely different than every
> other upstreaming which you can find on lore.

I literally just said they're not ready yet and that I was trying to
get ahead of them with this. There's almost a dozen new drivers,
several using this prefix, that have to be submitted before the device
trees can be submitted. But fine. I'll just pre-req this to whichever
sets of drivers I get ready to submit first.

> > in any order, so this needs submitted separately. I am submitting it
> > early to try to get it in before the rest are ready, so I don't have
> > to list this as a dependency to all of them.

Aaron

On Sat, Feb 21, 2026 at 11:22 AM Aaron Kling <webgeek1234@gmail.com> wrote:
>
> On Sat, Feb 21, 2026 at 10:56 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >
> > On 21/02/2026 17:31, Aaron Kling wrote:
> > > On Sat, Feb 21, 2026 at 4:55 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > >>
> > >> On Fri, Feb 20, 2026 at 04:11:11PM -0600, Aaron Kling wrote:
> > >>> From: Xilin Wu <wuxilin123@gmail.com>
> > >>>
> > >>> Add an entry for AYN Technologies (https://www.ayntec.com/)
> > >>>
> > >>> Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
> > >>> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> > >>> ---
> > >>> This was originally submitted as part of the original Odin 2 submission
> > >>> [0], but that series stalled, so submitting this separately. The prefix
> > >>> was renamed to ayntec as per the review comment on that patch.
> > >>
> > >> And why do we want it without the rest? Answering: we don't want unused
> > >> binding and nothing in the commit msg explains other options.
> > >
> > > You have told me repeatedly to not do monolithic series that cross
> > > subsystems. So I am working through support for the AYN qcs8550
> >
> > So why is this patch not with the rest for the same subsystem?
> >
> > > devices and splitting that into a bunch of different series. Several
> > > of those independently reference this vendor prefix and may progress
> >
> > Which one? I see only one in the patchset pointed by [0]. I really do
> > not understand why you are doing it completely different than every
> > other upstreaming which you can find on lore.
>
> I literally just said they're not ready yet and that I was trying to
> get ahead of them with this. There's almost a dozen new drivers,
> several using this prefix, that have to be submitted before the device
> trees can be submitted. But fine. I'll just pre-req this to whichever
> sets of drivers I get ready to submit first.
>
> > > in any order, so this needs submitted separately. I am submitting it
> > > early to try to get it in before the rest are ready, so I don't have
> > > to list this as a dependency to all of them.

This patch has been superseded by [0], as required by [1].

Aaron

[0] https://lore.kernel.org/linux-arm-msm/20260323-ayn-qcs8550-v4-0-33a8ac3d53fa@gmail.com/
[1] https://lore.kernel.org/linux-arm-msm/c7fb3f89-6574-4761-9ef2-2fdf6d4801b5@kernel.org