linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>, linux-can@vger.kernel.org
Cc: Dan Murphy <dmurphy@ti.com>,
	Sriram Dash <sriram.dash@samsung.com>,
	Patrik Flykt <patrik.flykt@linux.intel.com>
Subject: Re: [PATCH] can: m_can: Process interrupt only when not runtime suspended
Date: Wed, 18 Nov 2020 16:23:22 +0100	[thread overview]
Message-ID: <51aae4ee-5abf-8759-ca8d-627f661e9753@pengutronix.de> (raw)
In-Reply-To: <20200915134715.696303-1-jarkko.nikula@linux.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 749 bytes --]

On 9/15/20 3:47 PM, Jarkko Nikula wrote:
> Avoid processing bogus interrupt statuses when the HW is runtime
> suspended and the M_CAN_IR register read may get all bits 1's. Handler
> can be called if the interrupt request is shared with other peripherals
> or at the end of free_irq().
> 
> Therefore check the runtime suspended status before processing.
> 
> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>

Applied to linux-can/testing

Tnx,
Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-11-18 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 13:47 [PATCH] can: m_can: Process interrupt only when not runtime suspended Jarkko Nikula
2020-11-18 15:23 ` Marc Kleine-Budde [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=51aae4ee-5abf-8759-ca8d-627f661e9753@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=dmurphy@ti.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-can@vger.kernel.org \
    --cc=patrik.flykt@linux.intel.com \
    --cc=sriram.dash@samsung.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;
as well as URLs for NNTP newsgroup(s).