public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Gregg Nemas <gnemas@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Burst I/O on PPC440GP
Date: Thu, 6 Oct 2005 17:37:31 +0000 (UTC)	[thread overview]
Message-ID: <loom.20051006T192000-211@post.gmane.org> (raw)

I am trying to perform I/O with a device attached to the external peripheral bus
on a PPC440GP embedded processor. I am able to address the device and read and
write to it, but I am only able to do non-burst I/O. Do I need to do something
special to enable burst transactions? I've programmed the EBC0_B5CR and
EBC0_B5AP device control registers appropriately to enable burst mode, but the
transactions are still single I/O.

I've been testing this by using the u-boot mw.l command. Do I need to use
PPC-specific instructions to perform burst I/O, or should an ordinary programmed
I/O (using 32-bit write operations) be automatically queued up and converted to
burst transactions?

The TLB I've added for the I/O region has the caching inhibit (I) and guarded
(G) bits set. Does caching or speculative access need to be enabled to allow
bursting? Even if I added a TLB entry, it wouldn't do me any good in Linux,
since it manages TLBs itself. So how would I do this from a Linux kernel driver?

Thanks.

Gregg

             reply	other threads:[~2005-10-06 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 17:37 Gregg Nemas [this message]
2005-10-06 20:07 ` [U-Boot-Users] Burst I/O on PPC440GP Stefan Roese
2005-10-06 20:40   ` [U-Boot-Users] " Gregg Nemas
2005-10-06 20:54     ` Chuck Gales

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=loom.20051006T192000-211@post.gmane.org \
    --to=gnemas@gmail.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