From: Martyn Welch <martyn.welch@ge•com>
To: linuxppc-dev list <linuxppc-dev@ozlabs•org>
Subject: GE GPIO and PIC support.
Date: Mon, 18 Jan 2010 16:20:58 +0000 [thread overview]
Message-ID: <4B548A6A.5010708@ge.com> (raw)
Hi,
I'm currently adding support for a GE board based on the Freescale
P2020. This board has a cascaded interrupt controller and GPIO which
should be compatible with drivers currently provided for the MPC8641D
based boards that are already in the kernel.
At the moment the drivers (in gef_gpio.c and gef_pic.c) are in the
"arch/powerpc/platforms/86xx" folder. As the p2020 is not 86xx, I guess
I should move these drivers to a more central location. I'm currently
not sure where would be best to move them to, I see
"arch/powerpc/sysdev" and "arch/powerpc/platforms" as potential
locations, where would be the most suitable?
Martyn
--
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms | Wales (3828642) at 100
T +44(0)127322748 | Barbirolli Square, Manchester,
E martyn.welch@ge•com | M2 3AB VAT:GB 927559189
next reply other threads:[~2010-01-18 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 16:20 Martyn Welch [this message]
2010-01-18 19:41 ` GE GPIO and PIC support Kumar Gala
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=4B548A6A.5010708@ge.com \
--to=martyn.welch@ge$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/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