mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Ananthu C V <ananthu.cv@oss.qualcomm.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: sram: qcom,imem: Document glymur as compatible
Date: Sat, 24 Jan 2026 21:57:18 +0530	[thread overview]
Message-ID: <9febbe8e-3060-47cd-a1e8-5ee2b4de952b@oss.qualcomm.com> (raw)
In-Reply-To: <20260123101501.2836551-2-ananthu.cv@oss.qualcomm.com>


On 1/23/2026 3:46 PM, Ananthu C V wrote:
> Add compatible for Qualcomm's glymur IMEM.

Shouldn't we use "mmio-sram" binding? Please note, starting from 
"kaanapali", IMEM is described as "mmio-sram". If we need to stick with 
this binding, please describe the same on why so?

>
> Signed-off-by: Ananthu C V <ananthu.cv@oss.qualcomm.com>
> ---
> V1->V2 alphabetically sorted the placement of glymur in the list
> ---
>   Documentation/devicetree/bindings/sram/qcom,imem.yaml | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/sram/qcom,imem.yaml b/Documentation/devicetree/bindings/sram/qcom,imem.yaml
> index 6a627c57ae2f..5a4a2868388e 100644
> --- a/Documentation/devicetree/bindings/sram/qcom,imem.yaml
> +++ b/Documentation/devicetree/bindings/sram/qcom,imem.yaml
> @@ -18,6 +18,7 @@ properties:
>       items:
>         - enum:
>             - qcom,apq8064-imem
> +          - qcom,glymur-imem
>             - qcom,ipq5424-imem
>             - qcom,msm8226-imem
>             - qcom,msm8974-imem

  reply	other threads:[~2026-01-24 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 10:16 Ananthu C V
2026-01-24 16:27 ` Kathiravan Thirumoorthy [this message]
2026-01-27  6:59   ` Ananthu C V

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=9febbe8e-3060-47cd-a1e8-5ee2b4de952b@oss.qualcomm.com \
    --to=kathiravan.thirumoorthy@oss.qualcomm.com \
    --cc=ananthu.cv@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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 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®