summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat
-rw-r--r--.b4-config5
-rw-r--r--Makefile2
-rw-r--r--arch/arm/mach-stm32mp/stm32mp2/cpu.c16
-rw-r--r--board/microchip/mpfs_generic/mpfs_generic.c4
-rw-r--r--board/st/stm32mp1/stm32mp1.c2
-rw-r--r--boot/fdt_support.c17
-rw-r--r--configs/am62x_evm_r5_ethboot_defconfig2
-rw-r--r--configs/am65x_evm_r5_usbdfu_defconfig2
-rw-r--r--doc/develop/codingstyle.rst58
-rw-r--r--doc/develop/devicetree/control.rst14
-rw-r--r--doc/develop/pytest/usage.rst173
-rw-r--r--doc/develop/release_cycle.rst28
-rw-r--r--doc/develop/statistics/u-boot-stats-v2025.10.rst814
-rw-r--r--drivers/clk/ti/Kconfig4
-rw-r--r--drivers/net/Kconfig2
-rw-r--r--drivers/net/designware.c2
-rw-r--r--drivers/usb/common/fsl-errata.c2
-rw-r--r--env/Kconfig6
-rw-r--r--lib/lwip/u-boot/lwipopts.h1
-rw-r--r--net/lwip/dhcp.c14
-rw-r--r--net/lwip/net-lwip.c4
21 files changed, 1024 insertions, 148 deletions
diff --git a/.b4-config b/.b4-config
index 6ba10cf9b50..1f9ada793e6 100644
--- a/.b4-config
+++ b/.b4-config
@@ -2,6 +2,5 @@
# See https://b4.docs.kernel.org/en/latest/config.html
[b4]
- send-series-to = u-boot@lists.denx.de
- send-auto-to-cmd = echo ""
- send-auto-cc-cmd = scripts/get_maintainer.pl
+ send-auto-to-cmd = scripts/get_maintainer.pl --nogit --nogit-fallback --nogit-chief-penguins --norolestats --nom
+ send-auto-cc-cmd = scripts/get_maintainer.pl --nogit-fallback --nogit-chief-penguins --norolestats --nol
diff --git a/Makefile b/Makefile
index 0dc7da6ddac..2402f9313d8 100644
--- a/Makefile
+++ b/Makefile
@@ -3,7 +3,7 @@
VERSION = 2025
PATCHLEVEL = 10
SUBLEVEL =
-EXTRAVERSION = -rc5
+EXTRAVERSION =
NAME =
# *DOCUMENTATION*
diff --git a/arch/arm/mach-stm32mp/stm32mp2/cpu.c b/arch/arm/mach-stm32mp/stm32mp2/cpu.c
index c3b87d7f981..e081dc605b8 100644
--- a/arch/arm/mach-stm32mp/stm32mp2/cpu.c
+++ b/arch/arm/mach-stm32mp/stm32mp2/cpu.c
@@ -92,13 +92,21 @@ uintptr_t get_stm32mp_bl2_dtb(void)
}
/*
- * Save the FDT address provided by TF-A in r2 at boot time
+ * Save the FDT address provided by TF-A at boot time
* This function is called from start.S
*/
-void save_boot_params(unsigned long r0, unsigned long r1, unsigned long r2,
- unsigned long r3)
+void save_boot_params(unsigned long x0, unsigned long x1, unsigned long x2,
+ unsigned long x3)
{
- nt_fw_dtb = r2;
+ /* use the ARM64 kernel booting register settings:
+ * x0 = physical address of device tree blob (dtb) in system RAM.
+ * so kernel can replace U-Boot in FIP wihtout BL31 modification
+ * else falback to x2 used in previous TF-A version
+ */
+ if (x0)
+ nt_fw_dtb = x0;
+ else
+ nt_fw_dtb = x2;
save_boot_params_ret();
}
diff --git a/board/microchip/mpfs_generic/mpfs_generic.c b/board/microchip/mpfs_generic/mpfs_generic.c
index fac4b6aecba..f57f5f4046b 100644
--- a/board/microchip/mpfs_generic/mpfs_generic.c
+++ b/board/microchip/mpfs_generic/mpfs_generic.c
@@ -74,7 +74,7 @@ int board_fit_config_name_match(const char *name)
int board_fdt_blob_setup(void **fdtp)
{
- fdtp = (void *)_end;
+ *fdtp = (void *)_end;
/*
* The devicetree provided by the previous stage is very minimal due to
@@ -85,7 +85,7 @@ int board_fdt_blob_setup(void **fdtp)
*/
if (IS_ENABLED(CONFIG_OF_BOARD) && !IS_ENABLED(CONFIG_MULTI_DTB_FIT)) {
if (gd->arch.firmware_fdt_addr)
- fdtp = (void *)(uintptr_t)gd->arch.firmware_fdt_addr;
+ *fdtp = (void *)(uintptr_t)gd->arch.firmware_fdt_addr;
}
return 0;
diff --git a/board/st/stm32mp1/stm32mp1.c b/board/st/stm32mp1/stm32mp1.c
index ab7af69d472..cb5cab9f36a 100644
--- a/board/st/stm32mp1/stm32mp1.c
+++ b/board/st/stm32mp1/stm32mp1.c
@@ -751,6 +751,8 @@ enum env_location env_get_location(enum env_operation op, int prio)
case BOOT_FLASH_EMMC:
if (CONFIG_IS_ENABLED(ENV_IS_IN_MMC))
return ENVL_MMC;
+ else if (CONFIG_IS_ENABLED(ENV_IS_IN_EXT4))
+ return ENVL_EXT4;
else
return ENVL_NOWHERE;
diff --git a/boot/fdt_support.c b/boot/fdt_support.c
index b7331bb76b3..92f2f534ee0 100644
--- a/boot/fdt_support.c
+++ b/boot/fdt_support.c
@@ -224,24 +224,15 @@ int fdt_initrd(void *fdt, ulong initrd_start, ulong initrd_end)
int is_u64;
uint64_t addr, size;
+ /* just return if the size of initrd is zero */
+ if (initrd_start == initrd_end)
+ return 0;
+
/* find or create "/chosen" node. */
nodeoffset = fdt_find_or_add_subnode(fdt, 0, "chosen");
if (nodeoffset < 0)
return nodeoffset;
- /*
- * Although we didn't setup an initrd, there could be a stale
- * initrd setting from the previous boot firmware in the live
- * device tree. So, make sure there is no setting left if we
- * don't want an initrd.
- */
- if (initrd_start == initrd_end) {
- fdt_delprop(fdt, nodeoffset, "linux,initrd-start");
- fdt_delprop(fdt, nodeoffset, "linux,initrd-end");
-
- return 0;
- }
-
total = fdt_num_mem_rsv(fdt);
/*
diff --git a/configs/am62x_evm_r5_ethboot_defconfig b/configs/am62x_evm_r5_ethboot_defconfig
index 96b2c28825f..5ad4d3f0e5c 100644
--- a/configs/am62x_evm_r5_ethboot_defconfig
+++ b/configs/am62x_evm_r5_ethboot_defconfig
@@ -1,4 +1,4 @@
-#include<configs/am62x_evm_r5_defconfig>
+#include <configs/am62x_evm_r5_defconfig>
CONFIG_ARM=y
CONFIG_ARCH_K3=y
diff --git a/configs/am65x_evm_r5_usbdfu_defconfig b/configs/am65x_evm_r5_usbdfu_defconfig
index 3ac494f0126..f9161f1fe11 100644
--- a/configs/am65x_evm_r5_usbdfu_defconfig
+++ b/configs/am65x_evm_r5_usbdfu_defconfig
@@ -1,4 +1,4 @@
-#include<configs/am65x_evm_r5_defconfig>
+#include <configs/am65x_evm_r5_defconfig>
CONFIG_ARM=y
CONFIG_ARCH_K3=y
diff --git a/doc/develop/codingstyle.rst b/doc/develop/codingstyle.rst
index 10bfa747c6c..013bfebf7e4 100644
--- a/doc/develop/codingstyle.rst
+++ b/doc/develop/codingstyle.rst
@@ -24,6 +24,56 @@ The following rules apply:
<https://peps.python.org/pep-0008/>`_. Use `pylint
<https://github.com/pylint-dev/pylint>`_ for checking the code.
+* Use the `b4 <https://git.kernel.org/pub/scm/utils/b4/b4.git/>`_ tool to prepare and
+ send your patches. b4 has become the preferred tool to sending patches for many
+ Linux kernel contributors, and U-Boot ships with a ready-to-use ``.b4-config`` that
+ targets ``u-boot@lists.denx.de`` and integrates with ``scripts/get_maintainer.pl`` for
+ recipient discovery.
+
+ Start a topical series with ``b4 prep`` and keep the commits organised with
+ ``git rebase -i``. ``b4 prep --edit-cover`` opens an editor for the cover
+ letter, while ``b4 prep --auto-to-cc`` collects reviewers and maintainers from
+ both the configuration file and ``scripts/get_maintainer.pl``.
+
+ .. code-block:: bash
+
+ b4 prep -n mmc-fixes
+ git rebase -i origin/master
+ b4 prep --edit-cover
+ b4 prep --auto-to-cc
+
+ Run the style checks before sending. ``b4 prep --check`` wraps the existing
+ tooling so you see the output from ``scripts/checkpatch.pl`` alongside b4's
+ own validation. You can always invoke ``scripts/checkpatch.pl`` directly for
+ additional runs.
+
+ .. code-block:: bash
+
+ b4 prep --check
+
+ When the series is ready, use ``b4 send``. Begin with ``--dry-run`` to review
+ the generated emails and ``--reflect`` to copy yourself for records before
+ dispatching to ``u-boot@lists.denx.de``.
+
+ .. code-block:: bash
+
+ b4 send --dry-run
+ b4 send --reflect
+ b4 send
+
+ After reviews arrive, collect Acked-by/Tested-by tags with ``b4 trailers -u``
+ and fold them into your commits before resending the updated series.
+
+ .. code-block:: bash
+
+ b4 trailers -u
+ git rebase -i origin/master
+ b4 send
+
+* Run ``scripts/checkpatch.pl`` directly or via ``b4 prep --check`` so that all
+ issues are resolved *before* posting on the mailing list. For more information,
+ read :doc:`checkpatch`.
+
Code Formatting with clang-format
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -100,14 +150,6 @@ When using clang-format to format code, consider these best practices:
useful as it formats only the lines that have been modified in your current
changes, avoiding unnecessary formatting of unchanged code.
-* Use patman to send your patches (``tools/patman/patman -H`` for full
- instructions). With a few tags in your commits this will check your patches
- and take care of emailing them.
-
-* If you don't use patman, make sure to run ``scripts/checkpatch.pl``. For
- more information, read :doc:`checkpatch`. Note that this should be done
- *before* posting on the mailing list!
-
* Source files originating from different projects (for example the MTD
subsystem or the hush shell code from the BusyBox project) may, after
careful consideration, be exempted from these rules. For such files, the
diff --git a/doc/develop/devicetree/control.rst b/doc/develop/devicetree/control.rst
index 8811e1d5c23..c25b98683f8 100644
--- a/doc/develop/devicetree/control.rst
+++ b/doc/develop/devicetree/control.rst
@@ -79,7 +79,7 @@ regularly synced with the Linux kernel and hence no need for manual devicetree
sync. You may find that the `dts/upstream/` already has a suitable devicetree
file for your board. Look in `dts/upstream/src/<arch>/<vendor>`.
-If not you might find other boards with suitable files that you can
+If not, you might find other boards with suitable files that you can
modify to your needs. Look in the board directories for files with a
.dts extension.
@@ -98,7 +98,7 @@ Linux kernel release. To sync the `dts/upstream/` subtree, run::
./tools/update-subtree.sh pull dts <devicetree-rebasing-release-tag>
-If required it is also possible to cherry-pick fixes from the
+If required, it is also possible to cherry-pick fixes from the
devicetree-rebasing repository prior to next sync, usage::
./tools/update-subtree.sh pick dts <devicetree-rebasing-commit-id>
@@ -192,7 +192,7 @@ With `dts/upstream` Git subtree, it is ensured that devicetree files in U-Boot
are an exact copy of those in Linux kernel available under
`dts/upstream/src/<arch>/<vendor>`.
-U-Boot is of course a very different project from Linux, e.g. it operates under
+U-Boot is, of course, a very different project from Linux, e.g. it operates under
much more restrictive memory and code-size constraints. Where Linux may use a
full clock driver with Common Clock Format (CCF) to find the input clock to the
UART, U-Boot typically wants to output a banner as early as possible before too
@@ -212,7 +212,7 @@ order::
<CONFIG_SYS_VENDOR>-u-boot.dtsi
u-boot.dtsi
-Only one of these is selected but of course you can #include another one within
+Only one of these is selected, but, of course, you can #include another one within
that file, to create a hierarchy of shared files.
@@ -309,8 +309,8 @@ Limitations
Devicetrees can help reduce the complexity of supporting variants of boards
which use the same SOC / CPU.
-However U-Boot is designed to build for a single architecture type and CPU
-type. So for example it is not possible to build a single ARM binary
+However, U-Boot is designed to build for a single architecture type and CPU
+type. So, for example, it is not possible to build a single ARM binary
which runs on your AT91 and OMAP boards, relying on an fdt to configure
the various features. This is because you must select one of
the CPU families within arch/arm/cpu/arm926ejs (omap or at91) at build
@@ -328,7 +328,7 @@ files are pulled in, and the fdt controls *how* those files work.
History
-------
-U-Boot configuration was previous done using CONFIG options in the board
+U-Boot configuration was previously done using CONFIG options in the board
config file. This eventually got out of hand with nearly 10,000 options.
U-Boot adopted devicetrees around the same time as Linux and early boards
diff --git a/doc/develop/pytest/usage.rst b/doc/develop/pytest/usage.rst
index 779b2dbe24b..596b0397379 100644
--- a/doc/develop/pytest/usage.rst
+++ b/doc/develop/pytest/usage.rst
@@ -27,8 +27,8 @@ the appropriate time.
In order to run the test suite at a minimum we require that both Python 3 and
pip for Python 3 are installed. All of the required python modules are
-described in the requirements.txt file in the /test/py/ directory and can be
-installed via the command
+described in the ``requirements.txt`` file in the ``/test/py/`` directory and
+can be installed via the command
.. code-block:: bash
@@ -62,18 +62,18 @@ The test script supports either:
physical board, attach to the board's console stream, and reset the board.
Further details are described later.
-The usage of the command 'sudo' is not allowed in tests. Using elevated
+The usage of the command ``sudo`` is not allowed in tests. Using elevated
priviledges can lead to security concerns. Furthermore not all users may have
-administrator rights. Therefore the command 'sudo' must not be used in tests.
+administrator rights. Therefore the command ``sudo`` must not be used in tests.
To create disk images we have helper functions located in
-`test/py/tests/fs_helper.py` which shall be used in any tests that require
+``test/py/tests/fs_helper.py`` which shall be used in any tests that require
creating disk images.
Using a Python sandbox to provide requirements
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The recommended way to run the test suite, in order to ensure reproducibility
-is to use a Python sandbox such as `python -m venv` to set up the necessary
+is to use a Python sandbox such as ``python -m venv`` to set up the necessary
environment. This can be done via the following commands:
@@ -95,19 +95,19 @@ application), simply execute:
./test/py/test.py --bd sandbox --build
-The `--bd` option tells the test suite which board type is being tested. This
+The ``--bd`` option tells the test suite which board type is being tested. This
lets the test suite know which features the board has, and hence exactly what
can be tested.
-The `--build` option tells U-Boot to compile U-Boot. Alternatively, you may
+The ``--build`` option tells U-Boot to compile U-Boot. Alternatively, you may
omit this option and build U-Boot yourself, in whatever way you choose, before
running the test script.
The test script will attach to U-Boot, execute all valid tests for the board,
then print a summary of the test process. A complete log of the test session
-will be written to `${build_dir}/test-log.html`. This is best viewed in a web
+will be written to ``${build_dir}/test-log.html``. This is best viewed in a web
browser, but may be read directly as plain text, perhaps with the aid of the
-`html2text` utility.
+``html2text`` utility.
If sandbox crashes (e.g. with a segfault) you will see message like this::
@@ -134,23 +134,23 @@ First install support for parallel tests::
sudo apt install python3-pytest-xdist
-or:::
+or::
pip3 install pytest-xdist
-Then run the tests in parallel using the -n flag::
+Then run the tests in parallel using the ``-n`` flag::
test/py/test.py -B sandbox --build --build-dir /tmp/b/sandbox -q -k \
'not slow and not bootstd and not spi_flash' -n16
-You can also use `make pcheck` to run all tests in parallel. This uses a maximum
-of 16 threads, since the setup time is significant and there are under 1000
-tests.
+You can also use ``make pcheck`` to run all tests in parallel. This uses a
+maximum of 16 threads, since the setup time is significant and there are under
+1000 tests.
-Note that the `test-log.html` output does not work correctly at present with
+Note that the ``test-log.html`` output does not work correctly at present with
parallel testing. All the threads write to it at once, so it is garbled.
-Note that the `tools/` tests still run each tool's tests once after the other,
+Note that the ``tools/`` tests still run each tool's tests once after the other,
although within that, they do run in parallel. So for example, the buildman
tests run in parallel, then the binman tests run in parallel. There would be a
significant advantage to running them all in parallel together, but that would
@@ -163,12 +163,12 @@ Testing under a debugger
~~~~~~~~~~~~~~~~~~~~~~~~
If you need to run sandbox under a debugger, you may pass the command-line
-option `--gdbserver COMM`. This causes two things to happens:
+option ``--gdbserver COMM``. This causes two things to happens:
- Instead of running U-Boot directly, it will be run under gdbserver, with
- debug communication via the channel `COMM`. You can attach a debugger to the
- sandbox process in order to debug it. See `man gdbserver` and the example
- below for details of valid values for `COMM`.
+ debug communication via the channel ``COMM``. You can attach a debugger to the
+ sandbox process in order to debug it. See ``man gdbserver`` and the example
+ below for details of valid values for ``COMM``.
- All timeouts in tests are disabled, allowing U-Boot an arbitrary amount of
time to execute commands. This is useful if U-Boot is stopped at a breakpoint
during debugging.
@@ -187,7 +187,7 @@ Window 2:
gdb ./build-sandbox/u-boot -ex 'target remote localhost:1234'
-Alternatively, you could leave off the `-ex` option and type the command
+Alternatively, you could leave off the ``-ex`` option and type the command
manually into gdb once it starts.
You can use any debugger you wish, as long as it speaks the gdb remote
@@ -196,16 +196,17 @@ protocol, or any graphical wrapper around gdb.
Some tests deliberately cause the sandbox process to exit, e.g. to test the
reset command, or sandbox's CTRL-C handling. When this happens, you will need
to attach the debugger to the new sandbox instance. If these tests are not
-relevant to your debugging session, you can skip them using pytest's -k
+relevant to your debugging session, you can skip them using pytest's ``-k``
command-line option; see the next section.
Command-line options
--------------------
--board-type, --bd, -B
- set the type of the board to be tested. For example, `sandbox` or `seaboard`.
+ set the type of the board to be tested. For example, ``sandbox`` or
+ ``seaboard``.
---board-identity`, --id
+--board-identity, --id
sets the identity of the board to be tested. This allows differentiation
between multiple instances of the same type of physical board that are
attached to the same host machine. This parameter is not interpreted by th
@@ -215,15 +216,15 @@ Command-line options
--build
indicates that the test script should compile U-Boot itself before running
the tests. If using this option, make sure that any environment variables
- required by the build process are already set, such as `$CROSS_COMPILE`.
+ required by the build process are already set, such as ``$CROSS_COMPILE``.
--buildman
- indicates that `--build` should use buildman to build U-Boot. There is no need
- to set $CROSS_COMPILE` in this case since buildman handles it.
+ indicates that ``--build`` should use buildman to build U-Boot. There is no
+ need to set ``$CROSS_COMPILE`` in this case since buildman handles it.
--build-dir
sets the directory containing the compiled U-Boot binaries. If omitted, this
- is `${source_dir}/build-${board_type}`.
+ is ``${source_dir}/build-${board_type}``.
--result-dir
sets the directory to write results, such as log files, into.
@@ -266,10 +267,10 @@ Command-line options
<3.0s : 2.4s | 1
<7.5s : 6.1s | 1
-`pytest` also implements a number of its own command-line options. Commonly used
-options are mentioned below. Please see `pytest` documentation for complete
-details. Execute `py.test --version` for a brief summary. Note that U-Boot's
-test.py script passes all command-line arguments directly to `pytest` for
+pytest also implements a number of its own command-line options. Commonly used
+options are mentioned below. Please see pytest documentation for complete
+details. Execute ``py.test --version`` for a brief summary. Note that U-Boot's
+test.py script passes all command-line arguments directly to pytest for
processing.
-k
@@ -277,13 +278,13 @@ processing.
option takes a single argument which is used to filter test names. Simple
logical operators are supported. For example:
- - `'-k ums'` runs only tests with "ums" in their name.
- - `'-k ut_dm'` runs only tests with "ut_dm" in their name. Note that in this
+ - ``-k ums`` runs only tests with "ums" in their name.
+ - ``-k ut_dm`` runs only tests with "ut_dm" in their name. Note that in this
case, "ut_dm" is a parameter to a test rather than the test name. The full
test name is e.g. "test_ut[ut_dm_leak]".
- - `'-k not reset'` runs everything except tests with "reset" in their name.
- - `'-k ut or hush'` runs only tests with "ut" or "hush" in their name.
- - `'-k not (ut or hush)'` runs everything except tests with "ut" or "hush" in
+ - ``-k not reset`` runs everything except tests with "reset" in their name.
+ - ``-k ut or hush`` runs only tests with "ut" or "hush" in their name.
+ - ``-k not (ut or hush)`` runs everything except tests with "ut" or "hush" in
their name.
-s
@@ -297,7 +298,7 @@ The tools and techniques used to interact with real hardware will vary
radically between different host and target systems, and the whims of the user.
For this reason, the test suite does not attempt to directly interact with real
hardware in any way. Rather, it executes a standardized set of "hook" scripts
-via `$PATH`. These scripts implement certain actions on behalf of the test
+via ``$PATH``. These scripts implement certain actions on behalf of the test
suite. This keeps the test suite simple and isolated from system variances
unrelated to U-Boot features.
@@ -309,14 +310,14 @@ Environment variables
The following environment variables are set when running hook scripts:
-- `UBOOT_BOARD_TYPE` the board type being tested.
-- `UBOOT_BOARD_IDENTITY` the board identity being tested, or `na` if none was
- specified.
-- `UBOOT_SOURCE_DIR` the U-Boot source directory.
-- `UBOOT_TEST_PY_DIR` the full path to `test/py/` in the source directory.
-- `UBOOT_BUILD_DIR` the U-Boot build directory.
-- `UBOOT_RESULT_DIR` the test result directory.
-- `UBOOT_PERSISTENT_DATA_DIR` the test persistent data directory.
+- ``UBOOT_BOARD_TYPE`` the board type being tested.
+- ``UBOOT_BOARD_IDENTITY`` the board identity being tested, or ``na`` if none
+ was specified.
+- ``UBOOT_SOURCE_DIR`` the U-Boot source directory.
+- ``UBOOT_TEST_PY_DIR`` the full path to ``test/py/`` in the source directory.
+- ``UBOOT_BUILD_DIR`` the U-Boot build directory.
+- ``UBOOT_RESULT_DIR`` the test result directory.
+- ``UBOOT_PERSISTENT_DATA_DIR`` the test persistent data directory.
u-boot-test-console
'''''''''''''''''''
@@ -326,15 +327,15 @@ should be connected to the board's console. This process should continue to run
indefinitely, until killed. The test suite will run this script in parallel
with all other hooks.
-This script may be implemented e.g. by executing `cu`, `kermit`, `conmux`, etc.
-via exec().
+This script may be implemented e.g. by executing ``cu``, ``kermit``, ``conmux``,
+etc. via ``exec()``.
If you are able to run U-Boot under a hardware simulator such as QEMU, then
you would likely spawn that simulator from this script. However, note that
-`u-boot-test-reset` may be called multiple times per test script run, and must
+``u-boot-test-reset`` may be called multiple times per test script run, and must
cause U-Boot to start execution from scratch each time. Hopefully your
simulator includes a virtual reset button! If not, you can launch the
-simulator from `u-boot-test-reset` instead, while arranging for this console
+simulator from ``u-boot-test-reset`` instead, while arranging for this console
process to always communicate with the current simulator instance.
u-boot-test-flash
@@ -357,7 +358,7 @@ the following cases:
- The board allows U-Boot to be downloaded directly into RAM, and executed
from there. Use of this feature will reduce wear on the board's flash, so
may be preferable if available, and if cold boot testing of U-Boot is not
- required. If this feature is used, the `u-boot-test-reset` script should
+ required. If this feature is used, the ``u-boot-test-reset`` script should
perform this download, since the board could conceivably be reset multiple
times in a single test run.
@@ -386,8 +387,8 @@ to flash, pulsing the board's reset signal is likely all this script needs to
do. However, in some scenarios, this script may perform other actions. For
example, it may call out to some SoC- or board-specific vendor utility in order
to download the U-Boot binary directly into RAM and execute it. This would
-avoid the need for `u-boot-test-flash` to actually write U-Boot to flash, thus
-saving wear on the flash chip(s).
+avoid the need for ``u-boot-test-flash1`` to actually write U-Boot to flash,
+thus saving wear on the flash chip(s).
u-boot-test-release
'''''''''''''''''''
@@ -407,11 +408,11 @@ Board-type-specific configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Each board has a different configuration and behaviour. Many of these
-differences can be automatically detected by parsing the `.config` file in the
+differences can be automatically detected by parsing the ``.config`` file in the
build directory. However, some differences can't yet be handled automatically.
-For each board, an optional Python module `u_boot_board_${board_type}` may exist
-to provide board-specific information to the test script. Any global value
+For each board, an optional Python module ``u_boot_board_${board_type}`` may
+exist to provide board-specific information to the test script. Any global value
defined in these modules is available for use by any test function. The data
contained in these scripts must be purely derived from U-Boot source code.
Hence, these configuration files are part of the U-Boot source tree too.
@@ -425,14 +426,14 @@ U-Boot configuration may support USB device mode and USB Mass Storage, but this
can only be tested if a USB cable is connected between the board and the host
machine running the test script.
-For each board, optional Python modules `u_boot_boardenv_${board_type}` and
-`u_boot_boardenv_${board_type}_${board_identity}` may exist to provide
+For each board, optional Python modules ``u_boot_boardenv_${board_type}`` and
+``u_boot_boardenv_${board_type}_${board_identity}`` may exist to provide
board-specific and board-identity-specific information to the test script. Any
global value defined in these modules is available for use by any test
function. The data contained in these is specific to a particular user's
hardware configuration. Hence, these configuration files are not part of the
U-Boot source tree, and should be installed outside of the source tree. Users
-should set `$PYTHONPATH` prior to running the test script to allow these
+should set ``$PYTHONPATH`` prior to running the test script to allow these
modules to be loaded.
Board module parameter usage
@@ -443,29 +444,29 @@ module:
- none at present
-U-Boot `.config` feature usage
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+U-Boot ``.config`` feature usage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The test scripts rely on various U-Boot `.config` features, either directly in
+The test scripts rely on various U-Boot ``.config`` features, either directly in
order to test those features, or indirectly in order to query information from
the running U-Boot instance in order to test other features.
-One example is that testing of the `md` command requires knowledge of a RAM
+One example is that testing of the ``md`` command requires knowledge of a RAM
address to use for the test. This data is parsed from the output of the
-`bdinfo` command, and hence relies on CONFIG_CMD_BDI being enabled.
+``bdinfo`` command, and hence relies on CONFIG_CMD_BDI being enabled.
For a complete list of dependencies, please search the test scripts for
instances of:
-- `buildconfig.get(...`
-- `@pytest.mark.buildconfigspec(...`
-- `@pytest.mark.notbuildconfigspec(...`
+- ``buildconfig.get(...``
+- ``@pytest.mark.buildconfigspec(...``
+- ``@pytest.mark.notbuildconfigspec(...``
Complete invocation example
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Assuming that you have installed the hook scripts into $HOME/ubtest/bin, and
-any required environment configuration Python modules into $HOME/ubtest/py,
+Assuming that you have installed the hook scripts into ``$HOME/ubtest/bin``, and
+any required environment configuration Python modules into ``$HOME/ubtest/py``,
then you would likely invoke the test script as follows:
If U-Boot has already been built:
@@ -477,7 +478,7 @@ If U-Boot has already been built:
./test/py/test.py --bd seaboard
If you want the test script to compile U-Boot for you too, then you likely
-need to set `$CROSS_COMPILE` to allow this, and invoke the test script as
+need to set ``$CROSS_COMPILE`` to allow this, and invoke the test script as
follows:
.. code-block:: bash
@@ -501,47 +502,47 @@ Writing tests
Please refer to the pytest documentation for details of writing pytest tests.
Details specific to the U-Boot test suite are described below.
-A test fixture named `ubman` should be used by each test function. This
+A test fixture named ``ubman`` should be used by each test function. This
provides the means to interact with the U-Boot console, and retrieve board and
environment configuration information.
-The function `ubman.run_command()` executes a shell command on the
+The function ``ubman.run_command()`` executes a shell command on the
U-Boot console, and returns all output from that command. This allows
validation or interpretation of the command output. This function validates
that certain strings are not seen on the U-Boot console. These include shell
error messages and the U-Boot sign-on message (in order to detect unexpected
-board resets). See the source of `console_base.py` for a complete list of
+board resets). See the source of ``console_base.py`` for a complete list of
"bad" strings. Some test scenarios are expected to trigger these strings. Use
-`ubman.disable_check()` to temporarily disable checking for specific
-strings. See `test_unknown_cmd.py` for an example.
+``ubman.disable_check()`` to temporarily disable checking for specific
+strings. See ``test_unknown_cmd.py`` for an example.
Board- and board-environment configuration values may be accessed as sub-fields
-of the `ubman.config` object, for example
-`ubman.config.ram_base`.
+of the ``ubman.config`` object, for example
+``ubman.config.ram_base``.
-Build configuration values (from `.config`) may be accessed via the dictionary
-`ubman.config.buildconfig`, with keys equal to the Kconfig variable
+Build configuration values (from ``.config``) may be accessed via the dictionary
+``ubman.config.buildconfig``, with keys equal to the Kconfig variable
names.
-A required configuration setting can be defined via a buildconfigspec()
+A required configuration setting can be defined via a ``buildconfigspec()``
annotation. The name of the configuration option is specified in lower case. The
-following annotation for a test requires CONFIG_EFI_LOADER=y:
+following annotation for a test requires ``CONFIG_EFI_LOADER=y``:
.. code-block:: python
@pytest.mark.buildconfigspec('efi_loader')
Sometimes multiple configuration option supply the same functionality. If
-multiple arguments are passed to buildconfigspec(), only one of the
+multiple arguments are passed to ``buildconfigspec()``, only one of the
configuration options needs to be set. The following annotation requires that
-either of CONFIG_NET or CONFIG_NET_LWIP is set:
+either of ``CONFIG_NET`` or ``CONFIG_NET_LWIP`` is set:
.. code-block:: python
@pytest.mark.buildconfigspec('net', 'net lwip')
-The notbuildconfigspec() annotation can be used to require a configuration
-option not to be set. The following annotation requires CONFIG_RISCV=n:
+The ``notbuildconfigspec()`` annotation can be used to require a configuration
+option not to be set. The following annotation requires ``CONFIG_RISCV=n``:
.. code-block:: python
diff --git a/doc/develop/release_cycle.rst b/doc/develop/release_cycle.rst
index ebe92b6f189..37abe1c5040 100644
--- a/doc/develop/release_cycle.rst
+++ b/doc/develop/release_cycle.rst
@@ -1,4 +1,4 @@
-.. |next_ver| replace:: v2025.10
+.. |next_ver| replace:: v2026.01
Release Cycle
=============
@@ -53,15 +53,15 @@ Examples::
Current Status
--------------
-* U-Boot v2025.07 was released on Monday, 07 July 2025.
+* U-Boot v2025.10 was released on Monday, 06 October 2025.
-* The Merge Window for the next release (|next_ver|) is **closed** with the -rc1
- release on Monday, 28 July 2025.
+* The Merge Window for the next release (|next_ver|) is **open** until the -rc1
+ release on Monday, 27 October 2025.
* The next branch is now **open** with the -rc2 release on Monday, 11 August
2025.
-* Release "|next_ver|" is scheduled for Monday, 06 October 2025.
+* Release "|next_ver|" is scheduled for Monday, 05 January 2026.
Future Releases
---------------
@@ -69,29 +69,29 @@ Future Releases
.. The following commented out dates are for when release candidates are
planned to be tagged.
-For the next scheduled release, release candidates were made on::
+.. For the next scheduled release, release candidates were made on::
-* U-Boot |next_ver|-rc1 was released on Mon 28 July 2025.
+.. * U-Boot |next_ver|-rc1 was released on Mon 27 October 2025.
-* U-Boot |next_ver|-rc2 was released on Mon 11 August 2025.
+.. * U-Boot |next_ver|-rc2 was released on Mon 10 November 2025.
-* U-Boot |next_ver|-rc3 was released on Mon 25 August 2025.
+.. * U-Boot |next_ver|-rc3 was released on Mon 24 November 2025.
-* U-Boot |next_ver|-rc4 was released on Mon 08 September 2025.
+.. * U-Boot |next_ver|-rc4 was released on Mon 08 December 2025.
-* U-Boot |next_ver|-rc5 was released on Tue 23 September 2025.
+.. * U-Boot |next_ver|-rc5 was released on Tue 22 December 2025.
Please note that the following dates are planned only and may be deviated from
as needed.
-* "v2025.10": end of MW = Mon, Jul 28, 2025; release = Mon, Oct 06, 2025
-
* "v2026.01": end of MW = Mon, Oct 27, 2025; release = Mon, Jan 05, 2026
* "v2026.04": end of MW = Mon, Jan 26, 2026; release = Mon, Apr 06, 2026
* "v2026.07": end of MW = Mon, Apr 27, 2026; release = Mon, Jul 06, 2026
+* "v2026.10": end of MW = Mon, Jul 27, 2026; release = Mon, Oct 05, 2026
+
Previous Releases
-----------------
@@ -99,6 +99,8 @@ Note: these statistics are generated by our fork of `gitdm
<https://source.denx.de/u-boot/gitdm>`_, which was originally created by
Jonathan Corbet.
+* :doc:`statistics/u-boot-stats-v2025.10` which was released on 06 October 2025.
+
* :doc:`statistics/u-boot-stats-v2025.07` which was released on 07 July 2025.
* :doc:`statistics/u-boot-stats-v2025.04` which was released on 07 April 2025.
diff --git a/doc/develop/statistics/u-boot-stats-v2025.10.rst b/doc/develop/statistics/u-boot-stats-v2025.10.rst
new file mode 100644
index 00000000000..9588d174b6f
--- /dev/null
+++ b/doc/develop/statistics/u-boot-stats-v2025.10.rst
@@ -0,0 +1,814 @@
+:orphan:
+
+Release Statistics for U-Boot v2025.10
+======================================
+
+* Processed 1408 changesets from 189 developers
+
+* 25 employers found
+
+* A total of 248541 lines added, 98341 removed (delta 150200)
+
+.. table:: Developers with the most changesets
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Simon Glass 165 (11.7%)
+ Tom Rini 140 (9.9%)
+ Andrew Goodbody 105 (7.5%)
+ Marek Vasut 70 (5.0%)
+ Ilias Apalodimas 46 (3.3%)
+ Rasmus Villemoes 35 (2.5%)
+ Tim Harvey 28 (2.0%)
+ Andre Przywara 28 (2.0%)
+ Jerome Forissier 26 (1.8%)
+ Sam Protsenko 25 (1.8%)
+ Jonas Karlman 25 (1.8%)
+ Michal Simek 23 (1.6%)
+ Heinrich Schuchardt 22 (1.6%)
+ Yao Zi 21 (1.5%)
+ Quentin Schulz 19 (1.3%)
+ Alif Zakuan Yuslaimi 19 (1.3%)
+ Tingting Meng 18 (1.3%)
+ Dinesh Maniyam 17 (1.2%)
+ Ion Agorria 14 (1.0%)
+ Venkatesh Yadav Abbarapu 13 (0.9%)
+ Bryan Brattlof 13 (0.9%)
+ Martin Schwan 12 (0.9%)
+ Patrice Chotard 11 (0.8%)
+ E Shattow 11 (0.8%)
+ Wadim Egorov 11 (0.8%)
+ Casey Connolly 10 (0.7%)
+ Balaji Selvanathan 10 (0.7%)
+ Yannic Moog 10 (0.7%)
+ Aristo Chen 10 (0.7%)
+ Emanuele Ghidoli 10 (0.7%)
+ Patrick Delaunay 9 (0.6%)
+ Anshul Dalal 9 (0.6%)
+ Adriano Carvalho 9 (0.6%)
+ Anurag Dutta 9 (0.6%)
+ Varadarajan Narayanan 9 (0.6%)
+ Sughosh Ganu 9 (0.6%)
+ Dario Binacchi 9 (0.6%)
+ Ye Li 8 (0.6%)
+ Leo Yu-Chi Liang 8 (0.6%)
+ Moteen Shah 8 (0.6%)
+ Jamie Gibbons 7 (0.5%)
+ Peng Fan 7 (0.5%)
+ Michael Trimarchi 7 (0.5%)
+ Lukasz Czechowski 7 (0.5%)
+ Holger Brunck 7 (0.5%)
+ Christian Marangi 7 (0.5%)
+ Aswin Murugan 7 (0.5%)
+ Zixun LI 7 (0.5%)
+ Kongyang Liu 7 (0.5%)
+ Primoz Fiser 6 (0.4%)
+ Ryan Wanner 6 (0.4%)
+ Pieter Van Trappen 6 (0.4%)
+ Alice Guo 5 (0.4%)
+ Fabio Estevam 5 (0.4%)
+ Henrik Grimler 5 (0.4%)
+ Svyatoslav Ryhel 5 (0.4%)
+ João Paulo Gonçalves 5 (0.4%)
+ Naresh Kumar Ravulapalli 5 (0.4%)
+ Manorit Chawdhry 5 (0.4%)
+ Javier Martinez Canillas 5 (0.4%)
+ Ying-Chun Liu (PaulLiu) 5 (0.4%)
+ Luca Weiss 5 (0.4%)
+ Manikandan Muralidharan 5 (0.4%)
+ Yegor Yefremov 4 (0.3%)
+ Neha Malcom Francis 4 (0.3%)
+ david regan 4 (0.3%)
+ Ben Dooks 4 (0.3%)
+ Martin Herren 4 (0.3%)
+ Philip Molloy 4 (0.3%)
+ Varshini Rajendran 4 (0.3%)
+ Mikhail Kshevetskiy 4 (0.3%)
+ Weijie Gao 4 (0.3%)
+ Hrushikesh Salunke 4 (0.3%)
+ Lukasz Majewski 4 (0.3%)
+ Beleswar Padhi 4 (0.3%)
+ Gabriel Fernandez 4 (0.3%)
+ Conor Dooley 3 (0.2%)
+ Tony Dinh 3 (0.2%)
+ Heiko Thiery 3 (0.2%)
+ Paul Kocialkowski 3 (0.2%)
+ Mark Kettenis 3 (0.2%)
+ Shiji Yang 3 (0.2%)
+ David Zang 3 (0.2%)
+ Cheick Traore 3 (0.2%)
+ Frieder Schrempf 3 (0.2%)
+ Fiona Klute 3 (0.2%)
+ Padmarao Begari 3 (0.2%)
+ Magnus Damm 3 (0.2%)
+ George Chan 3 (0.2%)
+ Sukrut Bellary 3 (0.2%)
+ Sean Edmond 3 (0.2%)
+ Neil Armstrong 2 (0.1%)
+ Mattijs Korpershoek 2 (0.1%)
+ Heiko Schocher 2 (0.1%)
+ Raymond Mao 2 (0.1%)
+ Udit Kumar 2 (0.1%)
+ Jan Kiszka 2 (0.1%)
+ Heiko Stuebner 2 (0.1%)
+ Frank Wang 2 (0.1%)
+ Da Xue 2 (0.1%)
+ Christophe Kerello 2 (0.1%)
+ Junhui Liu 2 (0.1%)
+ Peter Robinson 2 (0.1%)
+ Jim Liu 2 (0.1%)
+ Jernej Skrabec 2 (0.1%)
+ Antonio Borneo 2 (0.1%)
+ Hugo Villeneuve 2 (0.1%)
+ Vitor Soares 2 (0.1%)
+ Tomas Alvarez Vanoli 2 (0.1%)
+ Eoin Dickson 2 (0.1%)
+ Romain Gantois 2 (0.1%)
+ Shmuel Leib Melamud 2 (0.1%)
+ Adriano Cordova 2 (0.1%)
+ Nathan Morrisson 2 (0.1%)
+ Thomas Bonnefille 1 (0.1%)
+ Javier Tia 1 (0.1%)
+ Kory Maincent 1 (0.1%)
+ Ben Wolsieffer 1 (0.1%)
+ Daniel P. Berrangé 1 (0.1%)
+ Jiaxun Yang 1 (0.1%)
+ Maksim Kiselev 1 (0.1%)
+ Alexander Dahl 1 (0.1%)
+ Ricardo Simoes 1 (0.1%)
+ Sidharth Seela 1 (0.1%)
+ Mathieu Othacehe 1 (0.1%)
+ Kunihiko Hayashi 1 (0.1%)
+ Christoph Niedermaier 1 (0.1%)
+ Prasanth Babu Mantena 1 (0.1%)
+ Patrick Rudolph 1 (0.1%)
+ Boon Khai Ng 1 (0.1%)
+ Niu Zhihong 1 (0.1%)
+ Diederik de Haas 1 (0.1%)
+ Jianwei Zheng 1 (0.1%)
+ Marius Dinu 1 (0.1%)
+ Jakob Unterwurzacher 1 (0.1%)
+ Jon Lin 1 (0.1%)
+ Chris Morgan 1 (0.1%)
+ Alex Shumsky 1 (0.1%)
+ Siddharth Vadapalli 1 (0.1%)
+ Frank Böwingloh 1 (0.1%)
+ Miquel Raynal 1 (0.1%)
+ Jonas Schwöbel 1 (0.1%)
+ Max Merchel 1 (0.1%)
+ Stefan Roese 1 (0.1%)
+ Lad Prabhakar 1 (0.1%)
+ Sumit Garg 1 (0.1%)
+ Ramin Moussavi 1 (0.1%)
+ Eric Anderson 1 (0.1%)
+ Tien Fong Chee 1 (0.1%)
+ Takahiro Kuwano 1 (0.1%)
+ Greg Malysa 1 (0.1%)
+ Mikko Rapeli 1 (0.1%)
+ Christian Speich 1 (0.1%)
+ Clément Le Goffic 1 (0.1%)
+ Justin Swartz 1 (0.1%)
+ Andrew Davis 1 (0.1%)
+ Mikhail Kalashnikov 1 (0.1%)
+ Enric Balletbo i Serra 1 (0.1%)
+ Rebecca Cran 1 (0.1%)
+ Iulian Banaga 1 (0.1%)
+ Jaehoon Chung 1 (0.1%)
+ Ariel D'Alessandro 1 (0.1%)
+ Francesco Dolcini 1 (0.1%)
+ Gokul Praveen 1 (0.1%)
+ Anatolij Gustschin 1 (0.1%)
+ Leonard Anderweit 1 (0.1%)
+ Lucas Dietrich 1 (0.1%)
+ Rui Miguel Silva 1 (0.1%)
+ Frank Wunderlich 1 (0.1%)
+ MD Danish Anwar 1 (0.1%)
+ Alexander Stein 1 (0.1%)
+ Tobias Olausson 1 (0.1%)
+ Michael Walle 1 (0.1%)
+ Chuanhong Guo 1 (0.1%)
+ Giulio Benetti 1 (0.1%)
+ Vignesh Raghavendra 1 (0.1%)
+ 牛 志宏 1 (0.1%)
+ Jamin Lin 1 (0.1%)
+ Cody Eksal 1 (0.1%)
+ Eric Schikschneit 1 (0.1%)
+ Richard Weinberger 1 (0.1%)
+ Simeon Marijon 1 (0.1%)
+ Valentin Caron 1 (0.1%)
+ Parth Pancholi 1 (0.1%)
+ Anis Chali 1 (0.1%)
+ Anton Moryakov 1 (0.1%)
+ SkyLake.Huang 1 (0.1%)
+ Alexander Sverdlin 1 (0.1%)
+ Johannes Krottmayer 1 (0.1%)
+ ==================================== =====
+
+
+.. table:: Developers with the most changed lines
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Tom Rini 192200 (63.3%)
+ Simon Glass 13843 (4.6%)
+ Neha Malcom Francis 8502 (2.8%)
+ Parth Pancholi 8340 (2.7%)
+ Marek Vasut 6133 (2.0%)
+ Dinesh Maniyam 5848 (1.9%)
+ Fabio Estevam 5363 (1.8%)
+ Michal Simek 4628 (1.5%)
+ Ion Agorria 3850 (1.3%)
+ Andre Przywara 2617 (0.9%)
+ Kongyang Liu 2532 (0.8%)
+ Gabriel Fernandez 2197 (0.7%)
+ Tingting Meng 2182 (0.7%)
+ Ryan Wanner 1919 (0.6%)
+ Jernej Skrabec 1795 (0.6%)
+ Tim Harvey 1769 (0.6%)
+ Cody Eksal 1722 (0.6%)
+ Paul Kocialkowski 1715 (0.6%)
+ Svyatoslav Ryhel 1666 (0.5%)
+ Sam Protsenko 1560 (0.5%)
+ Yao Zi 1484 (0.5%)
+ Varshini Rajendran 1374 (0.5%)
+ Lukasz Majewski 1332 (0.4%)
+ Ilias Apalodimas 1292 (0.4%)
+ Jonas Schwöbel 1203 (0.4%)
+ Neil Armstrong 1054 (0.3%)
+ Anshul Dalal 1007 (0.3%)
+ Alif Zakuan Yuslaimi 938 (0.3%)
+ Anis Chali 921 (0.3%)
+ Jerome Forissier 918 (0.3%)
+ Patrice Chotard 803 (0.3%)
+ Varadarajan Narayanan 802 (0.3%)
+ Sughosh Ganu 791 (0.3%)
+ Michael Trimarchi 775 (0.3%)
+ Simeon Marijon 677 (0.2%)
+ Martin Schwan 670 (0.2%)
+ Bryan Brattlof 640 (0.2%)
+ Leo Yu-Chi Liang 602 (0.2%)
+ Heinrich Schuchardt 595 (0.2%)
+ Andrew Goodbody 585 (0.2%)
+ Frieder Schrempf 538 (0.2%)
+ Jonas Karlman 536 (0.2%)
+ Hrushikesh Salunke 536 (0.2%)
+ Rasmus Villemoes 501 (0.2%)
+ Jamie Gibbons 492 (0.2%)
+ Alice Guo 445 (0.1%)
+ Casey Connolly 436 (0.1%)
+ Anurag Dutta 436 (0.1%)
+ Dario Binacchi 435 (0.1%)
+ Fiona Klute 429 (0.1%)
+ Ying-Chun Liu (PaulLiu) 408 (0.1%)
+ Aristo Chen 368 (0.1%)
+ Aswin Murugan 352 (0.1%)
+ Moteen Shah 333 (0.1%)
+ Balaji Selvanathan 326 (0.1%)
+ Padmarao Begari 326 (0.1%)
+ Ariel D'Alessandro 326 (0.1%)
+ Eoin Dickson 315 (0.1%)
+ Quentin Schulz 306 (0.1%)
+ Manikandan Muralidharan 296 (0.1%)
+ Sukrut Bellary 254 (0.1%)
+ Mikhail Kalashnikov 252 (0.1%)
+ Da Xue 227 (0.1%)
+ Yannic Moog 225 (0.1%)
+ Pieter Van Trappen 223 (0.1%)
+ Heiko Thiery 207 (0.1%)
+ Peng Fan 202 (0.1%)
+ Shmuel Leib Melamud 201 (0.1%)
+ João Paulo Gonçalves 192 (0.1%)
+ Chuanhong Guo 187 (0.1%)
+ Christian Marangi 181 (0.1%)
+ E Shattow 178 (0.1%)
+ Magnus Damm 178 (0.1%)
+ Wadim Egorov 177 (0.1%)
+ Jamin Lin 175 (0.1%)
+ Patrick Delaunay 147 (0.0%)
+ Jon Lin 147 (0.0%)
+ Javier Martinez Canillas 145 (0.0%)
+ Beleswar Padhi 136 (0.0%)
+ Adriano Carvalho 133 (0.0%)
+ Niu Zhihong 133 (0.0%)
+ Lukasz Czechowski 127 (0.0%)
+ Greg Malysa 112 (0.0%)
+ Jianwei Zheng 102 (0.0%)
+ Chris Morgan 100 (0.0%)
+ Zixun LI 97 (0.0%)
+ Junhui Liu 94 (0.0%)
+ Sean Edmond 85 (0.0%)
+ Holger Brunck 76 (0.0%)
+ Leonard Anderweit 75 (0.0%)
+ Conor Dooley 74 (0.0%)
+ Mikhail Kshevetskiy 65 (0.0%)
+ Emanuele Ghidoli 64 (0.0%)
+ Primoz Fiser 63 (0.0%)
+ Venkatesh Yadav Abbarapu 60 (0.0%)
+ Cheick Traore 56 (0.0%)
+ Valentin Caron 54 (0.0%)
+ Frank Wang 52 (0.0%)
+ Weijie Gao 50 (0.0%)
+ Javier Tia 48 (0.0%)
+ Ye Li 44 (0.0%)
+ Ben Dooks 43 (0.0%)
+ Tony Dinh 41 (0.0%)
+ MD Danish Anwar 41 (0.0%)
+ david regan 40 (0.0%)
+ Jim Liu 39 (0.0%)
+ Manorit Chawdhry 38 (0.0%)
+ Vitor Soares 38 (0.0%)
+ Martin Herren 35 (0.0%)
+ Antonio Borneo 35 (0.0%)
+ Christoph Niedermaier 33 (0.0%)
+ Clément Le Goffic 33 (0.0%)
+ Michael Walle 33 (0.0%)
+ Henrik Grimler 28 (0.0%)
+ Romain Gantois 28 (0.0%)
+ Siddharth Vadapalli 28 (0.0%)
+ Eric Schikschneit 26 (0.0%)
+ Heiko Stuebner 25 (0.0%)
+ George Chan 24 (0.0%)
+ Adriano Cordova 24 (0.0%)
+ Udit Kumar 23 (0.0%)
+ Naresh Kumar Ravulapalli 20 (0.0%)
+ Jakob Unterwurzacher 20 (0.0%)
+ Max Merchel 20 (0.0%)
+ Luca Weiss 19 (0.0%)
+ Heiko Schocher 19 (0.0%)
+ Peter Robinson 19 (0.0%)
+ Christophe Kerello 16 (0.0%)
+ Alex Shumsky 14 (0.0%)
+ Miquel Raynal 14 (0.0%)
+ Sumit Garg 13 (0.0%)
+ Richard Weinberger 13 (0.0%)
+ Johannes Krottmayer 13 (0.0%)
+ Yegor Yefremov 12 (0.0%)
+ Ramin Moussavi 12 (0.0%)
+ Mark Kettenis 11 (0.0%)
+ 牛 志宏 11 (0.0%)
+ Mattijs Korpershoek 10 (0.0%)
+ Hugo Villeneuve 10 (0.0%)
+ Tomas Alvarez Vanoli 10 (0.0%)
+ Sidharth Seela 10 (0.0%)
+ Iulian Banaga 10 (0.0%)
+ Philip Molloy 9 (0.0%)
+ Stefan Roese 9 (0.0%)
+ Lad Prabhakar 9 (0.0%)
+ Shiji Yang 8 (0.0%)
+ Giulio Benetti 8 (0.0%)
+ Jiaxun Yang 7 (0.0%)
+ Diederik de Haas 7 (0.0%)
+ Raymond Mao 6 (0.0%)
+ Jan Kiszka 6 (0.0%)
+ Boon Khai Ng 6 (0.0%)
+ Jaehoon Chung 6 (0.0%)
+ Lucas Dietrich 6 (0.0%)
+ Frank Wunderlich 6 (0.0%)
+ Anton Moryakov 6 (0.0%)
+ Mikko Rapeli 5 (0.0%)
+ Enric Balletbo i Serra 5 (0.0%)
+ Alexander Dahl 4 (0.0%)
+ Justin Swartz 4 (0.0%)
+ Francesco Dolcini 4 (0.0%)
+ Anatolij Gustschin 4 (0.0%)
+ Alexander Sverdlin 4 (0.0%)
+ David Zang 3 (0.0%)
+ Thomas Bonnefille 3 (0.0%)
+ Ricardo Simoes 3 (0.0%)
+ Mathieu Othacehe 3 (0.0%)
+ Prasanth Babu Mantena 3 (0.0%)
+ Tien Fong Chee 3 (0.0%)
+ Takahiro Kuwano 3 (0.0%)
+ Gokul Praveen 3 (0.0%)
+ Nathan Morrisson 2 (0.0%)
+ Kory Maincent 2 (0.0%)
+ Marius Dinu 2 (0.0%)
+ Tobias Olausson 2 (0.0%)
+ SkyLake.Huang 2 (0.0%)
+ Ben Wolsieffer 1 (0.0%)
+ Daniel P. Berrangé 1 (0.0%)
+ Maksim Kiselev 1 (0.0%)
+ Kunihiko Hayashi 1 (0.0%)
+ Patrick Rudolph 1 (0.0%)
+ Frank Böwingloh 1 (0.0%)
+ Eric Anderson 1 (0.0%)
+ Christian Speich 1 (0.0%)
+ Andrew Davis 1 (0.0%)
+ Rebecca Cran 1 (0.0%)
+ Rui Miguel Silva 1 (0.0%)
+ Alexander Stein 1 (0.0%)
+ Vignesh Raghavendra 1 (0.0%)
+ ==================================== =====
+
+
+.. table:: Developers with the most lines removed
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Michal Simek 4134 (4.2%)
+ Paul Kocialkowski 1710 (1.7%)
+ Frieder Schrempf 530 (0.5%)
+ Bryan Brattlof 357 (0.4%)
+ Kongyang Liu 351 (0.4%)
+ Heiko Thiery 202 (0.2%)
+ Greg Malysa 109 (0.1%)
+ Leonard Anderweit 55 (0.1%)
+ Junhui Liu 48 (0.0%)
+ Andrew Goodbody 38 (0.0%)
+ Yannic Moog 22 (0.0%)
+ Udit Kumar 22 (0.0%)
+ Primoz Fiser 18 (0.0%)
+ Martin Herren 18 (0.0%)
+ E Shattow 14 (0.0%)
+ Sumit Garg 13 (0.0%)
+ Anurag Dutta 11 (0.0%)
+ Henrik Grimler 9 (0.0%)
+ Lad Prabhakar 9 (0.0%)
+ Max Merchel 8 (0.0%)
+ Philip Molloy 7 (0.0%)
+ Giulio Benetti 7 (0.0%)
+ Pieter Van Trappen 3 (0.0%)
+ Jan Kiszka 3 (0.0%)
+ Alexander Dahl 3 (0.0%)
+ Prasanth Babu Mantena 3 (0.0%)
+ Hugo Villeneuve 2 (0.0%)
+ Enric Balletbo i Serra 2 (0.0%)
+ SkyLake.Huang 2 (0.0%)
+ Anatolij Gustschin 1 (0.0%)
+ Kunihiko Hayashi 1 (0.0%)
+ Vignesh Raghavendra 1 (0.0%)
+ ==================================== =====
+
+
+.. table:: Developers with the most signoffs (total 289)
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Casey Connolly 39 (13.5%)
+ Michal Simek 31 (10.7%)
+ Minkyu Kang 24 (8.3%)
+ Ilias Apalodimas 21 (7.3%)
+ Alif Zakuan Yuslaimi 17 (5.9%)
+ Mattijs Korpershoek 15 (5.2%)
+ Patrice Chotard 14 (4.8%)
+ Peng Fan 10 (3.5%)
+ Svyatoslav Ryhel 10 (3.5%)
+ Junhui Liu 7 (2.4%)
+ Chen-Yu Tsai 7 (2.4%)
+ Alexandre Torgue 7 (2.4%)
+ Heiko Stuebner 7 (2.4%)
+ Michael Trimarchi 7 (2.4%)
+ Randolph Sheng-Kai Lin 6 (2.1%)
+ Andre Przywara 5 (1.7%)
+ Caleb Connolly 4 (1.4%)
+ Tien Fong Chee 4 (1.4%)
+ Jonas Karlman 4 (1.4%)
+ Tom Rini 4 (1.4%)
+ Jerome Forissier 3 (1.0%)
+ Christian Hewitt 2 (0.7%)
+ Romain Sioen 2 (0.7%)
+ Jacky Bai 2 (0.7%)
+ Prasad Kummari 2 (0.7%)
+ Balamanikandan Gunasundar 2 (0.7%)
+ Antonio Borneo 2 (0.7%)
+ Holger Brunck 2 (0.7%)
+ Lukasz Czechowski 2 (0.7%)
+ Wadim Egorov 2 (0.7%)
+ Alice Guo 2 (0.7%)
+ Varshini Rajendran 2 (0.7%)
+ Henrik Grimler 1 (0.3%)
+ Mark Jonas 1 (0.3%)
+ Lee Jones 1 (0.3%)
+ Jérémie Dautheribes 1 (0.3%)
+ Stanley Chu 1 (0.3%)
+ Eugen Hristev 1 (0.3%)
+ Greg Kroah-Hartman 1 (0.3%)
+ Jonathan Stroud 1 (0.3%)
+ Ashok Reddy Soma 1 (0.3%)
+ Tejas Bhumkar 1 (0.3%)
+ Paul Sajna 1 (0.3%)
+ Sam Shih 1 (0.3%)
+ Tomas Alvarez Vanoli 1 (0.3%)
+ Boon Khai Ng 1 (0.3%)
+ Vitor Soares 1 (0.3%)
+ Valentin Caron 1 (0.3%)
+ Manikandan Muralidharan 1 (0.3%)
+ Heinrich Schuchardt 1 (0.3%)
+ Varadarajan Narayanan 1 (0.3%)
+ Fabio Estevam 1 (0.3%)
+ Simon Glass 1 (0.3%)
+ ==================================== =====
+
+
+.. table:: Developers with the most reviews (total 605)
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Kever Yang 50 (8.3%)
+ Tien Fong Chee 46 (7.6%)
+ Patrice Chotard 44 (7.3%)
+ Ilias Apalodimas 39 (6.4%)
+ Peng Fan 36 (6.0%)
+ Tom Rini 29 (4.8%)
+ Leo Yu-Chi Liang 28 (4.6%)
+ Mattijs Korpershoek 26 (4.3%)
+ Simon Glass 25 (4.1%)
+ Quentin Schulz 23 (3.8%)
+ Marek Vasut 22 (3.6%)
+ Casey Connolly 20 (3.3%)
+ Neil Armstrong 18 (3.0%)
+ Heinrich Schuchardt 16 (2.6%)
+ Stefan Roese 16 (2.6%)
+ Patrick Delaunay 15 (2.5%)
+ Neha Malcom Francis 14 (2.3%)
+ Bryan Brattlof 13 (2.1%)
+ Jerome Forissier 12 (2.0%)
+ Peter Robinson 8 (1.3%)
+ Svyatoslav Ryhel 7 (1.2%)
+ Sumit Garg 7 (1.2%)
+ Michael Trimarchi 6 (1.0%)
+ Jernej Skrabec 6 (1.0%)
+ Eugen Hristev 5 (0.8%)
+ Udit Kumar 5 (0.8%)
+ Sam Protsenko 5 (0.8%)
+ Dhruva Gole 4 (0.7%)
+ Anshul Dalal 4 (0.7%)
+ Andre Przywara 3 (0.5%)
+ Fabio Estevam 3 (0.5%)
+ Andrew Goodbody 3 (0.5%)
+ Rob Herring (Arm)" 3 (0.5%)
+ Anand Moon 3 (0.5%)
+ Heiko Schocher 3 (0.5%)
+ Christoph Niedermaier 3 (0.5%)
+ Tony Dinh 3 (0.5%)
+ Jonas Karlman 2 (0.3%)
+ Tudor Ambarus 2 (0.3%)
+ Rui Miguel Silva 2 (0.3%)
+ Javier Martinez Canillas 2 (0.3%)
+ Minkyu Kang 1 (0.2%)
+ Junhui Liu 1 (0.2%)
+ Alice Guo 1 (0.2%)
+ Greg Malysa 1 (0.2%)
+ Prasanth Babu Mantena 1 (0.2%)
+ Francesco Dolcini 1 (0.2%)
+ Andrew Davis 1 (0.2%)
+ Christophe ROULLIER 1 (0.2%)
+ Paul Barker 1 (0.2%)
+ Krzysztof Kozlowski 1 (0.2%)
+ Gao Xiang 1 (0.2%)
+ Aniket Limaye 1 (0.2%)
+ Wolfgang Wallner 1 (0.2%)
+ Martyn Welch 1 (0.2%)
+ Viacheslav Bocharov 1 (0.2%)
+ Manorit Chawdhry 1 (0.2%)
+ Mark Kettenis 1 (0.2%)
+ Miquel Raynal 1 (0.2%)
+ Siddharth Vadapalli 1 (0.2%)
+ Weijie Gao 1 (0.2%)
+ Venkatesh Yadav Abbarapu 1 (0.2%)
+ Conor Dooley 1 (0.2%)
+ Martin Schwan 1 (0.2%)
+ Lukasz Majewski 1 (0.2%)
+ ==================================== =====
+
+
+.. table:: Developers with the most test credits (total 44)
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Peter Robinson 8 (18.2%)
+ Wadim Egorov 7 (15.9%)
+ Ilias Apalodimas 2 (4.5%)
+ Heinrich Schuchardt 2 (4.5%)
+ Bryan Brattlof 2 (4.5%)
+ Anshul Dalal 2 (4.5%)
+ Christoph Niedermaier 2 (4.5%)
+ Judith Mendez 2 (4.5%)
+ Mikko Rapeli 2 (4.5%)
+ Tim Harvey 2 (4.5%)
+ Patrice Chotard 1 (2.3%)
+ Mattijs Korpershoek 1 (2.3%)
+ Quentin Schulz 1 (2.3%)
+ Marek Vasut 1 (2.3%)
+ Fabio Estevam 1 (2.3%)
+ Alice Guo 1 (2.3%)
+ Martin Schwan 1 (2.3%)
+ Michal Simek 1 (2.3%)
+ Paul Sajna 1 (2.3%)
+ Raffaele Tranquillini 1 (2.3%)
+ Adam Ford 1 (2.3%)
+ Alexey Minnekhanov 1 (2.3%)
+ Petr Štetiar 1 (2.3%)
+ ==================================== =====
+
+
+.. table:: Developers who gave the most tested-by credits (total 44)
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Kongyang Liu 7 (15.9%)
+ Martin Schwan 6 (13.6%)
+ Ilias Apalodimas 2 (4.5%)
+ Tom Rini 2 (4.5%)
+ Sam Protsenko 2 (4.5%)
+ Romain Gantois 2 (4.5%)
+ Rasmus Villemoes 2 (4.5%)
+ Ying-Chun Liu (PaulLiu) 2 (4.5%)
+ Yao Zi 2 (4.5%)
+ Tim Harvey 1 (2.3%)
+ Marek Vasut 1 (2.3%)
+ Alice Guo 1 (2.3%)
+ Casey Connolly 1 (2.3%)
+ Neil Armstrong 1 (2.3%)
+ Patrick Delaunay 1 (2.3%)
+ Svyatoslav Ryhel 1 (2.3%)
+ Michael Trimarchi 1 (2.3%)
+ Andrew Goodbody 1 (2.3%)
+ Junhui Liu 1 (2.3%)
+ Manorit Chawdhry 1 (2.3%)
+ Heiko Stuebner 1 (2.3%)
+ Leonard Anderweit 1 (2.3%)
+ Yannic Moog 1 (2.3%)
+ George Chan 1 (2.3%)
+ Christian Marangi 1 (2.3%)
+ Sughosh Ganu 1 (2.3%)
+ ==================================== =====
+
+
+.. table:: Developers with the most report credits (total 12)
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Simon Glass 2 (16.7%)
+ Tim Harvey 1 (8.3%)
+ Andrew Goodbody 1 (8.3%)
+ Mikko Rapeli 1 (8.3%)
+ Michal Simek 1 (8.3%)
+ Javier Martinez Canillas 1 (8.3%)
+ Alexander Dahl 1 (8.3%)
+ Alex Bennée 1 (8.3%)
+ Hal Feng 1 (8.3%)
+ Hiroyuki Saito 1 (8.3%)
+ Adriano Carvalho 1 (8.3%)
+ ==================================== =====
+
+
+.. table:: Developers who gave the most report credits (total 12)
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Yannic Moog 2 (16.7%)
+ Heinrich Schuchardt 2 (16.7%)
+ Ilias Apalodimas 1 (8.3%)
+ Anshul Dalal 1 (8.3%)
+ Neha Malcom Francis 1 (8.3%)
+ Jerome Forissier 1 (8.3%)
+ E Shattow 1 (8.3%)
+ Daniel P. Berrangé 1 (8.3%)
+ Takahiro Kuwano 1 (8.3%)
+ Ye Li 1 (8.3%)
+ ==================================== =====
+
+
+.. table:: Top changeset contributors by employer
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ (Unknown) 530 (37.6%)
+ Linaro 233 (16.5%)
+ Google LLC 165 (11.7%)
+ Konsulko Group 140 (9.9%)
+ Texas Instruments 64 (4.5%)
+ Renesas Electronics 44 (3.1%)
+ AMD 39 (2.8%)
+ Phytec 34 (2.4%)
+ ST Microelectronics 34 (2.4%)
+ ARM 28 (2.0%)
+ NXP 20 (1.4%)
+ Toradex 19 (1.3%)
+ Amarula Solutions 16 (1.1%)
+ Red Hat 8 (0.6%)
+ Bootlin 5 (0.4%)
+ DENX Software Engineering 5 (0.4%)
+ Analog Devices 4 (0.3%)
+ Broadcom 4 (0.3%)
+ Rockchip 4 (0.3%)
+ BayLibre SAS 3 (0.2%)
+ Intel 3 (0.2%)
+ Siemens 3 (0.2%)
+ Collabora Ltd. 1 (0.1%)
+ Samsung 1 (0.1%)
+ Socionext Inc. 1 (0.1%)
+ ==================================== =====
+
+
+.. table:: Top lines changed by employer
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ Konsulko Group 192200 (63.3%)
+ (Unknown) 49460 (16.3%)
+ Google LLC 13843 (4.6%)
+ Texas Instruments 11728 (3.9%)
+ Toradex 8638 (2.8%)
+ Linaro 7104 (2.3%)
+ AMD 5014 (1.7%)
+ ST Microelectronics 4018 (1.3%)
+ Renesas Electronics 3149 (1.0%)
+ ARM 2617 (0.9%)
+ DENX Software Engineering 1342 (0.4%)
+ Amarula Solutions 1210 (0.4%)
+ Phytec 1147 (0.4%)
+ NXP 691 (0.2%)
+ Red Hat 347 (0.1%)
+ Collabora Ltd. 326 (0.1%)
+ Rockchip 301 (0.1%)
+ BayLibre SAS 254 (0.1%)
+ Bootlin 47 (0.0%)
+ Broadcom 40 (0.0%)
+ Siemens 10 (0.0%)
+ Analog Devices 9 (0.0%)
+ Intel 7 (0.0%)
+ Samsung 6 (0.0%)
+ Socionext Inc. 1 (0.0%)
+ ==================================== =====
+
+
+.. table:: Employers with the most signoffs (total 289)
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ (Unknown) 100 (34.6%)
+ Linaro 68 (23.5%)
+ AMD 36 (12.5%)
+ ST Microelectronics 24 (8.3%)
+ Samsung 24 (8.3%)
+ NXP 14 (4.8%)
+ Amarula Solutions 7 (2.4%)
+ ARM 5 (1.7%)
+ Konsulko Group 4 (1.4%)
+ Phytec 2 (0.7%)
+ Google LLC 1 (0.3%)
+ Toradex 1 (0.3%)
+ Bootlin 1 (0.3%)
+ Bosch 1 (0.3%)
+ Canonical 1 (0.3%)
+ ==================================== =====
+
+
+.. table:: Employers with the most hackers (total 192)
+ :widths: auto
+
+ ==================================== =====
+ Name Count
+ ==================================== =====
+ (Unknown) 112 (58.3%)
+ Texas Instruments 15 (7.8%)
+ Linaro 12 (6.2%)
+ ST Microelectronics 9 (4.7%)
+ Toradex 5 (2.6%)
+ Phytec 4 (2.1%)
+ Bootlin 4 (2.1%)
+ AMD 3 (1.6%)
+ NXP 3 (1.6%)
+ Red Hat 3 (1.6%)
+ Rockchip 3 (1.6%)
+ Amarula Solutions 2 (1.0%)
+ Renesas Electronics 2 (1.0%)
+ DENX Software Engineering 2 (1.0%)
+ Siemens 2 (1.0%)
+ Intel 2 (1.0%)
+ Samsung 1 (0.5%)
+ ARM 1 (0.5%)
+ Konsulko Group 1 (0.5%)
+ Google LLC 1 (0.5%)
+ Collabora Ltd. 1 (0.5%)
+ BayLibre SAS 1 (0.5%)
+ Broadcom 1 (0.5%)
+ Analog Devices 1 (0.5%)
+ Socionext Inc. 1 (0.5%)
+ ==================================== =====
diff --git a/drivers/clk/ti/Kconfig b/drivers/clk/ti/Kconfig
index fbcdefd889a..bcf3976a09f 100644
--- a/drivers/clk/ti/Kconfig
+++ b/drivers/clk/ti/Kconfig
@@ -49,7 +49,7 @@ config CLK_K3_PLL
Enables PLL clock support for K3 SoC family of devices.
config SPL_CLK_K3_PLL
- bool "PLL clock support for K3 SoC family of devices"
+ bool "PLL clock support for K3 SoC family of devices in SPL"
depends on CLK && LIB_RATIONAL && SPL
help
Enables PLL clock support for K3 SoC family of devices.
@@ -61,7 +61,7 @@ config CLK_K3
Enables the clock translation layer from DT to device clocks.
config SPL_CLK_K3
- bool "Clock support for K3 SoC family of devices"
+ bool "Clock support for K3 SoC family of devices in SPL"
depends on CLK && SPL
help
Enables the clock translation layer from DT to device clocks.
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index d1cb69f85ad..7ae28c4e0d5 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -662,7 +662,7 @@ config MII
config RMII
bool "Enable RMII"
help
- Enable support of the Reduced Media-Independent Interface (MII)
+ Enable support of the Reduced Media-Independent Interface (RMII)
config PCNET
bool "AMD PCnet series Ethernet controller driver"
diff --git a/drivers/net/designware.c b/drivers/net/designware.c
index 7ecedc3d7f0..2fd92cf16bb 100644
--- a/drivers/net/designware.c
+++ b/drivers/net/designware.c
@@ -894,7 +894,7 @@ int designware_eth_probe(struct udevice *dev)
if (ret) {
debug("%s: No phy supply\n", dev->name);
} else {
- ret = regulator_set_enable(phy_supply, true);
+ ret = regulator_set_enable_if_allowed(phy_supply, true);
if (ret) {
puts("Error enabling phy supply\n");
return ret;
diff --git a/drivers/usb/common/fsl-errata.c b/drivers/usb/common/fsl-errata.c
index 89ae73f2ba4..66ff93b2982 100644
--- a/drivers/usb/common/fsl-errata.c
+++ b/drivers/usb/common/fsl-errata.c
@@ -7,7 +7,7 @@
#include <hwconfig.h>
#include <fsl_errata.h>
-#include<fsl_usb.h>
+#include <fsl_usb.h>
#if defined(CONFIG_FSL_LSCH2) || defined(CONFIG_FSL_LSCH3) || \
defined(CONFIG_ARM)
#include <asm/arch/clock.h>
diff --git a/env/Kconfig b/env/Kconfig
index adea277470f..678f362c455 100644
--- a/env/Kconfig
+++ b/env/Kconfig
@@ -481,7 +481,7 @@ config ENV_IS_IN_UBI
config ENV_REDUNDANT
bool "Enable redundant environment support"
help
- Normally, the environemt is stored in a single location. By
+ Normally, the environment is stored in a single location. By
selecting this option, you can then define where to hold a redundant
copy of the environment data, so that there is a valid backup copy in
case there is a power failure during a "saveenv" operation.
@@ -497,7 +497,7 @@ config ENV_FAT_INTERFACE
Define this to a string that is the name of the block device.
config ENV_FAT_DEVICE_AND_PART
- string "Device and partition for where to store the environemt in FAT"
+ string "Device and partition for where to store the environment in FAT"
depends on ENV_IS_IN_FAT
default "0:1" if TI_COMMON_CMD_OPTIONS
default "0:auto" if ARCH_ZYNQ || ARCH_ZYNQMP || ARCH_VERSAL || ARCH_VERSAL_NET || ARCH_VERSAL2
@@ -545,7 +545,7 @@ config ENV_EXT4_INTERFACE
Define this to a string that is the name of the block device.
config ENV_EXT4_DEVICE_AND_PART
- string "Device and partition for where to store the environemt in EXT4"
+ string "Device and partition for where to store the environment in EXT4"
depends on ENV_IS_IN_EXT4
help
Define this to a string to specify the partition of the device. It can
diff --git a/lib/lwip/u-boot/lwipopts.h b/lib/lwip/u-boot/lwipopts.h
index 80b93ea172d..e8a2c9d7a0a 100644
--- a/lib/lwip/u-boot/lwipopts.h
+++ b/lib/lwip/u-boot/lwipopts.h
@@ -44,6 +44,7 @@
#define DNS_DEBUG LWIP_DBG_ON
#define IP6_DEBUG LWIP_DBG_OFF
#define DHCP6_DEBUG LWIP_DBG_OFF
+#define SNTP_DEBUG LWIP_DBG_ON
#endif
#define LWIP_TESTMODE 0
diff --git a/net/lwip/dhcp.c b/net/lwip/dhcp.c
index 4c9cb0ecaa0..531bf2c6705 100644
--- a/net/lwip/dhcp.c
+++ b/net/lwip/dhcp.c
@@ -8,6 +8,7 @@
#include <dm/device.h>
#include <linux/delay.h>
#include <linux/errno.h>
+#include <lwip/apps/sntp.h>
#include <lwip/dhcp.h>
#include <lwip/dns.h>
#include <lwip/timeouts.h>
@@ -32,6 +33,7 @@ static int dhcp_loop(struct udevice *udev)
char ipstr[] = "ipaddr\0\0";
char maskstr[] = "netmask\0\0";
char gwstr[] = "gatewayip\0\0";
+ const ip_addr_t *ntpserverip;
unsigned long start;
struct netif *netif;
struct dhcp *dhcp;
@@ -48,6 +50,13 @@ static int dhcp_loop(struct udevice *udev)
if (!netif)
return CMD_RET_FAILURE;
+ /*
+ * Request the DHCP stack to parse and store the NTP servers for
+ * eventual use by the SNTP command
+ */
+ if (CONFIG_IS_ENABLED(CMD_SNTP))
+ sntp_servermode_dhcp(1);
+
start = get_timer(0);
if (dhcp_start(netif))
@@ -102,6 +111,11 @@ static int dhcp_loop(struct udevice *udev)
strncpy(boot_file_name, dhcp->boot_file_name,
sizeof(boot_file_name));
#endif
+ if (CONFIG_IS_ENABLED(CMD_SNTP)) {
+ ntpserverip = sntp_getserver(1);
+ if (ntpserverip != IP_ADDR_ANY)
+ env_set("ntpserverip", ip4addr_ntoa(ntpserverip));
+ }
printf("DHCP client bound to address %pI4 (%lu ms)\n",
&dhcp->offered_ip_addr, get_timer(start));
diff --git a/net/lwip/net-lwip.c b/net/lwip/net-lwip.c
index 1a70cedfb58..8741f65fe12 100644
--- a/net/lwip/net-lwip.c
+++ b/net/lwip/net-lwip.c
@@ -7,6 +7,7 @@
#include <dm/device.h>
#include <dm/uclass.h>
#include <hexdump.h>
+#include <linux/compiler_attributes.h>
#include <linux/kernel.h>
#include <lwip/ip4_addr.h>
#include <lwip/dns.h>
@@ -30,7 +31,8 @@ void (*push_packet)(void *, int len) = 0;
int net_try_count;
static int net_restarted;
int net_restart_wrap;
-static uchar net_pkt_buf[(PKTBUFSRX) * PKTSIZE_ALIGN + PKTALIGN];
+static uchar net_pkt_buf[(PKTBUFSRX) * PKTSIZE_ALIGN + PKTALIGN]
+ __aligned(PKTALIGN);
uchar *net_rx_packets[PKTBUFSRX];
uchar *net_rx_packet;
const u8 net_bcast_ethaddr[6] = { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff };
generated by cgit v1.2.3 (git 2.0.4) at 2025-10-13 14:13:00 +0000