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 AAFFEC6FD1C for ; Sat, 11 Mar 2023 14:38:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229601AbjCKOil (ORCPT ); Sat, 11 Mar 2023 09:38:41 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44662 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229810AbjCKOik (ORCPT ); Sat, 11 Mar 2023 09:38:40 -0500 Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 59A0B3772E for ; Sat, 11 Mar 2023 06:38:38 -0800 (PST) Received: by mail-wm1-x32e.google.com with SMTP id t25-20020a1c7719000000b003eb052cc5ccso8018937wmi.4 for ; Sat, 11 Mar 2023 06:38:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678545517; 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=O5MrZLG1fv/oDrj8G7OK4hTcqs75NSjsiUDq6tTXX/A=; b=tUJzepR1Ix0D0nJdvEWnL7/JVUQ9EThGCh03jr/kqxe1Ll9krTqBph8rLKDyX62Eis lPsOajtXFKhnoXm5fVdCMk5fZMXK4z9dlK1x9IutvGaL39aoLGDYLa+KJmvV9PsRt45Z zZfkUJejh0MXEuiBktz8VJdVgj1x3+YnfNyYSwCx11dyYGBLfrHP86BHP4yvCm0DSjUi e7jl8C5JbLRRLi9tS3Lxz5v9XkB+W+zWqESoUWAxwYywI8/xtKmzCkX4CDRgp6cLgpvw 9I2mthEpjT31jmDuHYZE9C7zwUUDLgZtbUXcgpDBhZs3JaUKp8L6kSo86quDTTHPOQ96 G3Cg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678545517; 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=O5MrZLG1fv/oDrj8G7OK4hTcqs75NSjsiUDq6tTXX/A=; b=4TLgelgeOctqb3nNzfxK+JHTv/UnwCCrNpPtSIFaCs04mZT4tWYvq+f2pc9bGLHCeS L42XQ9vWYJ2CkwCJ7nM/K8TpseU6wQ5j1T3HR/joOwt6xU9uN1zrH0CGKJoQYvGm+L89 juVYD0AAEigzBYsSMo+Sg3XPbOojY96eL2BTj5C6qErnAzMXOMnzrlMbVbdY1tk2Sqon qQgGE9We0keMgEs7iCw8p74i3KPPpTfiIQd0oxq9MtRsbZDPSD18ySH2N20x7JrRUq3S 9+2esW4R0eN59yMF2jM4i8IA/S34wB2h5EtrII7xesWNTkdi4YzUI48Tw5xmwegmmhZx wKGg== X-Gm-Message-State: AO0yUKVWoDxwh70SSLHAW6eIQjFPGZNP6o6c9XNuglFHXqj2CieBgJPh 7s80t7DbZU3JvSH+L/URpGjGXLAzFKm5I9G30Ao= X-Google-Smtp-Source: AK7set9D4WKtNwp5ftzZpljbf20TczUiOpHEKRh1CVjgoWBSvgoimsGH+LIlBWUDyb4cm8cXyTzddA== X-Received: by 2002:a05:600c:1d29:b0:3eb:6878:5523 with SMTP id l41-20020a05600c1d2900b003eb68785523mr6113109wms.12.1678545516843; Sat, 11 Mar 2023 06:38:36 -0800 (PST) Received: from [192.168.0.162] (188-141-3-169.dynamic.upc.ie. [188.141.3.169]) by smtp.gmail.com with ESMTPSA id 14-20020a05600c228e00b003ebff290a40sm3052198wmf.21.2023.03.11.06.38.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 11 Mar 2023 06:38:36 -0800 (PST) Message-ID: <51c41e49-5183-551e-c796-5b3d792b422f@linaro.org> Date: Sat, 11 Mar 2023 14:38:35 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v7 6/9] interconnect: qcom: rpm: Handle interface clocks Content-Language: en-US To: Dmitry Baryshkov Cc: Konrad Dybcio , Andy Gross , Bjorn Andersson , Georgi Djakov , linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230228-topic-qos-v7-0-815606092fff@linaro.org> <20230228-topic-qos-v7-6-815606092fff@linaro.org> <68a5d81a-5de8-798a-c150-d74c8ad38cb7@linaro.org> From: Bryan O'Donoghue In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On 11/03/2023 14:35, Dmitry Baryshkov wrote: >> Its probably worthwhile experimenting to see if the*ufs*_clk can/should >> be added to the UFS device list of clocks. > While we were doing this for some of the clocks (PCIe and USB, if I'm > not mistaken), I think that generally this is not fully correct. In my > opinion it should be in the interconnect driver, who turns > corresponding clocks on and off. These clocks correspond to the SoC > topology, rather than the end-device. > True enough, they are interconnect clocks. The question is how to only turn them on when the device that depends on them wants them. --- bod