From: David Brown <davidb@codeaurora.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: David Brown <davidb@codeaurora.org>,
Grant Likely <grant.likely@secretlab.ca>,
devicetree-discuss@lists.ozlabs.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH v2] of/address: Add of_iomap_nocache
Date: Thu, 4 Aug 2011 06:10:15 -0700 [thread overview]
Message-ID: <20110804131015.GA6596@huya.qualcomm.com> (raw)
In-Reply-To: <B148344E-9580-4C9B-A8FD-942A9713291C@kernel.crashing.org>
On Thu, Aug 04, 2011 at 07:44:07AM -0500, Kumar Gala wrote:
>
> On Aug 4, 2011, at 5:36 AM, David Brown wrote:
>
> > Add uncached mappings from devicetree nodes similar to regular io
> > mappings.
> >
> > SPARC is coherent, so there this call is the same as regular of_iomap.
> >
> > +extern void __iomem *of_iomap_nocache(struct device_node *device, int index);
>
> What about adding an of_iomap_prot() to match ioremap_prot().
It can be done, but I actually have a use for nocache. We can
probably add the prot version when first needed.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-08-04 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 9:53 [PATCH] of/address: Add of_iomap_nocache David Brown
2011-08-04 10:12 ` David Miller
2011-08-04 15:52 ` Rob Herring
2011-08-04 16:17 ` David Brown
2011-08-04 23:08 ` David Miller
2011-08-04 10:36 ` [PATCH v2] " David Brown
[not found] ` <1312454196-31028-1-git-send-email-davidb-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-08-04 11:51 ` David Miller
2011-08-04 12:53 ` Grant Likely
2011-08-04 12:44 ` Kumar Gala
2011-08-04 13:10 ` David Brown [this message]
2011-08-04 16:56 ` Scott Wood
2011-08-04 16:58 ` 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=20110804131015.GA6596@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=galak@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).