From: Michal Simek <michal.simek@amd.com>
To: Jay Buddhabhatti <jay.buddhabhatti@amd.com>,
linus.walleij@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
git@amd.com
Subject: Re: [PATCH 0/3] enhance zynqmp_pm_get_family_info()
Date: Fri, 18 Jul 2025 09:24:31 +0200 [thread overview]
Message-ID: <8b0c852a-e7dd-434a-a8f1-a39b5d5906ff@amd.com> (raw)
In-Reply-To: <20250701123851.1314531-1-jay.buddhabhatti@amd.com>
On 7/1/25 14:38, Jay Buddhabhatti wrote:
> Enhance the get family info functionality in the Xilinx firmware
> driver. Changes includes adding Versal NET compatible string in
> firmware driver, adding a new unique family code for all platforms,
> and modifying the get family info function to use the unique family
> code.
>
> Jay Buddhabhatti (3):
> firmware: xilinx: Add Versal NET platform compatible string
> drivers: firmware: xilinx: Add unique family code for all platforms
> drivers: firmware: xilinx: Switch to new family code in
> zynqmp_pm_get_family_info()
>
> drivers/firmware/xilinx/zynqmp.c | 73 +++++++++++++++----------
> drivers/pinctrl/pinctrl-zynqmp.c | 7 +--
> drivers/soc/xilinx/xlnx_event_manager.c | 8 +--
> drivers/soc/xilinx/zynqmp_power.c | 10 ++--
> include/linux/firmware/xlnx-zynqmp.h | 18 ++----
> 5 files changed, 64 insertions(+), 52 deletions(-)
>
Applied.
M
prev parent reply other threads:[~2025-07-18 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 12:38 Jay Buddhabhatti
2025-07-01 12:38 ` [PATCH 1/3] firmware: xilinx: Add Versal NET platform compatible string Jay Buddhabhatti
2025-07-01 12:38 ` [PATCH 2/3] drivers: firmware: xilinx: Add unique family code for all platforms Jay Buddhabhatti
2025-07-01 12:38 ` [PATCH 3/3] drivers: firmware: xilinx: Switch to new family code in zynqmp_pm_get_family_info() Jay Buddhabhatti
2025-07-18 7:24 ` Michal Simek [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=8b0c852a-e7dd-434a-a8f1-a39b5d5906ff@amd.com \
--to=michal.simek@amd.com \
--cc=git@amd.com \
--cc=jay.buddhabhatti@amd.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®