linux-kernel - Re: [PATCH] gpio: expose gpio_to

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]

Message-ID: <BANLkTikUVGBRvCAPDZTpzTfpHHTM8Y+iTA@mail.gmail.com>
Date:	Tue, 7 Jun 2011 15:46:52 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	linux-kernel@...r.kernel.org, Alan Cox <alan@...ux.intel.com>
Subject: Re: [PATCH] gpio: expose gpio_to_chip()

2011/4/14 Grant Likely <grant.likely@...retlab.ca>:
> On Thu, Apr 14, 2011 at 1:20 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
>> This makes the gpio_to_chip() function available to drivers. The
>> usecase is when you want to add a few chip-specific operations
>> apart from the ones exposed in struct gpio_chip.
>
> Similar to interrupt handling, it probably isn't a good idea to expose
> the gpio_chip directly.  Go ahead and add the ops you need and see
> what it looks like.

So have we come to a conclusion about what mechanism we shall use
for the custom GPIO ops? I need this to migrate the U300 and Nomadik
GPIO drivers to struct gpio_chip.

I suspect this patch will apply right off if you prefer this solution with
specific functions for specific stuff above the generic scheme of extending
the struct gpio_chip with a ioctl()-like vtable member that I and
Alan Cox came up with as a response to the above.

I'm happy to implement either, or even both if you like :-D

Yours,
Linus Walleij
--
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/