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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CA949C433FE for ; Fri, 30 Sep 2022 08:58:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229682AbiI3I60 (ORCPT ); Fri, 30 Sep 2022 04:58:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45788 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230379AbiI3I6W (ORCPT ); Fri, 30 Sep 2022 04:58:22 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e5ab]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 285AC10501C; Fri, 30 Sep 2022 01:58:21 -0700 (PDT) Received: from [192.168.1.100] (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id E567766022C7; Fri, 30 Sep 2022 09:58:18 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1664528299; bh=zxdofwuxNxIayRIjZB79Vj8Xca+pFxcHBS8ENGvGAGI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=hWSrC7qvOgH90ZvmWppW6hzm9sQjWPsVUKKu0PLZKXn3sR/RTEP1jAGd1Jci6SacZ CismWgxOP3oblzk/riHCdV6PRZsmEZ0CcV0bvT3dU4KBBKpUC5JYYkL3RhGJkho/z0 C+HL/LuRdB6sHaXhPuw8PCI/UQchsu98TD31/YRXduE+Y+QOZeaM42cSv3hHaW/jsE kwZNF2OlYMjFDKBE6ee3H9crldphCOZJw/qjkwrvgxkSeH1dOEIvsZfHVfabXT/FhB vJdDGcbXMnWSl0X1SbHh1X4dSszW4v5XxIvdTaWtLRN42vul8Qimz+HYWMxDsXYO5o 47fdnh6cy23HA== Message-ID: <5d62200e-e058-29ea-063f-91dd1fd92cf7@collabora.com> Date: Fri, 30 Sep 2022 10:58:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.0 Subject: Re: [PATCH v3 08/10] clk: mediatek: clk-mt8195-topckgen: Drop univplls from mfg mux parents Content-Language: en-US To: Chen-Yu Tsai Cc: =?UTF-8?B?TWFuZHlKSCBMaXUgKOWKieS6uuWDlik=?= , "matthias.bgg@gmail.com" , "linux-mediatek@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "robh+dt@kernel.org" , "mturquette@baylibre.com" , "jose.exposito89@gmail.com" , "drinkcat@chromium.org" , "devicetree@vger.kernel.org" , "sboyd@kernel.org" , =?UTF-8?B?Q2h1bi1KaWUgQ2hlbiAo6Zmz5rWa5qGAKQ==?= , "linux-arm-kernel@lists.infradead.org" , =?UTF-8?B?TWlsZXMgQ2hlbiAo6Zmz5rCR5qi6KQ==?= , =?UTF-8?B?V2VpeWkgTHUgKOWRguWogeWEgCk=?= , "linux-clk@vger.kernel.org" , =?UTF-8?B?UmV4LUJDIENoZW4gKOmZs+afj+i+sCk=?= , "krzysztof.kozlowski+dt@linaro.org" , "nfraprado@collabora.com" References: <20220927101128.44758-1-angelogioacchino.delregno@collabora.com> <20220927101128.44758-9-angelogioacchino.delregno@collabora.com> <79490e834466628a1b92e51f65aeb9e9ce82ddce.camel@mediatek.com> <5d8af9a1-3afc-bd69-8f34-164284a452c2@collabora.com> From: AngeloGioacchino Del Regno In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 30/09/22 10:44, Chen-Yu Tsai ha scritto: > On Fri, Sep 30, 2022 at 4:29 PM AngeloGioacchino Del Regno > wrote: >> >> Il 30/09/22 07:59, MandyJH Liu (劉人僖) ha scritto: >>> On Tue, 2022-09-27 at 12:11 +0200, AngeloGioacchino Del Regno wrote: >>>> These PLLs are conflicting with GPU rates that can be generated by >>>> the GPU-dedicated MFGPLL and would require a special clock handler >>>> to be used, for very little and ignorable power consumption benefits. >>>> Also, we're in any case unable to set the rate of these PLLs to >>>> something else that is sensible for this task, so simply drop them: >>>> this will make the GPU to be clocked exclusively from MFGPLL for >>>> "fast" rates, while still achieving the right "safe" rate during >>>> PLL frequency locking. >>>> >>>> Signed-off-by: AngeloGioacchino Del Regno < >>>> angelogioacchino.delregno@collabora.com> >>>> Reviewed-by: Chen-Yu Tsai >>>> --- >>>> drivers/clk/mediatek/clk-mt8195-topckgen.c | 9 ++++++--- >>>> 1 file changed, 6 insertions(+), 3 deletions(-) >>>> >>>> diff --git a/drivers/clk/mediatek/clk-mt8195-topckgen.c >>>> b/drivers/clk/mediatek/clk-mt8195-topckgen.c >>>> index 4dde23bece66..8cbab5ca2e58 100644 >>>> --- a/drivers/clk/mediatek/clk-mt8195-topckgen.c >>>> +++ b/drivers/clk/mediatek/clk-mt8195-topckgen.c >>>> @@ -298,11 +298,14 @@ static const char * const ipu_if_parents[] = { >>>> "mmpll_d4" >>>> }; >>>> >>>> +/* >>>> + * MFG can be also parented to "univpll_d6" and "univpll_d7": >>>> + * these have been removed from the parents list to let us >>>> + * achieve GPU DVFS without any special clock handlers. >>>> + */ >>>> static const char * const mfg_parents[] = { >>>> "clk26m", >>>> - "mainpll_d5_d2", >>>> - "univpll_d6", >>>> - "univpll_d7" >>>> + "mainpll_d5_d2" >>>> }; >>>> >>>> static const char * const camtg_parents[] = { >>> There might be a problem here. Since the univpll_d6 and univpll_d7 are >>> available parents in hardware design and they can be selected other >>> than kernel stage, like bootloader, the clk tree listed in clk_summary >>> cannot show the real parent-child relationship in such case. >> >> I agree about that, but the clock framework will change the parent to >> the "best parent" in that case... this was done to avoid writing complicated >> custom clock ops just for that one. >> >> This issue is present only on MT8195, so it can be safely solved this way, >> at least for now. >> >> Should this become a thing on another couple SoCs, it'll then make sense >> to write custom clock ops just for the MFG. > > Would CLK_SET_RATE_NO_REPARENT on the fast mux coupled with forcing > the clk tree to a state that we like (mfgpll->fast_mux->gate) work? I'm not sure that it would, and then this would mean that we'd have to add assigned-clock-parents to the devicetree and the day we will introduce the "complicated custom clock ops" for that, we'll most probably have to change the devicetree as well... which is something that I'm a bit reluctant to do as a kernel upgrade doesn't automatically mean that you upgrade the DT with it to get the "new full functionality". Introducing the new clock ops for the mfg mux is something that will happen for sure, but if we don't get new SoCs with a similar "issue", I don't feel confident to write them, as I fear these won't be as flexible as needed and will eventually need a rewrite; that's why I want to wait to get the same situation on "something new". In my opinion, it is safe to keep this change as it is, even though I do understand the shown concerns about the eventual unability to show the tree relationship in case the bootloader chooses to initialize the mfg mux with a univpll parent. Regards, Angelo