On Tue, 08 Apr 2025 08:28:28 +0200, Dario Binacchi wrote:
> The release commit for version v2025.04 forgot to update the next
> version (i. e. v2025.07) in the section where information about the
> merge window is provided.
>
>
Applied to u-boot/master, thanks!
[1/1] doc: release_cycle: fix ne
On Thu, 20 Mar 2025 07:59:21 -0600, Tom Rini wrote:
> Hey all,
>
> One thing that Simon Glass has noted is that our pytest run time keeps
> getting longer. Looking at:
> https://source.denx.de/u-boot/u-boot/-/pipelines/25011/test_report?job_name=sandbox%20test.py%3A%20%5Bfast%20amd64%5D
> we can
From: Samuel Holland
Now that the USB PHY driver uses the device tree to get VBUS supply
regulators, these Kconfig symbols are unused. Remove them.
Signed-off-by: Samuel Holland
Signed-off-by: Andre Przywara
---
arch/arm/mach-sunxi/Kconfig | 29
configs/A
From: Samuel Holland
AXP PMICs have a pin which can either report the USB VBUS state, or
driving a regulator that supplies USB VBUS. Add a regulator driver for
controlling this pin. The selection between input and output is done via
the x-powers,drive-vbus-en pin on the PMIC (parent) node.
Signe
So far Allwinner boards controlled the USB OTG ID detection via the
respective GPIO pin specified in Kconfig, as a string. All boards should
have the same GPIO already specified in the devicetree, in the
usb0_id_det-gpios property.
Convert the usage of the Kconfig configured GPIO over to query tha
So far Allwinner boards controlled the USB VBUS detection via the
respective GPIO pin specified in Kconfig, as a string. All boards should
have the same GPIO already specified in the devicetree, in the
usb0_vbus_det-gpios property.
Convert the usage of the Kconfig configured GPIO over to query tha
From: Samuel Holland
On many boards, the USB ports are powered by the PMIC's "drivevbus"
regulator. In preparation for switching the USB PHY driver to use the
regulator uclass instead of a virtual GPIO pin, ensure these boards
have AXP PMIC regulator support enabled.
Signed-off-by: Samuel Hollan
On 2025/1/29 20:42, Quentin Schulz wrote:
From: Quentin Schulz
There's no need to modify private data from the controller, so let's
make that struct const.
Signed-off-by: Quentin Schulz
Reviewed-by: Kever Yang
Thanks,
- Kever
---
drivers/pinctrl/rockchip/pinctrl-rk3368.c | 2 +-
1 fi
On 2025/4/6 08:24, Jonas Karlman wrote:
Ensure rk3588_common.h can be used by boards directly by defining a
blank ROCKCHIP_DEVICE_SETTINGS unless it already is defined.
Add a default SYS_CONFIG_NAME to include rk3588_common.h unless a board
target overrides it in its board Kconfig.
Signed-off
Hi Andre Przywara:
I can understand the motivation behind this patch, which
I think it's a good addition to BROM FEL mode..
On 00:59 Wed 09 Apr , Andre Przywara wrote:
> Some boards with Allwinner SoCs feature a "FEL" key, sometimes also
> labelled "uboot", which triggers the BootROM FEL mode
Some boards with Allwinner SoCs feature a "FEL" key, sometimes also
labelled "uboot", which triggers the BootROM FEL mode, when pressed upon
power-on or reset. This allows to access the SoC's memory via USB OTG,
and to upload and execute code. There is a tool to upload our U-Boot image
and immediat
101 - 111 of 111 matches
Mail list logo