From: Rabin Vincent <rabin.vincent@stericsson.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [RFC] gpio/stmpe: add bitmask to block requests to unavailable GPIOs
Date: Thu, 19 Aug 2010 18:36:05 +0530 [thread overview]
Message-ID: <20100819130605.GA25901@bnru01.bnr.st.com> (raw)
In-Reply-To: <20100818103137.GB3528@pengutronix.de>
On Wed, Aug 18, 2010 at 12:31:37 +0200, Wolfram Sang wrote:
> On Wed, Aug 18, 2010 at 03:39:50PM +0530, Rabin VINCENT wrote:
> > On Mon, Aug 16, 2010 at 17:14:44 +0200, Wolfram Sang wrote:
> > > GPIOs on these controller are multi-functional. If you decided to use
> > > some of them e.g. as input channels for the ADC, you surely don't want
> > > those pins to be reassigned as simple GPIOs (which may be triggered even
> > > from userspace via 'export'). Same for the touchscreen controller pins.
> > > Since knowledge about the hardware is needed to decide which GPIOs to
> > > reserve, let this bitmask be inside platform_data and provide some
> > > defines to assist potential users.
> >
> > Could this be done without the platform data, say something like the
> > below? (Though this does assume that nobody tries to request GPIOs
> > before the STMPE subdrivers reserve their pins.)
> >
>
> While I'd also like to skip the additional platform_data entry, your
> last comment is in deed a drawback.
Yes, especially if the subdrivers are dynamically loaded. Your patch is
fine with me:
Acked-by: Rabin Vincent <rabin.vincent@stericsson.com>
The only minor comment is that the STMPE_GPIO_NOREQ_811_TOUCH name could
perhaps be clearer. STMPE811_GPIO_NOREQ_TOUCHSCREEN, maybe?
Rabin
next prev parent reply other threads:[~2010-08-19 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 15:14 Wolfram Sang
2010-08-18 10:09 ` Rabin VINCENT
2010-08-18 10:31 ` Wolfram Sang
2010-08-19 13:06 ` Rabin Vincent [this message]
2010-08-19 13:26 ` Wolfram Sang
2010-08-20 22:25 ` Samuel Ortiz
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=20100819130605.GA25901@bnru01.bnr.st.com \
--to=rabin.vincent@stericsson.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=w.sang@pengutronix.de \
/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®