)]}' { "commit": "bcc1348b6bb2fcd987c8f047fa9f526f32768258", "tree": "467300236add1df4729e7911aadb71db52e7baf3", "parents": [ "97936d895b41bc7691edcbd5c24890764356e01c" ], "author": { "name": "Nava kishore Manne", "email": "nava.kishore.manne@amd.com", "time": "Wed Feb 15 16:13:48 2023 +0530" }, "committer": { "name": "Akshay Belsare", "email": "akshay.belsare@amd.com", "time": "Thu Feb 16 14:34:13 2023 +0530" }, "message": "fix(zynqmp): update the conflicting EEMI API IDs\n\nIn the ZynqMP, 0x36 EEMI API ID is used for PM_FPGA_GET_VERSION and 0x37\nis used for PM_FPGA_GET_FEATURE_LIST. The same ID numbers in the Versal\nare used for PM_ADD_SUBSYSTEM and PM_DESTROY_SUBSYSTEM and it leads to\nthe EEMI API ID conflict between the platforms. To fix this issue this\npatch updates the PM_FPGA_GET_VERSION and PM_FPGA_GET_FEATURE_LIST EEMI\nAPI ID\u0027s to 0x48 and 0x49.\n\nIn linux zynqmp_pm_fpga_get_version() and\nzynqmp_pm_fpga_get_feature_list() API\u0027s are uses PM_FPGA_GET_VERSION\nand PM_FPGA_GET_FEATURE_LIST to get the xilfpga version and\nxilfpga-supported feature list info. These API\u0027s are called only in\nzynqmp-fpga.c as part of the probe. In case of this caller API\u0027s are\nfailed it will fall to the default feature list and this default\nfeature list is same as latest xilfpga-supported feature list (No new\nfeature was added in the xilfpga after adding these APIs). So, these\nupdated IDs will not cause any functional issues between Linux, TF-A,\nand firmware components.\n\nSigned-off-by: Nava kishore Manne \u003cnava.kishore.manne@amd.com\u003e\nChange-Id: I14d974dd44651681ecbf726ad8b6940e1850cbec\n", "tree_diff": [ { "type": "modify", "old_id": "e335b944399d565edb18aff8cf55e49e9c2a0307", "old_mode": 33188, "old_path": "plat/xilinx/zynqmp/pm_service/pm_defs.h", "new_id": "628123545aa6e0fc8625bf2a3d2bec5d545ebe9d", "new_mode": 33188, "new_path": "plat/xilinx/zynqmp/pm_service/pm_defs.h" } ] }