linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	iommu@lists.linux-foundation.org,
	Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 4/5] ARM: shmobile: r8a7791: Add IPMMU DT nodes
Date: Mon, 31 Mar 2014 14:30:00 +0000	[thread overview]
Message-ID: <53397BE8.6030707@codethink.co.uk> (raw)
In-Reply-To: <2517875.vv2t3ch4DC@avalon>

On 31/03/14 15:01, Laurent Pinchart wrote:
> Hi Geert,
>
> On Monday 31 March 2014 10:52:28 Geert Uytterhoeven wrote:
>> On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote:
>>> +       ipmmu_sy0: mmu@e6280800 {
>>> +               compatible = "renesas,ipmmu-vmsa";
>>> +               reg = <0 0xe6280800 0 0x800>;
>>
>> Shouldn't this be "reg = <0 0xe6280000 0 0x1000>", i.e. expose both
>> banks?
>>
>> Is there any specific reason you're using the second bank of registers?
>> These may read as zero, depending on the SoC mode.
>
> That's a very good question, and I have no clear answer. According to the
> datasheet the second bank of registers is an alias for the non-secure IPMMU
> registers. It looks like we're running in secure mode (that's what I assume
> the "CPU: All CPU(s) started in SVC mode." kernel log message means), and the
> secure IPMMU didn't seem to be functional when I've tested it.
>
> This requires more investigation, but I'm not familiar with secure mode, and
> the IPMMU documentation is really sparse in that area.

The default for the R8A7790 is to start in secure-svc mode.

I would test it in non-secure SVC but the security framework we
are using blocks access to the IPMMU blocks :/


-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

  reply	other threads:[~2014-03-31 14:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 23:36 [PATCH 0/5] Renesas VMSA-compatible IPMMU DT support Laurent Pinchart
     [not found] ` <1396049781-12941-1-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-03-28 23:36   ` [PATCH 1/5] iommu/ipmmu-vmsa: Refactor micro-TLB lookup Laurent Pinchart
2014-03-28 23:36 ` [PATCH 2/5] iommu/ipmmu-vmsa: Add device tree bindings documentation Laurent Pinchart
2014-03-29 14:50   ` Sergei Shtylyov
2014-04-01 13:57     ` Laurent Pinchart
     [not found]   ` <1396049781-12941-3-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-03-31  8:39     ` Geert Uytterhoeven
2014-03-31 10:18       ` Laurent Pinchart
2014-03-28 23:36 ` [PATCH 3/5] iommu/ipmmu-vmsa: Add device tree support Laurent Pinchart
     [not found]   ` <1396049781-12941-4-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-03-31  8:45     ` Geert Uytterhoeven
     [not found]       ` <CAMuHMdU7esZ35xe+iTRNbeXmD7bSHXEakTOrTfXEs8h5yQLFfA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-31 14:09         ` Laurent Pinchart
2014-03-28 23:36 ` [PATCH 4/5] ARM: shmobile: r8a7791: Add IPMMU DT nodes Laurent Pinchart
     [not found]   ` <1396049781-12941-5-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-03-31  8:52     ` Geert Uytterhoeven
     [not found]       ` <CAMuHMdV5kV_cz3b1gW7qW_z22JtWd9BpoXN2=_XjBqJfcG-yWQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-31 13:59         ` Laurent Pinchart
2014-03-31 14:30           ` Ben Dooks [this message]
     [not found]             ` <53397BE8.6030707-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2014-04-01 13:26               ` Laurent Pinchart
2014-03-28 23:36 ` [PATCH 5/5] [TEST] ARM: shmobile: r8a7791: Enable IOMMU support for the VSP1 Laurent Pinchart

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=53397BE8.6030707@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=geert@linux-m68k.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@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).