From: "Heiko Stübner" <heiko@sntech.de>
To: Joerg Roedel <joro@8bytes.org>
Cc: Simon Xue <xxm@rock-chips.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-rockchip@lists.infradead.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 add iommu nodes
Date: Wed, 26 Jul 2017 13:44:02 +0200 [thread overview]
Message-ID: <7545443.2JTXH2SMA9@diego> (raw)
In-Reply-To: <20170726105818.GK15833@8bytes.org>
Hi Joerg,
Am Mittwoch, 26. Juli 2017, 12:58:19 CEST schrieb Joerg Roedel:
> On Mon, Jul 24, 2017 at 10:32:07AM +0800, Simon Xue wrote:
> > Add H265e/VEPU/VPU/VDEC/VOP iommu nodes
> >
> > Signed-off-by: Simon Xue <xxm@rock-chips.com>
> > ---
> >
> > changes since V2:
> > - none
> >
> > arch/arm64/boot/dts/rockchip/rk3328.dtsi | 45
> > ++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+)
>
> Applied all, thanks.
I really would prefer iommu dt-nodes going through my tree :-)
Especially as parts of these conflict with already pending patches for
graphics support and with the iommu nodes sitting in your tree these
would need to wait another kernel release.
Heiko
next prev parent reply other threads:[~2017-07-26 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 2:32 [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 add iommu nodes Simon Xue
2017-07-24 2:32 ` [PATCH V3 2/4] ARM: dts: rockchip: rk322x " Simon Xue
2017-08-21 21:17 ` Heiko Stuebner
2017-07-24 2:32 ` [PATCH V3 3/4] ARM64: dts: rockchip: rk3368 " Simon Xue
2017-08-21 21:08 ` Heiko Stuebner
2017-07-24 2:32 ` [PATCH V3 4/4] ARM64: dts: rockchip: rk3399 " Simon Xue
2017-08-21 21:14 ` Heiko Stuebner
2017-07-26 10:58 ` [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 " Joerg Roedel
2017-07-26 11:44 ` Heiko Stübner [this message]
2017-07-26 12:27 ` Joerg Roedel
2017-07-26 13:53 ` Heiko Stübner
2017-07-27 12:15 ` Joerg Roedel
2017-07-27 12:26 ` Heiko Stübner
2017-07-27 12:45 ` Joerg Roedel
2017-08-21 21:08 ` Heiko Stuebner
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=7545443.2JTXH2SMA9@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=xxm@rock-chips.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