linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	linux-riscv@lists.infradead.org, linux-serial@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH] serial: sifive: Remove 0 from fu540-c000-uart0 binding.
Date: Thu, 7 Mar 2024 17:56:02 +0000	[thread overview]
Message-ID: <20240307-busily-encrypt-507cae0e7564@spud> (raw)
In-Reply-To: <4d85215e-64ca-491c-8f69-f2c83c7e72d7@sifive.com>


[-- Attachment #1.1: Type: text/plain, Size: 1907 bytes --]

On Thu, Mar 07, 2024 at 11:43:53AM -0600, Samuel Holland wrote:
> Hi Conor, Sebastian,
> 
> On 2024-03-07 11:39 AM, Conor Dooley wrote:
> > On Thu, Mar 07, 2024 at 10:09:50AM +0100, Sebastian Andrzej Siewior wrote:
> >> The driver is using "sifive,fu540-c000-uart0" as a binding. The device
> >> tree and documentation states "sifive,fu540-c000-uart" instead. This
> >> means the binding is not matched and not used.
> >>
> >> This did not cause any problems because the alternative binding, used in
> >> the device tree, "sifive,uart0" is not handling the hardware any
> >> different.
> >>
> >> Align the binding in the driver with the documentation.
> >>
> >> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> >> ---
> >> On 2024-03-06 18:48:13 [-0800], Paul Walmsley wrote:
> >>> On Mon, 4 Mar 2024, Conor Dooley wrote:
> >>>> I suspect that the driver is what's incorrect, given there's little
> >>>> value in putting the IP version in the SoC-specific compatible as it's
> >>>> a fixed implementation. I'd change the driver to match the bindings.
> >>>
> >>> Agreed
> >>
> > 
> >> I didn't add any stable/ fixes tags as I guess there is no point in
> >> backporting this.
> > 
> > Every documented device falls back to "sifive,uart0", as you mention
> > above, so I think that's reasonable.
> 
> Right. In fact this means the sifive,fu540-c000-uart compatible can be removed
> from the driver entirely, since the driver would match sifive,uart0 anyway.

I'm always a bit hesitant when it comes to removing compatibles that are
backed up by a mandatory fallback in where there could be some old
firmware/DT floating around that didn't have the fallback. I think in
this case that's pretty moot though, so ye, it could totally be dropped
from the driver entirely. I'm happy with either, both cases are an
undocumented compatible being removed ;)

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

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2024-03-07 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 10:59 [RFC] Inconsistent sifive,fu540-c000-uart binding Sebastian Andrzej Siewior
2024-03-04 18:53 ` Conor Dooley
2024-03-07  2:48   ` Paul Walmsley
2024-03-07  9:09     ` [PATCH] serial: sifive: Remove 0 from fu540-c000-uart0 binding Sebastian Andrzej Siewior
2024-03-07 17:39       ` Conor Dooley
2024-03-07 17:43         ` Samuel Holland
2024-03-07 17:56           ` Conor Dooley [this message]

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=20240307-busily-encrypt-507cae0e7564@spud \
    --to=conor@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@sifive.com \
    --cc=tglx@linutronix.de \
    /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).