public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Thierry Bultel <thierry.bultel.yh@bp.renesas.com>,
	thierry.bultel@linatsea.fr, linux-renesas-soc@vger.kernel.org,
	paul.barker.ct@bp.renesas.com, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, Ulrich Hecht <uli@fpond.eu>,
	Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH v4 08/13] serial: sh-sci: Introduced function pointers
Date: Mon, 17 Mar 2025 10:55:09 +0100	[thread overview]
Message-ID: <Z9fxfV9jAGJ51fcn@shikoro> (raw)
In-Reply-To: <CAMuHMdVM_ozW4LAA4DstQuDfEcOnOcXZ2QHGv8nYMKDPWJe43Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

Hi all,

sorry for missing this series so far and thanks to Geert for pulling me
into the loop.

> While most rough edges have been polished by now (thanks!), and the
> driver seems to still work on a variety of platforms, I am still
> worried about the impact of this change:
>   - Maintainability and future bug fixing?

I hate to see development work going to waste, yet I have to say I am
also concerned about the maintainability of this driver after this very
intrusive changeset. The driver is already quite complex. Adding another
layer of complexity (function pointers) will make proper bugfixing for
all supported instances quite harder, I'd think.

Has it been discussed to have this as a separate driver? Were there
reasons against it? This is really an open question. Maybe it is
justified to do it like this if we have reasons for it.

Seeing that SCI core needs 800+ lines changed and we still have a
seperate driver with 460 lines driver, I do wonder if copying the logic
from SCI core to a seperate driver would make sense. I am aware that the
core has currently 3500+ lines currently. I'd estimate it would shrink
quite a bit when copying because you won't need to handle all the
differences to other SCI entries.

Again, this is not a request to follow my suggestion, it is an open
question to make sure all paths have been considered.

Thanks and happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-03-17  9:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250306152451.2356762-1-thierry.bultel.yh@bp.renesas.com>
2025-03-06 15:24 ` [PATCH v4 03/13] dt-bindings: serial: Add compatible for Renesas RZ/T2H SoC in sci Thierry Bultel
2025-03-07 21:45   ` Rob Herring (Arm)
2025-03-06 15:24 ` [PATCH v4 07/13] serial: sh-sci: Fix a comment about SCIFA Thierry Bultel
2025-03-18 21:50   ` Wolfram Sang
2025-03-06 15:24 ` [PATCH v4 08/13] serial: sh-sci: Introduced function pointers Thierry Bultel
2025-03-14 11:05   ` Geert Uytterhoeven
2025-03-17  9:55     ` Wolfram Sang [this message]
2025-03-17 10:27       ` Paul Barker
2025-03-18 21:45         ` Wolfram Sang
2025-03-24  9:25   ` Wolfram Sang
2025-03-24 10:02     ` Geert Uytterhoeven
2025-03-06 15:24 ` [PATCH v4 09/13] serial: sh-sci: Introduced sci_of_data Thierry Bultel
2025-03-24  9:37   ` Wolfram Sang
2025-03-24 10:03   ` Geert Uytterhoeven
2025-03-06 15:24 ` [PATCH v4 10/13] serial: sh-sci: Add support for RZ/T2H SCI Thierry Bultel
2025-03-24  9:43   ` Wolfram Sang
2025-03-24 12:49     ` Thierry Bultel
2025-03-24 21:56       ` Wolfram Sang
2025-03-25  6:29         ` Biju Das
2025-03-25  7:51           ` Wolfram Sang
2025-03-25 10:49             ` Thierry Bultel
2025-03-25 11:06               ` Wolfram Sang
2025-03-25 16:24               ` Geert Uytterhoeven

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=Z9fxfV9jAGJ51fcn@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=paul.barker.ct@bp.renesas.com \
    --cc=thierry.bultel.yh@bp.renesas.com \
    --cc=thierry.bultel@linatsea.fr \
    --cc=uli@fpond.eu \
    /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