From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Paul Burton <paul.burton@imgtec.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH 4/4] MIPS: Malta: initialise MAARs
Date: Mon, 14 Jul 2014 15:33:07 +0400 [thread overview]
Message-ID: <53C3BFF3.8050004@cogentembedded.com> (raw)
In-Reply-To: <1405330336-18167-5-git-send-email-paul.burton@imgtec.com>
Hello.
On 07/14/2014 01:32 PM, Paul Burton wrote:
> Initialise the MAARs such that speculation is enabled for all physical
> addresses outside of the I/O region.
> Signed-off-by: Paul Burton <paul.burton@imgtec.com>
> ---
> arch/mips/mti-malta/malta-memory.c | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
> diff --git a/arch/mips/mti-malta/malta-memory.c b/arch/mips/mti-malta/malta-memory.c
> index 6d97730..e96803d 100644
> --- a/arch/mips/mti-malta/malta-memory.c
> +++ b/arch/mips/mti-malta/malta-memory.c
[...]
> @@ -164,3 +165,28 @@ void __init prom_free_prom_memory(void)
> addr, addr + boot_mem_map.map[i].size);
> }
> }
> +
> +unsigned platform_maar_init(unsigned num_pairs)
> +{
> + phys_addr_t mem_end = (physical_memsize & ~0xffffull) - 1;
> + struct maar_config cfg[] = {
> + /* DRAM preceeding I/O */
Perhaps "preceding"?
WBR, Sergei
next prev parent reply other threads:[~2014-07-14 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 9:32 [PATCH 0/4] Memory Accessibility Attribute Register (MAAR) support Paul Burton
2014-07-14 9:32 ` Paul Burton
2014-07-14 9:32 ` [PATCH 1/4] MIPS: define MAAR register accessors & bits Paul Burton
2014-07-14 9:32 ` Paul Burton
2014-07-14 9:32 ` [PATCH 2/4] MIPS: detect presence of MAARs Paul Burton
2014-07-14 9:32 ` Paul Burton
2014-07-14 9:32 ` [PATCH 3/4] MIPS: initialise MAARs Paul Burton
2014-07-14 9:32 ` Paul Burton
2014-07-14 9:32 ` [PATCH 4/4] MIPS: Malta: " Paul Burton
2014-07-14 9:32 ` Paul Burton
2014-07-14 11:33 ` Sergei Shtylyov [this message]
2014-07-14 11:37 ` [PATCH v2 " Paul Burton
2014-07-14 11:37 ` Paul Burton
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=53C3BFF3.8050004@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
/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