Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp10654564ybi; Thu, 11 Jul 2019 08:49:47 -0700 (PDT) X-Google-Smtp-Source: APXvYqyxpKTVfmEzSdMnztlJL0e7Bh/jOt9tPMylnyB3Nfdoy2aW/nJ9tR31dik3XlhUh6FkTopi X-Received: by 2002:a17:902:934a:: with SMTP id g10mr5559104plp.18.1562860187720; Thu, 11 Jul 2019 08:49:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562860187; cv=none; d=google.com; s=arc-20160816; b=TYRpG8e5Sg47ztHHx+HZ+ubNShCKBIJxrJy5Vg8YaS01zKMRwDp5/LendoEZ0R3eCt hhiZVp2ms5GnDl5iLOTMsHbFAqi4i16DNshId62A2NmEDQTs4YeQp9SSCj9vCx9c9naT wcGJUemE5Y7uhQU1vFU9l24YEyN+UIsYWWLBiUTpfmujk9irX8u4/UQvJMHgdPUCdgGg anxzxaoj8Dr/N/HQNb0ht6s/HI5s/MZ6ckTm87OCvtfrdTQyHnTuEbvmNeIu0zEGG2VK FuTYwBUNMbu++J2En0wiX/2bG/OXYVgol6+HGGq4C4f/GmyREllf0mKJqMrsZdgnF0wm sb6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=NKwh0BaKc7HdLVY/44p+/9uGqJilXs/pFH756+9dwa4=; b=iKiouOdST6/SIPZxyC3whlLhZCJydc7kTX5jNOfjw2U6JzpWkqgHLjr1VFjyHDr9XK AiODmRjF8niGjVBvZdDH0zI/rn7RqIjEcjQqkX467vDzDycHaze31J63mxMv2DGn3Jcy IYZGtfVhCF1NNhKZcL8QFq0A21skC3PmANOBKEa5bLe288yFQATTnv0stePm7TgvH9uW G8R3zG3iP4sI3b6cvP0568F7ueXrr96DCAz2nolCJ0XwfK6+qwu/qH/yvNYG5kPD+IlK R/twh7hoUOQBXWQ5bOk5Bsa867nVFkl6iT/ecKGObAL/SVnhyBuh+6ho/VQ15Se1UYF5 fgSQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=pWNqSiF0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i17si5537239pgh.372.2019.07.11.08.49.32; Thu, 11 Jul 2019 08:49:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=pWNqSiF0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728864AbfGKPaH (ORCPT + 99 others); Thu, 11 Jul 2019 11:30:07 -0400 Received: from mail-vs1-f68.google.com ([209.85.217.68]:42908 "EHLO mail-vs1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728594AbfGKPaG (ORCPT ); Thu, 11 Jul 2019 11:30:06 -0400 Received: by mail-vs1-f68.google.com with SMTP id 190so4485210vsf.9; Thu, 11 Jul 2019 08:30:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NKwh0BaKc7HdLVY/44p+/9uGqJilXs/pFH756+9dwa4=; b=pWNqSiF0wI+NAhKUO9jeUT5ddMPc4IWrwifKWWXllUwVCKeE7nkFPXKD/OTuDl+7zE r5YMnOFNfrvWr3wNDsqvEtjxgi43PgnPfifLNFD0znDVYw3QjzufMDUOxPj7jM7Kx2zG dMB90OfJ7gdvM3hVMVoITiVJO+y2/x1NAfphjoOcE1sc2u55FCTGkL8m4NR9zpOy52Zs U+8l+AAaYyDoDiC4V1daq19Ag8wP59d+QTQmV1YFziXr9qldRdiS2U/xHMPtCh140S88 V9hJ7AYrOymLb5WnV96LZoEvmt6gKwMm2vYtzFmxitS1wPtZj8LwfPYM0p+Ucd3OVPNs u2iA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NKwh0BaKc7HdLVY/44p+/9uGqJilXs/pFH756+9dwa4=; b=t41VuBiemAJnqueBQBYT4y+ynH2AO7tvfDrlAboeCuNHP9EudRK9WHnLfCLk/wIXhy O7jmvpkwhH3GoVcNxYz0WnT9oGu0vg6f7gFKrZunnDsle/ducYhQ/ynCl6D9/gBnPuRC 9q2BwSPloPjVhuNzPf7yZGZyxuyCRiXLoBZaqLRTPEwZdaF00+Y16PJ9Rpbx0Kl48fvS F1jLcWRMIATIZL/3+5f4oYnVB07Ou6scslIvOkIMHMB0aIADH/R3Km4Y9kzeOyFFLHyF 2rlYP1o8CfKnUBVtdNy09/HpzcFkeW/FPIddsDe8S5Er15/3bs2JHd3OtgWHJARxrgd/ I/VQ== X-Gm-Message-State: APjAAAWiBTuUuZ4MvSpYTN8ub/SlgQLnLBCaPIOflZLCozqPajzJBM7c /HnYafdTBQqkNTz0q9BdtTjwEEJTO5zQ+7goLbNhGa1N828= X-Received: by 2002:a67:fc19:: with SMTP id o25mr5269898vsq.106.1562859005683; Thu, 11 Jul 2019 08:30:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Pintu Agarwal Date: Thu, 11 Jul 2019 20:59:54 +0530 Message-ID: Subject: Re: [IMX] [DRM]: help in analyzing clock_summary rate difference To: Fabio Estevam , s.hauer@pengutronix.de, p.zabel@pengutronix.de Cc: open list , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Kernelnewbies , linux-pm@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I need one general help in analyzing difference in clock_summary rate before and after the system resume. I am using custom IMX7 board with 4.9 Kernel. With this I am trying to support some functionality during suspend/resume. I am trying to analyze clk_summary from: # cat /sys/kernel/debug/clk/clk_summary I observed that there are difference in "clock rate" after system resume and module install. However the enable/prepare count remains the same. Since I am not much familiar with clock framework, I am looking for some help to analyze this issue. It's an internal issue. May be someone which is familiar with clock analysis or fixed the similar issue earlier can give me some guidance. What does the difference in clock rate indicates? What analysis can be done to narrow down the root cause? Any example of reference could be helpful to understand. Thank You! Regards, Pintu