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 6F47AC54E76 for ; Fri, 6 Jan 2023 07:45:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231364AbjAFHpz (ORCPT ); Fri, 6 Jan 2023 02:45:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59438 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229636AbjAFHps (ORCPT ); Fri, 6 Jan 2023 02:45:48 -0500 Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 09C6D78155 for ; Thu, 5 Jan 2023 23:45:47 -0800 (PST) Received: by mail-wm1-x336.google.com with SMTP id p1-20020a05600c1d8100b003d8c9b191e0so527670wms.4 for ; Thu, 05 Jan 2023 23:45:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=BWzIac1mQdA/HE3RfWrbgoLzJ/aPJCGCNKjxU7CNlVk=; b=jA7qrgj0BKbAUuBwRaUBJis0zSlr3wsts22b9lvfBwJ+2A5wnJgNUR54zHRs6/FlES KpT1LIxIgZIjubTPt5zvVur1WMu+Hjx2uL4c+ZwqichkLUxCdyaSIQvhSIfJjUtxWqwn elIcP9v3SqwBZbX1sDuvN6rCzSqG6n1uNqjgvJSYJtfvLIc7rt4TsFx65W9F0NLc3erq xLAAZM7tStCq0sdyROxnYW9Vy+JnPxdzWOCSRaN5VKxHxFBZ5EI5RPI2skKvWrwpad3N Lf8bxVU7Edt921X2f5834EvTXUky/uvN9u9bDZd75YZlQzzxHHDkGXHL+y11CsXO+A60 b4pQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=BWzIac1mQdA/HE3RfWrbgoLzJ/aPJCGCNKjxU7CNlVk=; b=fdxNqc5xOf3KCY0SNNuRNxE1JARuZbAISjB6EGgCxw4iWlcQBaw5TyP2Qp40SK3UmX vPK/u0BM0uKZWwlxfwt1ObUPMDx/o3WxNuwgq0Kesu/p7BGrDCsEwSC8SrMowIBIJ/VP xsqHgwGedaywiZhJV/GncDSgpZyVA8mmFv1YJ0KbuUlhBlvF//ZiG2mfk4+5N5pKw0L8 jRQv+FzONcvYAH/ETO3Qq3CgHKKclB9oUrvNmrSxtVyBxD2DUiOf/eQlMRX4cfn5co94 SGU6JzaD2vYK3ufNSEn8uLx1gub9rR0B868CVj9I6xZEe8yBpX+MO+68XpZShoDSgwg1 SfFw== X-Gm-Message-State: AFqh2kqf/G8nc3zIk4yEt1HWe9zOFnZwVf6x7eXEuJHJnL4gKLeWoxZl x93SATT0JsFZLOq0u5qSXlusG3hoCl8o/juT X-Google-Smtp-Source: AMrXdXuCnAAiEGnDDIF1f0v8D0Cm3uApENmX7jMXvcHmLWtjRg9DjUSiiKEoi7QWcFyQN8yza33tVA== X-Received: by 2002:a1c:4b03:0:b0:3d9:103d:9081 with SMTP id y3-20020a1c4b03000000b003d9103d9081mr38201497wma.28.1672991145540; Thu, 05 Jan 2023 23:45:45 -0800 (PST) Received: from [192.168.1.102] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id t14-20020adfeb8e000000b002baa780f0fasm356919wrn.111.2023.01.05.23.45.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 05 Jan 2023 23:45:45 -0800 (PST) Message-ID: Date: Fri, 6 Jan 2023 08:45:42 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v6 4/5] clk: qcom: rpmh: Add support for SM8550 rpmh clocks Content-Language: en-US To: Dmitry Baryshkov , Bjorn Andersson , Mike Tipton Cc: Abel Vesa , Andy Gross , Konrad Dybcio , Mike Turquette , Stephen Boyd , Rob Herring , Krzysztof Kozlowski , Linux Kernel Mailing List , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org References: <20221206224515.1495457-1-abel.vesa@linaro.org> <20221206224515.1495457-5-abel.vesa@linaro.org> <6fc64fae-e616-2038-0424-34ce0cb7e16d@linaro.org> <20221228185254.4acnjchbyq4krblb@builder.lan> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/12/2022 19:59, Dmitry Baryshkov wrote: > On 28/12/2022 20:52, Bjorn Andersson wrote: >> On Wed, Dec 14, 2022 at 06:25:01PM +0200, Dmitry Baryshkov wrote: >>> On 07/12/2022 00:45, Abel Vesa wrote: >>>> Adds the RPMH clocks present in SM8550 SoC. >>>> >>>> Signed-off-by: Abel Vesa >>>> Reviewed-by: Konrad Dybcio >>>> --- >>>> drivers/clk/qcom/clk-rpmh.c | 110 +++++++++++++++++++++++++++++------- >>>> 1 file changed, 90 insertions(+), 20 deletions(-) >>>> >>>> diff --git a/drivers/clk/qcom/clk-rpmh.c b/drivers/clk/qcom/clk-rpmh.c >>>> index 2c2ef4b6d130..ce81c76ed0fd 100644 >>>> --- a/drivers/clk/qcom/clk-rpmh.c >>>> +++ b/drivers/clk/qcom/clk-rpmh.c >>>> @@ -130,6 +130,34 @@ static DEFINE_MUTEX(rpmh_clk_lock); >>>> }, \ >>>> } >>>> +#define DEFINE_CLK_FIXED_FACTOR(_name, _parent_name, _div) \ >>>> + static struct clk_fixed_factor clk_fixed_factor##_##_name = { \ >>>> + .mult = 1, \ >>>> + .div = _div, \ >>>> + .hw.init = &(struct clk_init_data){ \ >>>> + .ops = &clk_fixed_factor_ops, \ >>>> + .name = #_name, \ >>>> + .parent_data = &(const struct clk_parent_data){ \ >>>> + .fw_name = #_parent_name, \ >>>> + .name = #_parent_name, \ >>>> + }, \ >>>> + .num_parents = 1, \ >>>> + }, \ >>>> + }; \ >>>> + static struct clk_fixed_factor clk_fixed_factor##_##_name##_ao = { \ >>>> + .mult = 1, \ >>>> + .div = _div, \ >>>> + .hw.init = &(struct clk_init_data){ \ >>>> + .ops = &clk_fixed_factor_ops, \ >>>> + .name = #_name "_ao", \ >>>> + .parent_data = &(const struct clk_parent_data){ \ >>>> + .fw_name = #_parent_name "_ao", \ >>>> + .name = #_parent_name "_ao", \ >>>> + }, \ >>>> + .num_parents = 1, \ >>>> + }, \ >>>> + } >>>> + >>>> static inline struct clk_rpmh *to_clk_rpmh(struct clk_hw *_hw) >>>> { >>>> return container_of(_hw, struct clk_rpmh, hw); >>>> @@ -345,6 +373,8 @@ DEFINE_CLK_RPMH_ARC(bi_tcxo, "xo.lvl", 0x3, 2); >>>> DEFINE_CLK_RPMH_ARC(bi_tcxo, "xo.lvl", 0x3, 4); >>>> DEFINE_CLK_RPMH_ARC(qlink, "qphy.lvl", 0x1, 4); >>>> +DEFINE_CLK_FIXED_FACTOR(bi_tcxo_div2, bi_tcxo, 2); >>>> + >>>> DEFINE_CLK_RPMH_VRM(ln_bb_clk1, _a2, "lnbclka1", 2); >>>> DEFINE_CLK_RPMH_VRM(ln_bb_clk2, _a2, "lnbclka2", 2); >>>> DEFINE_CLK_RPMH_VRM(ln_bb_clk3, _a2, "lnbclka3", 2); >>>> @@ -366,6 +396,16 @@ DEFINE_CLK_RPMH_VRM(rf_clk2, _d, "rfclkd2", 1); >>>> DEFINE_CLK_RPMH_VRM(rf_clk3, _d, "rfclkd3", 1); >>>> DEFINE_CLK_RPMH_VRM(rf_clk4, _d, "rfclkd4", 1); >>>> +DEFINE_CLK_RPMH_VRM(clk1, _a1, "clka1", 1); >>>> +DEFINE_CLK_RPMH_VRM(clk2, _a1, "clka2", 1); >>>> +DEFINE_CLK_RPMH_VRM(clk3, _a1, "clka3", 1); >>>> +DEFINE_CLK_RPMH_VRM(clk4, _a1, "clka4", 1); >>>> +DEFINE_CLK_RPMH_VRM(clk5, _a1, "clka5", 1); >>>> + >>>> +DEFINE_CLK_RPMH_VRM(clk6, _a2, "clka6", 2); >>>> +DEFINE_CLK_RPMH_VRM(clk7, _a2, "clka7", 2); >>>> +DEFINE_CLK_RPMH_VRM(clk8, _a2, "clka8", 2); >>>> + >>>> DEFINE_CLK_RPMH_VRM(div_clk1, _div2, "divclka1", 2); >>>> DEFINE_CLK_RPMH_BCM(ce, "CE0"); >>>> @@ -576,6 +616,33 @@ static const struct clk_rpmh_desc clk_rpmh_sm8450 = { >>>> .num_clks = ARRAY_SIZE(sm8450_rpmh_clocks), >>>> }; >>>> +static struct clk_hw *sm8550_rpmh_clocks[] = { >>>> + [RPMH_CXO_PAD_CLK] = &clk_rpmh_bi_tcxo_div2.hw, >>>> + [RPMH_CXO_PAD_CLK_A] = &clk_rpmh_bi_tcxo_div2_ao.hw, >>>> + [RPMH_CXO_CLK] = &clk_fixed_factor_bi_tcxo_div2.hw, >>>> + [RPMH_CXO_CLK_A] = &clk_fixed_factor_bi_tcxo_div2_ao.hw, >>>> + [RPMH_LN_BB_CLK1] = &clk_rpmh_clk6_a2.hw, >>>> + [RPMH_LN_BB_CLK1_A] = &clk_rpmh_clk6_a2_ao.hw, >>>> + [RPMH_LN_BB_CLK2] = &clk_rpmh_clk7_a2.hw, >>>> + [RPMH_LN_BB_CLK2_A] = &clk_rpmh_clk7_a2_ao.hw, >>>> + [RPMH_LN_BB_CLK3] = &clk_rpmh_clk8_a2.hw, >>>> + [RPMH_LN_BB_CLK3_A] = &clk_rpmh_clk8_a2_ao.hw, >>>> + [RPMH_RF_CLK1] = &clk_rpmh_clk1_a1.hw, >>>> + [RPMH_RF_CLK1_A] = &clk_rpmh_clk1_a1_ao.hw, >>>> + [RPMH_RF_CLK2] = &clk_rpmh_clk2_a1.hw, >>>> + [RPMH_RF_CLK2_A] = &clk_rpmh_clk2_a1_ao.hw, >>>> + [RPMH_RF_CLK3] = &clk_rpmh_clk3_a1.hw, >>>> + [RPMH_RF_CLK3_A] = &clk_rpmh_clk3_a1_ao.hw, >>>> + [RPMH_RF_CLK4] = &clk_rpmh_clk4_a1.hw, >>>> + [RPMH_RF_CLK4_A] = &clk_rpmh_clk4_a1_ao.hw, >>>> + [RPMH_IPA_CLK] = &clk_rpmh_ipa.hw, >>>> +}; >>>> + >>>> +static const struct clk_rpmh_desc clk_rpmh_sm8550 = { >>>> + .clks = sm8550_rpmh_clocks, >>>> + .num_clks = ARRAY_SIZE(sm8550_rpmh_clocks), >>>> +}; >>>> + >>>> static struct clk_hw *sc7280_rpmh_clocks[] = { >>>> [RPMH_CXO_CLK] = &clk_rpmh_bi_tcxo_div4.hw, >>>> [RPMH_CXO_CLK_A] = &clk_rpmh_bi_tcxo_div4_ao.hw, >>>> @@ -683,29 +750,31 @@ static int clk_rpmh_probe(struct platform_device *pdev) >>>> name = hw_clks[i]->init->name; >>>> - rpmh_clk = to_clk_rpmh(hw_clks[i]); >>>> - res_addr = cmd_db_read_addr(rpmh_clk->res_name); >>>> - if (!res_addr) { >>>> - dev_err(&pdev->dev, "missing RPMh resource address for %s\n", >>>> - rpmh_clk->res_name); >>>> - return -ENODEV; >>>> - } >>>> + if (hw_clks[i]->init->ops != &clk_fixed_factor_ops) { >>> >>> We discussed this separately, the fixed factor clocks will be moved to the >>> child nodes, leaving rpmhcc with only cmd-db based clocks. >>> >> >> Are you saying that you will represent bi_tcxo as a fixed-factor-clock >> under /clocks with RPMH_CXO_PAD_CLK as parent and a clock-div = <2>; ? > > Yes, this was the idea. The rpmhcc driver is pretty much centric around > the cmd-db clocks. Adding a fixed-factor clock results either in a > horrible hacks or in a significant code refactoring. However we already > have an existing way to fixed-factor clocks: DT nodes. Adding support > for such nodes to rpmhcc driver requires just a single additional API > call: devm_of_platform_populate(). Please no. DT is not to solve driver issues, skip some code or make things simpler for driver developers. If everyone - U-boot, *BSD, firmwares - pushes to DT stuff like this, because this makes their driver development easier, you would have total mess. Linux does not have any priorities here in this approach. Best regards, Krzysztof