linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH] pinctrl: cherryview: Mask all interrupts on Intel_Strago based systems
Date: Fri, 01 Dec 2017 14:35:32 +0200	[thread overview]
Message-ID: <1512131732.25007.534.camel@linux.intel.com> (raw)
In-Reply-To: <20171201102504.38709-1-mika.westerberg@linux.intel.com>

On Fri, 2017-12-01 at 13:25 +0300, Mika Westerberg wrote:
> Guenter Roeck reported an interrupt storm on a prototype system which
> is
> based on Cyan Chromebook. The root cause turned out to be a
> incorrectly
> configured pin that triggers spurious interrupts. This will be fixed
> in
> coreboot but currently we need to prevent the interrupt storm from
> happening by masking all interrupts (but not GPEs) on those systems.
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=194945

Shouldn't be this URL to the bug mentioned in the comments below?

> +	/*
> +	 * The same set of machines in chv_no_valid_mask[] have
> incorrectly
> +	 * configured GPIOs that generate spurious interrupts so we
> use
> +	 * this same list to apply another quirk for them.
> +	 *
> +	 * See also https://bugzilla.kernel.org/show_bug.cgi?id=19795
> 3.
> +	 */

> +		chv_writel(~(BIT(pctrl->community->nirqs) - 1),
> +			   pctrl->regs + CHV_INTMASK);

It might be considered to use

GENMASK(32, pctrl->community->nirqs)

instead of

~(BIT(pctrl->community->nirqs) - 1)

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-12-01 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 10:25 [PATCH] pinctrl: cherryview: Mask all interrupts on Intel_Strago based systems Mika Westerberg
2017-12-01 12:35 ` Andy Shevchenko [this message]
2017-12-01 13:33   ` Mika Westerberg
2017-12-01 18:21 ` Guenter Roeck
2017-12-02 15:51 ` Linus Walleij
2017-12-02 17:25   ` Guenter Roeck
2017-12-03 14:00     ` Mika Westerberg

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=1512131732.25007.534.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mika.westerberg@linux.intel.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).