- Oct 13, 2024
-
-
Update the MAINTAINERS file glob to cover all of i.MX8MP DHSOM related files. Signed-off-by:Marek Vasut <marex@denx.de>
-
Update the MAINTAINERS file glob to cover all of i.MX6 DHSOM related files. Signed-off-by: -
When OSCCA is enabled, FSB fuse shadow (offset 0x8000) access is disabled for SOC. So update the driver to read fuse from ELE API. The ELE has supported to read all shadow fuses like FSB, reuse the table of FSB for the word index used by ELE API. Add ELE shadow fuse read and write to current ELE fuse driver. But when LC is OEM closed, the ELE read/write shadow fuse APIs are forbidden. Reading from any fuse will return error. This causes problem to u-boot which must read out some fuse no matter whatever LC. So we have to change back to read from FSB and ELE common fuse read API. For using ELE shadow read API for development purpose like checking the ELE shadow fuse write result, user can set env variable "enable_ele_shd" to y to switch it. Reviewed-by:
Peng Fan <peng.fan@nxp.com> Signed-off-by:
Ye Li <ye.li@nxp.com> Signed-off-by:
-
There is a bug when checking fuse word with redundancy fuse in FSB table. The redundancy fuses are combined into 4 words, so we can't directly use word index to do the check, otherwise the high 4 words will fail to match. And When calling ELE API, res parameter will pass to ELE API to get ELE response value for failure. So most of usage does not initialize this variable and print it after calling ELE API. However, when ELE API returns failure, we can't ensure this res is always set because there may be other failure like MU failure. Reviewed-by:
-
Add ELE APIs to support read and write shadow fuses Reviewed-by:
-
On iMX8ULP, the word index 1 is used to read OTP_UNIQ_ID with 4 words data responsed. However this special index does not apply others. So restrict the check to i.MX8ULP to avoid problem when reading from fuse word 1 for others, such as i.MX93. Also update header order Signed-off-by: -
When OS is doing ELE API call, before OS get the response, OS is force reseted, then it is possible that MU RR has data during initialization in SPL stage. So clear the RR registers, otherwise SPL ELE API call will work abnormal. Cc: Alice Guo <alice.guo@nxp.com> Cc: Marek Vasut <marex@denx.de> Signed-off-by: -
The MU parameter register can provide the TR and RR number. For i.MX95 which has 8 RR is different with i.MX93 and i.MX8ULP, so update the driver to read the PAR for exact TR and RR number. Also update compatible string for i.MX95 ELE MU. Cc: Alice Guo <alice.guo@nxp.com> Cc: Marek Vasut <marex@denx.de> Reviewed-by:
-
- Oct 11, 2024
-
-
Tom Rini authored
Simon Glass <sjg@chromium.org> says: When the SPL build-phase was first created it was designed to solve a particular problem (the need to init SDRAM so that U-Boot proper could be loaded). It has since expanded to become an important part of U-Boot, with three phases now present: TPL, VPL and SPL Due to this history, the term 'SPL' is used to mean both a particular phase (the one before U-Boot proper) and all the non-proper phases. This has become confusing. For a similar reason CONFIG_SPL_BUILD is set to 'y' for all 'SPL' phases, not just SPL. So code which can only be compiled for actual SPL, for example, must use something like this: #if defined(CONFIG_SPL_BUILD) && !defined(CONFIG_TPL_BUILD) In Makefiles we have similar issues. SPL_ has been used as a variable which expands to either SPL_ or nothing, to chose between options like CONFIG_BLK and CONFIG_SPL_BLK. When TPL appeared, a new SPL_TPL variable was created which expanded to...
-
Take account of the new XPL_ and PHASE_ instead of the old SPL_ and SPL_TPL_ Signed-off-by:Simon Glass <sjg@chromium.org>
-
Rename these to use the word PHASE instead. Signed-off-by: -
Use PHASE_ as the symbol to select a particular XPL build. This means that SPL_TPL_ is no-longer set. Update the comment in bootstage to refer to this symbol, instead of SPL_ Signed-off-by: -
Use XPL_ as the symbol to indicate an SPL build. This means that SPL_ is no-longer set. Signed-off-by: -
Now that SPL means SPL (only) and is not defined for other phases, update kconfig rules. This is done in one patch since otherwise many Binman tests fail. Signed-off-by: -
Make this define mean SPL only, not TPL, VPL, etc. Signed-off-by: -
Complete this rename for all directories outside arch/ board/ drivers/ and include/ Use the new symbol to refer to any 'SPL' build, including TPL and VPL Signed-off-by: -
Use the new symbol to refer to any 'SPL' build, including TPL and VPL Signed-off-by: -
Use the new symbol to refer to any 'SPL' build, including TPL and VPL Signed-off-by: -
Use the new symbol to refer to any 'SPL' build, including TPL and VPL Signed-off-by: -
Use the new symbol to refer to any 'SPL' build, including TPL and VPL Signed-off-by: -
Update the documentation here to cover the meaning of xPL Signed-off-by: -
Move this section to rst, changing it just enough so that it builds. Signed-off-by: -
This should not be in the generic README file, so drop it. Signed-off-by: -
Update the various references to SPL in this document. Make sure to refer to 'phases' instead of 'stages', which is not a U-Boot term. Fix a few U-boot typos and try to improve grammar a little while we are here. Signed-off-by: -
This should now refer to xPL rather than SPL, so update it throughout the tree. Signed-off-by: -
Use simpler names for these functions. Signed-off-by: -
Rename this to use the xpl prefix. Signed-off-by: -
Add the opposite function to not_xpl() for completeness. Signed-off-by: -
Give this function a slightly easier name. Signed-off-by: -
Rename this function to indicate that it refers to any xPL phase. Signed-off-by: -
This name fits better with the new naming scheme, so update it. Signed-off-by: -
This is a better name for this function, so update it. Tidy up the function comment to mention VPL. Signed-off-by: -
This now appears in the code base, so add it to the list of ignored symbols in qconfig Signed-off-by: -
The new name 'xPL' is intended to indicate a build of any phase which is not U-Boot proper. Define it for all such phases. Note that we also define CONFIG_SPL_BUILD for all xPL builds. This preserves existing behaviour, but future patches will adjust that. Signed-off-by: -
Now that the conversion of all CONFIG options to Kconfig is complete, these files only contain the xPL_BUILD defines. Add a comment to make this clear. Signed-off-by: -
Rename this file to indicate that it refers to any non-U-Boot-proper phase, not just SPL, which is the phase immediately before U-Boot proper. Signed-off-by: -
This is always enabled for U-Boot proper, so simplify the condition in the common Makefile. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
This is always enabled for U-Boot proper, so simplify the condition in the common Makefile. Signed-off-by: -
SPL_BUILD is not a Kconfig symbol. Perhaps the intent here is to use SPL instead. However, this causes build errors, e.g. with T1024RDB_NAND So drop the dependency on !SPL_BUILD since it does nothing. Signed-off-by: -
SPL_BUILD is not a Kconfig symbol so perhaps the intent here is to use SPL instead. But that changes the output size. So drop the dependency on !SPL_BUILD since it does nothing. Signed-off-by:
-
