From: Vignesh Raghavendra <vigneshr@ti.com>
To: Greg KH <gregkh@linuxfoundation.org>, Udit Kumar <u-kumar1@ti.com>
Cc: <nm@ti.com>, <tony@atomide.com>, <jirislaby@kernel.org>,
<u.kleine-koenig@pengutronix.de>, <ronald.wahl@raritan.com>,
<thomas.richard@bootlin.com>, <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>
Subject: Re: [PATCH] serial: 8250_omap: Implementation of Errata i2310
Date: Fri, 14 Jun 2024 13:52:59 +0530 [thread overview]
Message-ID: <4220a910-b64a-4212-8d29-a4dbedfba735@ti.com> (raw)
In-Reply-To: <2024061435-reawake-smoking-f639@gregkh>
On 14/06/24 12:16, Greg KH wrote:
> On Fri, Jun 14, 2024 at 11:43:14AM +0530, Udit Kumar wrote:
>> As per Errata i2310[0], Erroneous timeout can be triggered,
>> if this Erroneous interrupt is not cleared then it may leads
>> to strom of interrupts, therefore apply Errata i2310 solution.
>>
s/strom/storm
>> [0] https://www.ti.com/lit/pdf/sprz536 page 23
>>
>> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
>> ---
>> drivers/tty/serial/8250/8250_omap.c | 25 ++++++++++++++++++++-----
>> 1 file changed, 20 insertions(+), 5 deletions(-)
>
> Does this need to go to older/stable kernels? If so, how far back?
>
Yes, this seems to be an updated workaround to existing errata.
Please add below Fixes tag when you respin
Fixes: b67e830d38fa ("serial: 8250: 8250_omap: Fix possible interrupt storm on K3 SoCs")
> thanks,
>
> greg k-h
--
Regards
Vignesh
next prev parent reply other threads:[~2024-06-14 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 6:13 [PATCH] serial: 8250_omap: Implementation of Errata i2310 Udit Kumar
2024-06-14 6:46 ` Greg KH
2024-06-14 8:22 ` Vignesh Raghavendra [this message]
2024-06-14 8:28 ` Ilpo Järvinen
2024-06-14 9:38 ` Kumar, Udit
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=4220a910-b64a-4212-8d29-a4dbedfba735@ti.com \
--to=vigneshr@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nm@ti.com \
--cc=ronald.wahl@raritan.com \
--cc=tglx@linutronix.de \
--cc=thomas.richard@bootlin.com \
--cc=tony@atomide.com \
--cc=u-kumar1@ti.com \
--cc=u.kleine-koenig@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