From: "Shah, Tanmay" <tanmays@amd.com>
To: Tanmay Shah <tanmay.shah@amd.com>, <andersson@kernel.org>,
<mathieu.poirier@linaro.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<michal.simek@amd.com>, <ben.levinsky@amd.com>
Cc: <linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] remoteproc: xlnx: add auto-boot support
Date: Fri, 1 May 2026 09:46:23 -0500 [thread overview]
Message-ID: <1997464a-26b0-4384-9dbd-4000582896c8@amd.com> (raw)
In-Reply-To: <20260501143707.1591110-1-tanmay.shah@amd.com>
On 5/1/2026 9:37 AM, Tanmay Shah wrote:
> The Cortex-R remote processors on AMD-Xilinx platforms can run
> before linux boot. Add auto-boot property to notify linux that remote
> processor is ready to be used, so linux can load fw and start it or
> attach to the running processor.
>
Missed the change log here:
Changes in v2:
- remove the auto-boot property from bindings patch (1/2)
- rebase on latest remoteproc for-next branch
- refactor the driver patch (2/2) and detect the auto-boot runtime
If needed, I will send v2 with the change log.
>
> Tanmay Shah (2):
> dt-bindings: remoteproc: xlnx: add firmware-name property
> remoteproc: xlnx: enable auto boot feature
>
> .../remoteproc/xlnx,zynqmp-r5fss.yaml | 4 ++
> drivers/remoteproc/xlnx_r5_remoteproc.c | 48 +++++++++++++------
> 2 files changed, 38 insertions(+), 14 deletions(-)
>
>
> base-commit: 54dacf6efe7196c1cd8ae4b5c691579d0510a8bd
prev parent reply other threads:[~2026-05-01 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 14:37 [PATCH v2 0/2] remoteproc: xlnx: add auto-boot support Tanmay Shah
2026-05-01 14:37 ` [PATCH v2 1/2] dt-bindings: remoteproc: xlnx: add firmware-name property Tanmay Shah
2026-05-01 15:49 ` Conor Dooley
2026-05-01 16:15 ` Shah, Tanmay
2026-05-01 16:43 ` Conor Dooley
2026-05-01 14:37 ` [PATCH v2 2/2] remoteproc: xlnx: enable auto boot feature Tanmay Shah
2026-05-01 14:46 ` Shah, Tanmay [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=1997464a-26b0-4384-9dbd-4000582896c8@amd.com \
--to=tanmays@amd.com \
--cc=andersson@kernel.org \
--cc=ben.levinsky@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@amd.com \
--cc=robh@kernel.org \
--cc=tanmay.shah@amd.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