From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Benjamin Larsson <benjamin.larsson@genexis.eu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
ansuelsmth@gmail.com, lorenzo@kernel.org
Subject: Re: [PATCH v4 0/2] Airoha UART support
Date: Sat, 22 Mar 2025 23:45:30 +0200 [thread overview]
Message-ID: <Z98veiHLkQWlCdBE@surfacebook.localdomain> (raw)
In-Reply-To: <28a3cbc9-53fb-44e3-bc87-d33cbc406c8e@genexis.eu>
Fri, Mar 21, 2025 at 09:37:09PM +0100, Benjamin Larsson kirjoitti:
> On 10/02/2025 07:14, Greg KH wrote:
> > On Sun, Feb 09, 2025 at 10:02:39PM +0100, Benjamin Larsson wrote:
...
> I would argue that I follow the current flow of the code. In 8250.h we have:
>
> CONFIG_SERIAL_8250_PNP
> CONFIG_SERIAL_8250_RSA
These are historically parts of the main driver, RSA code theoretically
can be removed.
> CONFIG_SERIAL_8250_FINTEK
I would love to see this being not part of main driver.
> none of those enables COMPILE_TEST or the option to compile as a module.
They all together may be compiled as a main driver module.
Again, this is all historical and new code would need a very good justification
why it can be held in a separate module.
> Neither the Airoha code or the other code is not intended to be its own
> separate module,
Why not?
> it is to be part of the 8250-driver. The 8250-driver can be
> loaded as a module with or without the Airoha baud rate code.
>
> Implementing COMPILE_TEST when the 8250-driver does not support it seems
> tricky. All the ways I could think of would result in messy code and logic.
> I came to the conclusion that a smaller patch that reuses the current logic
> was preferable. If that argument is not good enough then I need some
> guidance how to implement something what would be accepted.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-03-22 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 21:02 [PATCH v4 0/2] Airoha UART support Benjamin Larsson
2025-02-09 21:02 ` [PATCH 1/2] dt-bindings: serial: 8250: Add Airoha compatibles Benjamin Larsson
2025-02-09 21:02 ` [PATCH 2/2] serial: Airoha SoC UART and HSUART support Benjamin Larsson
2025-03-22 21:42 ` Andy Shevchenko
2025-03-25 14:19 ` Benjamin Larsson
2025-03-25 14:23 ` Andy Shevchenko
2025-02-10 6:14 ` [PATCH v4 0/2] Airoha UART support Greg KH
2025-03-21 20:37 ` Benjamin Larsson
2025-03-22 21:45 ` Andy Shevchenko [this message]
2025-03-25 14:45 ` Benjamin Larsson
2025-03-25 14:54 ` Andy Shevchenko
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=Z98veiHLkQWlCdBE@surfacebook.localdomain \
--to=andy.shevchenko@gmail.com \
--cc=ansuelsmth@gmail.com \
--cc=benjamin.larsson@genexis.eu \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=lorenzo@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