From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mailout3.w1.samsung.com ([210.118.77.13]:50186 "EHLO mailout3.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751655AbcFFHkt (ORCPT ); Mon, 6 Jun 2016 03:40:49 -0400 Subject: Re: [PATCH v4 5/7] ARM: Exynos: remove code for MFC custom reserved memory handling To: Javier Martinez Canillas , Marek Szyprowski , linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org References: <1464096690-23605-1-git-send-email-m.szyprowski@samsung.com> <1464096690-23605-6-git-send-email-m.szyprowski@samsung.com> <574BEBB8.8040606@samsung.com> <5a12a8be-0402-dc0c-d242-5d9f3145e001@osg.samsung.com> <57505F5B.90101@samsung.com> <57512A6A.1050209@samsung.com> Cc: devicetree@vger.kernel.org, Sylwester Nawrocki , Kamil Debski , Kukjin Kim , Uli Middelberg , Bartlomiej Zolnierkiewicz From: Krzysztof Kozlowski Message-id: <575528FC.6050707@samsung.com> Date: Mon, 06 Jun 2016 09:40:44 +0200 MIME-version: 1.0 In-reply-to: <57512A6A.1050209@samsung.com> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: On 06/03/2016 08:57 AM, Krzysztof Kozlowski wrote: > On 06/02/2016 07:25 PM, Javier Martinez Canillas wrote: >> Marek mentioned that bisectability is only partially broken because the old >> binding will still work after this series if IOMMU is enabled (because the >> properties are ignored in this case). But will break if IOMMU isn't enabled >> which will be the case for some boards that fails to boot with IOMMU due the >> bootloader leaving the FIMD enabled doing DMA operations automatically AFAIU. >> >> Now, I'm OK with not keeping backwards compatibility for the MFC dt bindings >> since arguably the driver has been broken for a long time and nobody cared >> and also I don't think anyone in practice boots a new kernel with an old DTB >> for Exynos. >> >> But I don't think is correct to introduce a new issue as is the case if this >> patch is applied before the previous patches in the series since this causes >> the driver to probe to fail and the following warn on boot (while it used to >> at least probe correctly in mainline): > > Okay but the patches will go through separate tree. This is not a > problem, as I said, I just need a stable tag from media tree with first > four patches (Mauro?). Applied again this and DTS changes (remaining two patches) for v4.8 on top of branch provided by Sylwester: https://git.kernel.org/cgit/linux/kernel/git/krzk/linux.git/log/?h=for-v4.8/exynos-mfc Best regards, Krzysztof