From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jason Li" <jason.li@cortina-access.com>,
"Jason Li" <jason.lee651024@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] tty: serial: Add Cortina-Access UART driver and platform support
Date: Thu, 11 Jun 2026 10:35:09 +0200 [thread overview]
Message-ID: <d62541fd-36bb-4c67-a81b-a8e66887a2cc@app.fastmail.com> (raw)
In-Reply-To: <JH0PR01MB5777B84BE8D9987329ABA54BA21B2@JH0PR01MB5777.apcprd01.prod.exchangelabs.com>
On Thu, Jun 11, 2026, at 07:27, Jason Li wrote:
> Hi Arnd,
>
> Your memory is truly amazing; you even remember a submission from a few
> years ago.
No, I just looked up your previous submissions when I saw the new one,
lore.kernel.org never forgets anything ;-)
> Yes, we expect actual end-user products based on these SoCs, and our
> intention is to provide complete upstream support over time. The UART
> driver and DTS support submitted in this series are the first step in
> that effort.
>
> Cortina-System and Cortina-Access are now totally different company.
> Current aarch64 chipset are totally different with legacy gemini
> processor.
> Realtek has many business unit, different BU may have upstream plan but
> they are individual.
> Although Cortina-Access is a wholly-owned subsidiary of Realtek, our
> product development is entirely independent.
Thanks for the information. Please make sure to add something along
these into the changeset text for the initial arm64 patch, along
with a brief description of what type of chip this is
Arnd
next prev parent reply other threads:[~2026-06-11 8:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 11:28 [PATCH 0/3] tty: serial: Add Cortina-Access UART driver and platform support Jason Li
2026-06-10 11:28 ` Jason Li
2026-06-10 12:50 ` Arnd Bergmann
2026-06-11 5:27 ` Jason Li
2026-06-11 8:35 ` Arnd Bergmann [this message]
2026-06-10 11:28 ` [PATCH 1/3] dt-bindings: serial: Add binding for Cortina-Access UART Jason Li
2026-06-10 11:46 ` Krzysztof Kozlowski
2026-06-11 5:25 ` Jason Li
2026-06-10 11:51 ` Krzysztof Kozlowski
2026-06-11 5:26 ` Jason Li
2026-06-10 11:28 ` [PATCH 2/3] tty: serial: Add UART driver for Cortina-Access platform Jason Li
2026-06-10 22:49 ` Randy Dunlap
2026-06-10 11:28 ` [PATCH 3/3] arm64: dts: cortina-access: Add DTS for CA8289 SoC and Venus board Jason Li
2026-06-10 11:49 ` Krzysztof Kozlowski
2026-06-11 5:26 ` Jason Li
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=d62541fd-36bb-4c67-a81b-a8e66887a2cc@app.fastmail.com \
--to=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jason.lee651024@gmail.com \
--cc=jason.li@cortina-access.com \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=will@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