From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] pinctrl: qcom: disable GPIO groups with no pins
Date: Fri, 14 Jul 2017 16:43:56 -0500 [thread overview]
Message-ID: <8eaeefc0-2f2c-a488-283f-80e26f4d13f5@codeaurora.org> (raw)
In-Reply-To: <20170714171148.GH22780@codeaurora.org>
On 07/14/2017 12:11 PM, Stephen Boyd wrote:
> gpiochips also have a request() hook. Can we use that before
> initializing direction to make sure the GPIO is accessible?
So I tried it, and it didn't work:
static int msm_gpio_request(struct gpio_chip *chip, unsigned int offset)
{
pr_info("%s:%u offset=%u\n", __func__, __LINE__, offset);
return 0;
}
static struct gpio_chip msm_gpio_template = {
.request = msm_gpio_request,
...
msm_gpio_request() is never called when the driver loads. In fact, I
can't figure out when it would be called.
--
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-07-14 21:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 21:52 [PATCH 0/2] pinctrl: qcom: add support for sparse GPIOs Timur Tabi
2017-07-13 21:52 ` [PATCH 1/2] pinctrl: qcom: disable GPIO groups with no pins Timur Tabi
2017-07-14 16:44 ` Bjorn Andersson
2017-07-14 17:01 ` Timur Tabi
2017-07-14 17:35 ` Bjorn Andersson
2017-07-14 17:11 ` Stephen Boyd
2017-07-14 17:17 ` Timur Tabi
2017-07-14 17:23 ` Bjorn Andersson
2017-07-14 21:43 ` Timur Tabi [this message]
2017-07-14 21:46 ` Stephen Boyd
2017-07-14 22:01 ` Timur Tabi
2017-07-14 22:04 ` Stephen Boyd
2017-07-13 21:52 ` [PATCH 2/2] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002 Timur Tabi
2017-07-14 17:21 ` Bjorn Andersson
2017-07-14 18:30 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2017-06-30 0:42 [PATCH 1/2] pinctrl: qcom: disable GPIO groups with no pins 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=8eaeefc0-2f2c-a488-283f-80e26f4d13f5@codeaurora.org \
--to=timur@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).