From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <Ashish.Jangam@kpitcummins.com>
Cc: "jic23@cam.ac.uk" <jic23@cam.ac.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dajun <dajun.chen@diasemi.com>,
"grant@secretlab.ca" <grant@secretlab.ca>
Subject: Re: [PATCH 02/11] GPIO: DA9052 GPIO module v1
Date: Thu, 30 Jun 2011 08:32:45 -0700 [thread overview]
Message-ID: <20110630152852.GC3249@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <E2CAE7F7B064EA49B5CE7EE9A4BB167D152EB8925D@KCINPUNHJCMS01.kpit.com>
On Thu, Jun 30, 2011 at 05:10:31PM +0530, Ashish Jangam wrote:
> > Why insist on platform data? gpiolib can dynamically allocate a GPIO
> > range to the device.
> Do you mean to use gpiochip_reserve() in machine file and not to have
> ngpio and base defined in GPIO platform driver but, this will fail the
> call to gpiochip_add()?
No, I mean that you should allow gpiolib to allocate a GPIO range if one
is not already allocated like other gpiolib drivers do by supplying -1
as the base.
prev parent reply other threads:[~2011-06-30 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 13:53 [PATCH 02/11] GPIO: DA9052 GPIO module v1 ashishj3
2011-06-30 5:37 ` Mark Brown
2011-06-30 11:40 ` Ashish Jangam
2011-06-30 15:32 ` Mark Brown [this message]
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=20110630152852.GC3249@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Ashish.Jangam@kpitcummins.com \
--cc=dajun.chen@diasemi.com \
--cc=grant@secretlab.ca \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox