From: "Grygorii.Strashko@linaro.org" <grygorii.strashko@linaro.org>
To: Johan Hovold <johan@kernel.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 16:06:08 +0300 [thread overview]
Message-ID: <5559E3C0.1040207@linaro.org> (raw)
In-Reply-To: <20150518110214.GC28127@localhost>
Hi Johan,
On 05/18/2015 02:02 PM, Johan Hovold wrote:
> 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.
Sry, but I didn't fully understand your point here ( - Why is it backward?
Now GPIO can be requested in three ways:
1) As pure GPIO (gpioX_request())
2) As pure GPIO IRQ, especially in DT boot case.
DT:
interrupt-parent = <&gpio6>;
interrupts = <11 IRQ_TYPE_EDGE_FALLING>;
Code:
platform_get_irq() or of_irq_get()
request_irq()
3) combination of (1) and (2) with one restriction
- GPIO direction should be 'In' and can't be changed.
Personally I'm using this case for debug purposes to do a fast check of GPIO pin state
through GPIO sysfs (GPIO export) when such GPIO is used as GPIO IRQ in some driver
and I don't see that corresponding IRQ is triggered as expected.
So, this patch just adds missed information in GPIO debugfs for the case (2) in general.
Of course, format of the marker "requested" is discussable. Could be:
- "requested" --> "not-requested"
- "I R" or "I G" where I - IRQ, G - GPIO, R - requested
- etc.
>
> 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").
I've thought about this, but finally decided not to split it.
Could be done, if you insist )
--
regards,
-grygorii
next prev parent reply other threads:[~2015-05-18 13:06 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
2015-05-18 13:06 ` Grygorii.Strashko@linaro.org [this message]
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=5559E3C0.1040207@linaro.org \
--to=grygorii.strashko@linaro.org \
--cc=gnurou@gmail.com \
--cc=johan@kernel.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).