Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965199AbcKLF2x (ORCPT ); Sat, 12 Nov 2016 00:28:53 -0500 Received: from sci-ig2.spreadtrum.com ([222.66.158.135]:36945 "EHLO SHSQR01.spreadtrum.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S932569AbcKLF2u (ORCPT ); Sat, 12 Nov 2016 00:28:50 -0500 Date: Sat, 12 Nov 2016 13:19:08 +0800 From: Xiaolong Zhang To: Stephen Boyd CC: , , , , , Subject: Re: [PATCH] clk: Register clkdev after setup of fixed-rate and fixed-factor clocks Message-ID: <20161112051907.GA8514@spreadtrum.com> References: <1476184424-8528-1-git-send-email-orson.zhai@spreadtrum.com> <20161020230103.GD26139@codeaurora.org> <20161022081448.GB32560@spreadtrum.com> <20161025204008.GE26139@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20161025204008.GE26139@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-MAIL: SHSQR01.spreadtrum.com uAC5PQnX009683 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2024 Lines: 51 On 二, 10月 25, 2016 at 08:40:08下午 +0000, Stephen Boyd wrote: > On 10/22, Xiaolong Zhang wrote: > > On 四, 10月 20, 2016 at 04:01:03下午 -0700, Stephen Boyd wrote: > > > On 10/11, Orson Zhai wrote: > > > > From: Xiaolong Zhang > > > > > > > > When common kernel setups fixed clock, of_clk_provider will be registerred. > > > > But there is no clkdev being registerred at the same time. This will make > > > > it difficult to get the clock by using clk_get(NULL, con_id). > > > > > > > > Add clkdev register for fixed-rate and fixed-factor clock and ignore > > > > the error if any. > > > > > > > > Signed-off-by: Xiaolong Zhang > > > > Signed-off-by: Orson Zhai > > > > --- > > > > > > Why are we using clkdev lookups for clks populated from DT? > > > Shouldn't we be able to point to them from the consumers that > > > would also be in DT? I'm a little lost. > > > > > The clk_get interface allows the first argument as NULL. We just assure > > consumers can get the clock from DT or by clock name. > > Ok. The first argument to clk_get() really shouldn't be NULL. It > should be the device pointer for the device that is associated > with the clk you want to get. The clock name (second argument to > clk_get()) should be device specific and not some globally unique > identifier. It seems that you're using the clk_get() API > incorrectly. > Sorry for late reply. There are two paths in clk_get: a) dev is not NULL, the calling procedure is as following clk_get(dev, con_id) --->of_clk_get_by_name(dev->of_node, con_id) b) dev is NULL, the calling procedure is as following clk_dev(NULL, con_id) --->clk_get_sys(NULL, con_id) --->clk_find(NULL, con_id) I just cann't understand why you say the first argument shouldn't be NULL. Is there other consideration in CCF? Thanks Xiaolong Zhang > -- > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, > a Linux Foundation Collaborative Project