From: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
To: Brian Masney <bmasney@redhat.com>
Cc: 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>, Arnd Bergmann <arnd@arndb.de>,
<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 V7 0/2] firmware: Add support for boot_stats
Date: Tue, 11 Jul 2023 11:00:59 +0530 [thread overview]
Message-ID: <de6a5d53-4b69-8dc9-648b-aa3f6ff772ac@quicinc.com> (raw)
In-Reply-To: <ZKwhwUnKR7vqQZms@brian-x1>
On 7/10/2023 8:50 PM, Brian Masney wrote:
> On Wed, Jul 05, 2023 at 11:02:30AM +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 by the bootloader and populated on
>> the device tree properties "pre-abl-time" and "abl-time" which can be
>> be viewed from the user space like as follows:-
>>
>> /sys/firmware/devicetree/base/bootstats # cat abl_time
>> 17898
>>
>> As a part of this patch series added the bindings for boot-stats which
>> was suggested in the v6 of the series. The link for the same is as
>> follows:-
>
> Should boot statistics be exposed to userspace through the qcom socinfo
> driver? I see that the socinfo v19 metadata has fields for the boot core
> and boot cluster [1], so boot timing wouldn't be out of place.
"Boot Cluster" and "boot core" are soc specific info which are fixed for
a particular qcom soc recorded in smem region of memory. "Boot_stats" is
not a property of a soc as such, they are KPI measurements in the boot
time path stored in the imem region. So I not sure if this is the right
home for it.
>
> Brian
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/soc/qcom/socinfo.c#n572
>
prev parent reply other threads:[~2023-07-11 5:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 5:32 Souradeep Chowdhury
2023-07-05 5:32 ` [PATCH V7 1/2] dt-bindings: firmware: bootstats: Add the dtschema Souradeep Chowdhury
2023-07-05 6:17 ` Krzysztof Kozlowski
2023-07-05 8:33 ` Souradeep Chowdhury
2023-07-05 9:34 ` Krzysztof Kozlowski
2023-07-05 19:30 ` Rob Herring
2023-07-05 21:14 ` Dmitry Baryshkov
2023-07-06 7:13 ` Souradeep Chowdhury
2023-07-05 5:32 ` [PATCH V7 2/2] MAINTAINERS: Add the entry for boot_stats support Souradeep Chowdhury
2023-07-10 15:20 ` [PATCH V7 0/2] firmware: Add support for boot_stats Brian Masney
2023-07-11 5:30 ` Souradeep Chowdhury [this message]
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=de6a5d53-4b69-8dc9-648b-aa3f6ff772ac@quicinc.com \
--to=quic_schowdhu@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=bmasney@redhat.com \
--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_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
all inboxes | Powered by JetHome®