From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: David Brownell <david-b@pacbell.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] GPIO-based flow control in the cpm_uart driver
Date: Tue, 20 May 2008 15:00:35 +0200 [thread overview]
Message-ID: <200805201500.38236.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <200805191731.33193.david-b@pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Tuesday 20 May 2008 02:31, David Brownell wrote:
> On Tuesday 15 April 2008, Laurent Pinchart wrote:
> > Or maybe some kind of gpio_set_option() with flags specific to the
> > controller ? This could be used to enable open-drain outputs or internal
> > pull-ups for instance.
>
> That presumes that the pin config is associated with the GPIO
> controller, rather than being an independent modules...
>
> In the cases that a platform has such an association, there
> should be no problem just using a platform-specific code to
> do the relevant magic.
To call GPIO chip specific functions, the driver needs a way to get the GPIO
chip associated with the GPIO.
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-20 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 13:22 [RFC] GPIO-based flow control in the cpm_uart driver Laurent Pinchart
2008-04-15 13:40 ` Anton Vorontsov
2008-04-15 13:47 ` Laurent Pinchart
2008-04-15 14:30 ` Anton Vorontsov
2008-05-20 0:31 ` David Brownell
2008-05-20 13:00 ` Laurent Pinchart [this message]
2008-05-20 0:25 ` David Brownell
2008-05-20 12:50 ` Laurent Pinchart
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=200805201500.38236.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=david-b@pacbell.net \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).