Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org, horms+renesas@verge.net.au,
	joro@8bytes.org, geert+renesas@glider.be
Subject: Re: [PATCH v2 02/02] arm64: dts: r8a7795: Hook up SYS-DMAC to IPMMU
Date: Mon, 19 Dec 2016 10:39:06 +0200	[thread overview]
Message-ID: <5954981.2Wsi8xXc7F@avalon> (raw)
In-Reply-To: <4878065.dMXMQ9htQo@avalon>

Hi Magnus,

On Monday 19 Dec 2016 09:51:44 Laurent Pinchart wrote:
> On Monday 19 Dec 2016 11:19:50 Magnus Damm wrote:
> > From: Magnus Damm <damm+renesas@opensource.se>
> > 
> > Hook up r8a7795 DMAC nodes to IPMMU-MP1, IPMMU-DS0 and IPMMU-DS1.
> 
> I assume you have verified that hooking up a disabled IOMMU doesn't
> adversely affect system operation.

I saw in a reply to v1 that you have verified this on top of the renesas-
drivers tree, so I give it a try on mainline. The DMAC devices get probed 
properly and dmatest completes without failures.

> > Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> > ---
> > 
> >  Changes from V1:
> >  - None
> >  
> >  arch/arm64/boot/dts/renesas/r8a7795.dtsi |   40 ++++++++++++++++++++++++
> >  1 file changed, 40 insertions(+)

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2016-12-19  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19  2:19 [PATCH v2 00/02] arm64: dts: r8a7795: IPMMU upstream integration V2 Magnus Damm
2016-12-19  2:19 ` [PATCH v2 01/02] arm64: dts: r8a7795: Add IPMMU device nodes Magnus Damm
2016-12-19  7:39   ` Laurent Pinchart
2016-12-19  2:19 ` [PATCH v2 02/02] arm64: dts: r8a7795: Hook up SYS-DMAC to IPMMU Magnus Damm
2016-12-19  7:51   ` Laurent Pinchart
2016-12-19  8:39     ` Laurent Pinchart [this message]
2017-02-07 10:23   ` Geert Uytterhoeven

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=5954981.2Wsi8xXc7F@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=joro@8bytes.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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