From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Timur Tabi <timur@codeaurora.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: qcom: qdf2xxx: expose only some GPIO pins
Date: Thu, 29 Jun 2017 14:49:22 -0700 [thread overview]
Message-ID: <20170629214922.GC18666@tuxbook> (raw)
In-Reply-To: <d5cb17b6-083a-58a0-caa6-01ee06ff1fd4@codeaurora.org>
On Thu 29 Jun 12:37 PDT 2017, Timur Tabi wrote:
> On 06/23/2017 07:33 AM, Linus Walleij wrote:
> > I think using "lsgpio" fron tools/gpio/lsgpio.c is better to inspect
> > the available GPIOs.
> >
> > If you haven't tested the GPIO tools, please try it out.
>
> Unfortunately, this tool isn't very useful:
>
I believe you have to come up with a separate array of names and attach
that to the gpio_chip in msm_gpio_init() for the _gpio_ pins to have
names. The names we specify in the pin driver is only the name of the
pinctrl pin...
Regards,
Bjorn
> $ sudo ./lsgpio
> GPIO chip: gpiochip0, "QCOM8001:00", 150 GPIO lines
> line 0: unnamed unused [output]
> line 1: unnamed unused [output]
> line 2: unnamed unused [output]
> line 3: unnamed unused [output]
> line 4: unnamed unused [output]
> line 5: unnamed unused [output]
> line 6: unnamed unused [output]
> line 7: unnamed unused [output]
> line 8: unnamed unused [output]
> line 9: unnamed unused [output]
> line 10: unnamed unused [output]
> line 11: unnamed unused [output]
> line 12: unnamed unused [output]
> line 13: unnamed unused [output]
> line 14: unnamed unused [output]
> line 15: unnamed unused [output]
> line 16: unnamed unused [output]
> line 17: unnamed unused [output]
> line 18: unnamed unused [output]
> line 19: unnamed unused [output]
> line 20: unnamed unused [output]
> line 21: unnamed unused [output]
> line 22: unnamed unused [output]
> line 23: unnamed unused [output]
> line 24: unnamed unused [output]
> line 25: unnamed unused [output]
> line 26: unnamed unused [output]
> line 27: unnamed unused [output]
> line 28: unnamed unused [output]
> line 29: unnamed unused [output]
> line 30: unnamed unused [output]
> line 31: unnamed unused [output]
> line 32: unnamed unused [output]
> line 33: unnamed unused [output]
> line 34: unnamed unused [output]
> line 35: unnamed unused [output]
> line 36: unnamed unused
> line 37: unnamed "sysfs" [kernel]
> line 38: unnamed unused
> line 39: unnamed unused
> line 40: unnamed unused [output]
> ...
>
> --
> Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
> Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
> Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-06-29 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 20:54 [PATCH] pinctrl: qcom: qdf2xxx: expose only some GPIO pins Timur Tabi
2017-06-23 12:33 ` Linus Walleij
2017-06-23 13:28 ` Timur Tabi
2017-06-28 19:12 ` Bjorn Andersson
2017-06-28 19:23 ` Timur Tabi
2017-06-28 22:38 ` Timur Tabi
2017-06-29 19:37 ` Timur Tabi
2017-06-29 21:49 ` Bjorn Andersson [this message]
2017-06-29 22:10 ` Linus Walleij
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=20170629214922.GC18666@tuxbook \
--to=bjorn.andersson@linaro.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=timur@codeaurora.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).