From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751294AbaA2JuS (ORCPT ); Wed, 29 Jan 2014 04:50:18 -0500 Received: from arroyo.ext.ti.com ([192.94.94.40]:32975 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750925AbaA2JuP (ORCPT ); Wed, 29 Jan 2014 04:50:15 -0500 Message-ID: <52E8CECE.5010905@ti.com> Date: Wed, 29 Jan 2014 11:50:06 +0200 From: Tero Kristo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Tomi Valkeinen , Ivaylo Dimitrov CC: "linux-omap@vger.kernel.org" , , , , , Subject: Re: [BISECTED] OMAP: DSS: clk rate mismatch References: <52E697C0.6000202@gmail.com> <52E7614E.8010903@ti.com> <52E76EE0.2060006@ti.com> <52E7F451.7040708@gmail.com> <52E8C586.7040907@ti.com> <52E8CA00.7060303@gmail.com> <52E8CC03.7080207@ti.com> In-Reply-To: <52E8CC03.7080207@ti.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/29/2014 11:38 AM, Tomi Valkeinen wrote: > On 2014-01-29 11:29, Ivaylo Dimitrov wrote: >> >> >> On 29.01.2014 11:10, Tero Kristo wrote: >> >>> >>> It looks like the omap36xx version of the omap96m_alwon_fck is modelled >>> improperly in the dts files. I don't have access to omap36xx hardware >>> myself, but give a try for the following patch: >>> >>> >> >> It could be that 36xx omap96m_alwon_fck clock is wrongly modeled, but I >> am testing on 1) 3430es2 (Nokia N900) and 2) legacy boot, so I guess >> that patch won't help much (unless I am missing something and DT is used >> even with legacy boot and 36xx clocks are used on 3430es2) > > I think Tero's reply was to Christoph. I believe the issues you see and > what Christoph sees are totally different. > > Tomi Oh yea sorry about the confusion, have too many separate issues listed under this thread. :P That was definitely for Christoph. For the DSS clk rate part, Tomi should answer that as it seems to come from some display driver changes. This might be caused by the infamous rounding issues with the clk_set_rate / clk_round_rate and the hackery around it in display driver... -Tero