u-boot.git/doc/develop, branch v2023.07-rc2 Unnamed repository; edit this file 'description' to name the repository. Prepare v2023.07-rc2 2023-05-08T18:16:32+00:00 Tom Rini trini@konsulko.com 2023-05-08T18:16:32+00:00 f1d33a44ca04fdca241c1d89fd79e2e56c930c7e Signed-off-by: Tom Rini <trini@konsulko.com> 
Signed-off-by: Tom Rini <trini@konsulko.com>
Merge branch '2023-05-03-assorted-updates-and-fixes' 2023-05-04T15:49:30+00:00 Tom Rini trini@konsulko.com 2023-05-04T15:49:30+00:00 7f30eec1779b8f641b9563a1dab6a6865916ec01 - Various typo fixes, pass -Werror to host tools builds, bdi cleanups, fix hush and local variables, a FSL PCI fix and correct some python in one of the tests. 
- Various typo fixes, pass -Werror to host tools builds, bdi cleanups,
  fix hush and local variables, a FSL PCI fix and correct some python in
  one of the tests.
docs: fix wrong proftool usage 2023-05-04T07:57:43+00:00 Pavel Skripkin paskripkin@gmail.com 2023-04-12T19:05:31+00:00 d53b2cfe0805cd84de16f4e2da396b75b409a8ab Guide shows incorrect usage of proftool, which is confusing. If proftool is used w/o '-o' argument it complains like following $ ./sandbox/tools/proftool -m sandbox/System.map -t trace dump-ftrace > trace.dat Must provide trace data, System.map file and output file Usage: proftool [-cmtv] <cmd> <profdata> s/>/-o/ fixes it and proftool outputs decoded data to trace.dat Signed-off-by: Pavel Skripkin <paskripkin@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Guide shows incorrect usage of proftool, which is confusing. If proftool
is used w/o '-o' argument it complains like following

$ ./sandbox/tools/proftool -m sandbox/System.map -t trace dump-ftrace > trace.dat
Must provide trace data, System.map file and output file
Usage: proftool [-cmtv] <cmd> <profdata>

s/>/-o/ fixes it and proftool outputs decoded data to trace.dat

Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
event: fix comments syntax error 2023-05-03T22:30:46+00:00 Hugo Villeneuve hvilleneuve@dimonoff.com 2023-04-25T13:46:45+00:00 ed356ac9300b6efca238d7058bbe8395aa9ff8c6 Fix comments syntax error in event description: creasted -> created Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Fix comments syntax error in event description:
    creasted -> created

Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Prepare v2023.07-rc1 2023-05-01T16:02:02+00:00 Tom Rini trini@konsulko.com 2023-05-01T16:02:02+00:00 6735ab59e6fd71ced1c58d8dfb3dd6baf3690d16 Signed-off-by: Tom Rini <trini@konsulko.com> 
Signed-off-by: Tom Rini <trini@konsulko.com>
sandbox64: add support for NVMXIP QSPI 2023-04-27T21:01:14+00:00 Abdellatif El Khlifi abdellatif.elkhlifi@arm.com 2023-04-17T09:11:55+00:00 cc89b7cf419223a746ab3cfc5741a19cd40ebabe enable NVMXIP QSPI for sandbox 64-bit Adding two NVM XIP QSPI storage devices. Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
enable NVMXIP QSPI for sandbox 64-bit

Adding two NVM XIP QSPI storage devices.

Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
drivers/mtd/nvmxip: introduce QSPI XIP driver 2023-04-27T21:01:14+00:00 Abdellatif El Khlifi abdellatif.elkhlifi@arm.com 2023-04-17T09:11:53+00:00 9e115ace358d9ed79844b27b06b3a0e8b23d49da add nvmxip_qspi driver under UCLASS_NVMXIP The device associated with this driver is the parent of the blk#<id> device nvmxip_qspi can be reused by other platforms. If the platform has custom settings to apply before using the flash, then the platform can provide its own parent driver belonging to UCLASS_NVMXIP and reuse nvmxip-blk driver. The custom driver can be implemented like nvmxip_qspi in addition to the platform custom settings. Platforms can use multiple NVM XIP devices at the same time by defining a DT node for each one of them. For more details please refer to doc/develop/driver-model/nvmxip_qspi.rst Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com> 
add nvmxip_qspi driver under UCLASS_NVMXIP

The device associated with this driver is the parent of the blk#<id> device
nvmxip_qspi can be reused by other platforms. If the platform
has custom settings to apply before using the flash, then the platform
can provide its own parent driver belonging to UCLASS_NVMXIP and reuse
nvmxip-blk driver. The custom driver can be implemented like nvmxip_qspi in
addition to the platform custom settings.

Platforms can use multiple NVM XIP devices at the same time by defining a
DT node for each one of them.

For more details please refer to doc/develop/driver-model/nvmxip_qspi.rst

Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
drivers/mtd/nvmxip: introduce NVM XIP block storage emulation 2023-04-27T21:01:14+00:00 Abdellatif El Khlifi abdellatif.elkhlifi@arm.com 2023-04-17T09:11:52+00:00 f37af2760ea92cec3fbdcfceb6df7be57a618165 add block storage emulation for NVM XIP flash devices Some paltforms such as Corstone-1000 need to see NVM XIP raw flash as a block storage device with read only capability. Here NVM flash devices are devices with addressable memory (e.g: QSPI NOR flash). The implementation is generic and can be used by different platforms. Two drivers are provided as follows. nvmxip-blk : a generic block driver allowing to read from the XIP flash nvmxip Uclass driver : When a device is described in the DT and associated with UCLASS_NVMXIP, the Uclass creates a block device and binds it with the nvmxip-blk. Platforms can use multiple NVM XIP devices at the same time by defining a DT node for each one of them. Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com> 
add block storage emulation for NVM XIP flash devices

Some paltforms such as Corstone-1000 need to see NVM XIP raw flash
as a block storage device with read only capability.

Here NVM flash devices are devices with addressable
memory (e.g: QSPI NOR flash).

The implementation is generic and can be used by different platforms.

Two drivers are provided as follows.

  nvmxip-blk :

    a generic block driver allowing to read from the XIP flash

  nvmxip Uclass driver :

        When a device is described in the DT and associated with
        UCLASS_NVMXIP, the Uclass creates a block device and binds it with
	 the nvmxip-blk.

Platforms can use multiple NVM XIP devices at the same time by defining a
DT node for each one of them.

Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
doc: codingstyle: Python coding style 2023-04-21T06:50:35+00:00 Heinrich Schuchardt heinrich.schuchardt@canonical.com 2023-04-19T06:45:34+00:00 8626ef32e9443353d40ec44d4a0c69deac011efb Indicate that we follow PEP8 and PEP257. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Indicate that we follow PEP8 and PEP257.

Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
doc: describe our documentation style 2023-04-08T05:44:33+00:00 Heinrich Schuchardt heinrich.schuchardt@canonical.com 2023-04-07T09:28:00+00:00 624faeecec5b0df74791d7eac3f9984673f5b33b Provide a reference document for the U-Boot documentation style. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Provide a reference document for the U-Boot documentation style.

Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass <sjg@chromium.org>