From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stephen Boyd <sboyd@codeaurora.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Timur Tabi <timur@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-gpio@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/3] dt-bindings: pinctrl: Add a ngpios-ranges property
Date: Wed, 10 Jan 2018 19:59:31 +0200 [thread overview]
Message-ID: <1515607171.7000.879.camel@linux.intel.com> (raw)
In-Reply-To: <20180110163733.GH21040@codeaurora.org>
On Wed, 2018-01-10 at 08:37 -0800, Stephen Boyd wrote:
> On 01/10, Linus Walleij wrote:
> > On Wed, Jan 10, 2018 at 2:58 AM, Stephen Boyd <sboyd@codeaurora.org>
> > wrote:
> for the qcom driver it was all fine
> because all three concepts: irq, gpios, and pins have a one to
> one relationship.
Just a side note: While it might be the case for most of the
controllers, don't assume it's a generic case.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
WARNING: multiple messages have this Message-ID (diff)
From: andriy.shevchenko@linux.intel.com (Andy Shevchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] dt-bindings: pinctrl: Add a ngpios-ranges property
Date: Wed, 10 Jan 2018 19:59:31 +0200 [thread overview]
Message-ID: <1515607171.7000.879.camel@linux.intel.com> (raw)
In-Reply-To: <20180110163733.GH21040@codeaurora.org>
On Wed, 2018-01-10 at 08:37 -0800, Stephen Boyd wrote:
> On 01/10, Linus Walleij wrote:
> > On Wed, Jan 10, 2018 at 2:58 AM, Stephen Boyd <sboyd@codeaurora.org>
> > wrote:
> for the qcom driver it was all fine
> because all three concepts: irq, gpios, and pins have a one to
> one relationship.
Just a side note: While it might be the case for most of the
controllers, don't assume it's a generic case.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-01-10 17:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 1:58 [PATCH 0/3] Support qcom pinctrl protected pins Stephen Boyd
2018-01-10 1:58 ` Stephen Boyd
[not found] ` <20180110015848.11480-1-sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-01-10 1:58 ` [PATCH 1/3] gpiolib: Export gpiochip_irqchip_irq_valid() to drivers Stephen Boyd
2018-01-10 1:58 ` Stephen Boyd
2018-01-10 1:58 ` Stephen Boyd
2018-01-10 6:16 ` Bjorn Andersson
2018-01-10 6:16 ` Bjorn Andersson
2018-01-10 13:22 ` Linus Walleij
2018-01-10 13:22 ` Linus Walleij
2018-01-10 1:58 ` [PATCH 2/3] dt-bindings: pinctrl: Add a ngpios-ranges property Stephen Boyd
2018-01-10 1:58 ` Stephen Boyd
2018-01-10 12:54 ` Andy Shevchenko
2018-01-10 12:54 ` Andy Shevchenko
[not found] ` <20180110015848.11480-3-sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-01-10 13:37 ` Linus Walleij
2018-01-10 13:37 ` Linus Walleij
2018-01-10 13:37 ` Linus Walleij
2018-01-10 16:37 ` Stephen Boyd
2018-01-10 16:37 ` Stephen Boyd
2018-01-10 17:59 ` Andy Shevchenko [this message]
2018-01-10 17:59 ` Andy Shevchenko
2018-01-11 16:33 ` Grant Likely
2018-01-11 16:33 ` Grant Likely
2018-01-11 16:36 ` Timur Tabi
2018-01-11 16:36 ` Timur Tabi
2018-01-11 19:56 ` Grant Likely
2018-01-11 19:56 ` Grant Likely
2018-01-10 1:58 ` [PATCH 3/3] pinctrl: qcom: Don't allow protected pins to be requested Stephen Boyd
2018-01-10 1:58 ` Stephen Boyd
2018-01-10 6:11 ` Bjorn Andersson
2018-01-10 6:11 ` Bjorn Andersson
2018-01-22 13:55 ` Timur Tabi
2018-01-22 13:55 ` Timur Tabi
2018-01-22 20:03 ` Timur Tabi
2018-01-22 20:03 ` Timur Tabi
2018-01-22 20:03 ` Timur Tabi
2018-01-25 21:51 ` Stephen Boyd
2018-01-25 21:51 ` Stephen Boyd
2018-01-25 21:53 ` Timur Tabi
2018-01-25 21:53 ` Timur Tabi
2018-01-25 20:48 ` Timur Tabi
2018-01-25 20:48 ` 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=1515607171.7000.879.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--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 \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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 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.