From: Rob Landley <rob@landley.net> To: Leif Lindholm <leif.lindholm@linaro.org> Cc: linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, patches@linaro.org, nico@linaro.org, Leif Lindholm <leif.lindholm@linaro.org> Subject: Re: [PATCH 1/2] Documentation: arm: early_ioremap Date: Sat, 29 Jun 2013 22:14:11 -0500 [thread overview] Message-ID: <1372562051.2776.162@driftwood> (raw) In-Reply-To: <1372182401-11029-2-git-send-email-leif.lindholm@linaro.org> (from leif.lindholm@linaro.org on Tue Jun 25 12:46:40 2013) On 06/25/2013 12:46:40 PM, Leif Lindholm wrote: > This patch provides documentation of the early_ioremap() > functionality, > including its implementation and usage instructions. > > Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org> > --- > Documentation/arm/00-INDEX | 2 ++ > Documentation/arm/early_ioremap.txt | 12 ++++++++++++ > 2 files changed, 14 insertions(+) > create mode 100644 Documentation/arm/early_ioremap.txt > > diff --git a/Documentation/arm/00-INDEX b/Documentation/arm/00-INDEX > index 36420e1..4978456 100644 > --- a/Documentation/arm/00-INDEX > +++ b/Documentation/arm/00-INDEX > @@ -24,6 +24,8 @@ SPEAr > - ST SPEAr platform Linux Overview > VFP/ > - Release notes for Linux Kernel Vector Floating Point support > code > +early_ioremap.txt > + - documentation of the early_ioremap() functionality > empeg/ > - Ltd's Empeg MP3 Car Audio Player > mem_alignment > diff --git a/Documentation/arm/early_ioremap.txt > b/Documentation/arm/early_ioremap.txt > new file mode 100644 > index 0000000..178f791 > --- /dev/null > +++ b/Documentation/arm/early_ioremap.txt > @@ -0,0 +1,12 @@ > +early_ioremap() and early_iounmap() rovide a mechanism for > temporarily mapping Typo: provide > +in small blocks of memory, identified by their physical address, > into the > +fixmap virtual address block before paging_init() has been called > and more > +flexible mapping functions are available. > + > +Due to its direct method, it also gets around potential need for > special > +handling of regions that end up in highmem. > + > +It supports up to 7 simultaneously mapped regions of up to 128KB > each. > +All regions are mapped as non-shareable device memory. > + > +Specify 'early_ioremap_debug' on the kernel commandline for verbose > output. > -- > 1.7.10.4 Minor quibble: this explains what it does, but nothing about how to use it. Do these mappings persist if you don't unmap them, or does paging_init() clear them? Oh well: Acked-by: Rob Landley <rob@landley.net> Rob
WARNING: multiple messages have this Message-ID (diff)
From: rob@landley.net (Rob Landley) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/2] Documentation: arm: early_ioremap Date: Sat, 29 Jun 2013 22:14:11 -0500 [thread overview] Message-ID: <1372562051.2776.162@driftwood> (raw) In-Reply-To: <1372182401-11029-2-git-send-email-leif.lindholm@linaro.org> (from leif.lindholm@linaro.org on Tue Jun 25 12:46:40 2013) On 06/25/2013 12:46:40 PM, Leif Lindholm wrote: > This patch provides documentation of the early_ioremap() > functionality, > including its implementation and usage instructions. > > Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org> > --- > Documentation/arm/00-INDEX | 2 ++ > Documentation/arm/early_ioremap.txt | 12 ++++++++++++ > 2 files changed, 14 insertions(+) > create mode 100644 Documentation/arm/early_ioremap.txt > > diff --git a/Documentation/arm/00-INDEX b/Documentation/arm/00-INDEX > index 36420e1..4978456 100644 > --- a/Documentation/arm/00-INDEX > +++ b/Documentation/arm/00-INDEX > @@ -24,6 +24,8 @@ SPEAr > - ST SPEAr platform Linux Overview > VFP/ > - Release notes for Linux Kernel Vector Floating Point support > code > +early_ioremap.txt > + - documentation of the early_ioremap() functionality > empeg/ > - Ltd's Empeg MP3 Car Audio Player > mem_alignment > diff --git a/Documentation/arm/early_ioremap.txt > b/Documentation/arm/early_ioremap.txt > new file mode 100644 > index 0000000..178f791 > --- /dev/null > +++ b/Documentation/arm/early_ioremap.txt > @@ -0,0 +1,12 @@ > +early_ioremap() and early_iounmap() rovide a mechanism for > temporarily mapping Typo: provide > +in small blocks of memory, identified by their physical address, > into the > +fixmap virtual address block before paging_init() has been called > and more > +flexible mapping functions are available. > + > +Due to its direct method, it also gets around potential need for > special > +handling of regions that end up in highmem. > + > +It supports up to 7 simultaneously mapped regions of up to 128KB > each. > +All regions are mapped as non-shareable device memory. > + > +Specify 'early_ioremap_debug' on the kernel commandline for verbose > output. > -- > 1.7.10.4 Minor quibble: this explains what it does, but nothing about how to use it. Do these mappings persist if you don't unmap them, or does paging_init() clear them? Oh well: Acked-by: Rob Landley <rob@landley.net> Rob
next prev parent reply other threads:[~2013-06-30 3:14 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-25 17:46 [PATCH 0/2] arm: add early_ioremap() support Leif Lindholm 2013-06-25 17:46 ` Leif Lindholm 2013-06-25 17:46 ` [PATCH 1/2] Documentation: arm: early_ioremap Leif Lindholm 2013-06-25 17:46 ` Leif Lindholm 2013-06-30 3:14 ` Rob Landley [this message] 2013-06-30 3:14 ` Rob Landley 2013-06-25 17:46 ` [PATCH 2/2] arm: add early_ioremap support Leif Lindholm 2013-06-25 17:46 ` Leif Lindholm 2013-06-26 18:52 ` [PATCH 0/2] arm: add early_ioremap() support Arnd Bergmann 2013-06-26 18:52 ` Arnd Bergmann 2013-06-26 19:23 ` Leif Lindholm 2013-06-26 19:23 ` Leif Lindholm 2013-06-26 21:23 ` Arnd Bergmann 2013-06-26 21:23 ` Arnd Bergmann 2013-06-26 21:34 ` Leif Lindholm 2013-06-26 21:34 ` Leif Lindholm 2013-06-26 22:13 ` Arnd Bergmann 2013-06-26 22:13 ` Arnd Bergmann 2013-06-26 23:25 ` Leif Lindholm 2013-06-26 23:25 ` Leif Lindholm 2013-06-27 8:47 ` Arnd Bergmann 2013-06-27 8:47 ` Arnd Bergmann 2013-06-27 9:29 ` Leif Lindholm 2013-06-27 9:29 ` Leif Lindholm 2013-06-27 11:55 ` Arnd Bergmann 2013-06-27 11:55 ` Arnd Bergmann
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=1372562051.2776.162@driftwood \ --to=rob@landley.net \ --cc=leif.lindholm@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=nico@linaro.org \ --cc=patches@linaro.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: linkBe 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.