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 B5802C46467 for ; Wed, 4 Jan 2023 12:45:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239264AbjADMpg (ORCPT ); Wed, 4 Jan 2023 07:45:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60026 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239196AbjADMpJ (ORCPT ); Wed, 4 Jan 2023 07:45:09 -0500 Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3463217E0F for ; Wed, 4 Jan 2023 04:45:08 -0800 (PST) Received: by mail-wm1-x32b.google.com with SMTP id b24-20020a05600c4a9800b003d21efdd61dso26319645wmp.3 for ; Wed, 04 Jan 2023 04:45:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=JoyE4PJWzp52kEQxZdg5xRzmINtYTSDR3GIdh/fen5o=; b=i2Q/j+795TYv9w0QGb5kGADj0/TDDYgZ7oc9eCOCy8Xrgx1fBkExbj4IrVJVkwUM21 8ES9qTesJVKLd49BSl+uXksWGO7vf8sI4EfhxMK67L6JQNFTqZHqwHTCWgxiEy+oavFK EeDqIPKvUKsMvoyQLGSptukGhbsdLBw/cZUVnLx2I4XaGt9RwZSdpqfmwgF3t991ES0p LVq9LKBrnxUzguC22xPQ/UT+gi43vjis4XleOV7RqPvh3jLowLV+eDI2POPaY/bIG1eF tHqFKVlTXMUYlTENM0qkltyKfY/W0kbXBdXeLdhJCffE1bB794OhfPPGSoBnCmWgTKsw Pu3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=JoyE4PJWzp52kEQxZdg5xRzmINtYTSDR3GIdh/fen5o=; b=bgrzUh0LjAPTDxijIWWbIkyCHrOuaXcGRU/Oz7n2b8emYetuT031iBkZ7d6hgHTuv8 2+CXH0vaH0+8TqESwvii9AdXLn/AipL6mlPcbzNkXg6jNrbzyzLKhUoceSIhlEsOJwoE qbqwbE//8RGycI814mxtHz6e03Qf3jriDBcHj3D6wZhRSAaLQmkkOt9Azw7bqr+uElgs NPHn+OuUH6LM3z7+CDnLDpApmcVsjL5lxCTJRRdhS+XgXfNHERb/4nxrGg6jtF1LHmfI bHW0s+kjrJN0I0nCnQ/I0m28wNw6hNPQpeZBl56PRT4cPb0/P0+KnX4xDVxCc8+uU5rd yH+w== X-Gm-Message-State: AFqh2kokyPYgUx0H1/DVRh0xikYMQZ8A6damQB+4vnj0ju2+aQvlHKey Ake93cg05NKSyIr19obI0AH4Og== X-Google-Smtp-Source: AMrXdXuOHq0R3jJqhQZ89qbuXqn8jDJ+4fL/qm9ZowCLln8b45hYqyJuEujJSRfFX1H2V9Pf4KG6pg== X-Received: by 2002:a05:600c:4a9b:b0:3d1:dc6f:b1a4 with SMTP id b27-20020a05600c4a9b00b003d1dc6fb1a4mr41485468wmp.5.1672836306720; Wed, 04 Jan 2023 04:45:06 -0800 (PST) Received: from linaro.org ([94.52.112.99]) by smtp.gmail.com with ESMTPSA id m28-20020a05600c3b1c00b003d1e3b1624dsm54726447wms.2.2023.01.04.04.45.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Jan 2023 04:45:06 -0800 (PST) Date: Wed, 4 Jan 2023 14:45:04 +0200 From: Abel Vesa To: Dmitry Baryshkov Cc: Andy Gross , Bjorn Andersson , 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 Subject: Re: [PATCH v8 3/4] clk: qcom: rpmh: Add support for SM8550 rpmh clocks Message-ID: References: <20230104093450.3150578-1-abel.vesa@linaro.org> <20230104093450.3150578-4-abel.vesa@linaro.org> <07a849a9-03dc-f3af-1d3f-2369cb71451e@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <07a849a9-03dc-f3af-1d3f-2369cb71451e@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org On 23-01-04 12:46:55, Dmitry Baryshkov wrote: > On 04/01/2023 11:34, 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 | 36 ++++++++++++++++++++++++++++++++++++ > > 1 file changed, 36 insertions(+) > > I think the plan was to have the _PAD clock as a child node of the rpmcc. Is > it still the planned implementation? Yes. Here is how the dts rpmhcc node will look like: rpmhcc: clock-controller { compatible = "qcom,sm8550-rpmh-clk"; #clock-cells = <1>; clock-names = "xo"; clocks = <&xo_board>; bi_tcxo_div2: bi-tcxo-div2-clk { #clock-cells = <0>; compatible = "fixed-factor-clock"; clocks = <&rpmhcc RPMH_CXO_CLK>; clock-mult = <1>; clock-div = <2>; }; bi_tcxo_ao_div2: bi-tcxo-div2-ao-clk { #clock-cells = <0>; compatible = "fixed-factor-clock"; clocks = <&rpmhcc RPMH_CXO_CLK_A>; clock-mult = <1>; clock-div = <2>; }; }; The clock nodes will be probed on of_clk_init. > > -- > With best wishes > Dmitry >