[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52FC8A78.1050500@ti.com>
Date: Thu, 13 Feb 2014 11:03:52 +0200
From: Tomi Valkeinen <tomi.valkeinen@...com>
To: Christoph Fritz <chf.fritz@...glemail.com>,
Tero Kristo <t-kristo@...com>
CC: Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <pali.rohar@...il.com>,
<pavel@....cz>, Nishanth Menon <nm@...com>
Subject: Re: OMAP: clock DT conversion issues with omap36xx
On 12/02/14 15:18, Tomi Valkeinen wrote:
> However, I hacked together the patch below, which "fixes" the issue for
> 96m and dss fclk. It sets the clock parents so that the x2 clocks are
> skipped, and makes the x2 clock nodes compatible with "unused", making
> them effectively disappear. I only verified dss fclk, so Christoph, can
> you verify the 96m clock?
Aaand the hack patch I sent is crap... We can't skip the x2 clock path,
as the dpll4_mNx2_ck clock nodes handle enable/disable bit, which is
present on 3630 also.
I think the best and simplest way to fix this is by setting the
multiplier in the dpll4_mNx2_mul_ck nodes to 1. I don't know why I
didn't think of it yesterday.
I have a bunch of other patches needed to get the clocks right, so I'll
send a series separately a bit later today.
Tomi
Download attachment "signature.asc" of type "application/pgp-signature" (902 bytes)
Powered by blists - more mailing lists