From: Kumar Gala <kumar.gala@freescale.com>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH][RFC] OCP support for MPC107 and relatives
Date: Mon, 14 Jun 2004 19:38:51 -0500 [thread overview]
Message-ID: <5F4101CA-BE64-11D8-ACA7-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <20040614084625.A29057@home.com>
Matt,
We know have several systems which have the same issue of updating a
paddr based on some offset.
I'm wondering if we should add something like the following code into
ocp.c (obviously, removing the 85xx specific aspects).
Called w/in board code:
ocp_for_each_device(mpc85xx_update_paddr_ocp,
&(binfo->bi_immr_base));
Or should we have a more explicit ocp_update_paddr(phys_addr_t x);
/*
************************************************************************
*/
/* Update the 85xx OCP tables paddr field */
void
mpc85xx_update_paddr_ocp(struct ocp_device *dev, void *arg)
{
phys_addr_t ccsrbar;
if (arg) {
ccsrbar = *(phys_addr_t *)arg;
dev->def->paddr += ccsrbar;
}
}
- kumar
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-15 0:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 10:10 [PATCH][RFC] OCP support for MPC107 and relatives Adrian Cox
2004-06-14 10:23 ` [PATCH][RFC] I2C " Adrian Cox
2004-06-14 11:01 ` Stefan Nickl
2004-06-14 11:37 ` Adrian Cox
2004-06-14 13:01 ` Stefan Nickl
2004-06-14 13:24 ` Adrian Cox
2004-06-14 13:39 ` Kumar Gala
2004-06-14 14:38 ` Pantelis Antoniou
2004-06-14 13:43 ` [PATCH][RFC] OCP " Kumar Gala
2004-06-14 13:59 ` Kumar Gala
2004-06-14 14:47 ` Adrian Cox
2004-06-14 15:46 ` Matt Porter
2004-06-15 0:38 ` Kumar Gala [this message]
2004-06-14 17:05 ` Mark A. Greer
2004-06-15 8:10 ` Adrian Cox
2004-06-15 17:33 ` Mark A. Greer
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=5F4101CA-BE64-11D8-ACA7-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mporter@kernel.crashing.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).