From: Timur Tabi <timur@freescale.com>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Discussion about iopa()
Date: Thu, 08 Feb 2007 07:41:58 -0600 [thread overview]
Message-ID: <45CB28A6.3050607@freescale.com> (raw)
In-Reply-To: <989B956029373F45A0B8AF02970818900D444B@zch01exm26.fsl.freescale.net>
Li Yang-r58472 wrote:
> Do you think we should remove iopa?
It's not used very much any more. If you do a grep of the code, I think
only some legacy drivers use it.
As long as ioremap'd memory is both physically and virtually contiguous,
I think iopa() is unnecessary.
> The information is often not so obvious. The most case of using iopa is
> that we allocate memory from MURAM using rheap, and then get the
> physical address of it. We can calculate phy_addr by using: virt_addr
> - virt_muram_base + phy_muram_base, but it is not as straightforward as
> just using the page table, let alone we need to keep track of
> virt_muram_base and phy_muram_base.
Walking the page table is slower than using pointer math, so you want to
avoid iopa() if you can.
I think in general, the driver that calls ioremap() should store the
physical address along with the virtual address of the base pointer.
next prev parent reply other threads:[~2007-02-08 13:42 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 11:31 [PATCH 1/4] ucc_geth: Change private immrbar_virt_to_phys to generic iopa Li Yang
2007-02-06 14:26 ` Kumar Gala
2007-02-07 9:34 ` Li Yang-r58472
2007-02-07 16:36 ` Kumar Gala
2007-02-07 16:43 ` Timur Tabi
2007-02-07 16:49 ` Kumar Gala
2007-02-07 17:03 ` Timur Tabi
2007-02-08 5:52 ` Li Yang-r58472
2007-02-08 5:57 ` Kumar Gala
2007-02-08 6:48 ` Li Yang-r58472
2007-02-08 6:53 ` Kumar Gala
2007-02-08 7:06 ` Li Yang-r58472
2007-02-08 7:16 ` Kumar Gala
2007-02-08 7:36 ` Li Yang-r58472
2007-02-08 7:41 ` Kumar Gala
2007-02-08 9:22 ` Discussion about iopa() Li Yang-r58472
2007-02-08 13:41 ` Timur Tabi [this message]
2007-02-09 17:08 ` Dan Malek
2007-02-10 2:37 ` Benjamin Herrenschmidt
2007-02-10 18:04 ` Dan Malek
2007-02-10 21:40 ` Benjamin Herrenschmidt
2007-02-10 22:27 ` Dan Malek
2007-02-10 22:42 ` Benjamin Herrenschmidt
2007-02-08 21:26 ` Benjamin Herrenschmidt
2007-02-09 17:13 ` Dan Malek
2007-02-09 22:06 ` Benjamin Herrenschmidt
2007-02-09 22:46 ` Kumar Gala
2007-02-09 22:51 ` Timur Tabi
2007-02-09 23:06 ` Kumar Gala
2007-02-09 23:10 ` Timur Tabi
2007-02-09 23:19 ` Benjamin Herrenschmidt
2007-02-09 23:22 ` Kumar Gala
2007-02-09 23:33 ` Timur Tabi
2007-02-09 23:43 ` Kumar Gala
2007-02-09 17:06 ` Dan Malek
2007-02-08 13:35 ` [PATCH 1/4] ucc_geth: Change private immrbar_virt_to_phys to generic iopa Timur Tabi
2007-02-09 17:22 ` Dan Malek
2007-02-09 17:26 ` Timur Tabi
2007-02-08 13:27 ` Timur Tabi
2007-02-07 0:19 ` Jeff Garzik
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=45CB28A6.3050607@freescale.com \
--to=timur@freescale.com \
--cc=LeoLi@freescale.com \
--cc=linuxppc-dev@ozlabs.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).