All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Dario Binacchi <dariobin@libero.it>
Subject: Re: [PATCH] dt-bindings: serial: Move omap-serial.txt to YAML schema
Date: Fri, 28 May 2021 10:05:47 +0300	[thread overview]
Message-ID: <YLCWS/+TwSs8HhRG@atomide.com> (raw)
In-Reply-To: <3760d1e6-2121-323b-d962-60e8291d0bb7@ti.com>

* Grygorii Strashko <grygorii.strashko@ti.com> [210527 17:49]:
> 
> 
> On 27/05/2021 19:56, Vignesh Raghavendra wrote:
> > Convert serial-omap.txt to YAML schema for better checks and documentation.
> > 
> > Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> > ---
> >   .../bindings/serial/omap_serial.txt           |  40 ------
> >   .../bindings/serial/ti,omap4-uart.yaml        | 116 ++++++++++++++++++
> >   2 files changed, 116 insertions(+), 40 deletions(-)
> >   delete mode 100644 Documentation/devicetree/bindings/serial/omap_serial.txt
> >   create mode 100644 Documentation/devicetree/bindings/serial/ti,omap4-uart.yaml
> 
> Why omap4? Seems ti,omap-uart.yaml is more suitable.

Additionally omap-serial should be deprecated in favor of 8250_omap and
omap-serial not used at all in general.

It seems some folks still stick to omap-serial for legacy reasons when
using an old .config. That's easy to fix by just changing inittab to
use ttyS instead of ttyO, the kernel cmdline is already fixed up on
init to use ttyS, but might as well update the bootloader cmdline too.

But why do we even allow using this driver on newer SoCs when we have
already planned to deprecate omap-serial.c years before the new SoCs?

I suggest we make omap-serial deprecated for all SoCs, and not even
allow it for am6, omap-serial.c only lists these:

        { .compatible = "ti,omap2-uart" },
        { .compatible = "ti,omap3-uart" },
        { .compatible = "ti,omap4-uart" },

And folks are also using it for some rs485 cases that should just be
really fixed for 8250_omap instead.. Adding Dario to Cc because of
these omap-serial patches:

e2a5e8448e73 ("serial: omap: fix rs485 half-duplex filtering")
45f6b6db53c8 ("serial: omap: don't disable rs485 if rts gpio is missing")

Dario, why not use 8250_omap instead?

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Dario Binacchi <dariobin@libero.it>
Subject: Re: [PATCH] dt-bindings: serial: Move omap-serial.txt to YAML schema
Date: Fri, 28 May 2021 10:05:47 +0300	[thread overview]
Message-ID: <YLCWS/+TwSs8HhRG@atomide.com> (raw)
In-Reply-To: <3760d1e6-2121-323b-d962-60e8291d0bb7@ti.com>

* Grygorii Strashko <grygorii.strashko@ti.com> [210527 17:49]:
> 
> 
> On 27/05/2021 19:56, Vignesh Raghavendra wrote:
> > Convert serial-omap.txt to YAML schema for better checks and documentation.
> > 
> > Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> > ---
> >   .../bindings/serial/omap_serial.txt           |  40 ------
> >   .../bindings/serial/ti,omap4-uart.yaml        | 116 ++++++++++++++++++
> >   2 files changed, 116 insertions(+), 40 deletions(-)
> >   delete mode 100644 Documentation/devicetree/bindings/serial/omap_serial.txt
> >   create mode 100644 Documentation/devicetree/bindings/serial/ti,omap4-uart.yaml
> 
> Why omap4? Seems ti,omap-uart.yaml is more suitable.

Additionally omap-serial should be deprecated in favor of 8250_omap and
omap-serial not used at all in general.

It seems some folks still stick to omap-serial for legacy reasons when
using an old .config. That's easy to fix by just changing inittab to
use ttyS instead of ttyO, the kernel cmdline is already fixed up on
init to use ttyS, but might as well update the bootloader cmdline too.

But why do we even allow using this driver on newer SoCs when we have
already planned to deprecate omap-serial.c years before the new SoCs?

I suggest we make omap-serial deprecated for all SoCs, and not even
allow it for am6, omap-serial.c only lists these:

        { .compatible = "ti,omap2-uart" },
        { .compatible = "ti,omap3-uart" },
        { .compatible = "ti,omap4-uart" },

And folks are also using it for some rs485 cases that should just be
really fixed for 8250_omap instead.. Adding Dario to Cc because of
these omap-serial patches:

e2a5e8448e73 ("serial: omap: fix rs485 half-duplex filtering")
45f6b6db53c8 ("serial: omap: don't disable rs485 if rts gpio is missing")

Dario, why not use 8250_omap instead?

Regards,

Tony

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

  reply	other threads:[~2021-05-28  7:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 16:56 [PATCH] dt-bindings: serial: Move omap-serial.txt to YAML schema Vignesh Raghavendra
2021-05-27 16:56 ` Vignesh Raghavendra
2021-05-27 17:49 ` Grygorii Strashko
2021-05-27 17:49   ` Grygorii Strashko
2021-05-28  7:05   ` Tony Lindgren [this message]
2021-05-28  7:05     ` Tony Lindgren
2021-06-04 20:48     ` Rob Herring
2021-06-04 20:48       ` Rob Herring
2021-06-07  7:25       ` Tony Lindgren
2021-06-07  7:25         ` Tony Lindgren
2021-06-04 20:52 ` Rob Herring
2021-06-04 20:52   ` Rob Herring

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=YLCWS/+TwSs8HhRG@atomide.com \
    --to=tony@atomide.com \
    --cc=dariobin@libero.it \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.