Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: linux-omap@vger.kernel.org
Subject: Re: AM5749: tty serial 8250 omap driver crash
Date: Thu, 17 Feb 2022 14:58:28 +0200	[thread overview]
Message-ID: <Yg5GdIp5Glp9p/G5@atomide.com> (raw)
In-Reply-To: <77a24941-4c46-8d78-391a-d3d1018f311a@smile.fr>

* Romain Naour <romain.naour@smile.fr> [220217 09:09]:
> On u-boot devicetree the uart4 node is missing, but we don't plan to use the gps
> from uboot :)
> Should I add the uart4 node?

There should be no need for that, kernel should be able to initialize it
properly no matter what the state is from the bootloader.

> Since removing the uart quirk had some other side effect, I did a shameless hack
> in 8250_omap.c to disable autosuspend.
> 
> -	pm_runtime_put_autosuspend(port->dev);
> +	pm_runtime_dont_use_autosuspend(port->dev);
> 
> With that the uart is always up and running.

Yes but note that 8250_omap autosuspend does not do anything unless the
timeouts are manually enabled by the userspace. They are initialized to -1
during probe.

> > The test script I posted does that for all the uarts, probably best not
> > to do that until the other issues are sorted out :) If so, maybe the issue
> > on close is that the uart has already autoidled.
> 
> Indeed. But I'm not sure why the autosuspend is enabled by default?

See above, it's always been initialized to -1 by default so it won't
do anything. But if you ran the test script I posted, autosuspend timeout
got enabled for all the uarts. But maybe the issue you posted is yet
another issue that I don't quite understand yet.

To me it seems we should always have runtime PM functions enable the
serial port to usable state and get rid of the conditional enable for
probe and dma.

Regards,

Tony

  reply	other threads:[~2022-02-17 12:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 13:39 AM5749: tty serial 8250 omap driver crash Romain Naour
2022-02-07  8:04 ` Tony Lindgren
2022-02-09  9:13   ` Romain Naour
2022-02-10 12:05     ` Tony Lindgren
2022-02-11 10:11       ` Romain Naour
2022-02-14  7:43         ` Tony Lindgren
2022-02-14 13:08           ` Tony Lindgren
2022-02-16  9:04             ` Romain Naour
2022-02-16 11:46               ` Tony Lindgren
2022-02-16 15:51                 ` Romain Naour
2022-02-17  8:08                   ` Tony Lindgren
2022-02-17  9:09                     ` Romain Naour
2022-02-17 12:58                       ` Tony Lindgren [this message]
2022-04-02 10:15                         ` Romain Naour
2022-05-03 10:05                           ` Tony Lindgren
2022-05-04 12:42                             ` Romain Naour
2022-05-05  4:33                               ` Tony Lindgren

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=Yg5GdIp5Glp9p/G5@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=romain.naour@smile.fr \
    /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