linux-kernel - Re: [PATCH 02/11] GPIO: DA9052 GPIO module v1

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, 30 Jun 2011 08:32:45 -0700
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Ashish Jangam <Ashish.Jangam@...tcummins.com>
Cc:	"jic23@....ac.uk" <jic23@....ac.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Dajun <dajun.chen@...semi.com>,
	"grant@...retlab.ca" <grant@...retlab.ca>
Subject: Re: [PATCH 02/11] GPIO: DA9052 GPIO module v1

On Thu, Jun 30, 2011 at 05:10:31PM +0530, Ashish Jangam wrote:

> > Why insist on platform data?  gpiolib can dynamically allocate a GPIO
> > range to the device.

> Do you mean to use gpiochip_reserve() in machine file and not to have
> ngpio and base defined in GPIO platform driver but, this will fail the
> call to gpiochip_add()?

No, I mean that you should allow gpiolib to allocate a GPIO range if one
is not already allocated like other gpiolib drivers do by supplying -1
as the base.
--
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/