From: Timur Tabi <timur@codeaurora.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] gliolib: request the gpio before querying its direction
Date: Mon, 21 Aug 2017 16:23:50 -0500 [thread overview]
Message-ID: <103341c8-6cc5-3d3f-eef7-28b9f31cdc71@codeaurora.org> (raw)
In-Reply-To: <CACRpkdYPBd4ZvuXo__LRQezTQD3u=3r2WO+2dTzBanLL1zX72w@mail.gmail.com>
On 07/31/2017 08:35 AM, Linus Walleij wrote:
>> Before querying a GPIO to determine its direction, the GPIO should be
>> formally requested. This allows the GPIO driver to block access to
>> unavailable GPIOs, which makes it easier for some drivers to support
>> sparse GPIO maps.
>>
>> Signed-off-by: Timur Tabi<timur@codeaurora.org>
> This makes all kind of semantic change, so patch applied.
Have you push it to git.kernel.org? I don't see it.
--
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.
WARNING: multiple messages have this Message-ID (diff)
From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] gliolib: request the gpio before querying its direction
Date: Mon, 21 Aug 2017 16:23:50 -0500 [thread overview]
Message-ID: <103341c8-6cc5-3d3f-eef7-28b9f31cdc71@codeaurora.org> (raw)
In-Reply-To: <CACRpkdYPBd4ZvuXo__LRQezTQD3u=3r2WO+2dTzBanLL1zX72w@mail.gmail.com>
On 07/31/2017 08:35 AM, Linus Walleij wrote:
>> Before querying a GPIO to determine its direction, the GPIO should be
>> formally requested. This allows the GPIO driver to block access to
>> unavailable GPIOs, which makes it easier for some drivers to support
>> sparse GPIO maps.
>>
>> Signed-off-by: Timur Tabi<timur@codeaurora.org>
> This makes all kind of semantic change, so patch applied.
Have you push it to git.kernel.org? I don't see it.
--
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-08-21 21:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 18:19 [PATCH 0/3][v3] pinctrl: qcom: add support for sparse GPIOs Timur Tabi
2017-07-27 18:19 ` Timur Tabi
2017-07-27 18:19 ` [PATCH 1/3] gliolib: request the gpio before querying its direction Timur Tabi
2017-07-27 18:19 ` Timur Tabi
2017-07-31 13:35 ` Linus Walleij
2017-07-31 13:35 ` Linus Walleij
2017-08-21 21:23 ` Timur Tabi [this message]
2017-08-21 21:23 ` Timur Tabi
2017-08-23 8:32 ` Linus Walleij
2017-08-23 8:32 ` Linus Walleij
2017-08-23 23:28 ` Timur Tabi
2017-08-23 23:28 ` Timur Tabi
2017-08-24 21:28 ` Linus Walleij
2017-08-24 21:28 ` Linus Walleij
2017-08-24 22:00 ` Timur Tabi
2017-08-24 22:00 ` Timur Tabi
2017-07-27 18:19 ` [PATCH 2/3] [v3] pinctrl: qcom: disable GPIO groups with no pins Timur Tabi
2017-07-27 18:19 ` Timur Tabi
2017-07-31 13:36 ` Linus Walleij
2017-07-31 13:36 ` Linus Walleij
2017-08-09 19:02 ` Timur Tabi
2017-08-09 19:02 ` Timur Tabi
2017-08-16 18:10 ` Jiandi An
2017-08-16 18:10 ` Jiandi An
2017-08-16 18:32 ` Timur Tabi
2017-08-16 18:32 ` Timur Tabi
2017-08-16 19:30 ` Jiandi An
2017-08-16 19:30 ` Jiandi An
2017-08-16 19:31 ` Jiandi An
2017-08-16 19:31 ` Jiandi An
2017-08-16 19:55 ` Timur Tabi
2017-08-16 19:55 ` Timur Tabi
2017-07-27 18:19 ` [PATCH 3/3] [v2] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002 Timur Tabi
2017-07-27 18:19 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2017-07-17 23:43 [PATCH 0/3][v2] pinctrl: qcom: add support for sparse GPIOs Timur Tabi
2017-07-17 23:43 ` [PATCH 1/3] gliolib: request the gpio before querying its direction Timur Tabi
2017-07-17 23:43 ` 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=103341c8-6cc5-3d3f-eef7-28b9f31cdc71@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.