From: "Arnd Bergmann" <arnd@arndb.de>
To: "Souradeep Chowdhury" <quic_schowdhu@quicinc.com>,
"Andy Gross" <agross@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@somainline.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org,
"Sibi Sankar" <quic_sibis@quicinc.com>,
"Rajendra Nayak" <quic_rjendra@quicinc.com>
Subject: Re: [PATCH V6 2/3] soc: qcom: boot_stat: Add Driver Support for Boot Stats
Date: Tue, 16 May 2023 10:19:38 +0200 [thread overview]
Message-ID: <3faa9bf7-b42c-4951-8103-9ea2fe02eac1@app.fastmail.com> (raw)
In-Reply-To: <35863b47c04c2edd7ae49c57d23682aba6111d4f.1683628357.git.quic_schowdhu@quicinc.com>
On Tue, May 9, 2023, at 12:52, Souradeep Chowdhury wrote:
> All of 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 show the information within debugfs file.
> This information is useful in verifying if the existing boot KPIs have
> regressed or not. The information is shown in milliseconds, a sample
> log from sm8450(waipio) device is as follows:-
>
> /sys/kernel/debug/qcom_boot_stats # cat abl_time
> 17898 ms
> /sys/kernel/debug/qcom_boot_stats # cat pre_abl_time
> 2879 ms
>
> 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". Documentation
> details are also added in Documentation/ABI/testing/debugfs-driver-bootstat
>
> Signed-off-by: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
> ---
> .../ABI/testing/debugfs-driver-bootstat | 17 +++
> drivers/soc/qcom/Kconfig | 10 ++
> drivers/soc/qcom/Makefile | 1 +
> drivers/soc/qcom/boot_stats.c | 100 ++++++++++++++++++
As mentioned in my reply to the binding, I don't think this should
be a driver at all. On top of that, even if it was a driver, it is
clearly not a "soc" driver since nothing in it has any relevance to
the hardware, rather than the first-stage loader, and drivers/soc/
drivers should never have their own user space interface either.
Arnd
next prev parent reply other threads:[~2023-05-16 8:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 10:52 [PATCH V6 0/3] soc: qcom: boot_stats: Add driver support for boot_stats Souradeep Chowdhury
2023-05-09 10:52 ` [PATCH V6 1/3] dt-bindings: sram: qcom,imem: Add Boot Stat region within IMEM Souradeep Chowdhury
2023-05-09 11:35 ` Dmitry Baryshkov
2023-05-09 12:21 ` Souradeep Chowdhury
2023-05-09 13:05 ` Dmitry Baryshkov
2023-05-11 5:59 ` Souradeep Chowdhury
2023-05-16 8:16 ` Arnd Bergmann
2023-05-16 18:34 ` Trilok Soni
2023-05-16 18:41 ` Arnd Bergmann
2023-05-16 19:17 ` Dmitry Baryshkov
2023-05-16 21:58 ` Trilok Soni
2023-05-09 10:52 ` [PATCH V6 2/3] soc: qcom: boot_stat: Add Driver Support for Boot Stats Souradeep Chowdhury
2023-05-09 11:39 ` Dmitry Baryshkov
2023-05-09 12:26 ` Souradeep Chowdhury
2023-05-09 13:01 ` Dmitry Baryshkov
2023-05-11 5:42 ` Souradeep Chowdhury
2023-05-09 14:06 ` kernel test robot
2023-05-10 8:18 ` kernel test robot
2023-05-11 17:07 ` Bjorn Andersson
2023-05-11 17:11 ` Trilok Soni
2023-05-12 11:46 ` Souradeep Chowdhury
2023-05-15 4:31 ` Satya Durga Srinivasu Prabhala
2023-05-16 8:19 ` Arnd Bergmann [this message]
2023-05-17 0:09 ` Dmitry Baryshkov
2023-05-09 10:52 ` [PATCH V6 3/3] MAINTAINERS: Add the entry for boot_stats driver support Souradeep Chowdhury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3faa9bf7-b42c-4951-8103-9ea2fe02eac1@app.fastmail.com \
--to=arnd@arndb.de \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=quic_schowdhu@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).