- Mar 05, 2021
-
-
Bin Meng authored
In phys_to_virt() and virt_to_phys(), if CONFIG_ADDR_MAP is defined, they use addrmap_ translation APIs to do the address translation. However these APIs only work in post-relocation phase. Update the code logic to fall back to use the default one when in pre-relocation phase. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
Mention that CONFIG_ADDR_MAP only works in the post-relocation phase. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
This adds a basic test for the newly introduced 'addrmap' command. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> [Rebase] Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
This adds a new command 'addrmap' to display the address map for non-identity virtual-physical memory mappings. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
At present address_map[] is static and its type is unknown to external modules. In preparation to create a command to list its contents, this patch moves its type definition and declaration to the header file. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
Remove the extern of the header because they are useless. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
At present QEMU ppce500 target has not been migrated to driver model yet. As a start, let's enable driver model and the 'dm' command. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
The QEMU ppce500 machine generates a device tree blob and passes it to U-Boot during boot. Let's enable OF_CONTROL with OF_BOARD and provide board_fdt_blob_setup() in the board codes. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
This function does nothing. Drop it. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
These are no longer needed. Drop them. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
LAW related codes should be wrapped with CONFIG_FSL_LAW. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
CONFIG_SYS_PCI_MAP_END currently points to 0xe8000000, which means the upper end of the virtual address mapped to PCI bus address ends at 0xe8000000. But this is wrong as the CCSBAR was already mapped at 0xe0000000 with a 1 MiB size. Fixes: fa08d395 ("PPC 85xx: Add qemu-ppce500 machine") Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
When QEMU originally supported the ppce500 machine back in Jan 2014, it was created with a 1:1 mapping of PCI bus address. Things seemed to change rapidly that in Nov 2014 with the following QEMU commits: commit e6b4e5f4795b ("PPC: e500: Move CCSR and MMIO space to upper end of address space") and commit cb3778a0455a ("PPC: e500 pci host: Add support for ATMUs") the PCI memory and IO physical address were moved to beyond 4 GiB, but PCI bus address remained below 4 GiB, hence a non-identity mapping was created. Unfortunately corresponding U-Boot updates were missed along with the QEMU changes and the U-Boot QEMU ppce500 PCI support has been broken since then. This commit makes the PCI (non-DM version) work again. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
At present fdt_read_prop() can only handle 1 or 2 cells. It is called by fdt_read_range() which may be used to read PCI address from <ranges> for a PCI bus node where the number of PCI address cell is 3. The <ranges> property is an array of: { <child address> <parent address> <size in child address space> } When trying to read <child address> from a PCI bus node using fdt_read_prop(), as the codes below: /* Read <child address> */ if (child_addr) { r = fdt_read_prop(ranges, ranges_len, cell, child_addr, acells); if (r) return r; } it will fail, because the PCI child address is made up of 3 cells but fdt_read_prop() cannot handle it. We advance the cell offset by 1 so that the <child address> can be correctly read. This adds the special handling of such case. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
Alex's previous email address is no longer reachable. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Bin Meng authored
Commit e0024741 ("pci: pci-uclass: Dynamically allocate the PCI regions") changes 'struct pci_controller'.regions from pre-allocated array of regions to dynamically allocated, which unfortunately broken lots of boards that still use the non-DM PCI driver. This patch changes the non-DM fsl_pci_init driver to dynamically allocate the regions, just like what's done in the pci uclass driver. Fixes: e0024741 ("pci: pci-uclass: Dynamically allocate the PCI regions") Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Michael Walle authored
Because we probe the master ourselves (and fail if there is no master), it is not possible that we don't have a master device. There is one catch though: device removal. We don't support that. It wasn't supported neither before this patch. Because the master device was only set in .pre_probe(), if a device was removed master_dev was a dangling pointer and transmitting a frame cause a panic. I don't see a good solution without having some sort of notify machanism when a udevice is removed. Signed-off-by:
Michael Walle <michael@walle.cc> Reviewed-by:
Vladimir Oltean <vladimir.oltean@nxp.com> Tested-by: Michael Walle <michael@walle.cc> [DSA unit tests] Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Michael Walle authored
Because the uclass has the "*_auto" properties set, the driver model will take care of allocating the private structures for us and they can't be NULL. Drop the checks. Signed-off-by:
Michael Walle <michael@walle.cc> Reviewed-by:
Vladimir Oltean <vladimir.oltean@nxp.com> Reviewed-by:
Ramon Fried <rfried.dev@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Michael Walle authored
DSA needs to have the master device probed first for MAC inheritance. Until now, it only works by chance because the only user (LS1028A SoC) will probe the master device first. The probe order is given by the PCI device ordering, thus it works because the master device has a "smaller" BDF then the switch device. Explicitly probe the master device in dsa_port_probe(). Fixes: fc054d56 ("net: Introduce DSA class for Ethernet switches") Signed-off-by:
Michael Walle <michael@walle.cc> Reviewed-by:
Vladimir Oltean <vladimir.oltean@nxp.com> Reviewed-by:
Ramon Fried <rfried.dev@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Michael Walle authored
It doesn't make sense to have DSA without a master port. Error out early if there is no master port. Fixes: fc054d56 ("net: Introduce DSA class for Ethernet switches") Signed-off-by:
Michael Walle <michael@walle.cc> Reviewed-by:
Vladimir Oltean <vladimir.oltean@nxp.com> Reviewed-by:
Ramon Fried <rfried.dev@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1012AQDS Board MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LX2160AQDS BOARD MAINTAINER entry to current MAINTAINER. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1046ARDB BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1046AQDS BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS2080ARDB BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS2080AQDS BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1088ARDB, LS1088AQDS BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1043ARDB BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1028AQDS, LS10128ARDB board MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1021ATWR BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1021AIOT BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1012ARDB BOARD MAINTAINERS entries to current MAINTAINERS. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Update LS1012AFRWY BOARD MAINTAINER entry to current MAINTAINER. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Remove MAINTAINERS entries for P3041DS_NAND_SECURE_BOOT_defconfig and P5040DS_NAND_SECURE_BOOT_defconfig as these configs support have been removed. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Rajesh Bhagat authored
Moves below via specific defines to Kconfig: CONFIG_FSL_VIA Signed-off-by:
Rajesh Bhagat <rajesh.bhagat@nxp.com> [Rebased] Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Rajesh Bhagat authored
Moves below bootrom specific defines to Kconfig: CONFIG_SYS_FSL_BOOTROM_BASE CONFIG_SYS_FSL_BOOTROM_SIZE Signed-off-by:
Rajesh Bhagat <rajesh.bhagat@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Stephen Carlson authored
This patch adds support for more PMBus compatible devices to the NXP drivers for its QorIQ family devices. At runtime, the voltage regulator is queried over I2C, and the required voltage multiplier determined. This change supports the DIRECT and LINEAR PMBus voltage reporting modes. Previously, the driver only supported a few specific devices such as the IR36021 and LTC3882, so this change allows the QorIQ series to be used with a much larger variety of core voltage regulator devices. checkpatch warning "Use if (IS_DEFINED (...))" was ignored to maintain consistency with the existing code. Signed-off-by:
Stephen Carlson <stcarlso@linux.microsoft.com> Signed-off-by:
Wasim Khan <wasim.khan@nxp.com> Tested-by:
Wasim Khan <wasim.khan@nxp.com> [Rebased] Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
- Mar 04, 2021
-
-
Tom Rini authored
There are times where buildman seems to get stuck in this job when in CI. Forcing single-threaded here allows us to complete and move on. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Simon Glass authored
At present even if only a single thread is in use, buildman still uses threading. For some debugging it is helpful to do everything in the main process. Allow -T0 to support this. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Pali Rohár authored
CONFIG_CMD_BOOTD provides 'boot' command which is required in more scripts. Signed-off-by:
Pali Rohár <pali@kernel.org>
-