Received: by 2002:a05:7412:f690:b0:e2:908c:2ebd with SMTP id ej16csp837079rdb; Fri, 20 Oct 2023 00:08:07 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHjF3QeXBHobX2o6rW1/Yv31a+0ClmtAYUKB2qTwgj6Ov5EN8hsBvOLugptELfMXcINuFVs X-Received: by 2002:a05:6a20:8f05:b0:161:aef5:6395 with SMTP id b5-20020a056a208f0500b00161aef56395mr1442548pzk.24.1697785687536; Fri, 20 Oct 2023 00:08:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1697785687; cv=none; d=google.com; s=arc-20160816; b=q33Vi7p8TpMQ5YWEFUet6NDXO0hX0LW/lQrbZCR3ALyOd9OvnmCiuozebjdGqpJSOd e3x+L+foER4sMXwUrtOt8a6xEdSkoVPY5woJQ+M9N3rGFk/GSvwQz4cR30Ys+KQoQY5i PVR/uyoiVZ2068dIpqw+pYJ2uHyG1smOQXt3dxvqlf4F8mowHrI6ASzJs4yuHu8Oz2Bc Aw3dtiWrIDzAeC2l4V9SnCow5r8XWOY1T/UsB1Kp4rTBT2s6E46PObRczv8j7Vz6xUx/ N50KBtMVkI3kSw2yJmwqIn4r8wiUA0ukgixq+1KcgHbBtmBi7ptjsLj92b27WTcITWGf k8SQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:sender :mime-version:dkim-signature; bh=GZ9uOsmItqlP8ZLKPIbsiuZsF/kvOeSSxkPvDynDyWE=; fh=T55PPni+AGBVbP74RJe+/lP2tU55tWVp/CBluRR+WdU=; b=PMJQfAl4y6LJvi7M2NWn9wHUxM8hWiAqgQz23L9E2WbQITzWOmLSdUei+zfEq9+pqk 8FC+V3McaaoswXwvHsBuUIP6vXZOf2d7qx0WeJscHRrMTBUvacMiijAPxIFQ+qMATEgl x5faTYrvqy/V2MMf8zzkXPH6sciQlGJSZ6X540pA1jyG2QQQPz+8uxTD2b4X6ffu/WJC aOcgfajqUp16WvphxOE/PIoaDxrfOoCXe9/yISELFQ7snf3ZXNzaKAr+Fwu8+/UiKh9P Jc6z39uxdVuE1JhdtfBE6T/JcmbtHzGK1oGkBjPDY72YQjGLJii1Yea3kH6Qz5Jfvpo7 FDmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=V4JhPmkw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from agentk.vger.email (agentk.vger.email. [2620:137:e000::3:2]) by mx.google.com with ESMTPS id v185-20020a6389c2000000b00573f9a427d6si1267378pgd.450.2023.10.20.00.08.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 20 Oct 2023 00:08:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=V4JhPmkw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by agentk.vger.email (Postfix) with ESMTP id 6656781EA73B; Fri, 20 Oct 2023 00:08:05 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at agentk.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1376359AbjJTHIA (ORCPT + 99 others); Fri, 20 Oct 2023 03:08:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1376326AbjJTHH7 (ORCPT ); Fri, 20 Oct 2023 03:07:59 -0400 Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F2CCE98 for ; Fri, 20 Oct 2023 00:07:57 -0700 (PDT) Received: by mail-oi1-x231.google.com with SMTP id 5614622812f47-3afc38cbdbcso289767b6e.1 for ; Fri, 20 Oct 2023 00:07:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697785677; x=1698390477; darn=vger.kernel.org; h=cc:to:subject:message-id:date:from:sender:mime-version:from:to:cc :subject:date:message-id:reply-to; bh=GZ9uOsmItqlP8ZLKPIbsiuZsF/kvOeSSxkPvDynDyWE=; b=V4JhPmkwbGfM0/zzosWIBkPALNWDIGjvEQc5rGvY5U7oMsb9YmP3WSYJ+1FNHQVU0G tgZ5fV0ZBa0YaLUmvfr0EtMokKBqV8IraYhyyMzhpoBLF66oGBPSTINfIr0t4EDrCalV QHXYCFrcFbWC1UeEq9qAEOCx1j9iKCZ9vR3MHRh+FW+PnZhigbCExy3FmPxxcGTqiyzs zjL3CH4rzOmNilfv1ogGcX82lQd6gtyPuYWbVH8OnmD2VN0ZAGmXzMvYrMDYjq5GXvDQ qqdc7gO6MKl1GT8Z0RMlVMyYNP83CkVUuz1XCZkDcfusYdsA9oguDVnB34Jx1nkvqXol v4Vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697785677; x=1698390477; h=cc:to:subject:message-id:date:from:sender:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=GZ9uOsmItqlP8ZLKPIbsiuZsF/kvOeSSxkPvDynDyWE=; b=mjN/eo1w3Ytpbf6ZjR4Ftvp8dEODaNuGVESszpbWLHT0bnt5iMZ5+L12TKicVUFJyN ZH4MRSCbOlBLwsEG0jGgshaWMqBgZMsSr1cQJBbdea1pOZl7i0YS+vXcQ3takbjcG5Ty yhP6tje5CLi/fwtgv4dYR6wG2ZTWcV/W1ZFlbRuqzHcdXV3raxTErB2gnda2EvqN05ra BggPpiiygFFEl/cieKO3TaW91NjM5Dg94Dc7lMRyppFVAVoKm3vSrgfYEixeHjTy2i2h mEOpbQahy6oHMl+MsXFxV69dWX4McR4jeyLhzvvV82ARh4OWx5K+DQI9kUx1/vRmvgm2 JYVA== X-Gm-Message-State: AOJu0YxgUKiqVCOTXy9s15mnoW3Or40OJRfYNFu3NvdwtSaZOWCJ8BRd e7VhN63y8LoQGdBaDNae6aj5Tj9YvwktZFJ9cWLfh2mY X-Received: by 2002:a05:6808:158e:b0:3b2:e557:2f1b with SMTP id t14-20020a056808158e00b003b2e5572f1bmr2194112oiw.14.1697785676980; Fri, 20 Oct 2023 00:07:56 -0700 (PDT) MIME-Version: 1.0 Sender: getarunks@gmail.com X-Google-Sender-Delegation: getarunks@gmail.com From: Arun KS Date: Fri, 20 Oct 2023 12:37:45 +0530 X-Google-Sender-Auth: suC3uqbKUJXbCe1qRnbBECSXlu0 Message-ID: Subject: Question on pre running clocks To: linux-kernel@vger.kernel.org Cc: sboyd@kernel.org, mturquette@baylibre.com, Arun KS Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on agentk.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (agentk.vger.email [0.0.0.0]); Fri, 20 Oct 2023 00:08:05 -0700 (PDT) Hello, Lets say there is a clock which is enabled by bootloaders and is pre running as linux boots. Is it mandatory for the client drivers to call clk_prepare_enable() on them to initialise the enable_count to 1? Or is there a way we can specify to the kernel that this clock is already enabled by bootloader and initialise the enable_count for this clock to 1. Because otherwise, clk_disable() prints a WARN() if a client driver uses clock handle where clk_prepare_enable() is not called. I grep through the code, but could find any details. Appreciate any pointers. Regards, Arun