From: Matt Porter <mporter@kernel•crashing.org>
To: "Travis B. Sawyer" <tsawyer+linuxppc@sandburst•com>
Cc: Steven Blakeslee <BlakesleeS@embeddedplanet•com>,
ppcembed <linuxppc-embedded@ozlabs•org>
Subject: Re: 2.6 4xx GPIO OCP driver?
Date: Fri, 25 Feb 2005 13:30:55 -0700 [thread overview]
Message-ID: <20050225133055.A28918@cox.net> (raw)
In-Reply-To: <421F89A0.8070502@sandburst.com>; from tsawyer+linuxppc@sandburst.com on Fri, Feb 25, 2005 at 03:25:04PM -0500
On Fri, Feb 25, 2005 at 03:25:04PM -0500, Travis B. Sawyer wrote:
> Steven Blakeslee wrote:
> >>In 2.4 we used the drivers/char/ibm_ocp_gpio.c module. I see
> >>no such support in 2.6.10. I perused the archives, found
> >>nothing (OBTW: can someone point me to the search engine for
> >>the list?)
> >
> >
> > I see it. Drivers/char/ibm_gpio.c in Linux 2.6.10-rc3.
>
> I guess I should be using the linuxppc-2.5 tree instead of straight from
> kernel.org.
I didn't bother merging it upstream at one time. It wasn't clear
if the driver had any value over just mmaping /dev/mem to bang
on the couple gpio registers directly. We can get it in real
2.6 if people really find it more convenient. My only argument
against it is that it's not much of a layer over the trivial
registers and each SoC requires completely different support
since the pin routings are SoC specific.
Anyway, just speak up. ;)
-Matt
next prev parent reply other threads:[~2005-02-25 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 19:40 2.6 4xx GPIO OCP driver? Steven Blakeslee
2005-02-25 20:25 ` Travis B. Sawyer
2005-02-25 20:30 ` Matt Porter [this message]
2005-02-25 20:51 ` Travis B. Sawyer
2005-02-25 21:19 ` Ralph Siemsen
2005-02-26 0:29 ` Matt Porter
2005-02-26 22:31 ` Travis Sawyer
2005-02-26 22:31 ` Travis B. Sawyer
-- strict thread matches above, loose matches on Subject: below --
2005-02-25 17:17 Travis B. Sawyer
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=20050225133055.A28918@cox.net \
--to=mporter@kernel$(echo .)crashing.org \
--cc=BlakesleeS@embeddedplanet$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=tsawyer+linuxppc@sandburst$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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