From: "Kumar, Udit" <u-kumar1@ti.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <vigneshr@ti.com>, <nm@ti.com>, <tony@atomide.com>,
<jirislaby@kernel.org>, <ronald.wahl@raritan.com>,
<thomas.richard@bootlin.com>, <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>,
<ilpo.jarvinen@linux.intel.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH v4] serial: 8250_omap: Implementation of Errata i2310
Date: Tue, 25 Jun 2024 10:47:04 +0530 [thread overview]
Message-ID: <ffbe6439-9696-4abe-976b-07286b37a219@ti.com> (raw)
In-Reply-To: <2024062525-venue-twine-aa79@gregkh>
Thanks Greg
On 6/25/2024 10:10 AM, Greg KH wrote:
> On Mon, Jun 24, 2024 at 10:26:56PM +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 storm of interrupts, therefore apply Errata i2310 solution.
>>
>> [0] https://www.ti.com/lit/pdf/sprz536 page 23
>>
>> Fixes: b67e830d38fa ("serial: 8250: 8250_omap: Fix possible interrupt storm on K3 SoCs")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
> As I have already taken the v3 patch to my tree, please send a "fix"
> patch on top of it, as I can not rebase a public tree.
I posted delta patch on top
https://lore.kernel.org/all/20240625051338.2761599-1-u-kumar1@ti.com/
> thanks,
>
> greg k-h
prev parent reply other threads:[~2024-06-25 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 16:56 [PATCH v4] serial: 8250_omap: Implementation of Errata i2310 Udit Kumar
2024-06-24 17:08 ` Raghavendra, Vignesh
2024-06-25 4:40 ` Greg KH
2024-06-25 5:17 ` Kumar, Udit [this message]
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=ffbe6439-9696-4abe-976b-07286b37a219@ti.com \
--to=u-kumar1@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--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=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.richard@bootlin.com \
--cc=tony@atomide.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox