public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: devicetree@vger.kernel.org,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Kamil Debski <k.debski@samsung.com>,
	Kukjin Kim <kgene@kernel.org>, Uli Middelberg <uli@middelberg.de>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v4 5/7] ARM: Exynos: remove code for MFC custom reserved memory handling
Date: Mon, 06 Jun 2016 09:40:44 +0200	[thread overview]
Message-ID: <575528FC.6050707@samsung.com> (raw)
In-Reply-To: <57512A6A.1050209@samsung.com>

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


  parent reply	other threads:[~2016-06-06  7:40 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 13:31 [PATCH v4 0/7] Exynos: MFC driver: reserved memory cleanup and IOMMU support Marek Szyprowski
2016-05-24 13:31 ` [PATCH v4 1/7] of: reserved_mem: add support for using more than one region for given device Marek Szyprowski
2016-05-26 19:08   ` Rob Herring
2016-05-24 13:31 ` [PATCH v4 2/7] media: s5p-mfc: use generic reserved memory bindings Marek Szyprowski
2016-05-25 15:18   ` Javier Martinez Canillas
2016-05-25 17:36     ` Rob Herring
2016-05-27  6:37       ` Marek Szyprowski
2016-05-27 20:41         ` Javier Martinez Canillas
2016-05-25 17:39   ` Rob Herring
2016-05-27  6:19   ` Krzysztof Kozlowski
2016-05-24 13:31 ` [PATCH v4 3/7] media: s5p-mfc: replace custom reserved memory handling code with generic one Marek Szyprowski
2016-05-25 15:42   ` Javier Martinez Canillas
2016-05-25 16:51     ` Javier Martinez Canillas
2016-06-08 10:36   ` Liviu Dudau
2016-06-08 11:33     ` [PATCH] media: s5p-mfc: fix error path in driver probe Marek Szyprowski
2016-06-08 14:35       ` Liviu Dudau
2016-06-08 21:44         ` Shuah Khan
2016-05-24 13:31 ` [PATCH v4 4/7] media: s5p-mfc: add iommu support Marek Szyprowski
2016-05-25 15:55   ` Javier Martinez Canillas
2016-05-24 13:31 ` [PATCH v4 5/7] ARM: Exynos: remove code for MFC custom reserved memory handling Marek Szyprowski
2016-05-25 15:57   ` Javier Martinez Canillas
2016-05-30  7:28   ` Krzysztof Kozlowski
2016-06-02 15:20     ` Javier Martinez Canillas
2016-06-02 16:31       ` Krzysztof Kozlowski
2016-06-02 17:25         ` Javier Martinez Canillas
2016-06-03  6:57           ` Krzysztof Kozlowski
2016-06-03  9:59             ` [ATTN] " Sylwester Nawrocki
2016-06-06  7:24               ` Krzysztof Kozlowski
2016-06-06  7:40             ` Krzysztof Kozlowski [this message]
2016-05-24 13:31 ` [PATCH v4 6/7] ARM: dts: exynos: convert MFC device to generic reserved memory bindings Marek Szyprowski
2016-05-25 11:13   ` Krzysztof Kozlowski
2016-05-25 17:11   ` Javier Martinez Canillas
2016-05-27 11:32     ` Marek Szyprowski
2016-05-27 20:54       ` Javier Martinez Canillas
2016-06-07 12:03         ` [PATCH 1/3] ARM: dts: exynos: replace hardcoded reserved memory ranges with auto-allocated ones Marek Szyprowski
2016-06-07 12:03           ` [PATCH 2/3] ARM: dts: exynos: move MFC reserved memory regions from boards to .dtsi Marek Szyprowski
2016-06-07 22:34             ` Javier Martinez Canillas
2016-06-07 12:03           ` [PATCH 3/3] ARM: dts: exynos: enable MFC device for all boards Marek Szyprowski
2016-06-07 22:34             ` Javier Martinez Canillas
2016-06-07 22:32           ` [PATCH 1/3] ARM: dts: exynos: replace hardcoded reserved memory ranges with auto-allocated ones Javier Martinez Canillas
2016-06-08  7:48           ` Krzysztof Kozlowski
2016-05-24 13:31 ` [PATCH v4 7/7] ARM: dts: exynos4412-odroid*: enable MFC device Marek Szyprowski
2016-05-25 17:13   ` Javier Martinez Canillas

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=575528FC.6050707@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=javier@osg.samsung.com \
    --cc=k.debski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=s.nawrocki@samsung.com \
    --cc=uli@middelberg.de \
    /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