From: Grant Likely <grant.likely@secretlab.ca>
To: Drasko DRASKOVIC <drasko.draskovic@gmail.com>,
linux-kernel@vger.kernel.org
Cc: linus.walleij@linaro.org
Subject: Re: [PATCH][GPIO] Add IRQ edge setter to gpiolib
Date: Fri, 30 Nov 2012 11:30:21 +0000 [thread overview]
Message-ID: <20121130113021.67D3A3E14C4@localhost> (raw)
In-Reply-To: <CAEk6gTD-Qqdm24VuPpLd9WCRG5NEwAZxi5V1_p-gMj1hhb+Krg@mail.gmail.com>
On Fri, 5 Oct 2012 14:20:55 +0200, Drasko DRASKOVIC <drasko.draskovic@gmail.com> wrote:
> Hi all,
> please find a patch that adds IRQ edge set-up mechanism to sysfs that
> can be called from the kernel.
>
> This functionality can be very useful for embedded systems, as it
> permits kernel to do GPIO set-up during boot stage. Configuration
> which defines pins behavior is often kept in NVRAM, and during boot
> stage these structures can be parsed and executed by the kernel, so
> that when user processes already find all sysfs environment ready and
> correctly set-up.
>
> While at the present it is possible to export GPIO pins to sysfs (and
> correct direction / value), it is not possible to export IRQ
> configuration as well, so this must be done in user space (most often
> via command line). this patch implements missing functionality, so
> that gpio_sysfs_set_edge() function can be called directly from the
> kernel.
This really seems like the wrong place to be doing this. If the GPIO
needs to be used with a particular configuration for an IRQ, then the
device tree or platform data on non-dt should be given that information.
I do not feel good about exporting anonymnous IRQ configuration to
userspace.
next prev parent reply other threads:[~2012-11-30 11:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 12:20 [PATCH][GPIO] Add IRQ edge setter to gpiolib Drasko DRASKOVIC
2012-10-05 12:40 ` Linus Walleij
2012-10-05 13:16 ` Drasko DRASKOVIC
2012-10-07 23:47 ` Drasko DRASKOVIC
2012-10-09 12:00 ` Linus Walleij
2012-10-09 12:27 ` Russell King - ARM Linux
2012-10-09 14:22 ` Drasko DRASKOVIC
2012-10-11 16:26 ` Linus Walleij
2012-11-30 11:30 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-05 10:45 Drasko DRASKOVIC
2012-10-05 11:09 ` Drasko DRASKOVIC
2012-10-05 11:50 ` Mark Brown
2012-10-05 12:15 ` Drasko DRASKOVIC
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121130113021.67D3A3E14C4@localhost \
--to=grant.likely@secretlab.ca \
--cc=drasko.draskovic@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.