From: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
To: <michal.simek@amd.com>, <gregkh@linuxfoundation.org>,
<tanmay.shah@amd.com>, <sai.krishna.potthuri@amd.com>,
<nava.kishore.manne@amd.com>, <ben.levinsky@amd.com>,
<dhaval.r.shah@amd.com>, <marex@denx.de>, <robh@kernel.org>,
<arnd@arndb.de>, <izhar.ameer.shaikh@amd.com>,
<ruanjinjie@huawei.com>, <mathieu.poirier@linaro.org>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Jay Buddhabhatti <jay.buddhabhatti@amd.com>
Subject: [PATCH 4/7] firmware: xilinx: Register event manager driver
Date: Fri, 29 Sep 2023 03:55:55 -0700 [thread overview]
Message-ID: <20230929105558.11893-5-jay.buddhabhatti@amd.com> (raw)
In-Reply-To: <20230929105558.11893-1-jay.buddhabhatti@amd.com>
Use family code in order to register event manager
driver for Versal and Versal NET platforms, instead
of using compatible string.
Signed-off-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
---
drivers/firmware/xilinx/zynqmp.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/firmware/xilinx/zynqmp.c b/drivers/firmware/xilinx/zynqmp.c
index 6583efa9ac48..c504702fe9c7 100644
--- a/drivers/firmware/xilinx/zynqmp.c
+++ b/drivers/firmware/xilinx/zynqmp.c
@@ -1953,7 +1953,6 @@ ATTRIBUTE_GROUPS(zynqmp_firmware);
static int zynqmp_firmware_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
- struct device_node *np;
struct zynqmp_devinfo *devinfo;
int ret;
@@ -2016,14 +2015,12 @@ static int zynqmp_firmware_probe(struct platform_device *pdev)
zynqmp_pm_api_debugfs_init();
- np = of_find_compatible_node(NULL, NULL, "xlnx,versal");
- if (np) {
+ if (pm_family_code == VERSAL_FAMILY_CODE) {
em_dev = platform_device_register_data(&pdev->dev, "xlnx_event_manager",
-1, &pm_sub_family_code, 4);
if (IS_ERR(em_dev))
dev_err_probe(&pdev->dev, PTR_ERR(em_dev), "EM register fail with error\n");
}
- of_node_put(np);
return of_platform_populate(dev->of_node, NULL, NULL, dev);
}
--
2.17.1
next prev parent reply other threads:[~2023-09-29 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 10:55 [PATCH 0/7] update for versal net platform Jay Buddhabhatti
2023-09-29 10:55 ` [PATCH 1/7] firmware: xilinx: Update firmware call interface to support additional arg Jay Buddhabhatti
2023-09-29 10:55 ` [PATCH 2/7] firmware: xilinx: Expand feature check to support all PLM modules Jay Buddhabhatti
2023-09-29 10:55 ` [PATCH 3/7] drivers: soc: xilinx: add check for platform Jay Buddhabhatti
2023-09-30 7:17 ` Greg KH
2023-10-02 6:09 ` Michal Simek
2023-10-02 6:20 ` Greg KH
2023-10-02 8:12 ` Michal Simek
2023-09-29 10:55 ` Jay Buddhabhatti [this message]
2023-09-29 10:55 ` [PATCH 5/7] drivers: soc: xilinx: Fix error message on SGI registration failure Jay Buddhabhatti
2023-09-29 10:55 ` [PATCH 6/7] firmware: zynqmp: Add support to handle IPI CRC failure Jay Buddhabhatti
2023-09-29 10:55 ` [PATCH 7/7] drivers: soc: xilinx: update maintainer of event manager driver Jay Buddhabhatti
2023-09-30 7:17 ` Greg KH
2023-10-02 6:10 ` Michal Simek
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=20230929105558.11893-5-jay.buddhabhatti@amd.com \
--to=jay.buddhabhatti@amd.com \
--cc=arnd@arndb.de \
--cc=ben.levinsky@amd.com \
--cc=dhaval.r.shah@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=izhar.ameer.shaikh@amd.com \
--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=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®