linux-kernel - linux-next: manual merge of the pmdomain tree with the xilinx tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250721123801.78841075@canb.auug.org.au>
Date: Mon, 21 Jul 2025 12:38:01 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Ulf Hansson <ulf.hansson@...aro.org>, Michal Simek <monstr@...str.eu>
Cc: Jay Buddhabhatti <jay.buddhabhatti@....com>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>, Michal Simek <michal.simek@....com>
Subject: linux-next: manual merge of the pmdomain tree with the xilinx tree

Hi all,

Today's linux-next merge of the pmdomain tree got a conflict in:

  drivers/firmware/xilinx/zynqmp.c

between commit:

  ef32394c6d34 ("drivers: firmware: xilinx: Add unique family code for all platforms")

from the xilinx tree and commits:

  3da405ead651 ("firmware/pmdomain: xilinx: Move ->sync_state() support to firmware driver")
  29ea33866d6d ("firmware: xilinx: Use of_genpd_sync_state()")

from the pmdomain tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/firmware/xilinx/zynqmp.c
index 906a7aae719e,02da3e48bc8f..000000000000
--- a/drivers/firmware/xilinx/zynqmp.c
+++ b/drivers/firmware/xilinx/zynqmp.c
@@@ -2143,22 -2100,22 +2143,35 @@@ static void zynqmp_firmware_remove(stru
  	platform_device_unregister(em_dev);
  }
  
+ static void zynqmp_firmware_sync_state(struct device *dev)
+ {
+ 	struct device_node *np = dev->of_node;
+ 
+ 	if (!of_device_is_compatible(np, "xlnx,zynqmp-firmware"))
+ 		return;
+ 
+ 	of_genpd_sync_state(np);
+ 
+ 	if (zynqmp_pm_init_finalize())
+ 		dev_warn(dev, "failed to release power management to firmware\n");
+ }
+ 
 +static const struct platform_fw_data platform_fw_data_versal = {
 +	.family_code = PM_VERSAL_FAMILY_CODE,
 +};
 +
 +static const struct platform_fw_data platform_fw_data_versal_net = {
 +	.family_code = PM_VERSAL_NET_FAMILY_CODE,
 +};
 +
 +static const struct platform_fw_data platform_fw_data_zynqmp = {
 +	.family_code = PM_ZYNQMP_FAMILY_CODE,
 +};
 +
  static const struct of_device_id zynqmp_firmware_of_match[] = {
 -	{.compatible = "xlnx,zynqmp-firmware"},
 -	{.compatible = "xlnx,versal-firmware"},
 +	{.compatible = "xlnx,zynqmp-firmware", .data = &platform_fw_data_zynqmp},
 +	{.compatible = "xlnx,versal-firmware", .data = &platform_fw_data_versal},
 +	{.compatible = "xlnx,versal-net-firmware", .data = &platform_fw_data_versal_net},
  	{},
  };
  MODULE_DEVICE_TABLE(of, zynqmp_firmware_of_match);

Content of type "application/pgp-signature" skipped