linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keerthy <j-keerthy@ti.com>
To: linus.walleij@linaro.org
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	gnurou@gmail.com, grygorii.strashko@ti.com, j-keerthy@ti.com,
	t-kristo@ti.com
Subject: [PATCH V3 0/5] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip
Date: Tue, 17 Jan 2017 21:49:10 +0530	[thread overview]
Message-ID: <1484669955-5349-1-git-send-email-j-keerthy@ti.com> (raw)

The Davinci GPIO driver is implemented to work with one monolithic
Davinci GPIO platform device which may have up to Y(144) gpios.
The Davinci GPIO driver instantiates number of GPIO chips with
max 32 gpio pins per each during initialization and one IRQ domain.
So, the current GPIO's  opjects structure is:

<platform device> Davinci GPIO controller
 |- <gpio0_chip0> ------|
 ...                    |--- irq_domain (hwirq [0..143])
 |- <gpio0_chipN> ------|

Current driver creates one chip for every 32 GPIOs in a controller.
This was a limitation earlier now there is no need for that. Hence
redesigning the driver to create one gpio chip for all the ngpio
in the controller.

|- <gpio0_chip0> ------|--- irq_domain (hwirq [0..143]).

The previous discussion on this can be found here:
https://www.spinics.net/lists/linux-omap/msg132869.html

The series is posted on top of: 

https://lkml.org/lkml/2017/1/4/94

Changes in v2:

  * Optimized the re-design patch.
  * Added couple of code clean ups after the re-design.
  * Included v2 of https://patchwork.ozlabs.org/patch/710855/ 

Changes in v3:

  * Removed one of the clean up patches. As the macros were needed.

Keerthy (5):
  gpio: davinci: Remove gpio2regs function to accommodate multi
    instances
  gpio: davinci: Remove unwanted blank line
  gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip
  gpio: davinci: Add support for multiple GPIO controllers
  gpio: davinci: Remove custom .xlate
  gpio: davinci: Remove redundant macros

 drivers/gpio/gpio-davinci.c                | 174 +++++++++++++----------------
 include/linux/platform_data/gpio-davinci.h |  20 ++--
 2 files changed, 90 insertions(+), 104 deletions(-)

-- 
1.9.1

             reply	other threads:[~2017-01-17 16:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 16:19 Keerthy [this message]
2017-01-17 16:19 ` [PATCH V3 1/5] gpio: davinci: Remove gpio2regs function to accommodate multi instances Keerthy
2017-01-18 23:17   ` Linus Walleij
2017-01-17 16:19 ` [PATCH V3 2/5] gpio: davinci: Remove unwanted blank line Keerthy
2017-01-18 23:18   ` Linus Walleij
2017-01-17 16:19 ` [PATCH V3 3/5] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip Keerthy
2017-01-17 16:19 ` [PATCH V3 4/5] gpio: davinci: Add support for multiple GPIO controllers Keerthy
2017-01-18 23:23   ` Linus Walleij
2017-01-17 16:32 ` [PATCH V3 0/5] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip Keerthy

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=1484669955-5349-1-git-send-email-j-keerthy@ti.com \
    --to=j-keerthy@ti.com \
    --cc=gnurou@gmail.com \
    --cc=grygorii.strashko@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t-kristo@ti.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 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).