From: Johan Hovold <johan@kernel.org>
To: grygorii.strashko@linaro.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: debugfs: display gpios requested as irq only
Date: Mon, 18 May 2015 13:02:14 +0200 [thread overview]
Message-ID: <20150518110214.GC28127@localhost> (raw)
In-Reply-To: <1431696321-7257-1-git-send-email-grygorii.strashko@linaro.org>
On Fri, May 15, 2015 at 04:25:21PM +0300, grygorii.strashko@linaro.org wrote:
> From: Grygorii Strashko <grygorii.strashko@linaro.org>
>
> Now GPIOs, wich are requested as IRQ only, will not be displayed
> through GPIO debugfs. For example:
> # cat /proc/interrupts
> CPU0 CPU1
> ...
> 209: 0 0 4805d000.gpio 11 Edge 0-0021
>
> # cat /debug/gpio
> ...
> GPIOs 160-191, platform/4805d000.gpio, gpio:
> <--- no info about gpio used as IRQ only here
>
> GPIOs 192-223, platform/48051000.gpio, gpio:
> gpio-203 (vtt_fixed ) out hi
> ...
>
> Hence, improve GPIO debugfs code to show such kind of gpio and print
> IRQ number also. In addition, add marker "requested" for GPIOs wich
> were requested by using gpioX_request().
>
> After this patch sys/kernel/debug/gpio will produce following output:
>
> # cat /debug/gpio
> ...
> GPIOs 160-191, platform/4805d000.gpio, gpio:
> gpio-171 ((null) ) in hi IRQ209
>
> GPIOs 192-223, platform/48051000.gpio, gpio:
> gpio-203 (vtt_fixed ) out hi requested
This is backwards. All gpios *should* be requested. *If* we are to
include not-requested gpios in the debug output, then it is those pins
that need to be marked as not-requested.
The irq-number mapping could perhaps be useful, but it should go in a
separate patch. I'd suggest adding a '-' before the irq-number (e.g.
"IRQ-209").
Thanks,
Johan
next prev parent reply other threads:[~2015-05-18 11:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 13:25 [PATCH] gpiolib: debugfs: display gpios requested as irq only grygorii.strashko
2015-05-18 11:02 ` Johan Hovold [this message]
2015-05-18 13:06 ` Grygorii.Strashko@linaro.org
2015-05-18 15:08 ` Johan Hovold
2015-05-18 15:17 ` Grygorii.Strashko@linaro.org
2015-05-18 15:58 ` Johan Hovold
2015-05-19 14:12 ` Linus Walleij
2015-05-19 14:37 ` Grygorii.Strashko@linaro.org
2015-05-19 14:50 ` Linus Walleij
2015-05-19 15:39 ` Johan Hovold
2015-05-20 7:21 ` Linus Walleij
2015-05-21 14:34 ` Johan Hovold
2015-05-19 14:28 ` Linus Walleij
2015-05-21 14:25 ` Johan Hovold
2015-05-21 20:33 ` Grygorii.Strashko@linaro.org
2015-05-24 17:12 ` Johan Hovold
2015-05-25 18:54 ` Grygorii.Strashko@linaro.org
2015-05-25 20:39 ` Johan Hovold
2015-06-01 13:09 ` Linus Walleij
2015-06-02 12:33 ` Grygorii.Strashko@linaro.org
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=20150518110214.GC28127@localhost \
--to=johan@kernel.org \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).