From: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
To: <michal.simek@amd.com>, <gregkh@linuxfoundation.org>,
<tanmay.shah@amd.com>, <mathieu.poirier@linaro.org>,
<nava.kishore.manne@amd.com>, <ben.levinsky@amd.com>,
<sai.krishna.potthuri@amd.com>, <marex@denx.de>,
<robh@kernel.org>, <ruanjinjie@huawei.com>, <arnd@arndb.de>,
<shubhrajyoti.datta@amd.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Jay Buddhabhatti <jay.buddhabhatti@amd.com>
Subject: [PATCH v4 0/5] update for versal net platform
Date: Wed, 8 Nov 2023 23:00:16 -0800 [thread overview]
Message-ID: <20231109070021.16291-1-jay.buddhabhatti@amd.com> (raw)
Update firmware and SoC drivers to support for Versal NET platform.
Versal Net is a new AMD/Xilinx SoC.
V1: https://lore.kernel.org/linux-arm-kernel/20230929105558.11893-1-jay.buddhabhatti@amd.com/
V2: https://lore.kernel.org/linux-arm-kernel/20231004094116.27128-1-jay.buddhabhatti@amd.com/
V3: https://lore.kernel.org/linux-arm-kernel/20231016111301.13369-1-jay.buddhabhatti@amd.com/
Changes in V4:
- Used variable arguments in patch #1 for adding support for additional
arguments
Changes in V3:
- Addressed formatting related comments
- Removed below patch to update maintainer of event management driver from v2 patch series
https://lore.kernel.org/linux-arm-kernel/20231004094116.27128-7-jay.buddhabhatti@amd.com/
Changes in V2:
- Removed below patch from V1 patch series
https://lore.kernel.org/linux-arm-kernel/20230929105558.11893-4-jay.buddhabhatti@amd.com/
- Corrected maintainer name format in patch #6 as per tool requirement
Jay Buddhabhatti (5):
firmware: xilinx: Update firmware call interface to support additional
args
firmware: xilinx: Expand feature check to support all PLM modules
firmware: xilinx: Register event manager driver
drivers: soc: xilinx: Fix error message on SGI registration failure
firmware: zynqmp: Add support to handle IPI CRC failure
drivers/firmware/xilinx/zynqmp.c | 329 ++++++++++++------------
drivers/soc/xilinx/xlnx_event_manager.c | 8 +-
drivers/soc/xilinx/zynqmp_power.c | 2 +-
include/linux/firmware/xlnx-zynqmp.h | 16 +-
4 files changed, 179 insertions(+), 176 deletions(-)
--
2.17.1
next reply other threads:[~2023-11-09 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 7:00 Jay Buddhabhatti [this message]
2023-11-09 7:00 ` [PATCH v4 1/5] firmware: xilinx: Update firmware call interface to support additional args Jay Buddhabhatti
2023-11-11 6:47 ` kernel test robot
2023-11-14 20:00 ` Nathan Chancellor
2023-11-09 7:00 ` [PATCH v4 2/5] firmware: xilinx: Expand feature check to support all PLM modules Jay Buddhabhatti
2023-11-09 7:00 ` [PATCH v4 3/5] firmware: xilinx: Register event manager driver Jay Buddhabhatti
2023-11-09 7:00 ` [PATCH v4 4/5] drivers: soc: xilinx: Fix error message on SGI registration failure Jay Buddhabhatti
2023-11-09 7:00 ` [PATCH v4 5/5] firmware: zynqmp: Add support to handle IPI CRC failure Jay Buddhabhatti
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=20231109070021.16291-1-jay.buddhabhatti@amd.com \
--to=jay.buddhabhatti@amd.com \
--cc=arnd@arndb.de \
--cc=ben.levinsky@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@amd.com \
--cc=nava.kishore.manne@amd.com \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=sai.krishna.potthuri@amd.com \
--cc=shubhrajyoti.datta@amd.com \
--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
all inboxes | Powered by JetHome®