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, 10 Feb 2022 14:05:18 +0200 [thread overview]
Message-ID: <YgT/fhpFQfkj1b0j@atomide.com> (raw)
In-Reply-To: <e3cf5082-b494-9309-6878-da208920fa5a@smile.fr>
Hi,
* Romain Naour <romain.naour@smile.fr> [220209 09:13]:
> Le 07/02/2022 à 09:04, Tony Lindgren a écrit :
> > Interesting, what's the exception you get with the -rt kernel? Is it an
> > unhandled external abort or something else?
>
> "asynchronous external abort"
OK
> Maybe there is something wrong with the smart-standby or smart-idle feature in
> the UART IP ? I'm not sure.
Could be that too, but maybe it's as simple as the patch below. Care to
give it a try?
> Are you able to reproduce it ?
> Maybe on a IDK574 or a Beaglebone-AI board ?
Not sure why I'm not seeing this one with my test systems.. Have not tried
with the RT patches for a while though.
Regards,
Tony
8< -------
diff --git a/drivers/tty/serial/8250/8250_omap.c b/drivers/tty/serial/8250/8250_omap.c
--- a/drivers/tty/serial/8250/8250_omap.c
+++ b/drivers/tty/serial/8250/8250_omap.c
@@ -163,6 +163,8 @@ static void omap8250_set_mctrl(struct uart_port *port, unsigned int mctrl)
struct omap8250_priv *priv = up->port.private_data;
u8 lcr;
+ pm_runtime_get_sync(port->dev);
+
serial8250_do_set_mctrl(port, mctrl);
if (!mctrl_gpio_to_gpiod(up->gpios, UART_GPIO_RTS)) {
@@ -179,6 +181,9 @@ static void omap8250_set_mctrl(struct uart_port *port, unsigned int mctrl)
serial_out(up, UART_EFR, priv->efr);
serial_out(up, UART_LCR, lcr);
}
+
+ pm_runtime_mark_last_busy(port->dev);
+ pm_runtime_put_autosuspend(port->dev);
}
/*
next prev parent reply other threads:[~2022-02-10 12:05 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 [this message]
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
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=YgT/fhpFQfkj1b0j@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