u-boot.git/drivers/fpga, branch v2024.01

arm64: zynqmp: Fix Siva's email address format

2023-10-09T08:25:32Z

Some patches didn't have his full name and also there was one more ">" at the end of email address. That's why correct both of these issues. Fixes: 174d728471d5 ("arm64: zynqmp: Switch to amd.com emails") Signed-off-by: Michal Simek Link: https://lore.kernel.org/r/e970cc0dfabe293c2baf6b231d34f3af0386f1eb.1695378830.git.michal.simek@amd.com

event: Add fpga load event

2023-07-21T07:00:39Z

This enables implementing custom logic after a bitstream was loaded into the fpga. Signed-off-by: Christian Taedcke Reviewed-by: Simon Glass Reviewed-by: Tom Rini Link: https://lore.kernel.org/r/20230720072724.11516-1-christian.taedcke-oss@weidmueller.com Signed-off-by: Michal Simek

arm64: zynqmp: Switch to amd.com emails

2023-07-21T07:00:38Z

Update my and DPs email address to match current setup. Signed-off-by: Michal Simek Link: https://lore.kernel.org/r/aba5b19b9c5a95608829e86ad5cc4671c940f1bb.1688992543.git.michal.simek@amd.com

fpga: zynqmppl: fix fpga loads command for unencrypted use case

2023-03-09T12:15:00Z

When using the fpga loads command, the driver is passing the AES encryption key address is all cases. However, for the authenticated, but not encrypted use case, there is no AES encryption key, and this value is 0. When AES encryption is not used on the fpga bitstream, the pmufw assumes that the AES key address is a bitstream size value like what is used by the unsecure fpga load command. To fix the problem, this patch checks to see if the AES key address is zero. If the AES key address is zero, it means that AES is not being used on the bitstream and the bitstream size should be passed instead. Thus, matching the fpga load functionality. Signed-off-by: Neal Frager Acked-by: Ashok Reddy Soma Link: https://lore.kernel.org/r/20230214131959.40298-1-neal.frager@amd.com Signed-off-by: Michal Simek

arm64: zynqmp: Add missing ZYNQMP_FIRMWARE dependencies

2023-03-09T12:14:59Z

There are missing Kconfig dependencies in the code which is using firmware interface. The commit 71efd45a5fc7 ("arm64: zynqmp: Change firmware dependency") add option to also disable ZYNQMP_FIRMWARE. But not all Kconfig dependencies were properly described and also sdhci and gem drivers didn't protect the code properly. So, add the missing ZYNQMP_FIRMWARE dependencies. Signed-off-by: Algapally Santosh Sagar Signed-off-by: Ashok Reddy Soma Link: https://lore.kernel.org/r/20230201095553.11219-1-ashok.reddy.soma@amd.com Signed-off-by: Michal Simek

fpga: Add a FPGA_STRATIX_II option

2023-02-07T19:33:48Z

There is no Kconfig option for this code, but it seems to be useful. Add one. Signed-off-by: Simon Glass

fpga: Add a LATTICE option

2023-02-07T19:33:48Z

There is no Kconfig option for this code, but it seems to be useful. Add one. Signed-off-by: Simon Glass

global: Finish CONFIG -> CFG migration

2023-01-20T17:27:24Z

At this point, the remaining places where we have a symbol that is defined as CONFIG_... are in fairly odd locations. While as much dead code has been removed as possible, some of these locations are simply less obvious at first. In other cases, this code is used, but was defined in such a way as to have been missed by earlier checks. Perform a rename of all such remaining symbols to be CFG_... rather than CONFIG_... Signed-off-by: Tom Rini Reviewed-by: Simon Glass

fpga: Migrate CONFIG_MAX_FPGA_DEVICES to Kconfig

2023-01-20T17:27:06Z

This is always defined to 5, so use that as the default. Cc: Michal Simek Signed-off-by: Tom Rini Reviewed-by: Michal Simek

misc: fs_loader: Add function to get the chosen loader

2023-01-12T19:06:15Z

The fs_loader device is used to pull in settings via the chosen node. However, there was no library function for this, so arria10 was doing it explicitly. This function subsumes that, and uses ofnode_get_chosen_node instead of navigating the device tree directly. Because fs_loader pulls its config from the environment by default, it's fine to create a device with nothing backing it at all. Doing this allows enabling CONFIG_FS_LOADER without needing to modify the device tree. Signed-off-by: Sean Anderson Reviewed-by: Simon Glass Reviewed-by: Ramon Fried