From: Kevin Hilman <khilman@kernel.org>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Inki Dae <inki.dae@samsung.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org,
Paolo Pisati <p.pisati@gmail.com>,
Vivek Gautam <gautam.vivek@samsung.com>
Subject: Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init
Date: Wed, 19 Nov 2014 11:52:50 -0800 [thread overview]
Message-ID: <7hbno3ufvx.fsf@deeprootsystems.com> (raw)
In-Reply-To: <546CCAB8.9050402@collabora.co.uk> (Javier Martinez Canillas's message of "Wed, 19 Nov 2014 17:52:08 +0100")
Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
> [adding Paolo and Vivek as cc]
>
> Hello,
>
> On 11/18/2014 07:41 PM, Kevin Hilman wrote:
>>
>> It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
>> it proceeds to panic in the workqueue code called by the asoc max98090
>> codec[1].
>>
>> If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
>> but I still don't have display output.
>>
>
> Paolo Pisati pointed out in another thread that he needed the patch
> "[PATCH v2 2/2] arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy"
> is also needed to get display working for exynos on linux-next.
>
> I've pinged Kukjin to apply this as a -rc fix since is needed after
> a5ec598 ("phy: exynos-dp-video: Use syscon support to control pmu register")
> landed in 3.18 which broke the Exynos Display Port PHY:
>
> exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU regmap
>
> I've an Exynos5800 Peach Pi now so I wanted to test display on it. Just $subject
> and [0] should be enough to have display working on Peach Pi
Yes, with those two patches, peach-pi display working on v3.18-rc5 for me.
> with linux-next but
> it fails to me with:
>
> exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
>
> The same issue was reported by Paolo a couple of days ago [1].
For me, with linux-next, I'm still getting the DRM deadlock. Trying
your patch that moves things to module_init gets past the deadlock, but
still doesn't boot unless I disable CONFIG_SND_SOC_SNOW. Doing that I
see the same video-phy error though.
Kevin
next prev parent reply other threads:[~2014-11-19 19:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 13:53 [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init Javier Martinez Canillas
2014-11-18 18:41 ` Kevin Hilman
2014-11-18 20:28 ` Gustavo Padovan
2014-11-18 22:46 ` Kevin Hilman
2014-11-19 10:09 ` Javier Martinez Canillas
2014-11-19 16:52 ` Javier Martinez Canillas
2014-11-19 19:52 ` Kevin Hilman [this message]
2014-11-19 22:29 ` Kevin Hilman
2014-11-20 7:06 ` Vivek Gautam
2014-11-20 7:51 ` Vivek Gautam
2014-11-20 8:45 ` Javier Martinez Canillas
2014-11-20 9:52 ` Vivek Gautam
2014-11-20 14:24 ` Pankaj Dubey
2014-11-20 15:57 ` Paolo Pisati
2014-11-20 16:44 ` Javier Martinez Canillas
2014-11-20 16:41 ` Kevin Hilman
2014-11-20 17:47 ` Javier Martinez Canillas
2014-11-20 18:22 ` Kevin Hilman
2014-11-20 23:49 ` Paolo Pisati
2014-11-21 11:33 ` Andreas Färber
2014-11-21 17:32 ` Ajay kumar
2014-11-21 20:57 ` Javier Martinez Canillas
2014-11-24 10:05 ` Javier Martinez Canillas
2014-11-24 10:36 ` Vivek Gautam
2014-11-24 15:05 ` Andreas Färber
2014-11-25 5:35 ` Ajay kumar
2014-11-21 13:03 ` Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init) Javier Martinez Canillas
2014-11-21 16:38 ` Kevin Hilman
2014-11-21 20:49 ` Javier Martinez Canillas
2014-11-22 10:21 ` Krzysztof Kozlowski
2014-11-24 9:38 ` Javier Martinez Canillas
2014-11-24 9:42 ` Javier Martinez Canillas
2014-11-24 10:13 ` Krzysztof Kozlowski
2014-11-24 11:07 ` Javier Martinez Canillas
2014-11-24 11:12 ` Krzysztof Kozlowski
2014-11-24 13:16 ` Javier Martinez Canillas
2014-11-24 13:28 ` Vivek Gautam
2014-11-24 13:53 ` Krzysztof Kozlowski
2014-11-24 9:51 ` Krzysztof Kozlowski
2014-11-20 14:07 ` [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init Inki Dae
2014-11-20 14:28 ` Javier Martinez Canillas
2014-11-20 15:06 ` Inki Dae
2014-11-20 15:26 ` Javier Martinez Canillas
2014-11-20 17:01 ` Inki Dae
2014-11-21 11:19 ` 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=7hbno3ufvx.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gautam.vivek@samsung.com \
--cc=inki.dae@samsung.com \
--cc=javier.martinez@collabora.co.uk \
--cc=k.kozlowski@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=p.pisati@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.