From: Trent Piepho <tpiepho@freescale.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [v5] powerpc: gpio driver for mpc8349/8572/8610 and compatible
Date: Wed, 29 Oct 2008 18:07:47 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0810291718350.25957@t2.domain.actdsltmp> (raw)
In-Reply-To: <1222184138-6151-1-git-send-email-jacmet@sunsite.dk>
On Tue, 23 Sep 2008, Peter Korsgaard wrote:
> +- compatible : "fsl,<CHIP>-gpio" followed by "fsl,mpc8349-gpio" for
> + 83xx, "fsl,mpc8572-gpio" for 85xx and "fsl,mpc8610-gpio" for 86xx.
Why have the three different compatible settings when the code doesn't do
anything different?
> +#define MPC8XXX_GPIO_PINS 32
8572 has eight GPIOs.
I wrote an MPC8572 GPIO driver back in March, and posted it internally at
Freescale on June 2nd. But it was just ignored... I wonder what your secret
is to get Kumar to apply your patches? It's too bad this work keeps getting
duplicated.
My patch started out *very* much like yours, except it pre-dated the OF gpio
controller stuff and of_mm_gpiochip so it didn't use that.
But, I'm using the GPIOs to bit-bang a JTAG bus in the 20-30 MHz range. The
obvious GPIO driver is *much* too slow for that. I got less than 3 MHz, and
your driver looks like it might be slightly slower than my initial driver.
So I went to a lot of effort to speed it up and managed to increase GPIO
performance by nearly a factor of 10. Trying to commit my driver at this
point is probably hopeless and I doubt anyone else cares about gpio speed.
But at least the number of gpios for 8572 can be fixed.
next prev parent reply other threads:[~2008-10-30 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 15:35 [PATCH v5] powerpc: gpio driver for mpc8349/8572/8610 and compatible Peter Korsgaard
2008-09-23 15:42 ` Kumar Gala
2008-10-30 1:07 ` Trent Piepho [this message]
2008-10-30 7:45 ` [v5] " Peter Korsgaard
2008-10-30 8:58 ` Trent Piepho
2008-10-30 13:44 ` Kumar Gala
2008-10-30 14:39 ` Nate Case
2008-10-30 18:04 ` Anton Vorontsov
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=Pine.LNX.4.64.0810291718350.25957@t2.domain.actdsltmp \
--to=tpiepho@freescale.com \
--cc=jacmet@sunsite.dk \
--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