From: Krzysztof Kozlowski <krzk@kernel.org>
To: Anvesh Jain P <anvesh.p@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>
Subject: Re: [PATCH 1/4] dt-bindings: remoteproc: qcom: Add Glymur OOBMSS PAS binding
Date: Mon, 12 Oct 2026 12:27:08 +0200 [thread overview]
Message-ID: <2183ffa6-040a-4c3f-86fd-5c317b850171@kernel.org> (raw)
In-Reply-To: <7a091ebe-86d7-4edb-9fa3-9026d2c44176@oss.qualcomm.com>
On 12/10/2026 11:36, Anvesh Jain P wrote:
>>> +required:
>>> + - compatible
>>> + - reg
>>> + - power-domains
>>> + - power-domain-names
>>> + - memory-region
>>
>> firmware-name as well, I guess?
>>
>>
>
> I think firmware-name should remain optional. The driver provides
> defaults when loading images, and attach-only operation does not request
> firmware.
ack
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-12 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 7:17 [PATCH 0/4] Add Glymur OOBMSS support Anvesh Jain P
2026-10-09 7:17 ` [PATCH 1/4] dt-bindings: remoteproc: qcom: Add Glymur OOBMSS PAS binding Anvesh Jain P
2026-10-12 8:55 ` Krzysztof Kozlowski
2026-10-12 9:36 ` Anvesh Jain P
2026-10-12 10:27 ` Krzysztof Kozlowski [this message]
2026-10-09 7:17 ` [PATCH 2/4] remoteproc: qcom: pas: Support secondary images Anvesh Jain P
2026-10-09 7:29 ` sashiko-bot
2026-10-09 7:17 ` [PATCH 3/4] remoteproc: qcom: pas: Add Glymur OOBMSS PAS parameters Anvesh Jain P
2026-10-09 7:17 ` [PATCH 4/4] remoteproc: qcom: pas: Add Glymur OOBMSS coredump support Anvesh Jain P
2026-10-09 7:33 ` sashiko-bot
2026-10-12 8:56 ` Krzysztof Kozlowski
2026-10-12 9:50 ` Anvesh Jain P
2026-10-12 10:28 ` Krzysztof Kozlowski
2026-10-12 15:33 ` Anvesh Jain P
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=2183ffa6-040a-4c3f-86fd-5c317b850171@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=anvesh.p@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 \
--cc=sibi.sankar@oss.qualcomm.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 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.