From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
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 17:33:38 +0100 [thread overview]
Message-ID: <cc30861f-1e10-41d5-87a7-496e18bd358e@kernel.org> (raw)
In-Reply-To: <33737c4f-b668-418c-ab03-f27ed3b6fcff@oss.qualcomm.com>
On 02/03/2026 15:56, Konrad Dybcio wrote:
> On 3/2/26 3:54 PM, Krzysztof Kozlowski wrote:
>> On 02/03/2026 15:10, Konrad Dybcio wrote:
>>>>
>>>> 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
>>
>> I know and sram is not part of "reboot-mode" name. It is "reboot-mode"
>> in existing binding and DTS, not "reboot-mode-sram".
>
> In any case, I believe it'd be good to drop that requirement
Ah, and one more thing, the syscon-reboot-mode is Linux driver with its
own Linux requirements - syscon - so probably not working with sram
bindings. That's another reason full binding should be posted and tested
- I speculate it simply does not work.
> Konrad
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-02 16:33 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
2026-03-02 14:54 ` Krzysztof Kozlowski
2026-03-02 14:56 ` Konrad Dybcio
2026-03-02 16:33 ` Krzysztof Kozlowski [this message]
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=cc30861f-1e10-41d5-87a7-496e18bd358e@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.