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 8DAC2E748F2 for ; Sat, 30 Sep 2023 23:02:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234030AbjI3Wxh (ORCPT ); Sat, 30 Sep 2023 18:53:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34552 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233924AbjI3Wxg (ORCPT ); Sat, 30 Sep 2023 18:53:36 -0400 Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 22E9AE1 for ; Sat, 30 Sep 2023 15:53:33 -0700 (PDT) Received: by mail-wr1-x433.google.com with SMTP id ffacd0b85a97d-32320381a07so10955290f8f.0 for ; Sat, 30 Sep 2023 15:53:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1696114411; x=1696719211; darn=vger.kernel.org; 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=mlBxctbB9FTcE/uWPk2Y2YEJ+iBtqk0tDnwZVGzZTPg=; b=CQlWxRzhpYeC5cfeXXFAVRNh1F/zkPTKC+ALBbflUCMAuXG/2x7l5U0qVBSois5o3/ UJyCjsnxUJHUBvtbjObtIy9Lm/yFpyCT/eHwvdcQOaWzcUvDH47ExZ7KNzof7j3binOs fTTk4eVcmMHhHcrYkQ+QKqOIVc1na/6iYYpX8/MyoYNowxsRZYdY2s9sIA6k2TSpGL6n sZwtgNY/g18hoCCaSRpKchVVPlcIhckJqRCx2tOKw4zAJY8X6LFBTN2vmfWa8O+udA/T dp6R170AWO2oLYNXbFspOUgSPJYjPaV1VeqN+yO79hYDY0Va2eBUqUQ8BqsDV7P+UMsM IgLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696114411; x=1696719211; 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=mlBxctbB9FTcE/uWPk2Y2YEJ+iBtqk0tDnwZVGzZTPg=; b=uF0cV4gbu99cF81jr6Hrn6jAoXcpn9Z8SJRkU6bjnNsUC9sEa2mV02bo6IUeF5uXJc 2DppyoOX/N7aoj6lGzdGq7QdMzFkkPjt4S1NTXMDwDjWaLziAPecnAB6OTMmmV0Z0yJd o434v/f57NsSKU7ZxB4hRyJ1RoBvqimQUdepU1kNJfLYzAtPTzlTLMQXBTXfb3daBYTN u84Ui8JwSVh8FJ4a3pCZB5UkyFFFIDxkBQfad0pLL0zKDUAukaKdkO2CoemlDMzM0cRl PDVjDNVbt3z9MnI24FJgVqezIHnGj8jFUphiJ1ZkZDb6E8+n4OrzU4Fa9iBiL87tsSDF 2kbg== X-Gm-Message-State: AOJu0YyB+ECb/z3DnWXQqFBe1+Z9ys/P0/bDvecXBXiwFCyXl65SX833 wFF+uXz/jisrVRQYrJkT+KAFQVOOb+Pywfl+VPG4aw== X-Google-Smtp-Source: AGHT+IE5hOVQVvMUhlW0QZGl9DnHrDheRfvw3wBLkVUUq9oMZKmKX3MibXuhOcdGuZqMIJkAkPKzbg== X-Received: by 2002:adf:fd47:0:b0:31f:fa38:425f with SMTP id h7-20020adffd47000000b0031ffa38425fmr8260573wrs.9.1696114411331; Sat, 30 Sep 2023 15:53:31 -0700 (PDT) Received: from [192.168.0.162] (188-141-3-169.dynamic.upc.ie. [188.141.3.169]) by smtp.gmail.com with ESMTPSA id x17-20020a5d6511000000b0031fd849e797sm24550153wru.105.2023.09.30.15.53.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 30 Sep 2023 15:53:30 -0700 (PDT) Message-ID: Date: Sat, 30 Sep 2023 23:53:29 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 4/5] clk: qcom: camcc-sc8280xp: Add sc8280xp CAMCC Content-Language: en-US To: Konrad Dybcio , Bryan O'Donoghue , andersson@kernel.org, agross@kernel.org, mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, jonathan@marek.ca, quic_tdas@quicinc.com, vladimir.zapolskiy@linaro.org Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230930134114.1816590-1-bryan.odonoghue@linaro.org> <20230930134114.1816590-5-bryan.odonoghue@linaro.org> From: Bryan O'Donoghue In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 30/09/2023 17:39, Konrad Dybcio wrote: > >> +static struct clk_branch camcc_gdsc_clk = { >> +    .halt_reg = 0xc1e4, >> +    .halt_check = BRANCH_HALT, >> +    .clkr = { >> +        .enable_reg = 0xc1e4, >> +        .enable_mask = BIT(0), >> +        .hw.init = &(struct clk_init_data){ >> +            .name = "camcc_gdsc_clk", >> +            .parent_hws = (const struct clk_hw*[]){ >> +                &camcc_xo_clk_src.clkr.hw, >> +            }, >> +            .num_parents = 1, >> +            .flags = CLK_IS_CRITICAL | CLK_SET_RATE_PARENT, > "meh" > > Is this clock only necessary for the GDSC to turn on? Most of this code is autogenerated in downstream as I understand it a script is run against some definition the RTL one would hope. I think that is probably how the gdsc clocks for the camcc are marked like this upstream already too. grep CRITICAL drivers/clk/qcom/*camcc* drivers/clk/qcom/camcc-sc7280.c: .flags = CLK_IS_CRITICAL | CLK_SET_RATE_PARENT, drivers/clk/qcom/camcc-sm8250.c: .flags = CLK_IS_CRITICAL | CLK_SET_RATE_PARENT, drivers/clk/qcom/camcc-sm8450.c: .flags = CLK_IS_CRITICAL | CLK_SET_RATE_PARENT, I can tell you what clocks this clock but I can't tell you where that clock routes too, so the best/only source of information I have is the flag that comes from the autogenerated downstream code. I think the safe thing to do is to leave the flag as is TBH. --- bod