From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: hdegoede@redhat.com, andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] pinctrl: cherryview: Fix irq_valid_mask calculation" failed to apply to 5.3-stable tree
Date: Mon, 11 Nov 2019 08:36:18 -0500 [thread overview]
Message-ID: <20191111133618.GT4787@sasha-vm> (raw)
In-Reply-To: <157345248387137@kroah.com>
On Mon, Nov 11, 2019 at 07:08:03AM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.3-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 63bdef6cd6941917c823b9cc9aa0219d19fcb716 Mon Sep 17 00:00:00 2001
>From: Hans de Goede <hdegoede@redhat.com>
>Date: Fri, 18 Oct 2019 11:08:42 +0200
>Subject: [PATCH] pinctrl: cherryview: Fix irq_valid_mask calculation
>
>Commit 03c4749dd6c7 ("gpio / ACPI: Drop unnecessary ACPI GPIO to Linux
>GPIO translation") has made the cherryview gpio numbers sparse, to get
>a 1:1 mapping between ACPI pin numbers and gpio numbers in Linux.
>
>This has greatly simplified things, but the code setting the
>irq_valid_mask was not updated for this, so the valid mask is still in
>the old "compressed" numbering with the gaps in the pin numbers skipped,
>which is wrong as irq_valid_mask needs to be expressed in gpio numbers.
>
>This results in the following error on devices using pin 24 (0x0018) on
>the north GPIO controller as an ACPI event source:
>
>[ 0.422452] cherryview-pinctrl INT33FF:01: Failed to translate GPIO to IRQ
>
>This has been reported (by email) to be happening on a Caterpillar CAT T20
>tablet and I've reproduced this myself on a Medion Akoya e2215t 2-in-1.
>
>This commit uses the pin number instead of the compressed index into
>community->pins to clear the correct bits in irq_valid_mask for GPIOs
>using GPEs for interrupts, fixing these errors and in case of the
>Medion Akoya e2215t also fixing the LID switch not working.
>
>Cc: stable@vger.kernel.org
>Fixes: 03c4749dd6c7 ("gpio / ACPI: Drop unnecessary ACPI GPIO to Linux GPIO translation")
>Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
I've adjust the patch to work around not having 5fbe5b5883f8 ("gpio:
Initialize the irqchip valid_mask with a callback") and queued it for
5.3 and 4.19.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-11-11 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 6:08 FAILED: patch "[PATCH] pinctrl: cherryview: Fix irq_valid_mask calculation" failed to apply to 5.3-stable tree gregkh
2019-11-11 13:36 ` Sasha Levin [this message]
2019-11-11 15:16 ` 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=20191111133618.GT4787@sasha-vm \
--to=sashal@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=mika.westerberg@linux.intel.com \
--cc=stable@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).