mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] serial: omap: make Linux console name configurable
Date: Wed, 19 Mar 2025 12:03:31 +0100	[thread overview]
Message-ID: <92d6e357-4620-4c3e-ac28-48804d74d192@pengutronix.de> (raw)
In-Reply-To: <Z9qkCsnzeOjtnJkh@pengutronix.de>



On 3/19/25 12:01, Sascha Hauer wrote:
> On Wed, Mar 19, 2025 at 11:55:53AM +0100, Ahmad Fatoum wrote:
>> Hello Sascha,
>>
>> On 3/19/25 11:22, Sascha Hauer wrote:
>>> Depending on the configuration Linux on OMAP SoCs either needs ttyO or
>>> ttyS as console name. We used to pass ttyO, but c1c0d18973
>>> ("serial: omap: Use ttyS as Linux console name") recently changed this
>>> to ttyS which breaks setups that used to work earlier. Make the
>>> name configurable to allow for setups requiring ttyS and use ttyO
>>> as default to keep existing setups working.
>>>
>>> Note that with ti,am4372-uart we used to pass ttyO as well, but this
>>> specific compatible is only supported by the 8250 based driver which
>>> needs ttyS as console name. 
>>
>> This reads as if 8250_omap supports only ttyS, but it has logic to
>> support ttyO as well.
> 
> s/needs/prefers/ maybe

Ye, further below there is also 'will also have no effect', which is not
true as it hides an ugly error message.

Can you reword these two parts and make the option default ARCH_K3?

Thanks,
Ahmad

> 
> Sascha
> 




  reply	other threads:[~2025-03-19 11:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 10:22 Sascha Hauer
2025-03-19 10:55 ` Ahmad Fatoum
2025-03-19 11:01   ` Sascha Hauer
2025-03-19 11:03     ` Ahmad Fatoum [this message]
2025-03-19 11:16       ` Sascha Hauer
2025-03-19 11:30         ` Ahmad Fatoum
2025-03-19 12:34 ` Sascha Hauer

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=92d6e357-4620-4c3e-ac28-48804d74d192@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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