From: akuster <akuster@dslextreme.com>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: [RFC/Patch] ppc4xx_dma.c
Date: Tue, 23 Jul 2002 12:10:15 -0700 [thread overview]
Message-ID: <3D3DAA17.7070406@dslextreme.com> (raw)
While working on an ocp ide driver using the DMA channel with
mtdcr/mfdcr calls , it became clear to me that some changes need to
occur in the ppc4xx_dma.c code.
1) I moved the scatter/gather code used by the 440GP, 405gp, np405l and
np405h to a separate file (ppc4xx_sgdma.c) and is now built when one of
those cpus are configured.
2) I moved the inline api out of /asm-ppc/ppc4xx_dma.h to either
ppc4xx_sgdam.c or ppc4xx_dma.c
3) I needed to add a few more api's for the stbx25xxx and am in the
process of determining if those need to go into a ppc4xxx_stbdma.c file.
int clr_dma_status(unsigned int dmanr)
int map_dma_port(unsigned int dmanr, unsigned int ocp_dma,short dma_chan)
int disable_dma_port(unsigned int dmanr, unsigned int ocp_dma,short
dma_chan)
and possible more to follow
The common API's will stay in /kernel/ppc4xx_dma.c and the common
defines in asm-ppc/ppc4xx_dma.h
armin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-07-23 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 19:10 akuster [this message]
2002-07-24 21:11 ` [RFC/Patch] ppc4xx_dma.c akuster
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=3D3DAA17.7070406@dslextreme.com \
--to=akuster@dslextreme.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).