All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@codeaurora.org>
To: linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	thierry.reding@gmail.com, Stephen Boyd <sboyd@codeaurora.org>,
	david.brown@linaro.org, andy.gross@linaro.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH 0/4] [v7] pinctrl: qcom: add support for sparse GPIOs
Date: Mon, 13 Nov 2017 13:19:02 -0600	[thread overview]
Message-ID: <c219c289-9cad-f96c-f766-ec28af8f078d@codeaurora.org> (raw)
In-Reply-To: <1510096056-13765-1-git-send-email-timur@codeaurora.org>

On 11/07/2017 05:07 PM, Timur Tabi wrote:
> A series of patches that add support for GPIO maps that have holes in
> them.  That is, even though a client driver has N consecutive GPIOs,
> some are just unavailable for whatever reason, and the hardware should
> not be accessed for those GPIOs.

Any chance of these patches going into 4.15?  I've been making lots of 
changes, but I haven't gotten a lot of feedback.  I still think that v7 
is more intrusive and risky than v5, with no real benefit.  But at this 
point, I just want something to be merged so that I stop thinking about 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 0/4] [v7] pinctrl: qcom: add support for sparse GPIOs
Date: Mon, 13 Nov 2017 13:19:02 -0600	[thread overview]
Message-ID: <c219c289-9cad-f96c-f766-ec28af8f078d@codeaurora.org> (raw)
In-Reply-To: <1510096056-13765-1-git-send-email-timur@codeaurora.org>

On 11/07/2017 05:07 PM, Timur Tabi wrote:
> A series of patches that add support for GPIO maps that have holes in
> them.  That is, even though a client driver has N consecutive GPIOs,
> some are just unavailable for whatever reason, and the hardware should
> not be accessed for those GPIOs.

Any chance of these patches going into 4.15?  I've been making lots of 
changes, but I haven't gotten a lot of feedback.  I still think that v7 
is more intrusive and risky than v5, with no real benefit.  But at this 
point, I just want something to be merged so that I stop thinking about 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.

  parent reply	other threads:[~2017-11-13 19:19 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 23:07 [PATCH 0/4] [v7] pinctrl: qcom: add support for sparse GPIOs Timur Tabi
2017-11-07 23:07 ` Timur Tabi
2017-11-07 23:07 ` [PATCH 1/4] [v2] Revert "gpio: set up initial state from .get_direction()" Timur Tabi
2017-11-07 23:07   ` Timur Tabi
2017-11-07 23:07 ` [PATCH 2/4] gpiolib: add bitmask for valid GPIO lines Timur Tabi
2017-11-07 23:07   ` Timur Tabi
     [not found]   ` <b2b5374b-17a6-e068-ef8b-edc90d34c352@codeaurora.org>
2017-11-15  6:28     ` Fwd: " Varadarajan Narayanan
2017-11-15  6:28       ` Varadarajan Narayanan
2017-11-15 11:38       ` Andy Shevchenko
2017-11-15 11:38         ` Andy Shevchenko
2017-11-15 15:15         ` Timur Tabi
2017-11-15 15:15           ` Timur Tabi
2017-12-01 11:38   ` Archit Taneja
2017-12-01 11:38     ` Archit Taneja
2017-12-01 17:16     ` Timur Tabi
2017-12-01 17:16       ` Timur Tabi
2017-11-07 23:07 ` [PATCH 3/4] [v6] pinctrl: qcom: disable GPIO groups with no pins Timur Tabi
2017-11-07 23:07   ` Timur Tabi
2017-11-17  2:43   ` Stephen Boyd
2017-11-17  2:43     ` Stephen Boyd
2017-11-17  2:58     ` Timur Tabi
2017-11-17  2:58       ` Timur Tabi
2017-11-17 17:46       ` Stephen Boyd
2017-11-17 17:46         ` Stephen Boyd
2017-11-17 17:49         ` Timur Tabi
2017-11-17 17:49           ` Timur Tabi
2017-11-17 21:42           ` Stephen Boyd
2017-11-17 21:42             ` Stephen Boyd
2017-11-17 21:44             ` Timur Tabi
2017-11-17 21:44               ` Timur Tabi
2017-11-07 23:07 ` [PATCH 4/4] [v3] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002 Timur Tabi
2017-11-07 23:07   ` Timur Tabi
     [not found]   ` <133cd447-c5c8-2b3e-1ae2-484307d5e39d@codeaurora.org>
2017-11-15  6:47     ` Fwd: " Varadarajan Narayanan
2017-11-15  6:47       ` Varadarajan Narayanan
2017-11-15 15:14       ` Timur Tabi
2017-11-15 15:14         ` Timur Tabi
2017-11-13 19:19 ` Timur Tabi [this message]
2017-11-13 19:19   ` [PATCH 0/4] [v7] pinctrl: qcom: add support for sparse GPIOs Timur Tabi
2017-11-13 21:49   ` Linus Walleij
2017-11-13 21:49     ` Linus Walleij
2017-11-13 21:53     ` Timur Tabi
2017-11-13 21:53       ` Timur Tabi
2017-11-14 10:03       ` Linus Walleij
2017-11-14 10:03         ` Linus Walleij
2017-11-15 15:06         ` Timur Tabi
2017-11-15 15:06           ` 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=c219c289-9cad-f96c-f766-ec28af8f078d@codeaurora.org \
    --to=timur@codeaurora.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --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 \
    --cc=mika.westerberg@linux.intel.com \
    --cc=sboyd@codeaurora.org \
    --cc=thierry.reding@gmail.com \
    /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.