From: Grant Likely <grant.likely@secretlab.ca>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: paulus@samba.org, miltonm@bga.com, linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH 1/3] powerpc: add ioremap_bat() function for setting up BAT translated IO regions.
Date: Tue, 12 Aug 2008 13:50:28 -0600 [thread overview]
Message-ID: <20080812195027.GB11386@secretlab.ca> (raw)
In-Reply-To: <8A11E9B3-4B7D-48CF-ABAB-625050D8FFFE@kernel.crashing.org>
On Thu, Aug 07, 2008 at 07:04:04PM -0500, Kumar Gala wrote:
>> mem_init_done isn't a good indication. We can do page tables when it's
>> 0, we would have to use a separate mem_preinit_done or something :-)
>>
>> I initially also though about a flag to ioremap_prot to be honest. But
>> it does obfuscate the normal ioremap code path and if there's a flag,
>> that means that callers know the difference and thus may as well call
>> a separate function, don't you think ?
>
> I'm ok with exposing a separate function as far as the API goes.. I'm
> not ok with duplicating the logic of __ioremap().
Turns out there is very little actual duplication of code with
__ioremap(). The checks for p_mapped_by_* are the same, but all the
alignment checks are different because different boundaries are used.
I attempted to break things down to a common function, but there is not
a lot there. But I will add a function to manage modification of
ioremap_bot.
g.
next prev parent reply other threads:[~2008-08-12 19:50 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 6:02 [RFC/PATCH 0/3] Attempt at making 32bit BAT assignment more intelligent Grant Likely
2008-08-06 6:02 ` [RFC/PATCH 1/3] powerpc: add ioremap_bat() function for setting up BAT translated IO regions Grant Likely
2008-08-06 14:07 ` Kumar Gala
2008-08-06 21:54 ` Grant Likely
2008-08-06 22:11 ` Kumar Gala
2008-08-06 22:28 ` Benjamin Herrenschmidt
2008-08-06 22:55 ` Brad Boyer
2008-08-06 23:11 ` Grant Likely
2008-08-07 1:49 ` Kumar Gala
2008-08-07 22:13 ` Benjamin Herrenschmidt
2008-08-08 0:04 ` Kumar Gala
2008-08-12 19:50 ` Grant Likely [this message]
2008-08-06 22:31 ` Scott Wood
2008-08-06 23:02 ` Grant Likely
2008-08-07 1:52 ` Kumar Gala
2008-08-06 22:26 ` Benjamin Herrenschmidt
2008-08-06 23:11 ` Grant Likely
2008-08-07 16:45 ` Scott Wood
2008-08-07 18:21 ` Kumar Gala
2008-08-07 22:09 ` Benjamin Herrenschmidt
2008-08-06 6:02 ` [RFC/PATCH 2/3] of: add of_lookup_stdout() utility function Grant Likely
2008-08-06 6:14 ` Michael Ellerman
2008-08-06 6:34 ` Grant Likely
2008-08-06 7:42 ` Stephen Rothwell
2008-08-06 7:44 ` David Miller
2008-08-06 7:57 ` Stephen Rothwell
2008-08-06 6:32 ` David Miller
2008-08-06 6:35 ` Grant Likely
2008-08-06 7:19 ` David Miller
2008-08-07 22:37 ` Benjamin Herrenschmidt
2008-08-06 10:21 ` Paul Mackerras
2008-08-06 10:52 ` David Miller
2008-08-06 13:31 ` Grant Likely
2008-08-06 16:25 ` Segher Boessenkool
2008-08-06 17:09 ` Mitch Bradley
2008-08-07 0:40 ` David Gibson
2008-08-07 22:35 ` Benjamin Herrenschmidt
2008-08-06 16:46 ` Timur Tabi
2008-08-07 6:12 ` David Gibson
2008-08-07 17:28 ` Yoder Stuart
2008-08-07 18:11 ` Timur Tabi
2008-08-13 5:41 ` Grant Likely
2008-08-13 14:32 ` Timur Tabi
2008-08-07 22:36 ` Benjamin Herrenschmidt
2008-08-06 6:02 ` [RFC/PATCH 3/3] powerpc/52xx: add udbg and early debug support for PSC serial console Grant Likely
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=20080812195027.GB11386@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=paulus@samba.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).