From: Tanmay Shah <tanmay.shah@amd.com>
To: <michal.simek@amd.com>, <andersson@kernel.org>,
<mathieu.poirier@linaro.org>, <jaswinder.singh@linaro.org>,
<ben.levinsky@amd.com>, <shubhrajyoti.datta@amd.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-remoteproc@vger.kernel.org>,
Tanmay Shah <tanmay.shah@amd.com>
Subject: [PATCH v5 0/5] drivers: remoteproc: xilinx: add mailbox support
Date: Fri, 10 Mar 2023 17:24:03 -0800 [thread overview]
Message-ID: <20230311012407.1292118-1-tanmay.shah@amd.com> (raw)
This series adds mailbox support required for rpmsg communication
in Xilinx remoteproc driver. It also fixes few bugs in Xilinx
zynqmp-ipi driver that handles corner cases.
---
Changes in v5:
- mailbox node count should not be 0 for driver to probe
- Remove spurious change
- Include kick op regardless status of mailbox nodes in dts
Changes in v4:
- split mailbox driver patch into 3 different patches
- use of_phandle_iterator_next to get memory-region nodes
- move zynqmp_r5_setup_mbox from zynqmp_r5_add_rproc_core to
zynqmp_r5_cluster_init
Changes in v3:
- split single patch into multiple patches
- add appropriate fixes tag for patches fixing previous bug in the driver
- make enhancements in zynqmp-ipi driver that handles corener cases
- fix memory-region carveout names
- fix multi-line comment format
- do not mixup mailbox information with memory-regions
- fix redundant dev_warn for split mode
- Setting up mailboxes should return an error code
- Move mailbox setup during driver probe
- Add .kick function only if mailbox setup is success
v2: https://lore.kernel.org/all/20230126213154.1707300-1-tanmay.shah@amd.com/
Tanmay Shah (5):
mailbox: zynqmp: fix counts of child nodes
mailbox: zynqmp: fix IPI isr handling
mailbox: zynqmp: fix typo in IPI documentation
drivers: remoteproc: xilinx: fix carveout names
remoteproc: xilinx: add mailbox channels for rpmsg
drivers/mailbox/zynqmp-ipi-mailbox.c | 13 +-
drivers/remoteproc/xlnx_r5_remoteproc.c | 308 ++++++++++++++++-----
include/linux/mailbox/zynqmp-ipi-message.h | 2 +-
3 files changed, 247 insertions(+), 76 deletions(-)
base-commit: fe15c26ee26efa11741a7b632e9f23b01aca4cc6
--
2.25.1
next reply other threads:[~2023-03-11 1:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 1:24 Tanmay Shah [this message]
2023-03-11 1:24 ` [PATCH v5 1/5] mailbox: zynqmp: fix counts of child nodes Tanmay Shah
2023-03-13 9:30 ` Michal Simek
2023-03-13 19:38 ` Mathieu Poirier
2023-03-14 7:26 ` Michal Simek
2023-03-11 1:24 ` [PATCH v5 2/5] mailbox: zynqmp: fix IPI isr handling Tanmay Shah
2023-03-11 1:24 ` [PATCH v5 3/5] mailbox: zynqmp: fix typo in IPI documentation Tanmay Shah
2023-03-11 1:24 ` [PATCH v5 4/5] drivers: remoteproc: xilinx: fix carveout names Tanmay Shah
2023-03-11 1:24 ` [PATCH v5 5/5] remoteproc: xilinx: add mailbox channels for rpmsg Tanmay Shah
2023-03-14 19:29 ` [PATCH v5 0/5] drivers: remoteproc: xilinx: add mailbox 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=20230311012407.1292118-1-tanmay.shah@amd.com \
--to=tanmay.shah@amd.com \
--cc=andersson@kernel.org \
--cc=ben.levinsky@amd.com \
--cc=jaswinder.singh@linaro.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=shubhrajyoti.datta@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
all inboxes | Powered by JetHome®