linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm64: mm: use pgprot_device for device in phys_mem_access_prot
Date: Thu, 21 Jul 2016 17:03:00 +0100	[thread overview]
Message-ID: <20160721160300.GF16666@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <20160721151344.36e29858@xhacker>

On Thu, Jul 21, 2016 at 03:13:44PM +0800, Jisheng Zhang wrote:
> Normally, in arm64, kernel driver maps register space as device nGnRE. But
> if we access the register space via. /dev/mem, then the mapping is
> device nGnRnE, is there a mismatch here?

Possibly, but the behaviour is not undefined. The nGnRnE may lose the nE
behaviour (which is a hint anyway, it may not be honoured).

/dev/mem is a pretty bad idea in general.

-- 
Catalin

  reply	other threads:[~2016-07-21 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21  7:13 [RFC] arm64: mm: use pgprot_device for device in phys_mem_access_prot Jisheng Zhang
2016-07-21 16:03 ` Catalin Marinas [this message]
2016-07-22  6:58   ` Jisheng Zhang

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=20160721160300.GF16666@e104818-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).