From: Mark Rutland <mark.rutland@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] armv8: caches: Added routine to set non cacheable region
Date: Wed, 13 May 2015 18:31:05 +0100 [thread overview]
Message-ID: <20150513173105.GC28377@leverpostej> (raw)
In-Reply-To: <D6974F69F1104444AD495091953B61F8496ADC54@XAP-PVEXMBX02.xlnx.xilinx.com>
On Tue, May 12, 2015 at 04:46:49AM +0100, Siva Durga Prasad Paladugu wrote:
> Hi Mark,
>
>
> > -----Original Message-----
> > From: Mark Rutland [mailto:mark.rutland at arm.com]
> > Sent: Wednesday, April 29, 2015 10:00 PM
> > To: Michal Simek
> > Cc: u-boot at lists.denx.de; Albert Aribaud; Marek Vasut; Tom Rini; Siva Durga
> > Prasad Paladugu; Varun Sethi; Thierry Reding; Arnab Basu; York Sun
> > Subject: Re: [U-Boot] [PATCH v2] armv8: caches: Added routine to set non
> > cacheable region
> >
> > Hi Michal,
> >
> > On Wed, Apr 29, 2015 at 09:35:35AM +0100, Michal Simek wrote:
> > > Added routine mmu_set_region_dcache_behaviour() to set a particular
> > > region as non cacheable.
> >
> > What's the intended use of this?
> This is intended to mark a dynamically allocated region as non-cacheable region in runtime.
Sure, but why does that region need to be non-cacheable?
I assume you want to give the region to some device?
Do you ever hand the memory back (and hence need to make it cacehable
again)?
> There is same kind of routine for armv7 but not for armv8. Do you think that the same functionality to be addressed for armv8 too?
>
> As per below comment, you are correct, this looks like to be more board specific.
While the address of the tables might be board-specific I'd imagine
that the manipulation routines can be shared.
Thanks,
Mark.
next prev parent reply other threads:[~2015-05-13 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 8:35 [U-Boot] [PATCH v2] armv8: caches: Added routine to set non cacheable region Michal Simek
2015-04-29 15:04 ` York Sun
2015-04-29 16:29 ` Mark Rutland
2015-05-12 3:46 ` Siva Durga Prasad Paladugu
2015-05-13 17:31 ` Mark Rutland [this message]
2015-05-14 5:01 ` Siva Durga Prasad Paladugu
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=20150513173105.GC28377@leverpostej \
--to=mark.rutland@arm.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.