mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>,
	Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Robert Marko <robimarko@gmail.com>,
	Das Srinagesh <quic_gurus@quicinc.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: firmware: qcom,scm: document Eliza SCM Firmware Interface
Date: Mon, 16 Mar 2026 11:17:04 +0100	[thread overview]
Message-ID: <0727b1ea-faef-4b7d-a60c-098a17c62b5c@oss.qualcomm.com> (raw)
In-Reply-To: <dqgcqu2wcskl7rxpv4gf2ltunopyjd2cpougkljga6ogih5x42@hji7dtp36cvu>

On 3/10/26 11:23 AM, Abel Vesa wrote:
> On 26-02-23 11:41:31, Krzysztof Kozlowski wrote:
>> On Mon, Feb 23, 2026 at 10:42:02AM +0200, Abel Vesa wrote:
>>> Document the SCM Firmware Interface on the Eliza SoC.
>>
>> So different than sm8750? Then you need to explain, because patch looks
>> odd (incomplete). Plus I am pretty sure it fails tests on your DTS. The
>> point of the bindings in DT schema is to actually use them...
> 
> So as discussed off-list, schema doesn't fail with this patch because
> interrupts property isn't marked as required. Not sure if it should or
> not.

No, that's for a "value-add" feature when multiple OSes run at the
same time

See 6bf325992236 ("firmware: qcom: scm: Add wait-queue handling logic")

Konrad

      reply	other threads:[~2026-03-16 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23  8:42 Abel Vesa
2026-02-23 10:41 ` Krzysztof Kozlowski
2026-03-10 10:23   ` Abel Vesa
2026-03-16 10:17     ` Konrad Dybcio [this message]

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=0727b1ea-faef-4b7d-a60c-098a17c62b5c@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=abel.vesa@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=quic_gurus@quicinc.com \
    --cc=robh@kernel.org \
    --cc=robimarko@gmail.com \
    /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®