Thread (10 messages) 10 messages, 4 authors, 2015-01-16

Re: [Patch v5 2/2] gpio: Document GPIO hogging mechanism

From: Benoit Parrot <hidden>
Date: 2015-01-12 16:42:18
Also in: linux-gpio, lkml

Linus Walleij [off-list ref] wrote on Mon [2015-Jan-12 11:20:14 +0100]:
On Fri, Dec 19, 2014 at 9:07 PM, Benoit Parrot [off-list ref] wrote:
quoted
Add GPIO hogging documentation to gpio.txt

Signed-off-by: Benoit Parrot <redacted>
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
This is starting to look good ...
quoted
+               line_b {
+                       gpio-hog;
+                       gpios = <6 0>;
+                       state = "output-low";
I don't like the state string.

Instead have boolean properties for all states.

line_b {
    gpio-hog;
    gpios = <6 0>;
    output-low;
    line-name = "foo-bar-gpio";
}

Then use of_property_read_bool() in the code to check which
state is to be selected intially. You can check that no mutually
exclusive state are selected, I don't like that an arbitrary string
select the state like that, if we do it that way an enumerator would
be better, I prefer bools.
I am sorry but that is how it was originally in the first patch.
Alexandre's review comment suggested this method in [1] and [2] (below).

Alexandre, any comments?

[1] http://marc.info/?l=linux-gpio&m=141456662426151&w=2

[2] http://marc.info/?l=linux-gpio&m=141715982424744&w=2
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help