summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/api/i3c.rst8
-rw-r--r--doc/api/index.rst1
-rw-r--r--doc/board/index.rst1
-rw-r--r--doc/board/pegatron/chagall.rst41
-rw-r--r--doc/board/pegatron/index.rst9
-rw-r--r--doc/board/samsung/index.rst1
-rw-r--r--doc/board/samsung/n1.rst51
-rw-r--r--doc/usage/cmd/i3c.rst146
-rw-r--r--doc/usage/environment.rst9
-rw-r--r--doc/usage/index.rst1
10 files changed, 268 insertions, 0 deletions
diff --git a/doc/api/i3c.rst b/doc/api/i3c.rst
new file mode 100644
index 00000000000..7906face080
--- /dev/null
+++ b/doc/api/i3c.rst
@@ -0,0 +1,8 @@
+.. SPDX-License-Identifier: GPL-2.0+
+.. Copyright (C) 2025 Altera Corporation <www.altera.com>
+
+I3C Subsystem
+===============
+
+.. kernel-doc:: include/i3c.h
+ :internal:
diff --git a/doc/api/index.rst b/doc/api/index.rst
index cf9d21e4c1c..d97630e7671 100644
--- a/doc/api/index.rst
+++ b/doc/api/index.rst
@@ -15,6 +15,7 @@ U-Boot API documentation
fs
getopt
interrupt
+ i3c
led
linker_lists
logging
diff --git a/doc/board/index.rst b/doc/board/index.rst
index e084c7fb1df..7870f1bc246 100644
--- a/doc/board/index.rst
+++ b/doc/board/index.rst
@@ -47,6 +47,7 @@ Board-specific doc
nxp/index
openpiton/index
ouya/index
+ pegatron/index
phytec/index
purism/index
qualcomm/index
diff --git a/doc/board/pegatron/chagall.rst b/doc/board/pegatron/chagall.rst
new file mode 100644
index 00000000000..18ed425ec73
--- /dev/null
+++ b/doc/board/pegatron/chagall.rst
@@ -0,0 +1,41 @@
+.. SPDX-License-Identifier: GPL-2.0+
+
+U-Boot for the Pegatron Chagall tablet
+======================================
+
+Quick Start
+-----------
+
+- Build U-Boot
+- Boot
+
+Build U-Boot
+------------
+
+.. code-block:: bash
+
+ $ export CROSS_COMPILE=arm-none-eabi-
+ $ make chagall_defconfig
+ $ make
+
+After the build succeeds, you will obtain the final ``u-boot-dtb-tegra.bin``
+image, ready for loading.
+
+Boot
+----
+
+Currently, U-Boot can be preloaded into RAM via the Fusée Gelée. To enter
+RCM protocol use ``power`` and ``volume up`` key combination from powered
+off device. The host PC should recognize an APX device.
+
+Built U-Boot ``u-boot-dtb-tegra.bin`` can be loaded from fusee-tools
+directory with
+
+.. code-block:: bash
+
+ $ ./run_bootloader.sh -s T30 -t ./bct/chagall.bct
+
+To boot Linux, U-Boot will look for an ``extlinux.conf`` on MicroSD and then on
+eMMC. Additionally, if the Volume Down button is pressed while loading, the
+device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC
+as mass storage, fastboot, reboot, reboot RCM and poweroff.
diff --git a/doc/board/pegatron/index.rst b/doc/board/pegatron/index.rst
new file mode 100644
index 00000000000..8fd8d5fa547
--- /dev/null
+++ b/doc/board/pegatron/index.rst
@@ -0,0 +1,9 @@
+.. SPDX-License-Identifier: GPL-2.0+
+
+Pegatron
+========
+
+.. toctree::
+ :maxdepth: 2
+
+ chagall
diff --git a/doc/board/samsung/index.rst b/doc/board/samsung/index.rst
index a1c9636b050..1b92c9518a5 100644
--- a/doc/board/samsung/index.rst
+++ b/doc/board/samsung/index.rst
@@ -8,3 +8,4 @@ Samsung
axy17lte
e850-96
+ n1
diff --git a/doc/board/samsung/n1.rst b/doc/board/samsung/n1.rst
new file mode 100644
index 00000000000..4dbb3141774
--- /dev/null
+++ b/doc/board/samsung/n1.rst
@@ -0,0 +1,51 @@
+.. SPDX-License-Identifier: GPL-2.0+
+
+U-Boot for the Samsung N1 device family
+=======================================
+
+``DISCLAMER!`` Moving your Samsung Galaxy R (GT-I9103) or Samsung Captivate Glide
+(SGH-i927) to use U-Boot assumes replacement of the sboot. Vendor android firmwares
+will no longer be able to run on the device. This replacement IS reversible.
+
+Quick Start
+-----------
+
+- Build U-Boot
+- Boot
+
+Build U-Boot
+------------
+
+Device support is implemented by applying config fragment to a generic board
+defconfig. Generic board defconfig is suitable for Samsung Galaxy R (GT-I9103)
+while Samsung Captivate Glide (SGH-i927) support is provided by applying
+``bose.config`` fragment.
+
+.. code-block:: bash
+
+ $ export CROSS_COMPILE=arm-none-eabi-
+ $ make n1_defconfig bose.config # For Captivate Glide
+ $ make
+
+After the build succeeds, you will obtain the final ``u-boot-dtb-tegra.bin``
+image, ready for further processing.
+
+Boot
+----
+
+Currently, U-Boot can be preloaded into RAM via the NvFlash. To enter
+RCM protocol use ``home`` and ``volume up`` for Galaxy R and ``volume down``
+and ``volume up`` Captivate Glide key combination plus plugging usb in.
+The host PC should recognize an APX device.
+
+Built U-Boot ``u-boot-dtb-tegra.bin`` can be loaded from fusee-tools
+directory with
+
+.. code-block:: bash
+
+ $ ./utils/nvflash_t20 --setbct --bct ./bct/i927.bct --configfile ./utils/flash.cfg --bl u-boot-dtb-tegra.bin --sbk (in form of 0xABCDABCD 4 times) --sync # For Captivate Glide
+
+To boot Linux, U-Boot will look for an ``extlinux.conf`` on MicroSD and then on
+eMMC. Additionally, if the Volume Down button is pressed while loading, the
+device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC
+as mass storage, fastboot, reboot, reboot RCM and poweroff.
diff --git a/doc/usage/cmd/i3c.rst b/doc/usage/cmd/i3c.rst
new file mode 100644
index 00000000000..922fa3ea37c
--- /dev/null
+++ b/doc/usage/cmd/i3c.rst
@@ -0,0 +1,146 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+.. index::
+ single: i3c (command)
+
+i3c command
+===========
+
+Synopsis
+--------
+
+::
+
+ i3c <host_controller>
+ i3c current
+ i3c list
+ i3c device_list
+ i3c write <mem_addr> <length> <device_number>
+ i3c read <mem_addr> <length> <device_number>
+
+Description
+-----------
+
+The ``i3c`` command is used to probe the i3c host controller and perform
+read and write operations on the connected i3c devices.
+
+i3c current
+------------
+
+Display the currently selected i3c host controller.
+
+i3c list
+---------
+
+List all the i3c hosts defined in the device-tree.
+
+i3c device_list
+----------------
+
+List all the i3c devices' device number, static address, dynamic address,
+PID, BCR, DCR, Max Write Speed, and Max Read Speed of the probed i3c host
+controller.
+
+i3c write
+----------
+
+Perform a write operation from memory to the connected i3c device. The data
+is read from a specified memory address and written to the selected i3c
+device, which is identified by its device number.
+
+You need to provide the memory address (``mem_addr``), the length of data
+to be written (``length``), and the device number (``device_number``). The
+data in memory will be transferred to the device in the specified order.
+
+i3c read
+---------
+
+Perform a read operation from the connected i3c device to memory. The data
+is read from the selected i3c device and stored at the specified memory
+address. You need to provide the memory address (``mem_addr``), the length
+of data to be read (``length``), and the device number (``device_number``).
+
+The device will send the requested data, which is then written to the memory
+location you specified. This operation allows you to retrieve information
+from the device and use it in your application. The data is read in the
+order specified and can be multiple bytes.
+
+host_controller
+ The name of the i3c host controller defined in the device-tree.
+
+length
+ The size of the data to be read or written.
+
+device_number
+ The device number in the driver model of the device connected to the i3c
+ host controller.
+
+mem_addr
+ The start address in memory from which to read or write the data.
+
+Examples
+--------
+
+Probe the ``i3c0`` controller::
+
+ => i3c i3c0
+
+Display the current i3c host controller::
+
+ => i3c current
+
+Check the device number and PID of the connected devices::
+
+ => i3c device_list
+
+Perform write operations on the connected i3c device (device 0) from memory::
+
+ => i3c write 0x1000 4 0
+
+ This command reads 4 bytes of data from memory starting at address
+ ``0x1000`` and writes them to device 0, which is identified by its device
+ number in the driver model. Example data from memory could look like this:
+
+ ```
+ Data at 0x1000: 0xAA 0xBB 0xCC 0xDD
+ ```
+
+ The bytes `0xAA`, `0xBB`, `0xCC`, and `0xDD` will be written to device 0.
+
+Perform a read operation from device 0 to memory (multiple bytes)::
+
+ => i3c read 0x1000 4 0
+
+ This command reads 4 bytes of data from device 0 and writes them to
+ memory starting at address ``0x1000``.
+
+ Example output after reading 4 bytes from device 0:
+
+ ```
+ i3c Read:
+ 00000000 AA BB CC DD
+ ```
+
+ The bytes `0xAA`, `0xBB`, `0xCC`, and `0xDD` are read from device 0
+ and written to memory at address `0x1000`.
+
+Configuration
+-------------
+
+The ``i3c`` command is only available if CONFIG_CMD_I3C=y.
+
+Return value
+------------
+
+If the command succeeds, the return value ``$?`` is set to 0. If an error
+occurs, the return value ``$?`` is set to 1.
+
+Note
+----
+
+When specifying the data to be written to the i3c device (for example, with
+the ``i3c write`` command), the data can be provided in either uppercase
+or lowercase hexadecimal format. Both are valid and will be processed
+correctly. Similarly, when reading data with ``i3c read``, the data will be
+retrieved in the specified length and can include multiple bytes, all
+formatted in the same way. \ No newline at end of file
diff --git a/doc/usage/environment.rst b/doc/usage/environment.rst
index bb6c351b441..77197d79380 100644
--- a/doc/usage/environment.rst
+++ b/doc/usage/environment.rst
@@ -335,6 +335,15 @@ netretry
Useful on scripts which control the retry operation
themselves.
+phy_aneg_timeout
+ If set, the specified value will override CONFIG_PHY_ANEG_TIMEOUT.
+ This variable has the same base and unit as CONFIG_PHY_ANEG_TIMEOUT
+ which is "decimal" and "millisecond" respectively. The default value
+ of CONFIG_PHY_ANEG_TIMEOUT may be sufficient for most use-cases, but
+ certain link-partners may require a larger timeout due to the Ethernet
+ PHY they use. Alternatively, the timeout can be reduced as well if the
+ use-case demands it.
+
rng_seed_size
Size of random value added to device-tree node /chosen/rng-seed.
This variable is given as a decimal number.
diff --git a/doc/usage/index.rst b/doc/usage/index.rst
index b9de87a6ed9..3a48521d5d5 100644
--- a/doc/usage/index.rst
+++ b/doc/usage/index.rst
@@ -82,6 +82,7 @@ Shell commands
cmd/if
cmd/itest
cmd/imxtract
+ cmd/i3c
cmd/load
cmd/loadb
cmd/loadm