From: Arun Kumar Neelakantam <quic_aneelaka@quicinc.com>
To: Ninad Naik <quic_ninanaik@quicinc.com>, <agross@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>
Cc: <psodagud@quicinc.com>, <quic_ppareek@quicinc.com>,
<quic_kprasan@quicinc.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <kernel@quicinc.com>
Subject: Re: [RFC PATCH 0/1] Add driver to read secondary bootloader (XBL) log
Date: Mon, 28 Aug 2023 22:49:01 +0530 [thread overview]
Message-ID: <badd7471-b28f-4948-b6b4-eddb8bf1b0d6@quicinc.com> (raw)
In-Reply-To: <20230822121512.8631-1-quic_ninanaik@quicinc.com>
On 8/22/2023 5:45 PM, Ninad Naik wrote:
> Boot time logs for Qualcomm secondary boot-loader or XBL can help to
> identify different set of information regarding firmware configuration,
> SoC boot KPIs. A dedicated region is carved out in the memory map in order
> to store this log in the memory.
>
> The objective of this driver is to read the XBL boot log stored in
> this memory region post boot-up, and provide an entry in debugfs, which
> can be used to read back the logs and print them on to the console.
>
I see couple of use cases for this kind of logging like logs from boot,
Hypervisor, Trusted Execution environments and also one in upstream for
chromeos EC console. Can this be made a generic driver which take log
name, log memory buffer address and size to read from debugfs.
> Further, this log can be parsed to extract different set of information
> as required.
>
> For example, one use case can be parsing boot time KPIs to calculate,
> - PBL End time
> - SBL End time
> - UEFI Start/Stop time
>
> Corresponding log contents as captured in /sys/kernel/debug/xbl_log entry
> which prints the above counters,
>
> S - 59378 - PBL, End
> B - 68198 - SBL1, Start
> B - 1308877 - SBL1, End
> UEFI Start [ 3370]
> - 0x0AF001000 [ 3375] Sec.efi
> UEFI Total : 466 m
> POST Time [ 3836] OS Loader
> - 0x0ABE10000 [ 3838] LinuxLoader.efi
> Exit EBS [ 4878] UEFI End
>
> /* Note - these are few excerpts picked from the complete XBL log
> * as tested on SA8775p
> */
>
> Ninad Naik (1):
> soc: qcom: Add driver to read secondary bootloader (XBL) log
>
> drivers/soc/qcom/Kconfig | 13 +++
> drivers/soc/qcom/Makefile | 1 +
> drivers/soc/qcom/dump_xbl_log.c | 139 ++++++++++++++++++++++++++++++++
> 3 files changed, 153 insertions(+)
> create mode 100644 drivers/soc/qcom/dump_xbl_log.c
>
next prev parent reply other threads:[~2023-08-28 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 12:15 Ninad Naik
2023-08-22 12:15 ` [RFC PATCH 1/1] soc: qcom: " Ninad Naik
2023-08-22 12:39 ` Pavan Kondeti
2023-08-23 11:06 ` Ninad Naik
2023-08-22 12:43 ` Bryan O'Donoghue
2023-08-22 15:14 ` Jeff Johnson
2023-08-23 11:08 ` Ninad Naik
2023-08-23 11:08 ` Ninad Naik
2023-08-22 13:41 ` Srinivas Kandagatla
2023-08-23 11:09 ` Ninad Naik
2023-08-22 16:08 ` Trilok Soni
2023-08-23 11:16 ` Ninad Naik
2023-08-23 19:32 ` Trilok Soni
2023-08-28 17:19 ` Arun Kumar Neelakantam [this message]
2023-08-28 18:44 ` [RFC PATCH 0/1] " Trilok Soni
2023-08-28 19:20 ` Bjorn Andersson
2023-09-12 16:08 ` Nikunj Kela
2023-09-12 16:11 ` Trilok Soni
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=badd7471-b28f-4948-b6b4-eddb8bf1b0d6@quicinc.com \
--to=quic_aneelaka@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psodagud@quicinc.com \
--cc=quic_kprasan@quicinc.com \
--cc=quic_ninanaik@quicinc.com \
--cc=quic_ppareek@quicinc.com \
/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®