From: Kevin Hilman <khilman@kernel.org>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Vivek Gautam <gautamvivek1987@gmail.com>,
Inki Dae <inki.dae@samsung.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-samsung-soc@vger.kernel.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: Thu, 20 Nov 2014 10:22:54 -0800 [thread overview]
Message-ID: <7hbno1spdt.fsf@deeprootsystems.com> (raw)
In-Reply-To: <546E293D.9000300@collabora.co.uk> (Javier Martinez Canillas's message of "Thu, 20 Nov 2014 18:47:41 +0100")
Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
> Hello,
>
> For completeness I'll comment what we talked with Kevin on IRC
> since probably this is the same issue that Paolo is facing.
>
> On 11/20/2014 05:41 PM, Kevin Hilman wrote:
>> Peach # setenv preboot "usb start; sleep 1"setenv bootargs
>> console=tty1 console=ttySAC3,115200 debug earlyprintk rw
>> root=/dev/mmcblk1p3 rootwait rootfstype=ext3
>
> My kernel command line is almost the same with the difference that I'm using
> clk_ignore_unused and I just checked that not passing that parameter, makes
> linux-next to hang showing the same output log that Kevin reported.
Ah! Good find. I confirm that adding clk_ignore_unused is getting me
booting again, but of course that is just masking a problem, so I hope
someone can shed light on which clock isn't being correctly managed.
Might I also suggest that folks have their default command-line to *not*
use clk_ignore_unused, since it's primary job is to workaround clock
bugs.
Kevin
next prev parent reply other threads:[~2014-11-20 18:22 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
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 [this message]
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=7hbno1spdt.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gautam.vivek@samsung.com \
--cc=gautamvivek1987@gmail.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.