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 B8D71C61DA4 for ; Sat, 11 Mar 2023 13:32:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229800AbjCKNcV (ORCPT ); Sat, 11 Mar 2023 08:32:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48024 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229655AbjCKNcT (ORCPT ); Sat, 11 Mar 2023 08:32:19 -0500 Received: from mail-yw1-x1133.google.com (mail-yw1-x1133.google.com [IPv6:2607:f8b0:4864:20::1133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 814CB110519 for ; Sat, 11 Mar 2023 05:32:17 -0800 (PST) Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-536bf92b55cso153078057b3.12 for ; Sat, 11 Mar 2023 05:32:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678541536; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JROGcEBcLkwWjsFbL29UK7bVFuHFrwh+heAFvT0sBUc=; b=y8M8LIyCYjgptBoJ7w1GsZrnQB8ex02EXdkVW0q4iX+ZYIo5qaJgM52z+EAzOhdpI7 U0m/s6UG1WEXitNCHizAT7u7UEn36f7JBvvLcHcHz6KTdEEVlsiLf6GU4D4hqzEhT7N7 fp3D/A4LrGRotn/4HUEpB748FEN6Eh3dladYyZApbrnfhsXN42YHny3lW4+AnRzCjTK8 BfGSayUI0ZxsddGbVjymkThUwsRHF5qoCuNs6KoLHbvx779xEkimrvhl7OQASqaU9dxz UUKtrkPwgcLQzVbHsSEgmJgjYh11m8hG885pM1zAGPyoMhewZUsWalV+oBZiOGEFNHzF 5WWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678541536; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JROGcEBcLkwWjsFbL29UK7bVFuHFrwh+heAFvT0sBUc=; b=5cXA8dxPzfumly4RPlU4K7vLqf9Bc4VizEi5sazbSbrATrSTSqA74tvjoivNwhMDzX jGSpQlUrngsAuf6Y2qD3REfR63XOAE/3ye2bxponoreDH9RQu/oZsnqluib8RoIWRm04 5LtIfn8ult/gmVTbLKMhfxLMMt2qcerVHiZ0imt59CH32opPPMmW3NUrVZxk6na4w66o 2QQ7ljGKgcXlCkzemrMQnf7aQBr5PfQ7B1NDr7XpiYP9wTNIHl/QFPNgchS3NPuqWfce bR0f9Yo7ndp/OBqbUwX8zSqZRh+6JbuteNpXxf7Qhxl6Mmwf6Bb9iNDW5epDGD/LRETS QD6A== X-Gm-Message-State: AO0yUKXeeWBheBP2QeU39qmoSkMzrfA5qxoH3F7ceO7tY3AkvYjN1jlZ e3ZhuGf2WCWJXQnhsrGKXYqoxEzVmfEFXzO0074SUQ== X-Google-Smtp-Source: AK7set/7HiHYL5eW78ZBNSZ38mIUB1aBNYtIXyUpaYdA5rIb/ax8pB0saCrGLSs60FsOsiJMqZI7dRGrbLExw+I5shQ= X-Received: by 2002:a81:ae66:0:b0:541:7266:3fd7 with SMTP id g38-20020a81ae66000000b0054172663fd7mr656589ywk.3.1678541536631; Sat, 11 Mar 2023 05:32:16 -0800 (PST) MIME-Version: 1.0 References: <20230228-topic-qos-v7-0-815606092fff@linaro.org> <20230228-topic-qos-v7-6-815606092fff@linaro.org> <50f03895-816f-be8d-d956-d237fb13f5a0@linaro.org> <6d10906e-08cd-0380-5f5d-3ac0eec60276@linaro.org> <67590cd3-5543-59ed-6158-b272103ebd05@linaro.org> <858a8925-f11b-652d-3f02-f5ceea7d11fa@linaro.org> <74c0c724-b6a9-3755-7f56-9f421cece1a3@linaro.org> <500c7924-c43c-4233-1688-f8b6fbbad66f@linaro.org> <544e6f22-f2f4-2c7c-1978-a96c9763e2ab@linaro.org> In-Reply-To: <544e6f22-f2f4-2c7c-1978-a96c9763e2ab@linaro.org> From: Dmitry Baryshkov Date: Sat, 11 Mar 2023 15:32:05 +0200 Message-ID: Subject: Re: [PATCH v7 6/9] interconnect: qcom: rpm: Handle interface clocks To: "Bryan O'Donoghue" 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 11 Mar 2023 at 14:11, Bryan O'Donoghue wrote: > > On 11/03/2023 00:54, Konrad Dybcio wrote: > >> - Update the commit log and potentially the structure comments > > I'm probably just very biased because I authored these commits, but I can't > > see which part is not clear.. Could I (and this is not passive-aggressive or > > anything) ask for a pointer there? > > > > I mean to say "non scaling clocks" isn't an indicator IMO of the fact > that these are QoS node specific clocks. > > Right now the interconnect model is predicated on bus and bus_a but, > you've found that on some SoCs we have node-specific clocks too. > > :g/non\ scaling/s//non-scaling\ node-specific/g > > would do or "QoS node-specific" the fact the clocks don't scale is > incidental the dependency though is that IMO at least these are > additional node-specific clocks we need to enable. This looks somewhat close to what we have observed in the patches for ipq9574 platform. It doesn't have a scaling interconnect (in other words, no bus clocks), but some devices have clocks driving the NIU (Network Interface Units) which connect the device to NoC. > > --- > bod -- With best wishes Dmitry