From: Dinh Nguyen <dinguyen@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 2/2] dt-bindings: soc: altera: combine Intel's SoCFPGA into altera.yaml
Date: Mon, 1 Dec 2025 06:26:25 -0600 [thread overview]
Message-ID: <35735aa9-26ce-4922-bd05-f68cc75353fb@kernel.org> (raw)
In-Reply-To: <20251126-blond-bat-of-emphasis-81c0a8@kuoka>
On 11/26/25 03:49, Krzysztof Kozlowski wrote:
> On Tue, Nov 25, 2025 at 07:40:03AM -0600, Dinh Nguyen wrote:
>> For all SoCFPGA platforms, whether it has the "intel" or "altr" vendor
>> prefix are referring to the same business unit that is responsible for
>> the platform. Thus, it would make sense to have the device bindings
>> documentation in the same location. Move the Intel AgileX board binding
>> documentations into the same file that contains the Altera ones.
>
> I had impression that "intel" is the new, thus preferred vendor prefix
> and actual owner, so please describe here why this is the other way.
>
Altera has just spun off to be a separate business entity from Intel.
Yes, while Intel is still a minority owner, Altera is technically on
it's own. Moving forward, "altr" would be the preferred vendor prefix
for SoCFPGA parts.
Dinh
next prev parent reply other threads:[~2025-12-01 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 13:40 [RESEND PATCH 1/2] dt-bindings: soc: altera: Move altera.yaml from arm to soc Dinh Nguyen
2025-11-25 13:40 ` [RESEND PATCH 2/2] dt-bindings: soc: altera: combine Intel's SoCFPGA into altera.yaml Dinh Nguyen
2025-11-26 9:49 ` Krzysztof Kozlowski
2025-12-01 12:26 ` Dinh Nguyen [this message]
2025-11-26 9:46 ` [RESEND PATCH 1/2] dt-bindings: soc: altera: Move altera.yaml from arm to soc Krzysztof Kozlowski
2025-12-02 21:04 ` Dinh Nguyen
2025-12-03 7:30 ` 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=35735aa9-26ce-4922-bd05-f68cc75353fb@kernel.org \
--to=dinguyen@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.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®