From: Timur Tabi <timur@codeaurora.org>
To: andy.gross@linaro.org, david.brown@linaro.org,
Linus Walleij <linus.walleij@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-gpio@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: timur@codeaurora.org
Subject: [PATCH 0/3][v2] pinctrl: qcom: add support for sparse GPIOs
Date: Mon, 17 Jul 2017 18:43:58 -0500 [thread overview]
Message-ID: <1500335041-32711-1-git-send-email-timur@codeaurora.org> (raw)
First patch update gpiolib so that it requests the GPIO before trying to
initialize it.
Second patch allows for for pinctrl-msm to understand GPIO groups with
no pins. Such pins are "hidden" and can't be exported or accessed.
Last patch updates the QDF2xxx driver to take advantage of all that.
Timur Tabi (3):
gliolib: request the gpio before querying its direction
[v2] pinctrl: qcom: disable GPIO groups with no pins
[v2] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002
drivers/gpio/gpiolib.c | 11 +++
drivers/pinctrl/qcom/pinctrl-msm.c | 22 ++++--
drivers/pinctrl/qcom/pinctrl-qdf2xxx.c | 139 ++++++++++++++++++++++++---------
3 files changed, 131 insertions(+), 41 deletions(-)
--
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 reply other threads:[~2017-07-17 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 23:43 Timur Tabi [this message]
2017-07-17 23:43 ` [PATCH 1/3] gliolib: request the gpio before querying its direction Timur Tabi
2017-07-17 23:44 ` [PATCH 2/3] [v2] pinctrl: qcom: disable GPIO groups with no pins Timur Tabi
2017-07-17 23:44 ` [PATCH 3/3] [v2] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002 Timur Tabi
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=1500335041-32711-1-git-send-email-timur@codeaurora.org \
--to=timur@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@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).