[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170515204856.p7zwsfwear5b6nyx@rob-hp-laptop>
Date: Mon, 15 May 2017 15:48:56 -0500
From: Rob Herring <robh@...nel.org>
To: Minghsiu Tsai <minghsiu.tsai@...iatek.com>
Cc: Hans Verkuil <hans.verkuil@...co.com>, daniel.thompson@...aro.org,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Daniel Kurtz <djkurtz@...omium.org>,
Pawel Osciak <posciak@...omium.org>,
Houlong Wei <houlong.wei@...iatek.com>,
srv_heupstream@...iatek.com,
Eddie Huang <eddie.huang@...iatek.com>,
Yingjoe Chen <yingjoe.chen@...iatek.com>,
Wu-Cheng Li <wuchengli@...gle.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-media@...r.kernel.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v3 1/3] dt-bindings: mt8173: Fix mdp device tree
On Fri, May 12, 2017 at 11:22:39AM +0800, Minghsiu Tsai wrote:
> 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.
>
> Signed-off-by: Minghsiu Tsai <minghsiu.tsai@...iatek.com>
>
> ---
> Documentation/devicetree/bindings/media/mediatek-mdp.txt | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
Acked-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists