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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B0EE4C6FD1D for ; Fri, 7 Apr 2023 15:42:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=nERIEwBhcO/XRtGCy8a2im7U1Z/HgpO8l0P+q5cwA4Y=; b=HVRTevfdfdH8P5 gaw+WAjS7yBuQPx3IYVYf/W4JPDSUo6grCViP3drsbDz5ctAAww/xsiHo6/e3Nosyul6GnpG5rxjl fe/REtY19uEmDTNyRiWHC4L60zQp86of3NnJPzglCs618VEkJKhku6CDgkJzHq/CsQOxH12YHImwj pbpYTj3lJ+aXdBgrnzZ64iKOOMIIqjbGKeXCyL7OZvkoN2qusBtzuV2nfDHVh9v2TDqHvr2hfyrWg 815QfCbXBF2pVxJ1EykHkQefiLp1ZQvAJ0QQ2uy4bzrK3fw/7r1N2ZC6zQzVa/lDs/T1jHMktlFK7 uVm67anyA2cIm406ztkw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1pkoDm-00Ae0M-0x; Fri, 07 Apr 2023 15:41:50 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1pkoDj-00Adzr-2T for linux-arm-kernel@lists.infradead.org; Fri, 07 Apr 2023 15:41:49 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 49E7B60F35; Fri, 7 Apr 2023 15:41:46 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DEB0AC433D2; Fri, 7 Apr 2023 15:41:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1680882105; bh=0TH7wao0u0XHYRas2C6c5JKYGQoZXugn+nq3+N4xTJk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mPzV60c1UwAVMfNfbVy+e73ZkApGMgI0fINmSiICLkTrG0kedj+gAsbihCIGgLkGp DY+Zwd0haHBBiTu/VLN0HuGGMvYsuHwk+1eosEdCfDOg/L9nXsa9ZqYyf/afsVZ39K HfenXNdWQhJ5L6w0qeqrB+YY/LCKKciwE1QLAuXvbbCIGoIZ4m4UZhNK5Nh04eV4l8 DTiPPszubCoToxejLfmHSkVrnt0+AScVDDg4YOapAmoX7NRV84rpNBrQRBVKVHjsSw 8jvtW0niDXS6uqs7DDs6xmrJ+Cybs+M9GXFyFdBQMnsTOQkspBqV4UAftUjCkqeQ84 MhVDemxnuQHTA== Date: Fri, 7 Apr 2023 08:44:35 -0700 From: Bjorn Andersson To: Souradeep Chowdhury Cc: Andy Gross , Konrad Dybcio , Krzysztof Kozlowski , Rob Herring , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, Sibi Sankar , Rajendra Nayak Subject: Re: [PATCH V2 0/3] soc: qcom: boot_stats: Add driver support for boot_stats Message-ID: <20230407154435.2wzrld365p3dcabd@ripper> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230407_084147_881070_3F061625 X-CRM114-Status: GOOD ( 25.12 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Apr 07, 2023 at 07:34:34PM +0530, Souradeep Chowdhury wrote: > Qualcomm's proprietary Android boot-loaders capture boot time > stats, like the time when the bootloader started execution and at what > point the bootloader handed over control to the kernel etc. in the IMEM > region. This information is captured in a specific format by this driver > by mapping a structure to the IMEM memory region and then accessing the > members of the structure to print the information. This information is > useful in verifying if existing boot KPIs have regressed or not. > A sample log in SM8450(waipio) device is as follows:- > > KPI: Pre ABL Time = 3s > KPI: ABL Time = 14s > KPI: Kernel MPM timestamp = 890206 > > The Module Power Manager(MPM) sleep counter starts ticking at the PBL > stage and the timestamp generated by the sleep counter is logged by > the Qualcomm proprietary bootloader(ABL) at two points-> First when it > starts execution which is logged here as "Pre ABL Time" and the second > when it is about to load the kernel logged as "ABL Time". Both these > values are read up by the driver from IMEM region and printed as above. > The current sleep counter timestamp is also logged by the driver. > > Changes in V2 > > *Implemented comments on version 1 of the patch This doesn't give a particular good indication of what you actually changed. So please spell it out going forward. Thanks, Bjorn > > *Changed the boot_stats driver to module_platform_driver > > *Dropped the DT binding for mpm sleep counter > > Souradeep Chowdhury (3): > dt-bindings: sram: qcom,imem: Add Boot Stat region within IMEM > soc: qcom: boot_stat: Add Driver Support for Boot Stats > MAINTAINERS: Add the entry for boot_stats driver support > > .../devicetree/bindings/sram/qcom,imem.yaml | 21 +++++ > MAINTAINERS | 6 ++ > drivers/soc/qcom/Kconfig | 7 ++ > drivers/soc/qcom/Makefile | 1 + > drivers/soc/qcom/boot_stats.c | 95 ++++++++++++++++++++++ > 5 files changed, 130 insertions(+) > create mode 100644 drivers/soc/qcom/boot_stats.c > > -- > 2.7.4 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel