From: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
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: Thu, 11 May 2023 11:29:12 +0530 [thread overview]
Message-ID: <15042631-4012-61bd-11ef-dde378215fed@quicinc.com> (raw)
In-Reply-To: <CAA8EJprJfmtFs1dx0uJw0bi1ig2JsCYzH_4BncPop4aO16D2aA@mail.gmail.com>
On 5/9/2023 6:35 PM, Dmitry Baryshkov wrote:
> On Tue, 9 May 2023 at 15:21, Souradeep Chowdhury
> <quic_schowdhu@quicinc.com> wrote:
>>
>>
>>
>> On 5/9/2023 5:05 PM, Dmitry Baryshkov wrote:
>>> On Tue, 9 May 2023 at 13:53, Souradeep Chowdhury
>>> <quic_schowdhu@quicinc.com> wrote:
>>>>
>>>> All Qualcomm bootloaders log useful timestamp information related
>>>> to bootloader stats in the IMEM region. Add the child node within
>>>> IMEM for the boot stat region containing register address and
>>>> compatible string.
>>>
>>> I might have a minor vote here. Is there any reason why you have to
>>> instantiate the device from DT?
>>> It looks like a software interface. Ideally software should not be
>>> described in DT (e.g. this can be instantiated from imem
>>> driver-to-be).
>>> Or we can follow the RPM master-stats approach, where the device is a
>>> top-level device, having handle pointers to the sram regions.
>>
>> This is a dedicated region of IMEM reserved for storing stats related
>> information. So it is represented as a child of IMEM, please
>> refer to Documentation/devicetree/bindings/sram/sram.yaml which
>> follows a similar philosophy. Also since this is a child of IMEM with
>> a specific purpose, does it not warrant a dedicated driver?
>
> I do not question a dedicated driver. I was asking about the DT node.
> Even the mentioned bindings file describes the SRAM regions inside the
> SRAM, rather than a proper device to be instantiated in the SRAM node.
> I'd point to the boot_stats discussions (present on the list in the
> last several months).
>
Ack. Will instantiate the device from the parent node in the driver and
access the stats region to print the boot_stats information.
>>
>>>
>>>>
>>>> Signed-off-by: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
>>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>> ---
>>>> .../devicetree/bindings/sram/qcom,imem.yaml | 22 +++++++++++++++++++
>>>> 1 file changed, 22 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/sram/qcom,imem.yaml b/Documentation/devicetree/bindings/sram/qcom,imem.yaml
>>>> index 0548e8e0d30b..bb884c5c8952 100644
>>>> --- a/Documentation/devicetree/bindings/sram/qcom,imem.yaml
>>>> +++ b/Documentation/devicetree/bindings/sram/qcom,imem.yaml
>>>> @@ -50,6 +50,28 @@ patternProperties:
>>>> $ref: /schemas/remoteproc/qcom,pil-info.yaml#
>>>> description: Peripheral image loader relocation region
>>>>
>>>> + "^stats@[0-9a-f]+$":
>>>> + type: object
>>>> + description:
>>>> + Imem region dedicated for storing timestamps related
>>>> + information regarding bootstats.
>>>> +
>>>> + additionalProperties: false
>>>> +
>>>> + properties:
>>>> + compatible:
>>>> + items:
>>>> + - enum:
>>>> + - qcom,sm8450-bootstats
>>>> + - const: qcom,imem-bootstats
>>>> +
>>>> + reg:
>>>> + maxItems: 1
>>>> +
>>>> + required:
>>>> + - compatible
>>>> + - reg
>>>> +
>>>> required:
>>>> - compatible
>>>> - reg
>>>> --
>>>> 2.17.1
>>>>
>>>
>>>
>
>
>
next prev parent reply other threads:[~2023-05-11 5:59 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 [this message]
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
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=15042631-4012-61bd-11ef-dde378215fed@quicinc.com \
--to=quic_schowdhu@quicinc.com \
--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_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®