From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ppc4xx: gpio setup broken for ppc405ep
Date: Mon, 31 Mar 2008 13:13:33 +0200 [thread overview]
Message-ID: <200803311313.33224.sr@denx.de> (raw)
In-Reply-To: <6a6049b80803310351v751b21f4ya120841fb7a5845f@mail.gmail.com>
On Monday 31 March 2008, M B wrote:
> > No. High and low *are* swapped. I just re-checked with users manual rev
> > 1.08. GPIO0_OSRH has offset 0x0C and GPIO0_OSRL has offset 0x08. So this
> > matches the offsets of all other 4xx GPIO registers I have seen so far.
>
> You're right. This was fixed in v 1.06, so this explains why I and
> ppc405.h was wrong.
> btw. v1.10 of the Users Manual is out.
Thanks. I'll download right away.
> > I'm not really sure if this is true though since Taihu is using
> > gpio_set_chip_configuration() without known problems. Could you please
> > re-check with AMCC support, if this statement for 405EP is correct? If
> > this pin assignment of the 405EP GPIO block is incompatible with other
> > GPIO cores, like the one on 440EP or 405EX.
>
> I will do.
> All ppc405 which used the CFG_GPIO0_*{H,L} defines in their config
> file were using the "wrong" address.
No. 405EX & 405EZ which were added recently are using the correct addresses.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-03-31 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 18:04 [U-Boot-Users] ppc4xx: gpio setup broken for ppc405ep M B
2008-03-28 10:34 ` Stefan Roese
2008-03-31 8:54 ` Markus Brunner
2008-03-31 9:20 ` Stefan Roese
2008-03-31 10:51 ` M B
2008-03-31 11:13 ` Stefan Roese [this message]
2008-03-31 11:33 ` M B
2008-04-23 6:54 ` Markus Brunner
2008-04-23 14:25 ` Stefan Roese
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=200803311313.33224.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.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