linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: javier@dowhile0.org (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Samsung fixes-2 for v4.0
Date: Fri, 6 Mar 2015 11:07:34 +0100	[thread overview]
Message-ID: <CABxcv==QyMUr6jUpzkWqpKCWc_msokCefxrBGvmDHrtgXmevig@mail.gmail.com> (raw)
In-Reply-To: <027501d057f1$f13a5090$d3aef1b0$@kernel.org>

Hello Kukjin,

On Fri, Mar 6, 2015 at 10:43 AM, Kukjin Kim <kgene@kernel.org> wrote:
> Javier Martinez Canillas wrote:
>>
>> Hello Arnd,
>>
> Hi,
>
>> On Thu, Mar 5, 2015 at 12:04 AM, Arnd Bergmann <arnd@arndb.de> wrote:
>> > On Wednesday 04 March 2015 21:04:40 Arnd Bergmann wrote:
>> >> On Tuesday 03 March 2015 04:00:14 Kukjin Kim wrote:
>> >> > Please pull Samsung tmu and hdmi regression fixes for v4.0 and I know
>> >> > this is quite big for fixes but I couldn't handle this series for
>> >> > previous merge window because of dependency with driver side...sorry for
>> >> > that and please pull so that we could support them in v4.0 on exynos
>> >> > platforms.
>> >>
>> >> What kind of dependency do you have there? It really should not be
>> >> necessary to wait for driver changes, unless you do an incompatible
>> >> DT binding change, which you should avoid.
>> >>
>> >> I've pulled it into fixes, but won't forward it until I hear a
>> >> good explanation.
>> >
>> > Even with both fixes-1 and fixes-2 applied, we still get boot failures
>> > on Exynos:
>> >
>> > http://arm-soc.lixom.net/bootlogs/arm-soc/v4.0-rc2-104-g2ee4716/
>> >
>> > Any idea what is going on?
>> >
>>
>> Yes, the problem is the Exynos DRM driver which has a lot of issues.
>> It's broken if CONFIG_DRM_EXYNOS_IOMMU is enabled which defaults to
>> yes after commit 8dcc14f82f06 ("drm/exynos: IOMMU support should not
>> be selectable by user").
>>
>> I posted a patch to disable IOMMU support on Exynos to avoid these
>> boot failures and also mentioned to Kukjin that it should be a fix for
>> 4.0 [0]. But even with IOMMU disabled, the Exynos DRM is broken in
>> some boards [1] so we may have to disable that driver until everything
>> gets sorted out and is stable again.
>>
> Yes, the fix is in my tree and it will be sent to upstream via arm-soc soon.
>

Thanks a lot for your help. You meant the patch to disable IOMMU
support right? While being there could you please also disable the DRM
driver as discussed since is unlikely that the Exynos DRM maintainers
would be able to sort out all the issues in time for 4.0.

> Thanks,
> Kukjin
>

Best regards,
Javier

  reply	other threads:[~2015-03-06 10:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 19:00 [GIT PULL 2/2] Samsung fixes-2 for v4.0 Kukjin Kim
2015-03-04 20:04 ` Arnd Bergmann
2015-03-04 23:04   ` Arnd Bergmann
2015-03-05  0:38     ` Javier Martinez Canillas
2015-03-06  9:43       ` Kukjin Kim
2015-03-06 10:07         ` Javier Martinez Canillas [this message]
2015-03-14 13:17         ` Javier Martinez Canillas
2015-03-06 10:16   ` Kukjin Kim
2015-03-05 12:34     ` Eduardo Valentin
2015-03-09  7:44       ` Lukasz Majewski
2015-03-09  8:19         ` Kukjin Kim
2015-03-09  8:28           ` Lukasz Majewski
2015-03-12 11:15       ` Kukjin Kim

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='CABxcv==QyMUr6jUpzkWqpKCWc_msokCefxrBGvmDHrtgXmevig@mail.gmail.com' \
    --to=javier@dowhile0.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).