linux-kernel - Re: [PATCH] pinctrl: cherryview: Add quirk with custom translation of ACPI GPIO numbers

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20200818135909.GS1891694@smile.fi.intel.com>
Date:   Tue, 18 Aug 2020 16:59:09 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Brian Norris <briannorris@...omium.org>
Cc:     Mika Westerberg <mika.westerberg@...ux.intel.com>,
        linux-gpio@...r.kernel.org,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Linux Kernel <linux-kernel@...r.kernel.org>,
        stanekm@...gle.com, stable <stable@...r.kernel.org>,
        Marcin Wojtas <mw@...ihalf.com>, levinale@...omium.org,
        Linus Walleij <linus.walleij@...aro.org>,
        bgolaszewski@...libre.com,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [PATCH] pinctrl: cherryview: Add quirk with custom translation
 of ACPI GPIO numbers

On Fri, Apr 17, 2020 at 05:55:44PM -0700, Brian Norris wrote:
> - Michal (bouncing)
> 
> On Fri, Apr 17, 2020 at 2:05 AM Mika Westerberg
> <mika.westerberg@...ux.intel.com> wrote:
> > I wonder if we can add back the previous GPIO base like this?
> 
> Thanks for the patch! At first glance, it looks like the right kind of
> thing. Unfortunately, it doesn't appear to work quite right for me.
> I'm out of time for today to look any further, but I (or perhaps
> someone else on this email) will try to follow up next week sometime.

Just in case you are going to do something about this, take into consideration
that Cherryview driver got several cleanups in the past, it may require to
rework this on top of the made changes.

P.S. Currently they are in my branch, but within couple of days it will be in
Linux Next if nothing prevents it.

-- 
With Best Regards,
Andy Shevchenko