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: <20100108082826.GC1224@trinity.fluff.org>
Date:	Fri, 8 Jan 2010 08:28:26 +0000
From:	Ben Dooks <ben-linux@...ff.org>
To:	Eric Miao <eric.y.miao@...il.com>
Cc:	Ben Dooks <ben-linux@...ff.org>, linux-samsung-soc@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] gpiolib: add gpio_lookup_chip() to get chip
	information for gpio

On Fri, Jan 08, 2010 at 03:30:36PM +0800, Eric Miao wrote:
> On Fri, Jan 8, 2010 at 2:32 PM, Ben Dooks <ben-linux@...ff.org> wrote:
> > Add a call to get the 'struct gpio_chip' pointer for a given gpio, so
> > that core implementations which want to use gpiolib gpio numbering for
> > things like mux configuration can get back to the gpio_chip that they
> > registered without having to have their own list of gpio.
> >
> > This is especially useful for the Samsung S3C64XX series where the GPIO
> > bank sizes can vary from 32 down to 3, making it difficult to store an
> > array to convert a number to chip.
> >
> 
> I think this is generally a good idea. Will most likely be useful to
> pxa platforms as well. Not sure though if you want to export this
> symbol as well since we do allow gpio chip drivers to be modules.

Probably not, since all the gpio call methods pass gpio_chip as their
first parameter. This is only in the case we want to use gpios for
something other than in/out/irq.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