From: Tanmay Shah <tanmay.shah@amd•com>
To: <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>,
<tanmay.shah@amd•com>
Cc: <linux-remoteproc@vger•kernel.org>, <devicetree@vger•kernel.org>,
<linux-arm-kernel@lists•infradead.org>,
<linux-kernel@vger•kernel.org>
Subject: [PATCH v3 0/2] remoteproc: xlnx: add auto-boot support
Date: Tue, 26 May 2026 22:16:09 -0700 [thread overview]
Message-ID: <20260527051611.194844-1-tanmay.shah@amd.com> (raw)
The Linux kernel remoteproc framework provides auto boot feature. When
enabled, the remote processor framework attempts to start the remote
processor based on the firmware-name provided in the device-tree or
attach to the remote processor if bootloader has already started the
remote processor. Enable this auto boot feature for all AMD-xilinx
platforms.
Changes in v3:
- add more descriptive commit message in the patch 2/2.
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
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: 90de217305800ff32df4c0308e240925c8deb385
--
2.34.1
next reply other threads:[~2026-05-27 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 5:16 Tanmay Shah [this message]
2026-05-27 5:16 ` [PATCH v3 1/2] dt-bindings: remoteproc: xlnx: add firmware-name property Tanmay Shah
2026-05-27 5:16 ` [PATCH v3 2/2] remoteproc: xlnx: enable auto boot feature Tanmay Shah
2026-05-29 15:14 ` [PATCH v3 0/2] remoteproc: xlnx: add auto-boot support Mathieu Poirier
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=20260527051611.194844-1-tanmay.shah@amd.com \
--to=tanmay.shah@amd$(echo .)com \
--cc=andersson@kernel$(echo .)org \
--cc=ben.levinsky@amd$(echo .)com \
--cc=conor+dt@kernel$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=krzk+dt@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-remoteproc@vger$(echo .)kernel.org \
--cc=mathieu.poirier@linaro$(echo .)org \
--cc=michal.simek@amd$(echo .)com \
--cc=robh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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