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 4F01FC64ED6 for ; Thu, 16 Feb 2023 08:56:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229957AbjBPI4V (ORCPT ); Thu, 16 Feb 2023 03:56:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42814 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229828AbjBPI4N (ORCPT ); Thu, 16 Feb 2023 03:56:13 -0500 Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0916B4A1CF for ; Thu, 16 Feb 2023 00:56:07 -0800 (PST) Received: by mail-vs1-xe2f.google.com with SMTP id d66so1194190vsd.9 for ; Thu, 16 Feb 2023 00:56:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=SHowq6DBf2cQJTeoPMKiGvKAjNuUb3fl52JbQ7+XiTQ=; b=fhvc6hUjWFRQPnJCbs+gDum3iHeWp5QtJVemXtboy3T9nV+apTLF+hpD6+8Q3K2E6i yL5qd4ZnxGbaHgUyFVVUCZi9pKI4I5Q6t3tqURU6rWctfCtScC5nsVIAd1XrmNBgbxaq jXSSbyO+OpNzI61O85gfJbT1Feed2X+YxFxpI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=SHowq6DBf2cQJTeoPMKiGvKAjNuUb3fl52JbQ7+XiTQ=; b=B9sP7GKfELctwGL/I8r/6xS52jMRUC9upWTcRaHNFZhVtJx09VcF+fVL4VlF4acySx XfpRXoXP7l+NTFhDKwRSbwHb4ur1miy2fjfH2mYZbOApMCkTvHJlr4+/OsQ8jFTZk+fm ZxMSNKnfqMsAzm8mS7+dNJtB0pyUeKLOtL9uL1ddotWqrKFfTERv1y481ohsulQ8f4T1 /9nphf3UvuroF9Hat9W8ylU/jcroHMbe2mWdtmDolQ0+BO3WB/DLz0DlhEuS9EZkKzl+ PMkXVXMe2fTIZouVwzoD0ykNgUuIXKZ2+9FkRUYy4XmVFrnMi148am5KYFCFHkJKHrBB Qghg== X-Gm-Message-State: AO0yUKXwdUSg+YRsHrgS/4OEjiA84Qrgh6xVXtKa10QmGnFQ0jglIiJ3 1GskYe0xMPywFAT5snBv6jdkQYoFkJvIJAqkpKqMgA== X-Google-Smtp-Source: AK7set+vp6162xHF8teoDckEkkowi9+9lSlBTLWUQzkpE/prNx60QCTqa0FZ8/nPJQXtuohzL5bzLLspqVQH4Bpkn+g= X-Received: by 2002:a67:f749:0:b0:3fc:58d:f90f with SMTP id w9-20020a67f749000000b003fc058df90fmr965643vso.60.1676537766972; Thu, 16 Feb 2023 00:56:06 -0800 (PST) MIME-Version: 1.0 References: <20230214134127.59273-1-angelogioacchino.delregno@collabora.com> <20230214134127.59273-21-angelogioacchino.delregno@collabora.com> In-Reply-To: <20230214134127.59273-21-angelogioacchino.delregno@collabora.com> From: Chen-Yu Tsai Date: Thu, 16 Feb 2023 16:55:55 +0800 Message-ID: Subject: Re: [PATCH v2 20/47] clk: mediatek: mt8183: Convert all remaining clocks to common probe To: AngeloGioacchino Del Regno Cc: mturquette@baylibre.com, sboyd@kernel.org, matthias.bgg@gmail.com, johnson.wang@mediatek.com, miles.chen@mediatek.com, chun-jie.chen@mediatek.com, daniel@makrotopia.org, fparent@baylibre.com, msp@baylibre.com, nfraprado@collabora.com, rex-bc.chen@mediatek.com, zhaojh329@gmail.com, sam.shih@mediatek.com, edward-jw.yang@mediatek.com, yangyingliang@huawei.com, granquet@baylibre.com, pablo.sun@mediatek.com, sean.wang@mediatek.com, chen.zhong@mediatek.com, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, kernel@collabora.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 14, 2023 at 9:42 PM AngeloGioacchino Del Regno wrote: > > Switch to mtk_clk_simple_{probe,remove}() for infracfg and topckgen > clocks on MT8183 to allow full module build for clock drivers. > > Differently from other MediaTek clock drivers, it was necessary to > change the name of the `clk13m` clock, as that is already declared > in the SoC's devicetree as a "fixed-factor-clock" (with the same > name) and redeclaring it here would obviously fail to register the > entire clock controller; this clock wasn't dropped only to retain > compatibility with older devicetrees > > As a note, the `clk13m` clock is not mentioned in any parent names > array(s) as the correct one (csw_f26m_d2) is already used in place > of that. > > Signed-off-by: AngeloGioacchino Del Regno Reviewed-by: Chen-Yu Tsai