| Age | Commit message (Collapse) | Author |
|---|
|
Add support for the USB 3.0 devices in rk3588:
- USB DRD(dual role device) 3.0 #0 as usbdrd3_0 which is available in
rk3588s
- USB DRD(dual role device) 3.0 #1 as usbdrd3_1 which is available in
rk3588 only
- USB DP PHY (combo USB3.0 and DisplayPort Alt Mode ) #0 phy interface
as usbdp_phy0
- USB DP PHY (combo USB3.0 and DisplayPort Alt Mode ) #1 phy interface
as usbdp_phy1
- USB 2.0 phy #2 , the USB 3.0 device can work with this phy in USB 2.0
mode
- associated GRFs (general register files) for the devices.
Signed-off-by: Joseph Chen <[email protected]>
[[email protected]: move nodes to right place, adapt from latest
linux kernel]
Signed-off-by: Eugen Hristev <[email protected]>
Reviewed-by: Kever Yang <[email protected]>
|
|
This adds a new USBDP combo PHY with Samsung IP block driver.
The PHY is a combo between USB 3.0 and DisplayPort alt mode.
Signed-off-by: Frank Wang <[email protected]>
[[email protected]: ported to 2023.07, clean-up]
Signed-off-by: Eugen Hristev <[email protected]>
Reviewed-by: Kever Yang <[email protected]>
|
|
Sync the devicetree with linux-next tag: next-20230525
Signed-off-by: Eugen Hristev <[email protected]>
Reviewed-by: Kever Yang <[email protected]>
|
|
This just needs some extra clocks enabled, and different registers
configured. Copied from Linux, just like the original submitter
of this driver did for rk3568.
Tested on Pinephone Pro.
Signed-off-by: Ondrej Jirman <[email protected]>
Cc: Anatolij Gustschin <[email protected]>
Cc: Simon Glass <[email protected]>
Cc: Philipp Tomsich <[email protected]>
Cc: Kever Yang <[email protected]>
Cc: Chris Morgan <[email protected]>
Reviewed-by: Kever Yang <[email protected]>
|
|
Update the board.c file for the Odroid Go Advance to support the
Black Edition and the Odroid Go Super. The Odroid Go Advance Black
Edition differs from the original model with the addition of 2
extra buttons and an ESP8266 WiFi module. The Odroid Go Super
adds an additional 2 buttons compared to the Black Edition, along
with a larger panel and larger battery.
This change uses the value of ADC0 to determine which of these
3 models it is, and then changes the ${fdtfile} environment variable
to match the proper devicetree name in mainline Linux.
Tested on an Odroid Go Advance (first revision) and an Odroid Go Super.
The correct ${fdtfile} variable was set for each device.
Signed-off-by: Chris Morgan <[email protected]>
Reviewed-by: Kever Yang <[email protected]>
|
|
Add the rtl8169 driver, which supports the rtl8125b device, which is
connected on the pciE bus on this board.
Enable also CONFIG_SYS_HAS_NONCACHED_MEMORY to have the descriptors stored.
Signed-off-by: Eugen Hristev <[email protected]>
Reviewed-by: Kever Yang <[email protected]>
|
|
Replace the ascii flow diagram with svg.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Keep the boards sorted in alphabetical order.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Add link to the actual platform for folks to find details about the
board in addition to the SoC's TRM.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Convert the emmc memory layout to svg
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Convert the emmc memory layout to svg
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Convert the memory map for OSPI as a common memory map
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Use list tables to map up the UART Boot responsibility table.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Use list tables to map up the dip switch settings
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Use list tables to map up the dip switch settings
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Add labels around the A53 SPL DDR memory layout to be able to reuse the
memory map.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Convert the image format into svg that can be reused across platforms as
needed.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Convert the image format into svg that can be reused across platforms as
needed.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Convert the image format into svg that can be reused across platforms as
needed.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Convert the image format into svg that can be reused across platforms as
needed.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Introduce common variables to define a generic build instruction that is
then used in specific board specific description.
Labels are introduced in the evm.rst files to be then reused in variant
board documentation as well.
While at this, drop using ARCH=arm when building u-boot sources. This
practice has been discouraged for some time and can potentially create
problems with Kconfig rules related to aarch64. It's best to avoid
this approach.
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Update the bootflow svg diagram instead of the ascii version
Reviewed-by: Neha Malcom Francis <[email protected]>
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Update the bootflow svg diagram instead of the ascii version
Reviewed-by: Neha Malcom Francis <[email protected]>
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Update the bootflow svg diagram and reuse across the platforms as they
are common.
Reviewed-by: Neha Malcom Francis <[email protected]>
Signed-off-by: Nishanth Menon <[email protected]>
|
|
We have duplication of sources which makes it hard to sustain across the
board, but at the same time, we'd like to ensure readers get specific
information without having to cross refer to different documentation to
get piecemeal information that they need to put together.
Reviewed-by: Neha Malcom Francis <[email protected]>
Reviewed-by: Tom Rini <[email protected]>
Signed-off-by: Nishanth Menon <[email protected]>
|
|
Check for efi_search_protocol() failure before dereferencing "handler"
to avoid a crash.
Signed-off-by: Dan Carpenter <[email protected]>
|
|
Now that we are using binman in all cases on these platforms, reword
things to be clearer that for filesystem booting we need to use a
specific name for each component.
Signed-off-by: Tom Rini <[email protected]>
Reviewed-by: Neha Malcom Francis <[email protected]>
|
|
The EFI doesn't allow removal of handles, unless all hosted protocols
are cleanly removed. Our efi_delete_handle() is a bit intrusive.
Although it does try to delete protocols before removing a handle,
it doesn't care if that fails. Instead it only returns an error if the
handle is invalid. On top of that none of the callers of that function
check the return code.
So let's rewrite this in a way that fits the EFI spec better. Instead
of forcing the handle removal, gracefully uninstall all the handle
protocols. According to the EFI spec when the last protocol is removed
the handle will be deleted. Also switch all the callers and check the
return code. Some callers can't do anything useful apart from reporting
an error. The disk related functions on the other hand, can prevent a
medium that is being used by EFI from removal.
The only function that doesn't check the result is efi_delete_image().
But that function needs a bigger rework anyway, so we can clean it up in
the future
Signed-off-by: Ilias Apalodimas <[email protected]>
Reviewed-by: Heinrich Schuchardt <[email protected]>
|
|
* Add a new page about the emulation of block devices
* Add semihosting to the emulation index page
* Set toc maxdepth to 1 to improve readability
Signed-off-by: Heinrich Schuchardt <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
|
|
%s/device_compat\/.h/device_compat.h/
Signed-off-by: Heinrich Schuchardt <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
|
|
Move the recursive dp_fill(dev->parent) call to a single location.
Determine uclass_id only once.
Signed-off-by: Heinrich Schuchardt <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
|
|
The UEFI specification does not provide node types matching UCLASS_BLKMAP,
UCLASS_HOST, UCLASS_VIRTIO block devices.
The current implementation uses VenHw() nodes with uclass specific GUIDs
and a single byte for the device number appended. This leads to unaligned
integers in succeeding device path nodes.
The current implementation fails to create unique device paths for block
devices based on other uclasses like UCLASS_PVBLOCK.
Let's use a VenHw() node with the U-Boot GUID with a length dividable by
four and encoding blkdesc->uclass_id as well as blkdesc->devnum.
Signed-off-by: Heinrich Schuchardt <[email protected]>
Reviewed-by: Ilias Apalodimas <[email protected]>
|
|
Update the following requirements to their latest version:
* Pygments - syntax highlighting
* pytz - world timezone definitions
* certifi - Mozilla's CA bundle
Signed-off-by: Heinrich Schuchardt <[email protected]>
|
|
Approved DT binding has the port mode register in the
"phys" property. Get it from there instead of the custom
"cpsw-phy-sel" property.
This will allow us to keep DT in sync with Linux.
Signed-off-by: Roger Quadros <[email protected]>
Acked-by: Nishanth Menon <[email protected]>
|
|
The approved DT property for MAC efuse (ROM) address is
"ti,syscon-efuse".
Use that and drop custom property "mac_efuse".
Signed-off-by: Roger Quadros <[email protected]>
Acked-by: Nishanth Menon <[email protected]>
|
|
The binding represents the MDIO controller as a child device tree
node of the MAC device tree node.
The U-Boot driver mostly ignores that child device tree node and just
hardcodes the resources it uses to support both the MAC and MDIO in a
single driver.
However, some resources like pinctrl muxing states are thus ignored.
This has been a problem with some device trees that will put some
pinctrl states on the MDIO device tree node, like the SK-AM62 Device
Tree does.
Let's rework the driver a bit to create a dummy MDIO driver that we will
then get during our initialization to force the core to select the right
muxing.
Signed-off-by: Maxime Ripard <[email protected]>
Reviewed-by: Siddharth Vadapalli <[email protected]>
Acked-by: Roger Quadros <[email protected]>
Acked-by: Nishanth Menon <[email protected]>
|
|
- Merge a few network updates
|
|
The adin phy has extended registers that can be accessed using
adin_ext_read and adin_ext_write. These registers can be read directly
using the mdio command using readext and writext. For example:
=> mdio rx ethernet@428a0000 0xff23
Reading from bus ethernet@428a0000
PHY at address 0:
65315 - 0xe01
Signed-off-by: Nate Drude <[email protected]>
Reviewed-by: Marek Vasut <[email protected]>
|
|
Copy and tweak the required code from the linux kernel.
Only the KSZ9893 has been tested.
Signed-off-by: Karsten Wiese <[email protected]>
Reviewed-by: Ramon Fried <[email protected]>
|
|
The structure icmp6_ra_prefix_info needs to be packed because it is read
from a network stream.
Signed-off-by: Ehsan Mohandesi <[email protected]>
Reviewed-by: Viacheslav Mitrofanov <[email protected]>
Reviewed-by: Ramon Fried <[email protected]>
|
|
The argument len passed to function process_ra is the length of the IPv6
router advertisement message and needs to be between 0 and MTU because
it is assigned to remaining_option_len and used as a loop variable.
Addresses-Coverity-ID: 450971 ("TAINTED_SCALAR")
Signed-off-by: Ehsan Mohandesi <[email protected]>
Reviewed-by: Viacheslav Mitrofanov <[email protected]>
Reviewed-by: Ramon Fried <[email protected]>
|
|
|
|
drivers/core/device.c will call `device_free()` after xhci_register
already frees the private device data. This can cause a crash later
during the boot process, observed on aarch64 RPi4b as a synchronous
exception. All callers of xhci_register use priv_auto, so this won't
lead to memory leaks.
Signed-off-by: Richard Habeeb <[email protected]>
Reviewed-by: Bin Meng <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
|
|
- Watchdog updates, and more MAINTAINERS entries
|
|
This commit was not intended for this tree but rather
u-boot-test-scripts (where it is applied).
This reverts commit f04ef0a7a0166e91729b45b1db22f5cc3b3b2f99.
Signed-off-by: Tom Rini <[email protected]>
|
|
Signed-off-by: Angelo Dureghello <[email protected]>
---
Changes for v2:
- none
Changes for v3:
- none
|
|
Add config options for mcf_wdt driver.
Signed-off-by: Angelo Dureghello <[email protected]>
---
Changes for v2:
- none
Changes for v3:
- none
|
|
Add watchdog node for the implemented mcf_wdt driver.
Signed-off-by: Angelo Dureghello <[email protected]>
---
Changes for v2:
- remove unnecessary big-endian property
Changes for v3:
- none
|
|
Move watchdog functions inside a separate watchdog driver.
Signed-off-by: Angelo Dureghello <[email protected]>
---
Changes for v2:
- none
Changes for v3:
- none
|
|
This watchdog driver applies to the following
mcf families:
- mcf52x2 (5271 5275 5282)
- mcf532x (5329 5373)
- mcf523x (5235)
Cpu's not listed for each family does not have WDT module.
Note, after some attempts testing by qemu on 5208 i
finally abandoned, watchdog seems not implemented properly.
The driver has been tested in a real M5282EVM.
Signed-off-by: Angelo Dureghello <[email protected]>
---
Changes for v2:
- remove unnecessary hardcoded timeouts
- remove unnecessary hw_watchdog_xxx stuff
- rewrite wdog module reg calculation
- using IS_ENABLED() where possible
Changes for v3:
- remove hardcoded 4s test
|
