summaryrefslogtreecommitdiffstats
path: root/doc/imx
Commit message (Collapse)AuthorAgeFilesLines
* dm: treewide: Rename auto_alloc_size members to be shorterSimon Glass2020-12-131-1/+1
| | | | | | | | | | | | This construct is quite long-winded. In earlier days it made some sense since auto-allocation was a strange concept. But with driver model now used pretty universally, we can shorten this to 'auto'. This reduces verbosity and makes it easier to read. Coincidentally it also ensures that every declaration is on one line, thus making dtoc's job easier. Signed-off-by: Simon Glass <sjg@chromium.org>
* clk: Always use the supplied struct clkSean Anderson2020-07-011-31/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | CCF clocks should always use the struct clock passed to their methods for extracting the driver-specific clock information struct. Previously, many functions would use the clk->dev->priv if the device was bound. This could cause problems with composite clocks. The individual clocks in a composite clock did not have the ->dev field filled in. This was fine, because the device-specific clock information would be used. However, since there was no ->dev, there was no way to get the parent clock. This caused the recalc_rate method of the CCF divider clock to fail. One option would be to use the clk->priv field to get the composite clock and from there get the appropriate parent device. However, this would tie the implementation to the composite clock. In general, different devices should not rely on the contents of ->priv from another device. The simple solution to this problem is to just always use the supplied struct clock. The composite clock now fills in the ->dev pointer of its child clocks. This allows child clocks to make calls like clk_get_parent() without issue. imx avoided the above problem by using a custom get_rate function with composite clocks. Signed-off-by: Sean Anderson <seanga2@gmail.com> Acked-by: Lukasz Majewski <lukma@denx.de>
* doc: ahab: Add encrypted boot documentation for i.MX8/8x devicesBreno Lima2020-05-012-0/+320
| | | | | | | | | | | | | | | Add AHAB encrypted boot documentation for i.MX8/8x family devices covering the following topics: - How to encrypt and sign the 2nd container in flash.bin image. - How to encrypt and sign a standalone container image. Include a CSF example to encrypt 2nd container in flash.bin image. Reviewed-by: Fabio Estevam <festevam@gmail.com> Signed-off-by: Catia Han <yaqian.han@nxp.com> Signed-off-by: Breno Lima <breno.lima@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
* doc: update reference to README.imximagePatrick Delaunay2020-04-161-1/+1
| | | | | | | | | Update reference in many files detected by scripts/documentation-file-ref-check README.imximage => imx/mkimage/imximage.txt Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
* imx: replace CONFIG_SECURE_BOOT with CONFIG_IMX_HABStefano Babic2019-10-083-7/+7
| | | | | | | | CONFIG_SECURE_BOOT is too generic and forbids to use it for cross architecture purposes. If Secure Boot is required for imx, this means to enable and use the HAB processor in the soc. Signed-off-by: Stefano Babic <sbabic@denx.de>
* imx: mxs: Fix location for the elftosb toolFabio Estevam2019-10-081-1/+1
| | | | | | | | The Denx FTP location is no longer reachable. Switch to the Timesys repository instead. Signed-off-by: Fabio Estevam <festevam@gmail.com>
* doc: imx: mkimage: introduce i.MX8 image formatPeng Fan2019-10-081-0/+45
| | | | | | Introduce i.MX8 container set configuration file and add example Signed-off-by: Peng Fan <peng.fan@nxp.com>
* doc: imx: Add documentation for nandbcb commandShyam Saini2019-07-191-0/+74
| | | | Signed-off-by: Shyam Saini <shyam.saini@amarulasolutions.com>
* clk: doc: Add documentation entry for Common Clock Framework [CCF] (i.MX)Lukasz Majewski2019-07-191-0/+101
| | | | | | | This patch describes the design decisions considerations and taken approach for porting in a separate documentation entry. Signed-off-by: Lukasz Majewski <lukma@denx.de>
* doc: imx: habv4: Remove secure_boot.txt guideBreno Matheus Lima2019-02-151-100/+0
| | | | | | | | | | The secure_boot.txt guide was replaced by mx6_mx7_secure_boot.txt and mx6_mx7_spl_secure_boot.txt documents. Both documents covers all steps needed for SPL and non-SPL tagets, so remove secure_boot.txt file to avoid duplicated content. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: habv4: Move encrypted boot guideBreno Matheus Lima2019-02-151-0/+0
| | | | | | | | All guides are currently located at doc/imx/habv4/guides/ directory. Move encrypted_boot.txt document to guides directory. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: habv4: Add Secure Boot guide for i.MX6 and i.MX7 SPL targetsBreno Matheus Lima2019-02-151-0/+181
| | | | | | | | | | | | | | | The current U-Boot implementation includes SPL targets for some NXP development boards: - mx6sabreauto_defconfig - mx6sabresd_defconfig - mx6ul_14x14_evk_defconfig - mx6ul_9x9_evk_defconfig Add additional steps needed to completly secure the bootloader image. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: habv4: Add Secure Boot guide for i.MX6 and i.MX7 non-SPL targetsBreno Matheus Lima2019-02-155-0/+503
| | | | | | | | | | | | | | Add HABv4 documentation for non-SPL targets covering the following topics: - How to sign an securely boot an u-boot-dtb.imx image. - How to extend the root of trust for additional boot images. - Add 3 CSF examples. - Add IVT generation script example. Reviewed-by: Ye Li <ye.li@nxp.com> Reviewed-by: Utkarsh Gupta <utkarsh.gupta@nxp.com> Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: habv4: Add HABv4 introductionBreno Matheus Lima2019-02-151-0/+262
| | | | | | | | | | | | | | | | | | The HABv4 is supported in i.MX50, i.MX53, i.MX6, i.MX7, series and i.MX 8M, i.MX8MM devices. Add an introductory document containing the following topics: - HABv4 Introduction - HABv4 Secure Boot - HABv4 Encrypted Boot - HAB PKI tree generation - HAB Fast Authentication PKI tree generation - SRK Table and SRK Hash generation Reviewed-by: Ye Li <ye.li@nxp.com> Reviewed-by: Utkarsh Gupta <utkarsh.gupta@nxp.com> Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: habv4: Remove extra hab directory for a cleaner documentation ↵Breno Matheus Lima2019-02-152-0/+0
| | | | | | | | | | | structure There is no need to have an extra hab directory under doc/imx/. Habv4 and AHAB documentation can be added directly in doc/imx/ for a cleaner documentation structure. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: fix typos in mxsimage.txtMichael Heimpold2019-01-011-2/+2
| | | | | | | This fixes two small typos in mxsimage.txt. Signed-off-by: Michael Heimpold <mhei@heimpold.de> Reviewed-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: fix typo in imximage.txtMichael Heimpold2019-01-011-1/+1
| | | | | Signed-off-by: Michael Heimpold <mhei@heimpold.de> Reviewed-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: Improve i.MX documentation namingBreno Matheus Lima2018-10-228-0/+0
| | | | | | | | There is no need to have README in all i.MX documents name. Remove README from i.MX docs name and add .txt file extension. Signed-off-by: Breno Lima <breno.lima@nxp.com> Reviewed-by: Ye Li <ye.li@nxp.com>
* doc: imx: misc: Reorganize miscellaneous documentationBreno Matheus Lima2018-10-221-0/+0
| | | | | | | | | The Serial Download Protocol feature is availible in various i.MX SoCs. Move README.sdp document to imx/misc directory. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: hab: Reorganize High Assurance Boot documentationBreno Matheus Lima2018-10-222-44/+43
| | | | | | | | | | | | | | The current High Assurance Boot document README.mxc_hab include details for the following features in a single file: - HAB Secure Boot - HAB Encrypted Boot Split HAB documentation in a specific directory for a cleaner documentation structure, subsequent patches will include more content in HAB documentation. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: Reorganize i.MX SoC common documentationBreno Matheus Lima2018-10-225-0/+0
| | | | | | | | | | | | | | | | The following documents describe device details according to the i.MX family: - README.imx25 - README.imx27 - README.imx5 - README.imx6 - README.mxs Move all device common related document to doc/imx/common for a better directory structure. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: mkimage: reorganize i.MX mkimage documentationBreno Matheus Lima2018-10-222-0/+0
| | | | | | | | | | | | | The following documents describe the image type used by the mkimage tool to generate U-Boot images for i.MX devices. - README.imximage - README.mxsimage Move all mkimage related document to doc/imx/mkimage for a better directory structure. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: Move SPD related info to the appropriate docBreno Matheus Lima2018-10-222-27/+20
| | | | | | | | | | | | | | Currently the Serial Download Protocol tools and procedure are documented in two places: - doc/imx/README.sdp - doc/imx/README.imx6 It is better to consolidate all SDP related information into README.sdp file, so move the content from README.imx6 to README.sdp. Signed-off-by: Breno Lima <breno.lima@nxp.com>
* doc: imx: reorganize i.MX documentationBreno Matheus Lima2018-10-229-0/+1118
Currently the U-Boot doc/ directory contains the following files that are only relevant for i.MX devices: - doc/README.imx25 - doc/README.imx27 - doc/README.imx5 - doc/README.imx6 - doc/README.imximage - doc/README.mxc_hab - doc/README.mxs - doc/README.mxsimage - doc/README.sdp Move all content to a common i.MX folder for a better documentation structure. Signed-off-by: Breno Lima <breno.lima@nxp.com>
generated by cgit (git 2.34.1) at 2024-11-12 13:46:16 +0000