From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-gpio@vger.kernel.org, Andy Shevchenko <andy@kernel.org>
Subject: Re: pinctrl-cherryview regression in linux-next on preproduction Braswell
Date: Tue, 4 Jan 2022 17:26:11 +0200 [thread overview]
Message-ID: <YdRnExZuPuvdfXgT@lahna> (raw)
In-Reply-To: <27a870e5-675a-564f-2bfe-ee913bdec0ac@redhat.com>
Hi,
On Tue, Jan 04, 2022 at 11:22:53AM +0100, Hans de Goede wrote:
> Andy, Mika, why don't we just mask out all IRQs at boot unconditionally:
>
> diff --git a/drivers/pinctrl/intel/pinctrl-cherryview.c b/drivers/pinctrl/intel/pinctrl-cherryview.c
> index 683b95e9639a..8981755a5d83 100644
> --- a/drivers/pinctrl/intel/pinctrl-cherryview.c
> +++ b/drivers/pinctrl/intel/pinctrl-cherryview.c
> @@ -1552,19 +1552,10 @@ static int chv_gpio_irq_init_hw(struct gpio_chip *chip)
> const struct intel_community *community = &pctrl->communities[0];
>
> /*
> - * 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=197953.
> + * Start with all normal interrupts in the community masked,
> + * but leave the ones that can only generate GPEs unmasked.
> */
> - if (!pctrl->chip.irq.init_valid_mask) {
> - /*
> - * Mask all interrupts the community is able to generate
> - * but leave the ones that can only generate GPEs unmasked.
> - */
> - chv_pctrl_writel(pctrl, CHV_INTMASK, GENMASK(31, community->nirqs));
> - }
> + chv_pctrl_writel(pctrl, CHV_INTMASK, GENMASK(31, community->nirqs));
>
> /* Clear all interrupts */
> chv_pctrl_writel(pctrl, CHV_INTSTAT, 0xffff);
>
> ?
IIRC masking them all broke some systems at the time. Unfortunately I
don't remember the details anymore :(
next prev parent reply other threads:[~2022-01-04 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 9:42 pinctrl-cherryview regression in linux-next on preproduction Braswell Jarkko Nikula
2022-01-03 10:42 ` Hans de Goede
2022-01-03 12:34 ` Jarkko Nikula
2022-01-03 16:06 ` Hans de Goede
2022-01-03 16:40 ` Hans de Goede
2022-01-04 9:43 ` Jarkko Nikula
2022-01-04 10:22 ` Hans de Goede
2022-01-04 10:48 ` Hans de Goede
2022-01-04 14:38 ` Jarkko Nikula
2022-01-04 14:47 ` Hans de Goede
2022-01-05 14:23 ` Jarkko Nikula
2022-01-10 15:44 ` Hans de Goede
2022-01-04 15:26 ` Mika Westerberg [this message]
2022-01-04 16:37 ` Hans de Goede
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=YdRnExZuPuvdfXgT@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-gpio@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).