From: Dmitry Rokosov <ddrokosov@sberdevices.ru>
To: <gregkh@linuxfoundation.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<neil.armstrong@linaro.org>, <jbrunet@baylibre.com>,
<jirislaby@kernel.org>, <khilman@baylibre.com>,
<martin.blumenstingl@googlemail.com>
Cc: <kelvin.zhang@amlogic.com>, <xianwei.zhao@amlogic.com>,
<kernel@sberdevices.ru>, <rockosov@gmail.com>,
<linux-amlogic@lists.infradead.org>,
<linux-serial@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Dmitry Rokosov <ddrokosov@sberdevices.ru>
Subject: [PATCH v2 0/7] tty: serial: meson: support ttyS devname
Date: Wed, 5 Jul 2023 21:18:26 +0300 [thread overview]
Message-ID: <20230705181833.16137-1-ddrokosov@sberdevices.ru> (raw)
During a IRC discussion with Neil, as reported in reference [1], an idea
emerged to provide support for a standard devname 'ttyS' in new SoCs
such as A1, S4, T7, C3 and others. The current devname 'ttyAML' is not
widely known and has caused several issues with both low and high-level
software, without any apparent justification for its implementation.
Consequently, it has been deemed necessary to introduce the 'ttyS'
devname for all new 'compatible' entries, while still retaining backward
compatibility with the old 'ttyAML' devname by supporting it in parallel
with the new approach. This patch series therefore aims to implement
these changes.
Changes v2 since v1 at [2]:
- as suggested by Conor, relocate modifications with the new
uart_data structures of S4 and A1 SoC from the main meson_uart
patchset to a separate patchsets
- ensure that the uart_driver is not unregistered if there is at
least one active port
- per Neil's suggestion declare separate uart_driver and console
objects for both tty devnames (ttyAML and ttyS) to enable the use
of multiple uart objects with different compatibility strings
Links:
[1]: https://libera.irclog.whitequark.org/linux-amlogic/2023-07-03
[2]: https://lore.kernel.org/linux-amlogic/20230704135936.14697-1-ddrokosov@sberdevices.ru/
Dmitry Rokosov (7):
tty: serial: meson: use dev_err_probe
tty: serial: meson: redesign the module to platform_driver
tty: serial: meson: apply ttyS devname instead of ttyAML for new SoCs
tty: serial: meson: introduce separate uart_data for S4 SoC family
tty: serial: meson: add independent uart_data for A1 SoC family
dt-bindings: serial: amlogic,meson-uart: support Amlogic A1
arm64: dts: meson: a1: change uart compatible string
.../bindings/serial/amlogic,meson-uart.yaml | 2 +
arch/arm64/boot/dts/amlogic/meson-a1.dtsi | 4 +-
drivers/tty/serial/meson_uart.c | 145 ++++++++++--------
3 files changed, 88 insertions(+), 63 deletions(-)
--
2.36.0
next reply other threads:[~2023-07-05 18:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 18:18 Dmitry Rokosov [this message]
2023-07-05 18:18 ` [PATCH v2 1/7] tty: serial: meson: use dev_err_probe Dmitry Rokosov
2023-07-06 6:59 ` neil.armstrong
2023-07-05 18:18 ` [PATCH v2 2/7] tty: serial: meson: redesign the module to platform_driver Dmitry Rokosov
2023-07-06 6:59 ` neil.armstrong
2023-07-05 18:18 ` [PATCH v2 3/7] tty: serial: meson: apply ttyS devname instead of ttyAML for new SoCs Dmitry Rokosov
2023-07-06 7:08 ` neil.armstrong
2023-07-05 18:18 ` [PATCH v2 4/7] tty: serial: meson: introduce separate uart_data for S4 SoC family Dmitry Rokosov
2023-07-06 7:09 ` neil.armstrong
2023-07-05 18:18 ` [PATCH v2 5/7] tty: serial: meson: add independent uart_data for A1 " Dmitry Rokosov
2023-07-06 7:09 ` neil.armstrong
2023-07-05 18:18 ` [PATCH v2 6/7] dt-bindings: serial: amlogic,meson-uart: support Amlogic A1 Dmitry Rokosov
2023-07-05 21:10 ` Conor Dooley
2023-07-06 17:57 ` Rob Herring
2023-07-05 18:18 ` [PATCH v2 7/7] arm64: dts: meson: a1: change uart compatible string Dmitry Rokosov
2023-07-06 7:10 ` neil.armstrong
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=20230705181833.16137-1-ddrokosov@sberdevices.ru \
--to=ddrokosov@sberdevices.ru \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=jirislaby@kernel.org \
--cc=kelvin.zhang@amlogic.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=rockosov@gmail.com \
--cc=xianwei.zhao@amlogic.com \
/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;
as well as URLs for NNTP newsgroup(s).