linux-kernel - RE: [PATCH v9 2/9] Input: goodix

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1F3AC3675D538145B1661F571FE1805F2F101AC0@irsmsx105.ger.corp.intel.com>
Date:	Mon, 19 Oct 2015 14:32:24 +0000
From:	"Tirdea, Irina" <irina.tirdea@...el.com>
To:	"mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	Bastien Nocera <hadess@...ess.net>,
	Aleksei Mamlin <mamlinav@...il.com>,
	Karsten Merker <merker@...ian.org>,
	"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
	Mark Rutland <mark.rutland@....com>,
	"Purdila, Octavian" <octavian.purdila@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"Dolca, Robert" <robert.dolca@...el.com>
Subject: RE: [PATCH v9 2/9] Input: goodix - reset device at init



> -----Original Message-----
> From: linux-input-owner@...r.kernel.org [mailto:linux-input-owner@...r.kernel.org] On Behalf Of
> mika.westerberg@...ux.intel.com
> Sent: 14 October, 2015 16:44
> To: Dmitry Torokhov
> Cc: Tirdea, Irina; Bastien Nocera; Aleksei Mamlin; Karsten Merker; linux-input@...r.kernel.org; Mark Rutland; Purdila, Octavian; linux-
> kernel@...r.kernel.org; devicetree@...r.kernel.org
> Subject: Re: [PATCH v9 2/9] Input: goodix - reset device at init
> 
> On Wed, Oct 14, 2015 at 02:18:20PM +0300, mika.westerberg@...ux.intel.com wrote:
> > On Tue, Oct 13, 2015 at 11:23:03PM -0700, Dmitry Torokhov wrote:
> > > I understand why one might use acpi_dev_add_driver_gpios() to augment
> > > data in ACPI, however here we have completely different issue: driver
> > > that expects named gpios gets returned gpio that has nothing to do with
> > > what it requested, because gpiolib acpi code always falls back to
> > > unnamed gpio if it does not find named gpio. That can be acceptable if
> > > driver uses the same con_id for all requests to gpiolib, but is not
> > > working when driver supplies different con_ids.
> >
> > Right, the ACPI fallback ignores con_id completely and uses only the
> > index.
> >
> > AFAIK there is only one driver using ACPI _CRS index method:
> > sdhci-[acpi|pci].c. If we can convert that to use acpi_dev_add_driver_gpios()
> > to feed names for card detection GPIOs, I think we can remove the
> > fallback alltogether in favor of named GPIOs for ACPI.
> 
> Nah, there seems to be several drivers relying on this already :-/

Would it be possible to add an optional parameter to the GPIO API
to specify whether we want to fall back to indexed GPIOs for ACPI?

> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/