From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
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>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v7 1/5] dt-bindings: sram: describe the IPQ5424 IMEM as mmio-sram
Date: Wed, 25 Feb 2026 16:58:28 +0530 [thread overview]
Message-ID: <cbb7ba3d-2b75-47e6-ad46-c37f1dab7fca@oss.qualcomm.com> (raw)
In-Reply-To: <20260225-purple-rat-of-blizzard-dafcd6@quoll>
On 2/25/2026 3:43 PM, Krzysztof Kozlowski wrote:
> On Wed, Feb 25, 2026 at 12:13:10PM +0530, Kathiravan Thirumoorthy wrote:
>> Based on the discussion in the linux-arm-msm list[1], it is not
>> appropriate to define the IMEM (On-Chip SRAM) as syscon or MFD.
> The reason should be here. I asked that referencing 3rd party resources
> is not the same as providing the reason.
Sorry, I misunderstood your statement. Let me rewrite as below. Please
let me know if this is okay.
"IMEM shouldn’t be treated as a syscon or simple-mfd because it’s really
just on‑chip SRAM, not a block of control registers or a device with
multiple hardware functions. In reality it’s just memory that different
pieces of software read or write. Describing it as generic mmio‑SRAM
keeps the model simple and closer to what the hardware actually is."
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-02-25 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 6:43 [PATCH v7 0/5] Add support to read the watchdog bootstatus from IMEM Kathiravan Thirumoorthy
2026-02-25 6:43 ` [PATCH v7 1/5] dt-bindings: sram: describe the IPQ5424 IMEM as mmio-sram Kathiravan Thirumoorthy
2026-02-25 10:13 ` Krzysztof Kozlowski
2026-02-25 11:28 ` Kathiravan Thirumoorthy [this message]
2026-02-25 6:43 ` [PATCH v7 2/5] arm64: dts: qcom: ipq5424: Add the IMEM node Kathiravan Thirumoorthy
2026-02-25 12:34 ` Konrad Dybcio
2026-02-25 6:43 ` [PATCH v7 3/5] dt-bindings: watchdog: qcom-wdt: Document sram property Kathiravan Thirumoorthy
2026-02-25 6:43 ` [PATCH v7 4/5] watchdog: qcom: add support to get the bootstatus from IMEM Kathiravan Thirumoorthy
2026-02-25 12:41 ` Konrad Dybcio
2026-02-25 13:25 ` Kathiravan Thirumoorthy
2026-02-25 6:43 ` [PATCH v7 5/5] arm64: dts: qcom: ipq5424: add support to get watchdog " Kathiravan Thirumoorthy
2026-02-25 12:34 ` Konrad Dybcio
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=cbb7ba3d-2b75-47e6-ad46-c37f1dab7fca@oss.qualcomm.com \
--to=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=quic_rjendra@quicinc.com \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.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®