linux-kernel - Re: [PATCH v2] pinctrl: intel: Fix Jasperlake HOSTSW

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 12 Nov 2020 15:57:22 +0200
From:   Andy Shevchenko <andriy.shevchenko@...el.com>
To:     Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:     Evan Green <evgreen@...omium.org>,
        Andy Shevchenko <andy@...nel.org>, stable@...r.kernel.org,
        Linus Walleij <linus.walleij@...aro.org>,
        linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] pinctrl: intel: Fix Jasperlake HOSTSW_OWN offset

On Thu, Nov 12, 2020 at 11:11:00AM +0200, Mika Westerberg wrote:
> On Wed, Nov 11, 2020 at 03:17:28PM -0800, Evan Green wrote:
> > GPIOs that attempt to use interrupts get thwarted with a message like:
> > "pin 161 cannot be used as IRQ" (for instance with SD_CD). This is because
> > the HOSTSW_OWN offset is incorrect, so every GPIO looks like it's
> > owned by ACPI.
> > 
> > Fixes: e278dcb7048b1 ("pinctrl: intel: Add Intel Jasper Lake pin controller support")
> > Cc: stable@...r.kernel.org
> > Signed-off-by: Evan Green <evgreen@...omium.org>
> 
> Acked-by: Mika Westerberg <mika.westerberg@...ux.intel.com>

Pushed to my review and testing queue, thanks!

-- 
With Best Regards,
Andy Shevchenko