From: Hans Verkuil <hverkuil@xs4all.nl>
To: Minghsiu Tsai <minghsiu.tsai@mediatek.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
daniel.thompson@linaro.org, Rob Herring <robh+dt@kernel.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Pawel Osciak <posciak@chromium.org>,
Houlong Wei <houlong.wei@mediatek.com>
Cc: srv_heupstream@mediatek.com,
Eddie Huang <eddie.huang@mediatek.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Wu-Cheng Li <wuchengli@google.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 0/3] Fix mdp device tree
Date: Mon, 22 May 2017 11:09:05 +0200 [thread overview]
Message-ID: <20ba4f83-7d22-2a8e-4eb6-7d4eba92e2ae@xs4all.nl> (raw)
In-Reply-To: <1494559361-42835-1-git-send-email-minghsiu.tsai@mediatek.com>
On 05/12/2017 05:22 AM, Minghsiu Tsai wrote:
Who should take care of the dtsi changes? I'm not sure who maintains the mdp dts.
The driver change and the dtsi change need to be in sync, so it is probably easiest
to merge this via one tree.
Here is my Acked-by for these three patches:
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
I can take all three, provided I have the Ack of the mdp dts maintainer. Or it can
go through him with my Ack.
Regards,
Hans
> Changes in v3:
> - Upload patches again because forget to add v2 in title
>
> Changes in v2:
> - Update commit message
>
> If the mdp_* nodes are under an mdp sub-node, their corresponding
> platform device does not automatically get its iommu assigned properly.
>
> Fix this by moving the mdp component nodes up a level such that they are
> siblings of mdp and all other SoC subsystems. This also simplifies the
> device tree.
>
> Although it fixes iommu assignment issue, it also break compatibility
> with old device tree. So, the patch in driver is needed to iterate over
> sibling mdp device nodes, not child ones, to keep driver work properly.
>
> Daniel Kurtz (2):
> arm64: dts: mt8173: Fix mdp device tree
> media: mtk-mdp: Fix mdp device tree
>
> Minghsiu Tsai (1):
> dt-bindings: mt8173: Fix mdp device tree
>
> .../devicetree/bindings/media/mediatek-mdp.txt | 12 +-
> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 126 ++++++++++-----------
> drivers/media/platform/mtk-mdp/mtk_mdp_core.c | 2 +-
> 3 files changed, 64 insertions(+), 76 deletions(-)
>
next prev parent reply other threads:[~2017-05-22 9:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 3:22 Minghsiu Tsai
2017-05-12 3:22 ` [PATCH v3 1/3] dt-bindings: mt8173: " Minghsiu Tsai
2017-05-15 20:48 ` Rob Herring
2017-05-12 3:22 ` [PATCH v3 2/3] arm64: dts: " Minghsiu Tsai
2017-05-12 3:22 ` [PATCH v3 3/3] media: mtk-mdp: " Minghsiu Tsai
2017-05-12 15:05 ` Matthias Brugger
2017-05-15 2:31 ` Minghsiu Tsai
2017-05-15 7:27 ` Matthias Brugger
2017-05-22 9:09 ` Hans Verkuil [this message]
2017-05-22 14:14 ` [PATCH v3 0/3] " Matthias Brugger
2017-05-22 14:16 ` Hans Verkuil
2017-05-23 3:35 ` Minghsiu Tsai
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=20ba4f83-7d22-2a8e-4eb6-7d4eba92e2ae@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=eddie.huang@mediatek.com \
--cc=hans.verkuil@cisco.com \
--cc=houlong.wei@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@osg.samsung.com \
--cc=minghsiu.tsai@mediatek.com \
--cc=posciak@chromium.org \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=wuchengli@google.com \
--cc=yingjoe.chen@mediatek.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
all inboxes | Powered by JetHome®