tpmdd-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: About devm_ioremap_resource()
Date: Wed, 3 Feb 2016 17:16:12 -0800	[thread overview]
Message-ID: <20160204011612.GA6357@intel.com> (raw)
In-Reply-To: <20160204003108.GA26123-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>

On Wed, Feb 03, 2016 at 05:31:08PM -0700, Jason Gunthorpe wrote:
> On Wed, Feb 03, 2016 at 02:55:19PM -0800, Jarkko Sakkinen wrote:
> > Hi
> > 
> > I have couple of concerns with tpm_crb changes made for 4.5:
> > 
> > * I used devm_ioremap_nocache() to disable WB. This does not
> >   matter when one has ACPI start as it goes through SMM and caches are
> >   flushed. It might be a problem with a CRB start only TPM device. How does
> >   devm_ioremap_resource address this?
> 
> ioremap_nocache and ioremap() are the same thing, the former is just
> more descriptive.
> 
> devm_ioremap_resource calls ioremap which does ioremap_nocache.
> 
> Resources are assumed to be memory mapped registers, and are always
> handled appropriately.
> 
> > * I'm a bit puzzled with that function. Why there exists ioremaps that
> >   do not add stuff to a resource tree and those that do? Maybe you have
> >   a deeper understanding in this area could enlighten me since you did
> >   the commit.
> 
> The resource tree and mapping are different things, not all drivers
> can use the resource tree all the time, but certainly the majority of
> drivers should be using it, hence the devm helper to do both.
> 
> When you see a ioremap without resource handling in a driver it is
> probably a mistake, and if it isn't, IMHO there should be a comment
> discussing why this driver cannot lock the resource region.

Thank you for clearing these out! I have nothing to add here. The
reason for two interfaces was what I expected...

> Jason

/Jarkko

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

      parent reply	other threads:[~2016-02-04  1:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 22:55 About devm_ioremap_resource() Jarkko Sakkinen
     [not found] ` <20160203225519.GA8647-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-02-04  0:31   ` Jason Gunthorpe
     [not found]     ` <20160204003108.GA26123-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-02-04  1:16       ` Jarkko Sakkinen [this message]

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=20160204011612.GA6357@intel.com \
    --to=jarkko.sakkinen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).