<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/lib/Kconfig, branch v2023.10</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/lib/Kconfig?h=v2023.10</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/lib/Kconfig?h=v2023.10'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2023-08-07T17:41:44Z</updated>
<entry>
<title>spl: move SPL_CRC32 option to lib/Kconfig</title>
<updated>2023-08-07T17:41:44Z</updated>
<author>
<name>Oleksandr Suvorov</name>
<email>oleksandr.suvorov@foundries.io</email>
</author>
<published>2023-08-03T16:05:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=af62d83cc0ee27ca5051718a0df44341f71abff1'/>
<id>urn:sha1:af62d83cc0ee27ca5051718a0df44341f71abff1</id>
<content type='text'>
All SPL hash algorithm options are collected in lib/Kconfig. Move
SPL_CRC32 there as well.

Signed-off-by: Oleksandr Suvorov &lt;oleksandr.suvorov@foundries.io&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>lib: Kconfig: k3: Enable SHA512 for fit signature</title>
<updated>2023-07-22T02:07:46Z</updated>
<author>
<name>Manorit Chawdhry</name>
<email>m-chawdhry@ti.com</email>
</author>
<published>2023-07-14T05:52:39Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=dfe00b34ce6644ac37b8ab009359db8193af2ed4'/>
<id>urn:sha1:dfe00b34ce6644ac37b8ab009359db8193af2ed4</id>
<content type='text'>
We are using our custMpk for signing that is a 4096 bit key, 4096 bit
rsa key requires a SHA512 hashing algorithm to be enabled as per the
source. Even though it is not mandated but this is how it works and is
tested.

Enables SHA512 if fit signature is enabled on K3 platforms.

Signed-off-by: Manorit Chawdhry &lt;m-chawdhry@ti.com&gt;
</content>
</entry>
<entry>
<title>acpi: Create a new Kconfig for ACPI</title>
<updated>2023-05-11T02:25:29Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2023-05-04T22:54:57Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0992a90daa80a17f9e7e33a56fd3f9660ee84c97'/>
<id>urn:sha1:0992a90daa80a17f9e7e33a56fd3f9660ee84c97</id>
<content type='text'>
We have several Kconfig options for ACPI, but all relate to specific
functions, such as generating tables and AML code.

Add a new option which controls including basic ACPI library code,
including the lib/acpi directory. This will allow us to add functions
which are available even if table generation is not supported.

Adjust the command to avoid a build error when ACPIGEN is not enabled.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>lmb: Fix LMB_MEMORY_REGIONS flag usage</title>
<updated>2023-04-06T19:08:46Z</updated>
<author>
<name>Patrick Delaunay</name>
<email>patrick.delaunay@foss.st.com</email>
</author>
<published>2023-03-22T18:12:25Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=94c8da21216ac077842c413a4339e71285bcf94d'/>
<id>urn:sha1:94c8da21216ac077842c413a4339e71285bcf94d</id>
<content type='text'>
Remove test on CONFIG_LMB_MEMORY_REGIONS introduced by commit
7c1860fce4e3 ("lmb: Fix lmb property's defination under struct lmb").

This code in lmb_init() is strange, because if CONFIG_LMB_USE_MAX_REGIONS
and CONFIG_LMB_MEMORY_REGIONS are not defined, the implicit #else is empty
and the required initialization is not done:
lmb-&gt;memory.max = ?
lmb-&gt;reserved.max = ?

But this setting is not possible:
- CONFIG_LMB_USE_MAX_REGIONS not defined
- CONFIG_LMB_MEMORY_REGIONS not defined
because CONFIG_LMB_MEMORY_REGIONS and CONFIG_LMB_RESERVED_REGIONS are
defined as soon as the CONFIG_LMB_USE_MAX_REGIONS is not defined.

This patch removes this impossible case #elif and I add some
explanation in lmb.h to explain why in the struct lmb {} the lmb
property is defined if CONFIG_LMB_MEMORY_REGIONS is NOT defined.

This patch also removes CONFIG_LMB_XXX dependency on CONFIG_LMB as these
defines are used in API file lmb.h and not only in library file.

