From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 1/6] dt-bindings: sram: Describe the IMEM present in Qualcomm IPQ SoCs
Date: Mon, 2 Mar 2026 15:10:59 +0100 [thread overview]
Message-ID: <d3de0b25-861a-4261-8d9b-a3785187bfdb@oss.qualcomm.com> (raw)
In-Reply-To: <edffecfc-ea3a-4c1e-9e72-58c7c134248e@kernel.org>
On 3/2/26 2:56 PM, Krzysztof Kozlowski wrote:
> On 02/03/2026 14:52, Konrad Dybcio wrote:
>> On 3/1/26 12:27 PM, Krzysztof Kozlowski wrote:
>>> On Sat, Feb 28, 2026 at 06:38:00PM +0530, Kathiravan Thirumoorthy wrote:
>>>> Qualcomm IPQ SoCs also have the IMEM(On-chip SRAM) region and used for
>>>> the various debugging purposes like storing system restart reason and
>>>
>>> This binding does not allow restart reason. pil-reloc-info was kind of
>>> allowed, but now I think this might have been a mistake because that
>>> bindings were posted incomplete.
>>
>> The sram.yaml binding allows any arbitrrary subnode (sort of like nvmem),
>
> Not, true, look at the compatible. It requires a specific type of nodes.
Right, I didn't scroll far enough!
>> so long as the name includes 'smem'
>
> Also not accurate - "sram" is not the reboot reason, which has node name
> called "reboot-mode".
What I was referring to is:
patternProperties:
"^([a-z0-9]*-)?sram(-section)?@[a-f0-9]+$":
where the 'sram' (not 'smem' as I typo'd above) is obligatory
Konrad
next prev parent reply other threads:[~2026-03-02 14:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 13:07 [PATCH v3 0/6] Describe the IMEM present in Qualcomm IPQ SoC's Kathiravan Thirumoorthy
2026-02-28 13:08 ` [PATCH v3 1/6] dt-bindings: sram: Describe the IMEM present in Qualcomm IPQ SoCs Kathiravan Thirumoorthy
2026-03-01 11:27 ` Krzysztof Kozlowski
2026-03-02 13:52 ` Konrad Dybcio
2026-03-02 13:56 ` Krzysztof Kozlowski
2026-03-02 14:10 ` Konrad Dybcio [this message]
2026-03-02 14:54 ` Krzysztof Kozlowski
2026-03-02 14:56 ` Konrad Dybcio
2026-03-02 16:33 ` Krzysztof Kozlowski
2026-03-03 10:48 ` Konrad Dybcio
2026-03-04 11:16 ` Kathiravan Thirumoorthy
2026-03-04 11:29 ` Krzysztof Kozlowski
2026-03-04 11:38 ` Konrad Dybcio
2026-03-04 11:44 ` Krzysztof Kozlowski
2026-02-28 13:08 ` [PATCH v3 2/6] arm64: dts: qcom: ipq8074: Add the IMEM node Kathiravan Thirumoorthy
2026-03-01 11:29 ` Krzysztof Kozlowski
2026-02-28 13:08 ` [PATCH v3 3/6] arm64: dts: qcom: ipq6018: " Kathiravan Thirumoorthy
2026-02-28 13:08 ` [PATCH v3 4/6] arm64: dts: qcom: ipq5018: " Kathiravan Thirumoorthy
2026-02-28 13:08 ` [PATCH v3 5/6] arm64: dts: qcom: ipq9574: " Kathiravan Thirumoorthy
2026-02-28 13:08 ` [PATCH v3 6/6] arm64: dts: qcom: ipq5332: " Kathiravan Thirumoorthy
2026-03-01 11:28 ` Krzysztof Kozlowski
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=d3de0b25-861a-4261-8d9b-a3785187bfdb@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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