From: Fil Dunsky <filipp.dunsky@gmail.com>
To: Jason Li <jason.li@cortina-access.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Linus Walleij <linusw@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Drew Fustini <fustini@kernel.org>,
Lorenzo Pieralisi <lpieralisi@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>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: RE: [PATCH RFC 07/10] tty: serial: Add Cortina Systems CS75xx UART driver
Date: Thu, 01 Oct 2026 08:26:39 +0300 [thread overview]
Message-ID: <179083239972.193541.4791387611943615705@gmail.com> (raw)
In-Reply-To: <SEZPR01MB4208B8B4A5A7F48F7FFE0C9FA28A2@SEZPR01MB4208.apcprd01.prod.exchangelabs.com>
On Thu, Oct 01, 2026 at 05:14:59AM +0000, Jason Li wrote:
> We agree with the approach of using a single UART driver since the
> CS75xx and CA series share the same UART hardware implementation.
> For the Device Tree compatible strings, we would prefer using the
> "cortina-access" vendor prefix for the CA SoCs (e.g.
> "cortina-access,<soc>-uart").
> We do not have concerns with using a neutral driver name such as
> cortina-uart. However, for DT bindings and related documentation
> describing the CA devices, we would prefer the wording "Cortina
> Access" to distinguish them from the legacy Cortina/Marvell branded
> devices.
Thanks, that works for me. So for v2:
- drivers/tty/serial/cortina-uart.c, SERIAL_CORTINA,
SERIAL_CORTINA_CONSOLE;
- the CS75xx parts keep the existing "cortina" prefix
("cortina,cs7542-uart"), the CA parts get "cortina-access,<soc>-uart"
when they are added;
- the binding and the Kconfig help name both families, as "Cortina
Systems CS75xx" and "Cortina Access CAxxxx".
Arnd, this also answers the prefix question from patch 4 for me: I
would leave the CS75xx compatibles and the dts directory on "cortina"
then, and use "cortina-access" only for the parts that Cortina Access
made. Please shout if you or the DT maintainers see it differently.
Thanks,
Fil
next prev parent reply other threads:[~2026-10-01 5:28 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 6:59 [PATCH RFC 00/10] ARM: Add support for Cortina Systems CS75xx and Securifi Almond+ Fil Dunsky via B4 Relay
2026-09-30 7:00 ` [PATCH RFC 01/10] dt-bindings: vendor-prefixes: Add Securifi Fil Dunsky via B4 Relay
2026-09-30 9:58 ` Linus Walleij
2026-10-01 18:44 ` Conor Dooley
2026-09-30 7:00 ` [PATCH RFC 02/10] dt-bindings: arm: Add Cortina Systems CS7542 and Securifi Almond+ Fil Dunsky via B4 Relay
2026-09-30 9:59 ` Linus Walleij
2026-10-01 18:45 ` Conor Dooley
2026-09-30 7:00 ` [PATCH RFC 03/10] dt-bindings: arm: cpus: Add Cortina Systems CS7542 enable method Fil Dunsky via B4 Relay
2026-09-30 9:59 ` Linus Walleij
2026-09-30 7:00 ` [PATCH RFC 04/10] ARM: cortina: Add support for the CS75xx SoC family Fil Dunsky via B4 Relay
2026-09-30 10:11 ` Linus Walleij
2026-09-30 10:18 ` Fil Dunsky
2026-09-30 10:20 ` Krzysztof Kozlowski
2026-09-30 10:57 ` Fil Dunsky
2026-09-30 11:01 ` Linus Walleij
2026-09-30 11:36 ` Arnd Bergmann
2026-09-30 11:43 ` Fil Dunsky
2026-09-30 12:02 ` Arnd Bergmann
2026-09-30 12:11 ` Fil Dunsky
2026-09-30 12:55 ` Arnd Bergmann
2026-09-30 13:05 ` Fil Dunsky
2026-09-30 7:00 ` [PATCH RFC 05/10] ARM: debug: Add Cortina Systems CS75xx UART0 support Fil Dunsky via B4 Relay
2026-09-30 10:23 ` Linus Walleij
2026-09-30 7:00 ` [PATCH RFC 06/10] dt-bindings: serial: Add Cortina Systems CS7542 UART Fil Dunsky via B4 Relay
2026-10-01 18:48 ` Conor Dooley
2026-10-01 19:03 ` Fil Dunsky
2026-09-30 7:00 ` [PATCH RFC 07/10] tty: serial: Add Cortina Systems CS75xx UART driver Fil Dunsky via B4 Relay
2026-09-30 7:14 ` Greg Kroah-Hartman
2026-09-30 7:52 ` Fil Dunsky
2026-09-30 10:57 ` Linus Walleij
2026-09-30 11:08 ` Arnd Bergmann
2026-09-30 11:24 ` Fil Dunsky
2026-09-30 12:05 ` Arnd Bergmann
2026-10-01 3:17 ` Jason Li
2026-10-01 3:26 ` Fil Dunsky
2026-10-01 5:14 ` Jason Li
2026-10-01 5:26 ` Fil Dunsky [this message]
2026-10-01 6:18 ` Arnd Bergmann
2026-10-01 6:29 ` Fil Dunsky
2026-10-01 7:03 ` Jason Li
2026-10-01 7:14 ` Fil Dunsky
2026-09-30 7:00 ` [PATCH RFC 08/10] ARM: dts: cortina: Add CS7542 SoC and Securifi Almond+ board Fil Dunsky via B4 Relay
2026-09-30 7:00 ` [PATCH RFC 09/10] ARM: multi_v7_defconfig: Enable Cortina Systems CS75xx support Fil Dunsky via B4 Relay
2026-09-30 7:00 ` [PATCH RFC 10/10] MAINTAINERS: Add entry for Cortina Systems CS75xx Fil Dunsky via B4 Relay
2026-09-30 10:39 ` [PATCH RFC 00/10] ARM: Add support for Cortina Systems CS75xx and Securifi Almond+ Linus Walleij
2026-09-30 10:57 ` Fil Dunsky
2026-09-30 11:06 ` Linus Walleij
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=179083239972.193541.4791387611943615705@gmail.com \
--to=filipp.dunsky@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fustini@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jason.li@cortina-access.com \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lpieralisi@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®