[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=UcKTBjKtyQFY4odTpBDKbNQEAHjyahqgNCsD570zq=pw@mail.gmail.com>
Date: Mon, 8 Apr 2013 12:21:32 -0700
From: Doug Anderson <dianders@...omium.org>
To: Kukjin Kim <kgene.kim@...il.com>
Cc: Kukjin Kim <kgene.kim@...sung.com>,
linux-samsung-soc@...r.kernel.org,
Russell King <linux@....linux.org.uk>,
Leela Krishna Amudala <l.krishna@...sung.com>,
Jingoo Han <jg1.han@...sung.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Abraham <thomas.abraham@...aro.org>,
Olof Johansson <olof@...om.net>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Rahul Sharma <rahul.sharma@...sung.com>
Subject: Re: [PATCH] ARM: dts: fix bad merge of display timing node to exynos5250-smdk5250.dts
Kukjin,
On Mon, Apr 8, 2013 at 11:29 AM, Kukjin Kim <kgene.kim@...il.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.
-Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists