mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Val Packett <val@packett.cool>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] remoteproc: qcom: pas: Add SC8180X SLPI compatible
Date: Wed, 4 Nov 2026 05:07:22 -0300	[thread overview]
Message-ID: <4953dc2f-d998-43fe-b02f-597d5d7b23b4@packett.cool> (raw)
In-Reply-To: <1f57f491-56a5-42ad-91c0-9c55e1c6ef4b@oss.qualcomm.com>


On 11/4/26 5:03 AM, Konrad Dybcio wrote:
> On 11/4/26 9:01 AM, Val Packett wrote:
>> The SLPI on the SC8180X is identical to the one on SM8150, reuse the
>> same data SM8150 (and SDM845) uses.
> fallback to 8150?

The current binding for all the remoteprocs (which already mentions 
slpi) doesn't use a fallback..

(in sm8150-pas.yaml only qcs615 uses the fallback right now)

Between editing the bindings and adding the compatible to the driver, I 
chose the option that was consistent with how the others are done..


~val


      reply	other threads:[~2026-11-04  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  8:01 [PATCH v2 1/2] arm64: dts: qcom: sc8180x: Add SLPI remoteproc node Val Packett
2026-11-04  8:01 ` [PATCH v2 2/2] remoteproc: qcom: pas: Add SC8180X SLPI compatible Val Packett
2026-11-04  8:03   ` Konrad Dybcio
2026-11-04  8:07     ` Val Packett [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=4953dc2f-d998-43fe-b02f-597d5d7b23b4@packett.cool \
    --to=val@packett.cool \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.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®