From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter De Schrijver Subject: Re: [PATCH 0/4] clk: dt: add support for default rate/parent Date: Fri, 21 Mar 2014 10:12:17 +0200 Message-ID: <20140321081217.GD26674@tbergstrom-lnx.Nvidia.com> References: <1392282048-6284-1-git-send-email-t-kristo@ti.com> <53172239.3030705@ti.com> <20140320212308.21989.36094@quantum> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20140320212308.21989.36094@quantum> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Mike Turquette Cc: Tero Kristo , "devicetree@vger.kernel.org" , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" List-Id: devicetree@vger.kernel.org On Thu, Mar 20, 2014 at 10:23:08PM +0100, Mike Turquette wrote: > Quoting Tero Kristo (2014-03-05 05:10:17) > > Ping. > > > > Mike, any feedback on this? > > Hi Tero, > > Have you seen Sylwester's approach[1]? I prefer it since it is more > device-oriented and less "centralized". The clock consumer enumerates > the default parent or rate of a consumed clock. This can be made to work That assumes driver writers are aware of the clock tree topology. IME that's seldomly the case. Cheers, Peter.