From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F1FFFC432C0 for ; Mon, 25 Nov 2019 12:02:02 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BF0212075C for ; Mon, 25 Nov 2019 12:02:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="roTn9szc" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BF0212075C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=amlogic.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Content-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=SBS6SKdayDyMwUOA64zQ+yjcE4aeyi5ge3Q5ieL6Dnc=; b=roTn9szcC1BZ4Cn8/90p1zubi K0SWFI+KtH3kj45AAxyIUTJHDdFZXvlwuMyCmkXJtO0C9AwEpJ8A3NiTFSq3S4BNsvunEulaj5xNP n6biTkcpf/2dAh/GLLLmZBG57EEzwJ5HTPvmp+blqhQsLJc6j5zBDY3B2hPwnE+S1uRGo/bXeUKCj /m7jE1ZlUfUmh908leUKVDVI44Yt04BHOJpwyMi6/LOUfar43SIPL92dekNEYvrWN4h7caORmkaxQ s66fNLu6nljdN6qxQVLK3RxIdAyp9tCWDJg2tcvfgoI4Y2Zjl7MKsIGslL4JXW6d+905emNs2h9ue MZDSnNbbg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1iZD42-0008AA-4u; Mon, 25 Nov 2019 12:01:58 +0000 Received: from mail-sz.amlogic.com ([211.162.65.117]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iZD3r-0007zG-9k; Mon, 25 Nov 2019 12:01:49 +0000 Received: from [10.28.39.99] (10.28.39.99) by mail-sz.amlogic.com (10.28.11.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1591.10; Mon, 25 Nov 2019 20:01:56 +0800 Subject: Re: [PATCH v2 3/3] clk: meson: a1: add support for Amlogic A1 clock driver To: Jerome Brunet , Neil Armstrong References: <1571382865-41978-1-git-send-email-jian.hu@amlogic.com> <1571382865-41978-4-git-send-email-jian.hu@amlogic.com> <1jsgnmba1a.fsf@starbuckisacylon.baylibre.com> <49b33e94-910b-3fd9-4da1-050742d07e93@amlogic.com> <1jblts3v7e.fsf@starbuckisacylon.baylibre.com> <1jh839f2ue.fsf@starbuckisacylon.baylibre.com> <20d04452-fc63-9e9e-220f-146b493a860f@amlogic.com> <1695e9b0-1730-eef6-491d-fe90ac897ee9@amlogic.com> <1jtv6yftmm.fsf@starbuckisacylon.baylibre.com> <9e652ed1-384e-f630-f2a4-0aa4486df577@amlogic.com> <1j7e3oqn36.fsf@starbuckisacylon.baylibre.com> From: Jian Hu Message-ID: <9ec317e8-136e-1ab4-4e9b-21210e7f3e05@amlogic.com> Date: Mon, 25 Nov 2019 20:01:56 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: <1j7e3oqn36.fsf@starbuckisacylon.baylibre.com> Content-Language: en-US X-Originating-IP: [10.28.39.99] X-ClientProxiedBy: mail-sz.amlogic.com (10.28.11.5) To mail-sz.amlogic.com (10.28.11.5) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191125_040147_677016_21DBB993 X-CRM114-Status: GOOD ( 18.14 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Rob Herring , Victor Wan , Jianxin Pan , Martin Blumenstingl , Kevin Hilman , Michael Turquette , linux-kernel@vger.kernel.org, Stephen Boyd , Qiufang Dai , Chandle Zou , linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 2019/11/25 18:14, Jerome Brunet wrote: > > On Thu 21 Nov 2019 at 04:21, Jian Hu wrote: > >> Hi, Jerome >> >> On 2019/11/20 23:35, Jerome Brunet wrote: >>> >>> On Wed 20 Nov 2019 at 10:28, Jian Hu wrote: >>> >>>> Hi, jerome >>>> >>>> Is there any problem about fixed_pll_dco's parent_data? >>>> >>>> Now both name and fw_name are described in parent_data. >>> >>> Yes, there is a problem. This approach is incorrect, as I've tried to >>> explain a couple times already. Let me try to re-summarize why this >>> approach is incorrect. >>> >>> Both fw_name and name should be provided when it is possible that >>> the DT does not describe the input clock. IOW, it is only for controllers >>> which relied on the global name so far and are now starting to describe >>> the clock input in DT >>> >>> This is not your case. >>> Your controller is new and DT will have the correct >>> info >>> >>> You are trying work around an ordering issue by providing both fw_name >>> and name. This is not correct and I'll continue to nack it. >>> >>> If the orphan clock is not reparented as you would expect, I suggest you >>> try to look a bit further at how the reparenting of orphans is done in >>> CCF and why it does not match your expectation. >>> >> I have debugged the handle for orphan clock in CCF, Maybe you are missing >> the last email. > > Nope, got it the first time > >> Even though the clock index exit, it will get failed for the orphan clock's >> parent clock due to it has not beed added to the provider. > > If the provider is not registered yet, of course any query to it won't > work. This why I have suggested to this debug *further* : > > * Is the orphan reparenting done when a new provider is registered ? > * If not, should it be done ? is this your problem ? > Yes, the orphan reparenting is done when the new provider is registered. Reparenting the orphan will be done when each clock is registered by devm_clk_hw_register. And at this time the provider has not been registered. After all clocks are registered by devm_clk_hw_register, the provider will be registered by devm_of_clk_add_hw_provider. Reparenting the orphan will fail when fw_name is added alone, the couse is that devm_clk_hw_register is always running ahead of devm_of_clk_add_hw_provider. That is why it will failed to get parent for the orphan clock. > > . > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel