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 464F6C54EAA for ; Fri, 27 Jan 2023 13:12:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234523AbjA0NM5 (ORCPT ); Fri, 27 Jan 2023 08:12:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56116 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232489AbjA0NMv (ORCPT ); Fri, 27 Jan 2023 08:12:51 -0500 Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1557D15CA5 for ; Fri, 27 Jan 2023 05:12:19 -0800 (PST) Received: by mail-ej1-x633.google.com with SMTP id ud5so13608402ejc.4 for ; Fri, 27 Jan 2023 05:12:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fairphone.com; s=fair; h=in-reply-to:references:cc:to:from:subject:message-id:date :content-transfer-encoding:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Pu1HTphj/Rd+hvsmfPEOQ6MqsGz846VOWoOD9sOistQ=; b=W/E5rIznkAUn0gpNPXRTLyh4NVlL5sSBE3DMefgPKKEJfF0sP62XHai51Ky8UKJRup 1Jo++Y1Q0N42fbS71zOEpwOtEqWOEvD6MMGiJ+iSsoPzGDDKjVZaENephTqcMrOP1kUV DqRUr2ZjY2EUpzh1DYsi/pruy7lsyBCvEIK1ooaOtVj3qqxvzCiKUtc6JD9vf6ZE/x2x sPU8+qKbIug0hwUnydlz0bpv9dHu/kFyoQPYcVfoHqAN2sIOl0hYQUP1jdxD+It6lNOQ mcUvvhPP4zOHAkmN7tqCV3TAb78hvVzJ92I9EuwDrEK6C9/LZFpN4HeF5dFkHq1dG82r fYGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:references:cc:to:from:subject:message-id:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=Pu1HTphj/Rd+hvsmfPEOQ6MqsGz846VOWoOD9sOistQ=; b=N7fovtUz+Fcu4NQve/X42HIW2WoacYKiCu5QwyppR6Zo7wPS+qUmejH3mW9gxPMSuo PQ31Q6X++y9ESbB3d9J5PeC2YAiVbGkgelgk43E6hqrXwqeW8hJVvntvxaQ6+booP2Ha 8VcWNWvr8JOdy6nOncQHsK8qbu/8zIvRsuXlIP0Meee3qmUGdPOymCjpXruSGsjrDM17 zaIGWoXoutLDC4eFADLPFof1PD1RF1USSNSNo33AkH7eulxcODFkydsfrqmrFL2C7p1e FVuezcZaGYmtmR98BuLgZSjm33dBeJK0v6LxmDxDlmJWUtIdKtd81KDTYwvA6bjOvRrn CHbg== X-Gm-Message-State: AFqh2kpPq3MDTDNuPh8CGFKzOsy1jf/Ys2y3d7D+x2gg25Xv8O/fiWFw ukabqjk31BcUVfhPs9GFwLYFuw== X-Google-Smtp-Source: AMrXdXtSn4UtqYZrwl5P+2ddPBf9wah+lahWSRiqA6L8PTwwWCdsQoRkV9HoNaXhwa8nKtrN4I01bw== X-Received: by 2002:a17:906:b806:b0:84d:430a:5e63 with SMTP id dv6-20020a170906b80600b0084d430a5e63mr39507156ejb.27.1674825091449; Fri, 27 Jan 2023 05:11:31 -0800 (PST) Received: from localhost (144-178-202-138.static.ef-service.nl. [144.178.202.138]) by smtp.gmail.com with ESMTPSA id n5-20020a1709061d0500b0084d420503a3sm2234999ejh.178.2023.01.27.05.11.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 27 Jan 2023 05:11:30 -0800 (PST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 27 Jan 2023 14:11:30 +0100 Message-Id: Subject: Re: [PATCH v2 2/4] arm64: dts: qcom: sm6350: Add camera clock controller From: "Luca Weiss" To: "Bryan O'Donoghue" , "Andy Gross" , "Bjorn Andersson" , "Konrad Dybcio" , "Loic Poulain" , "Robert Foss" , "Rob Herring" , "Krzysztof Kozlowski" Cc: <~postmarketos/upstreaming@lists.sr.ht>, , , , , X-Mailer: aerc 0.14.0 References: <20221213-sm6350-cci-v2-0-15c2c14c34bb@fairphone.com> <20221213-sm6350-cci-v2-2-15c2c14c34bb@fairphone.com> <3ae863df-3260-4863-d88f-da4d3f442174@linaro.org> <2989138a-8f4b-50a0-3e90-98b6785f2690@linaro.org> In-Reply-To: <2989138a-8f4b-50a0-3e90-98b6785f2690@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri Jan 27, 2023 at 1:49 PM CET, Bryan O'Donoghue wrote: > On 27/01/2023 12:45, Luca Weiss wrote: > > Can I reference <&camcc TITAN_TOP_GDSC> from itself? I know that having > > it on is required to turn on at least some clocks (maybe all clocks). > > But from what I understand how power domains are normally handled, the > > driver core enables them before the driver is probed, so self > > referencing wouldn't work. > >=20 > > And at least no other SoC upstream references TITAN_TOP_GDSC in camcc. > >=20 > > Regards > > Luca > > Doh I meant to say a power-domain to an mmcx a la > > power-domains =3D <&rpmhpd SM8250_MMCX>; > required-opps =3D <&rpmhpd_opp_low_svs>; > > TITAN_TOP should be in your cci and camss dt nodes. Okay, that makes more sense. What I don't quite understand is why sm8250 only has MMCX listed there since downstream has both vdd_mx-supply =3D <&VDD_MX_LEVEL> and vdd_mm-supply =3D <&VDD_MMCX_LEVEL> and both "supplies" are used for different clocks using .vdd_class But back to sm6350, downstream has vdd_mx-supply =3D <&VDD_MX_LEVEL> and vdd_cx-supply =3D <&VDD_CX_LEVEL> and like sm8250 uses cx and mx for different clocks. Not sure if I should add both, and I guess mainline also currently doesn't use higher ops for the power domain when higher clock rate is needed, from what I understand? > > --- > bod