From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 3/4] arm64: dts: renesas: r8a7796: Add DU device to DT
Date: Thu, 27 Oct 2016 09:13:48 +0200 [thread overview]
Message-ID: <20161027071348.GC7706@verge.net.au> (raw)
In-Reply-To: <CANqRtoRvvkr-HPTz9qGgxg6SK=FNZbO1gdxCDuxeUeGBzAhQ1g@mail.gmail.com>
On Thu, Oct 27, 2016 at 03:52:44PM +0900, Magnus Damm wrote:
> Hi Simon, everyone,
>
> On Thu, Oct 20, 2016 at 5:56 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Tue, Oct 18, 2016 at 12:19:26PM +0300, Laurent Pinchart wrote:
> >> Hi Simon,
> >>
> >> On Tuesday 18 Oct 2016 11:05:32 Geert Uytterhoeven wrote:
> >> > On Mon, Oct 17, 2016 at 11:34 PM, Laurent Pinchart wrote:
> >> > > Add the DU device to r8a7796.dtsi in a disabled state.
> >> > >
> >> > > Signed-off-by: Laurent Pinchart
> >> > > <laurent.pinchart+renesas@ideasonboard.com>
> >> >
> >> > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >>
> >> Could you please pick patches 1/4 to 3/4 from this series and apply them to
> >> your tree ? For convenience I've pushed them to
> >>
> >> git://linuxtv.org/pinchartl/media.git drm/r8a7796/dt
> >>
> >> along with patch "arm64: dts: renesas: r8a7795: Remove FCP SoC-specific
> >> compatible strings" that has been acked too. If you pull from that branch
> >> please make sure you skip the top-most patch "arm64: dts: renesas: r8a7796-
> >> salvator-x: Enable DU" for now.
> >
> > Sure, done.
>
> I think we should hold off with the upstreaming of the DU and VSP
> integration code for now. Sorry for noticing this late, but I thought
> we had already discussed the integration order and that merge of
> non-64-bit capable devices need to be put on hold.
>
> In particular, not so much the DU device (this patch) but more the VSP
> instances. The reason for that is that VSP devices can only perform
> 32-bit bus mastering without IOMMU. I believe next step for all this
> would be to enable all on-board memory on r8a7796 Salvator-x, but I
> think Geert is working on that.
So you would like to see the following patches dropped?
ee73acb13978 arm64: dts: renesas: r8a7796: Add VSP instances
0a6519d782fd arm64: dts: renesas: r8a7796: Add FCPF and FCPV instances
> Regarding IOMMU support, more effort is needed to get the IPMMU driver
> with r8a7796 (and r8a7795) support upstream. Some stuff for r8a7795
> exists in renesas-drivers and experimental r8a7796 support as well.
>
> One issue is that the DU driver itself is not ready to be used with
> IOMMU yet (below patches not upstream yet), and more work is needed as
> well - please see my reply (and prototype patch that fixes the issue
> locally):
> [PATCH 0/6] R-Car DU: Fix IOMMU operation when connected to VSP
> http://www.spinics.net/lists/dri-devel/msg117494.html
>
> Also, the r8a7796 DU driver code is not yet merged upstream and the
> binding is also not yet documented. So either way you look at it it
> seems a tad early for upstream merge.
>
> Thanks,
>
> / magnus
>
next prev parent reply other threads:[~2016-10-27 7:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 21:34 [PATCH 0/4] R-Car Salvator-X M3-W: Enable DU support Laurent Pinchart
2016-10-17 21:34 ` [PATCH 1/4] arm64: dts: renesas: r8a7796: Add FCPF and FCPV instances Laurent Pinchart
2016-10-18 8:49 ` Geert Uytterhoeven
2016-10-17 21:34 ` [PATCH 2/4] arm64: dts: renesas: r8a7796: Add VSP instances Laurent Pinchart
2016-10-18 9:02 ` Geert Uytterhoeven
2016-10-17 21:34 ` [PATCH 3/4] arm64: dts: renesas: r8a7796: Add DU device to DT Laurent Pinchart
2016-10-18 9:05 ` Geert Uytterhoeven
2016-10-18 9:19 ` Laurent Pinchart
2016-10-20 8:56 ` Simon Horman
2016-10-27 6:52 ` Magnus Damm
2016-10-27 7:04 ` Geert Uytterhoeven
2016-10-27 7:09 ` Magnus Damm
2016-10-27 7:13 ` Simon Horman [this message]
2016-10-27 7:25 ` Magnus Damm
2016-10-27 10:18 ` Simon Horman
2016-10-27 13:00 ` Simon Horman
2016-10-27 15:40 ` Laurent Pinchart
2016-11-15 19:12 ` Laurent Pinchart
2016-11-17 2:28 ` Magnus Damm
2016-11-17 8:31 ` Geert Uytterhoeven
2016-11-17 8:51 ` Magnus Damm
2016-11-21 11:09 ` Geert Uytterhoeven
2016-11-25 8:16 ` Magnus Damm
2016-11-25 9:22 ` Geert Uytterhoeven
2016-12-08 13:28 ` Simon Horman
2016-12-08 13:45 ` Geert Uytterhoeven
2016-11-17 9:12 ` Laurent Pinchart
2016-10-17 21:34 ` [PATCH 4/4] arm64: dts: renesas: r8a7796-salvator-x: Enable DU 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=20161027071348.GC7706@verge.net.au \
--to=horms@verge.net.au \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--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