linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [RFC PATCH 0/2] serial: sci: fix OOPS because of wrongly running hrtimer
Date: Tue, 16 Apr 2024 14:35:46 +0200	[thread overview]
Message-ID: <20240416123545.7098-4-wsa+renesas@sang-engineering.com> (raw)

Dirk sent a very interesting bug report[1]. This series is what I found
out by reviewing the driver. It is not tested yet because I couldn't
trigger the code path yet. The console still works normally with these
patches. Still, I am already curious in hearing your opinions, so here
is what I have...

[1] https://lore.kernel.org/r/ee6c9e16-9f29-450e-81da-4a8dceaa8fc7@de.bosch.com

Wolfram Sang (2):
  serial: sh-sci: start hrtimer after setting up DMA
  serial: sh-sci: always cancel hrtimer when DMA RX is invalidated

 drivers/tty/serial/sh-sci.c | 13 +++----------
 1 file changed, 3 insertions(+), 10 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-04-16 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 12:35 Wolfram Sang [this message]
2024-04-16 12:35 ` [RFC PATCH 1/2] serial: sh-sci: start hrtimer after setting up DMA Wolfram Sang
2024-04-24  9:41   ` Geert Uytterhoeven
2024-05-02 18:01   ` Wolfram Sang
2024-04-16 12:35 ` [RFC PATCH 2/2] serial: sh-sci: always cancel hrtimer when DMA RX is invalidated Wolfram Sang
2024-04-24  9:48   ` Geert Uytterhoeven
2024-05-02 18:17     ` Wolfram Sang
     [not found] <20240416123545.7098-4-wsa+renesas () sang-engineering ! com>
2024-04-17  5:10 ` [RFC PATCH 0/2] serial: sci: fix OOPS because of wrongly running hrtimer Dirk Behme

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=20240416123545.7098-4-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).