Fixes: 5e2548c1d6e03 ("lmb: Fix LMB_MEMORY_REGIONS flag usage")
Reported-by: Mark Millard &lt;marklmi@yahoo.com&gt;
Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@foss.st.com&gt;
Acked-by: Michal Simek &lt;michal.simek@amd.com&gt;
</content>
</entry>
<entry>
<title>lib: Fix SYS_TIMER_COUNTS_DOWN description in Kconfig</title>
<updated>2023-03-30T19:09:59Z</updated>
<author>
<name>Marek Vasut</name>
<email>marek.vasut+renesas@mailbox.org</email>
</author>
<published>2023-03-19T03:13:02Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c61df34009c3ad46b5798e1d13fd640419bf17e6'/>
<id>urn:sha1:c61df34009c3ad46b5798e1d13fd640419bf17e6</id>
<content type='text'>
The SYS_TIMER_COUNTS_DOWN description contains a typo,
s@rathe@&amp;r@ , fix it.

Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
</content>
</entry>
<entry>
<title>lib: Add an SPL config for LIB_UUID</title>
<updated>2023-03-02T22:45:58Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2023-02-22T16:34:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3b510807f59d6602df5b3de3ac5c2f8f6e1bd265'/>
<id>urn:sha1:3b510807f59d6602df5b3de3ac5c2f8f6e1bd265</id>
<content type='text'>
This is selected by PARTITION_UUIDS which has a separate option for SPL.
Add an SPL option for LIB_UUID also, so that we can keep them consistent.

Also add one for PARTITION_TYPE_GUID to avoid a build error in part_efi.c
which wants to call a uuid function in SPL.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>lib: Add VPL options for SHA1 and SHA256</title>
<updated>2023-03-02T22:45:58Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2023-02-22T16:34:01Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5a6bc166eff7835943958a1a732ae92c8904c140'/>
<id>urn:sha1:5a6bc166eff7835943958a1a732ae92c8904c140</id>
<content type='text'>
Add these options so these algorithms can be used in VPL.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>lib: Add a Kconfig for SPL_BZIP2</title>
<updated>2023-03-02T22:45:58Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2023-02-22T16:33:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ae625d92873d37679611e8d4bf58d2f23bf21446'/>
<id>urn:sha1:ae625d92873d37679611e8d4bf58d2f23bf21446</id>
<content type='text'>
This is implicitly used in the source and seems useful, so add it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>trace: Reduce the default for TRACE_EARLY_CALL_DEPTH_LIMIT</title>
<updated>2023-02-11T17:22:34Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2023-01-15T21:15:44Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c33425c6f960944ba88104f281217de5a89a5562'/>
<id>urn:sha1:c33425c6f960944ba88104f281217de5a89a5562</id>
<content type='text'>
This is a silly value at present, since U-Boot's call depth never reaches
200. Fix it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Bump LMB_MAX_REGIONS default to 16</title>
<updated>2023-02-08T19:09:39Z</updated>
<author>
<name>Sjoerd Simons</name>
<email>sjoerd@collabora.com</email>
</author>
<published>2023-01-19T08:38:17Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2dc16a2c1f924985216b3f1d6710f96d6c4fb1ab'/>
<id>urn:sha1:2dc16a2c1f924985216b3f1d6710f96d6c4fb1ab</id>
<content type='text'>
Since commit 06d514d77c37 ("lmb: consider EFI memory map") the EFI regions
are also pushed into the lmb if EFI_LOADER is enabled (which is by
default on most system). Which can cause the number of entries to go
over the maximum as it's default is only 8.

Specifically i ran into this case on an TI am62 which has an fdt with
4 reserved regions (in practice 3 lmb entries due to adjecent ranges).

As this is likely to impact more devices bump the default max
regions to 16 so there is a bit more slack.

Fixes: 06d514d77c ("lmb: consider EFI memory map")
Link: https://bugzilla.opensuse.org/show_bug.cgi?id=1207562
Reviewed-by: Francesco Dolcini &lt;francesco.dolcini@toradex.com&gt;
Signed-off-by: Sjoerd Simons &lt;sjoerd@collabora.com&gt;
Signed-off-by: Michal Suchanek &lt;msuchanek@suse.de&gt;
[trini: collect tags from the other equivalent patch]
</content>
</entry>
</feed>
