Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <soete.joel@scarlet.be>
Cc: parisc-linux <parisc-linux@parisc-linux.org>
Subject: [parisc-linux] Re: CCIO dma io_command and related io_tlb format questions.
Date: Tue, 10 Oct 2006 16:08:41 -0600	[thread overview]
Message-ID: <20061010220841.GG12490@colo.lackof.org> (raw)
In-Reply-To: <J6V48N$07BEC56C541729714304848986C290A3@scarlet.be>

On Mon, Oct 09, 2006 at 11:41:11AM +0200, Joel Soete wrote:
> Hello Grant,
> 
> I back port the sba sg list manager in ccio-dma on my d380 (not enough time to
> test c110).
...

Sounds like you have some debugging to do still...I'll try to
answer the questions below.

> That said, there are no public doc of this IO stuff

There is none for CCIO. And I no longer have access to those
documents (deleted them from my laptop/workstations).
You'd need access to U2/Uturn ERS via OSDL.


> and so I didn't change those 2 hunks:
> [snip]
> static CCIO_INLINE void
> ccio_clear_io_tlb(struct ioc *ioc, dma_addr_t iovp, size_t byte_cnt)
...
> ccio_ioc_init(struct ioc *ioc)
...
> About which cames to me 2 questions:
>    1/ what is supposed to contain an io_tlb entry:

You want to know the layout of the "ioc_command" register.
It is a combination of iovp and command.


>       a io (page size) address as seems to say the value
>      ("CMD_TLB_PURGE | iovp") in ccio_clear_io_tlb()

Offhand I'm not sure of the exact split but guess it's
lower 12 bits for command and upper 20 bits for IO Virtual Page
as used in ccio_clear_io_tlb().

>       or a memory page size should be splited in
>       severall tlb entries per ioc->chainid_shift?

ccio_ioc_init is just clearing the entire IO TLB.
We know there are only "1<<CCIO_CHAINID_SHIFT" IO TLB entries.
See comments above where CCIO_CHAINID_SHIFT is defined.
ccio_clear_io_tlb() is just purging all of them.

>    2/ what is supposed to contain the ccio io_command register, I mean that
>       I don't understand what seems to me to be different io_command
>       contents for CMD_TLB_DIRECT_WRITE or CMD_TLB_PURGE?

Generally we only need to use CMD_TLB_PURGE to avoid use of stale entries.
You shouldn't need to change the uses of CMD_TLB_DIRECT_WRITE.

> If you still have (or access to) this internal doc, it would be great if you
> could find some time to explain me those stuff.

Sorry - I don't.

Hope that helps,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2006-10-10 22:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09  9:41 [parisc-linux] CCIO dma io_command and related io_tlb format questions Joel Soete
2006-10-10 22:08 ` Grant Grundler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-11  8:48 [parisc-linux] " Joel Soete
2006-10-12  1:04 ` Grant Grundler
2006-10-12  3:27   ` James Bottomley
     [not found]   ` <4538BB5F.5040703@scarlet.be>
2006-10-20 15:50     ` Grant Grundler
2006-10-20 16:31       ` Grant Grundler
2006-10-20 17:18       ` Joel Soete
2006-10-21  6:19         ` Grant Grundler
2006-10-21 17:17           ` Joel Soete
2006-10-23  4:34             ` Grant Grundler
     [not found] <J70JNP$255156D3B4F90827118C5EFE40FD3ABF@scarlet.be>
2006-10-12 19:55 ` Grant Grundler
2006-10-13 10:56   ` Joel Soete
2006-10-13 16:44     ` Grant Grundler
     [not found]       ` <4530DF1F.5060601@scarlet.be>
2006-10-14 14:11         ` Matthew Wilcox
2006-10-14 16:40           ` Michael S. Zick
2006-10-14 23:35           ` Joel Soete
2006-10-15  3:28             ` Grant Grundler
     [not found] <J788XR$E1A2FE043CF88207AEC13412E82258F2@scarlet.be>
2006-10-16 14:37 ` Michael S. Zick
2006-10-17  5:59 ` Grant Grundler
     [not found] <J7AHPO$ED967CCDD9E203D6968EA2045C11A08A@scarlet.be>
     [not found] ` <45351637.4070604@computer.org>
2006-10-17 19:07   ` Kyle McMartin

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=20061010220841.GG12490@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=parisc-linux@parisc-linux.org \
    --cc=soete.joel@scarlet.be \
    /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