From: "Arnd Bergmann" <arnd@arndb.de>
To: "Trilok Soni" <quic_tsoni@quicinc.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Souradeep Chowdhury" <quic_schowdhu@quicinc.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>,
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 1/3] dt-bindings: sram: qcom,imem: Add Boot Stat region within IMEM
Date: Tue, 16 May 2023 20:41:32 +0200 [thread overview]
Message-ID: <14213f52-5460-4455-9e15-739b04fda1ed@app.fastmail.com> (raw)
In-Reply-To: <64cdd9b6-dae3-f335-63a7-c20ed9b63920@quicinc.com>
On Tue, May 16, 2023, at 20:34, Trilok Soni wrote:
> On 5/16/2023 1:16 AM, Arnd Bergmann wrote:
>
> To understand bit better here, what you are suggesting here that
> application bootloader (e.g., UEFI app for Linux) can read these
> boot values from the IMEM and encode them into the devicetree properties
> which can be later retrieved directly from the userspace.
I'm not entirely sure I understand the concept of "application bootloader",
but in principle this can be anything that runs before the devicetree
is handed off from the final boot loader to the kernel.
> I am fine with this approach as well and in this case we just
> need to submit the bindings document, right?
Yes, exactly.
Arnd
next prev parent reply other threads:[~2023-05-16 18:42 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 [this message]
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
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=14213f52-5460-4455-9e15-739b04fda1ed@app.fastmail.com \
--to=arnd@arndb.de \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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=quic_tsoni@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