Received: by 2002:a05:6358:c692:b0:131:369:b2a3 with SMTP id fe18csp4004974rwb; Sun, 30 Jul 2023 22:37:42 -0700 (PDT) X-Google-Smtp-Source: APBJJlHEVLM1SfAwuXYT3B2kLhe9oCzSaA68WoQjm7vqStfgzWvyUF/uUTpOrngRDWkNNTH77HdV X-Received: by 2002:a17:902:ee91:b0:1bb:3979:d467 with SMTP id a17-20020a170902ee9100b001bb3979d467mr8294511pld.63.1690781862528; Sun, 30 Jul 2023 22:37:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690781862; cv=none; d=google.com; s=arc-20160816; b=WChXpIX+YobMnHFDKOIAQ1nmH63/zsaaRTdpinkOpwvbhT8jrvceGZsICeNjHyg4kX qfNs3BHiOETYyx6YLDtfLG49+W/yskiStlDKMwTIP6UOHBG1N+LlOhckaNpb4nko9N+k XYlEKG+VJ9kMsmCy1n21aY/gZJGv8msAYjrpfu/wsNboB5gpRu2A/zomOQa+QWnVgAKD WPHEqqYlldBLdAOTlZ9vXOODWim12vfNlhKGSLtNzBI8LzXiWWk3j1k+WxsAccR4GNfJ oCAbVaGCeUtbvzM33J39TH26eQvU97d2VrHctO0ZxIzM0vlihOAOKV+iIa12OJMNHfjy GoFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=5A36sJfoTWTZxxRtlkUpT4+tRtDcKRqPwRCEoULd4eU=; fh=LwiSCrYaTDmfUb+3QeqHt5xk0+ngdz5YNZgqvCYefls=; b=g8NDhWwFhpy/dBAvlQi61a0SS1mxDgNYmRLa8zwWSCMZvR8rzs03CIYHwG50qWGO1C bnvdDhY6xTuonIA8ijiFGygmLytX8cKUUZzRfA78inguoUF8GM9Tg9DaMEB1XpujcsxH c5ZT3/bWiw+/w+YiGwgeZ4nSjyAH7+lB2z+Ao3ChGgJdtr7Yt0fFs+I7zDjbODaKfHKa TC3DurxwCn4gLHpWXWpXtrseQ6FXyDM3GeU/zph4fWJoX9q5Spv6IIL3KCmA9ryATEac O7HKKvgK8aRt4PhvF4uMD6J3AScrwhvw5UqYhS1/l3G9qsrJ417crRxwOmcfmzovpbki FQGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=b5DQ6Rly; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id kl5-20020a170903074500b001b895a2c09esi6496989plb.381.2023.07.30.22.37.30; Sun, 30 Jul 2023 22:37:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=b5DQ6Rly; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229712AbjGaE22 (ORCPT + 99 others); Mon, 31 Jul 2023 00:28:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40304 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229464AbjGaE20 (ORCPT ); Mon, 31 Jul 2023 00:28:26 -0400 Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 52C64E6D for ; Sun, 30 Jul 2023 21:28:25 -0700 (PDT) Received: by mail-pl1-x62e.google.com with SMTP id d9443c01a7336-1bbc87ded50so24703585ad.1 for ; Sun, 30 Jul 2023 21:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1690777704; x=1691382504; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=5A36sJfoTWTZxxRtlkUpT4+tRtDcKRqPwRCEoULd4eU=; b=b5DQ6Rlyi7Lq9BXtLOOwalkREoNbb87b7unENttOCjxE8BVeLJiZVLColztFw+ksZi T5RO9eNtw8w4tbxo8yjiH8JdzdVbiLrXtczhvTfIZrpykQ7oQia1ZRmOGhd2hBXjrtZT V8fl0WKyk3tkCepVejzvfjyVLsuOV988AmZX4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690777704; x=1691382504; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5A36sJfoTWTZxxRtlkUpT4+tRtDcKRqPwRCEoULd4eU=; b=Fa3pkgkyEml/pABE4e0PAR+9PWiu4IelTkZkTN3vgTKldSP9/RcdPT2iHCCL1+bCH6 bQH+3p5UF4UBLSaoK3BzZUVN1id5a7JVcLbSMt6gu7sCuJMSAjeck6tnT5rdGVGt6TrC BmlBVc46eRkLWzXkrSMgCITnzVhbrl1DaKwkJCyrN2+gLaVEapZmkbk8yNxRJ/6qQTFW Fr2Sx6UTxGmj4DyNVrQXpoNkNLKW9+B6K3a//TpiCbJVa45uNYXQFXyyCANSS1M8897g bMSCyjsdlPN6B6qYfNtzrW+4+hB77rQZdWsLUiJ+Tm4aWVQe+SwJxIEMp+GPT6ElXIb0 9x3w== X-Gm-Message-State: ABy/qLZ8I/CGHo5O8afZxI53N9rtQJ+2unfgrvr/wqD9aZk4Es1IwVpj npHkLjCIr+4RNMqtiVfG13M78Q== X-Received: by 2002:a17:902:d4c3:b0:1b8:b3f0:3d57 with SMTP id o3-20020a170902d4c300b001b8b3f03d57mr9821918plg.31.1690777704531; Sun, 30 Jul 2023 21:28:24 -0700 (PDT) Received: from wenstp920.tpe.corp.google.com ([2401:fa00:1:10:fd7a:6af2:fca:ff71]) by smtp.gmail.com with ESMTPSA id t15-20020a170902b20f00b001b9df8f14d7sm7349096plr.267.2023.07.30.21.28.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 30 Jul 2023 21:28:24 -0700 (PDT) From: Chen-Yu Tsai To: Neil Armstrong , Jerome Brunet , Kevin Hilman , Martin Blumenstingl , Stephen Boyd Cc: Chen-Yu Tsai , linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH] clk: meson: meson8b: Simplify notifier clock lookup Date: Mon, 31 Jul 2023 12:27:53 +0800 Message-ID: <20230731042807.1322972-1-wenst@chromium.org> X-Mailer: git-send-email 2.41.0.487.g6d72f3e995-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The driver registers a clock notifier by first getting the name of one of its clocks it just registered, then uses the name to look up the clock. The lookup is not needed, since each clock provider already has a clock attached to it. Use that instead to get rid of a __clk_lookup() call. Signed-off-by: Chen-Yu Tsai --- Found this could be simplified while looking through some clk core code. drivers/clk/meson/meson8b.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/clk/meson/meson8b.c b/drivers/clk/meson/meson8b.c index 827e78fb16a8..c4336ac012bf 100644 --- a/drivers/clk/meson/meson8b.c +++ b/drivers/clk/meson/meson8b.c @@ -3793,7 +3793,6 @@ static void __init meson8b_clkc_init_common(struct device_node *np, { struct meson8b_clk_reset *rstc; struct device_node *parent_np; - const char *notifier_clk_name; struct clk *notifier_clk; struct regmap *map; int i, ret; @@ -3847,9 +3846,7 @@ static void __init meson8b_clkc_init_common(struct device_node *np, * tricky programming sequence will be handled by the forthcoming * coordinated clock rates mechanism once that feature is released. */ - notifier_clk_name = clk_hw_get_name(&meson8b_cpu_scale_out_sel.hw); - notifier_clk = __clk_lookup(notifier_clk_name); - ret = clk_notifier_register(notifier_clk, &meson8b_cpu_nb_data.nb); + ret = clk_notifier_register(meson8b_cpu_scale_out_sel.hw.clk, &meson8b_cpu_nb_data.nb); if (ret) { pr_err("%s: failed to register the CPU clock notifier\n", __func__); -- 2.41.0.487.g6d72f3e995-goog