From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH v5] QE IO: Add initial data to pin configuration + read/write functions
Date: Fri, 29 Feb 2008 10:48:40 -0600 [thread overview]
Message-ID: <47C83768.9010200@freescale.com> (raw)
In-Reply-To: <15337956.post@talk.nabble.com>
David Saada wrote:
> On the MPC83xx & MPC85xx architectures that have QE, add initial data to the
> pin configuration table (qe_iop_conf_tab). This is relevant for GPIO pins
> defined as output. One can setup a value of -1 to leave the value unchanged.
> QE initialization tables in all relevant boards were also replaced.
> In addition, add IO pin read & write functions.
> This patch also includes commands for reading and writing parallel I/O ports
> (pario command).
>
> Signed-off-by: David Saada <david.saada@ecitele.com>
Acked-by: Timur Tabi <timur@freescale.com>
FYI David, I just noticed this patch yesterday. I would have noticed it and
ack'd it back on the 7th if you had included my email address on the "To:" line.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-02-29 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 16:45 [U-Boot-Users] [PATCH v5] QE IO: Add initial data to pin configuration + read/write functions David Saada
2008-02-29 16:48 ` Timur Tabi [this message]
2008-03-02 9:06 ` David Saada
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=47C83768.9010200@freescale.com \
--to=timur@freescale.com \
--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