From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tero Kristo Subject: Re: [PATCH] clk: ti: change clock init to use generic of_clk_init Date: Mon, 22 Sep 2014 09:52:04 +0300 Message-ID: <541FC714.9050203@ti.com> References: <1408628959-32442-1-git-send-email-t-kristo@ti.com> <20140918171725.GL14505@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from arroyo.ext.ti.com ([192.94.94.40]:58142 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750961AbaIVGv4 (ORCPT ); Mon, 22 Sep 2014 02:51:56 -0400 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Paul Walmsley , Tony Lindgren Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Mike Turquette , Mark Rutland , Peter Ujfalusi , Jyri Sarha , Stefan Assmann On 09/19/2014 07:33 PM, Paul Walmsley wrote: > On Thu, 18 Sep 2014, Tony Lindgren wrote: > >> * Tero Kristo [140821 06:52]: >>> Previously, the TI clock driver initialized all the clocks hierarchically >>> under each separate clock provider node. Now, each clock that requires >>> IO access will instead check their parent node to find out which IO range >>> to use. >>> >>> This patch allows the TI clock driver to use a few new features provided >>> by the generic of_clk_init, and also allows registration of clock nodes >>> outside the clock hierarchy (for example, any external clocks.) >> >> Paul, any comments on this one? > > Not at this point. Tony, ok to merge this through clock tree? -Tero From mboxrd@z Thu Jan 1 00:00:00 1970 From: t-kristo@ti.com (Tero Kristo) Date: Mon, 22 Sep 2014 09:52:04 +0300 Subject: [PATCH] clk: ti: change clock init to use generic of_clk_init In-Reply-To: References: <1408628959-32442-1-git-send-email-t-kristo@ti.com> <20140918171725.GL14505@atomide.com> Message-ID: <541FC714.9050203@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 09/19/2014 07:33 PM, Paul Walmsley wrote: > On Thu, 18 Sep 2014, Tony Lindgren wrote: > >> * Tero Kristo [140821 06:52]: >>> Previously, the TI clock driver initialized all the clocks hierarchically >>> under each separate clock provider node. Now, each clock that requires >>> IO access will instead check their parent node to find out which IO range >>> to use. >>> >>> This patch allows the TI clock driver to use a few new features provided >>> by the generic of_clk_init, and also allows registration of clock nodes >>> outside the clock hierarchy (for example, any external clocks.) >> >> Paul, any comments on this one? > > Not at this point. Tony, ok to merge this through clock tree? -Tero