From: Keerthy <j-keerthy@ti.com>
To: <linus.walleij@linaro.org>, <t-kristo@ti.com>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<gnurou@gmail.com>, <grygorii.strashko@ti.com>,
<j-keerthy@ti.com>
Subject: [PATCH 0/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip
Date: Wed, 11 Jan 2017 10:30:38 +0530 [thread overview]
Message-ID: <1484110841-2391-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 coouple of clean up patches:
https://lkml.org/lkml/2017/1/4/94
https://patchwork.ozlabs.org/patch/710855/
Keerthy (3):
gpio: davinci: Remove unwanted blank line
gpio: davinci: Redesign driver to accomodate ngpio in one gpio chip
gpio: davinci: Add support for multiple GPIO controllers
drivers/gpio/gpio-davinci.c | 129 +++++++++++++++++------------
include/linux/platform_data/gpio-davinci.h | 13 ++-
2 files changed, 86 insertions(+), 56 deletions(-)
--
1.9.1
next reply other threads:[~2017-01-11 5:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 5:00 Keerthy [this message]
2017-01-11 5:00 ` [PATCH 1/3] gpio: davinci: Remove unwanted blank line Keerthy
2017-01-11 17:37 ` Grygorii Strashko
2017-01-12 1:53 ` Keerthy
2017-01-11 5:00 ` [PATCH 2/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip Keerthy
2017-01-11 17:53 ` Grygorii Strashko
2017-01-12 2:00 ` Keerthy
2017-01-12 19:06 ` Grygorii Strashko
2017-01-13 3:42 ` Keerthy
2017-01-11 5:00 ` [PATCH 3/3] gpio: davinci: Add support for multiple GPIO controllers Keerthy
2017-01-17 14:52 ` [PATCH 0/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip Linus Walleij
2017-01-17 16:14 ` 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=1484110841-2391-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
all inboxes | Powered by JetHome®