From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: fix bad merge of display timing node to exynos5250-smdk5250.dts
Date: Mon, 08 Apr 2013 21:27:14 +0200 [thread overview]
Message-ID: <2824266.emLkgITIHc@flatron> (raw)
In-Reply-To: <CAD=FV=UcKTBjKtyQFY4odTpBDKbNQEAHjyahqgNCsD570zq=pw@mail.gmail.com>
Hi Doug,
On Monday 08 of April 2013 12:21:32 Doug Anderson wrote:
> Kukjin,
>
> On Mon, Apr 8, 2013 at 11:29 AM, Kukjin Kim <kgene.kim@gmail.com> wrote:
> > BTW, if any problems on current for-next, please kindly let me know.
>
> I usually try to check linux-next at least once a week, but sometimes
> it's more or less often. At the moment I'm trying to track something
> weird down but it seems like it has some userspace component to it.
> I'll post a separate thread if I find a kernel problem there.
>
> Aside from the RTC, my biggest problem right now is that reboot
> stopped working at the same time as the common clock. The
> exynos5_restart() function is essentially behaving as a no-op since
> the clock to the IP block that handles reset has been gated. :( The
> bit "CLK_PMU_APBIF" is gated in "CLK_GATE_IP_PERIS". This used to be
> ungated in exynos5_clk_ip_peris_ctrl().
>
> I'm happy to test a patch that fixes this but I haven't yet had time
> to try to fix it cleanly myself.
Common Clock Framework by default automatically gates unused clocks, just
like regulator core does with unused regulators. Maybe this is the cause?
There is a CLK_IGNORE_UNUSED flag which disables this behavior for all
clocks which have it set. Maybe it should be set for the problematic
clock?
Best regards,
Tomasz
next prev parent reply other threads:[~2013-04-08 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 16:51 [PATCH] ARM: dts: fix bad merge of display timing node to exynos5250-smdk5250.dts Doug Anderson
2013-04-08 18:23 ` Kukjin Kim
2013-04-08 18:25 ` Doug Anderson
2013-04-08 18:29 ` Kukjin Kim
2013-04-08 19:21 ` Doug Anderson
2013-04-08 19:27 ` Tomasz Figa [this message]
2013-04-08 19:41 ` Doug Anderson
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=2824266.emLkgITIHc@flatron \
--to=tomasz.figa@gmail.com \
--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).