- 12 7月, 2017 40 次提交
-
-
由 Patrick Bruenn 提交于
Replace fdtaddr and rdaddr variable names with u-boot standard names fdt_addr_r and ramdisk_addr_r. This will make the use of pxe boot more easy. Signed-off-by: NPatrick Bruenn <p.bruenn@beckhoff.com>
-
由 Diego Dorta 提交于
Add support for Falcon mode and explain in the README the steps to boot the kernel directly without loading the full U-Boot. Signed-off-by: NDiego Dorta <diego.dorta@nxp.com> Acked-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
warp can run different kernel versions, such as NXP 4.1 or mainline. Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. Succesfully tested booting a NXP 4.1 and also a mainline 4.12 kernel. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com> Acked-by: NOtavio Salvador <otavio@ossystems.com.br>
-
由 Fabio Berton 提交于
Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. Also add CONFIG_BOOTCOMMAND to run finduuid function and distro_bootcmd. This change was made based on U-Boot commit: - ca4f338eSigned-off-by: NFabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Berton 提交于
Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. This change was made based on U-Boot commit: - ca4f338eSigned-off-by: NFabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Berton 提交于
Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. This change was made based on U-Boot commit: - ca4f338eSigned-off-by: NFabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
mx6sabre boards can run different kernel versions, such as NXP 4.1 or mainline. Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. Succesfully tested booting a NXP 4.1 and also a mainline kernel on a mx6qsabresd and mx6dlsabreauto. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
WEIM cannot be used when I2C3 is enabled due to pin conflict, so keep WEIM disabled by default. I2C3 controls GPIO I2C expander (USB host and OTG have VBUS controlled by the GPIO I2C expander), magnetometer, accelerometer. Not disabling WEIM in U-Boot causes I2C3 to behave badly when booting a NXP 4.1 kernel, which leads to probe failure on several devices, including the lack of USB: imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517 By keeping WEIM disabled in U-Boot these kernel issues are gone. Reported-by: NTakashi Matsuzawa <tmatsuzawa@xevo.com> Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Stefano Babic 提交于
Change is consistent with other SOCs and it is in preparation for adding SOMs. SOC's related files are moved from cpu/ to mach-imx/<SOC>. This change is also coherent with the structure in kernel. Signed-off-by: NStefano Babic <sbabic@denx.de> CC: Fabio Estevam <fabio.estevam@nxp.com> CC: Akshay Bhat <akshaybhat@timesys.com> CC: Ken Lin <Ken.Lin@advantech.com.tw> CC: Marek Vasut <marek.vasut@gmail.com> CC: Heiko Schocher <hs@denx.de> CC: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com> CC: Christian Gmeiner <christian.gmeiner@gmail.com> CC: Stefan Roese <sr@denx.de> CC: Patrick Bruenn <p.bruenn@beckhoff.com> CC: Troy Kisky <troy.kisky@boundarydevices.com> CC: Nikita Kiryanov <nikita@compulab.co.il> CC: Otavio Salvador <otavio@ossystems.com.br> CC: "Eric Bénard" <eric@eukrea.com> CC: Jagan Teki <jagan@amarulasolutions.com> CC: Ye Li <ye.li@nxp.com> CC: Peng Fan <peng.fan@nxp.com> CC: Adrian Alonso <adrian.alonso@nxp.com> CC: Alison Wang <b18965@freescale.com> CC: Tim Harvey <tharvey@gateworks.com> CC: Martin Donnelly <martin.donnelly@ge.com> CC: Marcin Niestroj <m.niestroj@grinn-global.com> CC: Lukasz Majewski <lukma@denx.de> CC: Adam Ford <aford173@gmail.com> CC: "Albert ARIBAUD (3ADEV)" <albert.aribaud@3adev.fr> CC: Boris Brezillon <boris.brezillon@free-electrons.com> CC: Soeren Moch <smoch@web.de> CC: Richard Hu <richard.hu@technexion.com> CC: Wig Cheng <wig.cheng@technexion.com> CC: Vanessa Maegima <vanessa.maegima@nxp.com> CC: Max Krummenacher <max.krummenacher@toradex.com> CC: Stefan Agner <stefan.agner@toradex.com> CC: Markus Niebel <Markus.Niebel@tq-group.com> CC: Breno Lima <breno.lima@nxp.com> CC: Francesco Montefoschi <francesco.montefoschi@udoo.org> CC: Jaehoon Chung <jh80.chung@samsung.com> CC: Scott Wood <oss@buserror.net> CC: Joe Hershberger <joe.hershberger@ni.com> CC: Anatolij Gustschin <agust@denx.de> CC: Simon Glass <sjg@chromium.org> CC: "Andrew F. Davis" <afd@ti.com> CC: "Łukasz Majewski" <l.majewski@samsung.com> CC: Patrice Chotard <patrice.chotard@st.com> CC: Nobuhiro Iwamatsu <iwamatsu@nigauri.org> CC: Hans de Goede <hdegoede@redhat.com> CC: Masahiro Yamada <yamada.masahiro@socionext.com> CC: Stephen Warren <swarren@nvidia.com> CC: Andre Przywara <andre.przywara@arm.com> CC: "Álvaro Fernández Rojas" <noltari@gmail.com> CC: York Sun <york.sun@nxp.com> CC: Xiaoliang Yang <xiaoliang.yang@nxp.com> CC: Chen-Yu Tsai <wens@csie.org> CC: George McCollister <george.mccollister@gmail.com> CC: Sven Ebenfeld <sven.ebenfeld@gmail.com> CC: Filip Brozovic <fbrozovic@gmail.com> CC: Petr Kulhavy <brain@jikos.cz> CC: Eric Nelson <eric@nelint.com> CC: Bai Ping <ping.bai@nxp.com> CC: Anson Huang <Anson.Huang@nxp.com> CC: Sanchayan Maity <maitysanchayan@gmail.com> CC: Lokesh Vutla <lokeshvutla@ti.com> CC: Patrick Delaunay <patrick.delaunay@st.com> CC: Gary Bisson <gary.bisson@boundarydevices.com> CC: Alexander Graf <agraf@suse.de> CC: u-boot@lists.denx.de Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com> Reviewed-by: NChristian Gmeiner <christian.gmeiner@gmail.com>
-
由 Peng Fan 提交于
CONFIG_SYS_FSL_ESDHC_FORCE_VSELECT is not the correct method to set I/O to 1.8. To boards that does not support vqmmc-supply, use vs18_enable in fsl_esdhc_cfg. If regulator is supported, use fixed 1.8V regulator for vqmmc-supply. Signed-off-by: NPeng Fan <peng.fan@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: York Sun <york.sun@nxp.com> Cc: Stefano Babic <sbabic@denx.de>
-
由 Peng Fan 提交于
Handle vqmmc supply. Some boards have a fixed I/O voltage at 1.8V for emmc, so the usdhc also needs to be configured as 1.8V by setting VSELECT bit. The vs18_enable is the one that used to checking whether setting VSELECT or not in the driver. So if vqmmc supply is 1.8V, set vs18_enable, the driver will set VSELECT. Signed-off-by: NPeng Fan <peng.fan@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: York Sun <york.sun@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Peng Fan 提交于
When using eMMC with 1.8V I/O, the VSELECT bit need to be set in the USDHC controller when init. This patch adds a parameter "vs18_enable" in fsl_esdhc_cfg structure and priv data, so each controller can have different settings. We could not use CONFIG_SYS_FSL_ESDHC_FORCE_VSELECT, it has problem that it will apply to all USDHC controllers and it only set the 1.8V at init phase. So if user does not select to the eMMC device, the voltage on the I/O pins are not correct. Signed-off-by: NPeng Fan <peng.fan@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: York Sun <york.sun@nxp.com> Cc: Stefano Babic <sbabic@denx.de>
-
由 Peng Fan 提交于
The type should be int, not u8. cfg->wp_enable will finally be assigned to priv->wp_enable whose type is int. Signed-off-by: NPeng Fan <peng.fan@nxp.com>
-
由 Jagan Teki 提交于
Add u-boot-dtb.img for SPL_FS_LOAD_PAYLOAD_NAME when OF_CONTROL used. Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Vanessa Maegima 提交于
As mx6sabreauto supports SPL now, all variants can boot using the same defconfig. This patch: - Removes non-SPL targets. - Renames target to mx6sabreauto_defconfig. - Renames folder and board files to mx6sabreauto. - Updates MAINTAINERS, Makefile and Kconfig accordingly. - Removes .cfg files. - Adds a README with instructions to build and flash SPL and u-boot.img. Signed-off-by: NVanessa Maegima <vanessa.maegima@nxp.com> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com> Reviewed-by: NStefano Babic <sbabic@denx.de>
-
由 Vanessa Maegima 提交于
Add support for mx6q, mx6dl and mx6qp sabreauto boards in SPL. Retrieved the mx6q DCD table from: board/freescale/mx6qsabreauto/imximage.cfg Retrieved the mx6dl DCD table from: board/freescale/mx6qsabreauto/mx6dl.cfg Retrieved the mx6qp DCD table from: board/freescale/mx6qsabreauto/mx6qp.cfg Flashed SPL and u-boot.img to an SD card and could successfully boot it on mx6q, mx6qp and mx6dl sabreauto boards. Signed-off-by: NVanessa Maegima <vanessa.maegima@nxp.com> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com> Reviewed-by: NStefano Babic <sbabic@denx.de>
-
由 Peter Robinson 提交于
The Cubox-i and Hummingboard series of devices have an option of SATA on board, and depending on how the fuses are blown even the option to boot SPL from SATA. So enable support for it so it can be used to boot the OS from if people desire. Cc: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: NPeter Robinson <pbrobinson@gmail.com> Acked-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Gautam Bhat 提交于
This change sets the VLDO4 settings output to 2.8V in PMIC initialization so that the MIPI DSI/CSI input voltage is 2.8V as per the schematics. The original code provides an output of 3.3V which violates the voltage mentioned in the schematics. Signed-off-by: NGautam Bhat <mindentropy@gmail.com> Acked-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
Currently the following build error is seen when a board using MMC SPL is built and the MXS nand driver is also selected: arch/arm/cpu/armv7/built-in.o: In function `arch_cpu_init': arch/arm/cpu/armv7/mx6/soc.c:432: undefined reference to 'mxs_dma_init' On mx6 the only user of mxs_dma_init() is the mxs nand driver, so move it there. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Lothar Waßmann 提交于
When CONFIG_DM_ETH is set, the FEC ethernet controller is reset after the PHY has been set up and initialzed. This breaks the communication with the PHY and results in an inoperable ethernet interface. Do the initialization with CONFIG_DM_ETH in the same order as with legacy ETH support to fix this. Signed-off-by: NLothar Waßmann <LW@KARO-electronics.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Jagan Teki 提交于
imx6qdl_icore_mmc_defconfig => imx6qdl_icore_rqs_defconfig Since icorem6_rqs support MMC/eMMC boot, so doesn't need to name it explicitly. Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Florian Fainelli 提交于
Document the binding for the Broadcom STB SoCs wake-up timer node allowing the system to generate alarms and exit low power states. Acked-by: NRob Herring <robh@kernel.org> Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
-
由 Jagan Teki 提交于
Add support for the debug UART to assist with early debugging. Enable it for i.CoreM6 as an example. Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Jagan Teki 提交于
- Remove space between #define to macro - Add tab between macro and value Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Jagan Teki 提交于
Move the common baud generation code into _mxc_serial_setbrg so-that dm and non-dm can call this func. Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Jagan Teki 提交于
Move the common initialization code into _mxc_serial_init so-that dm and non-dm can call this func. Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Jagan Teki 提交于
Control reg write should be part of setbrg for better buadrate generation, so move cr1 and cr2 write to mxc_serial_setbrg Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Jagan Teki 提交于
Use RFDIV in dm-code instead of numeric value, so-that it can be common for dm and non-dm. Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Jagan Teki 提交于
This patch will add common reg space for non-dm and dm code and non-dm reg space can be accessed using mxc_base. This will - get rid of __REG volatile assignments - Make common reg_space by removing unneeded macros Signed-off-by: NJagan Teki <jagan@amarulasolutions.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Stefan Agner 提交于
i.MX 6UL and 6ULL have different boot device capabilities and use therefor use a different boot device selection table than other i.MX 6 devices. Particularly, the value which has been used so far (b0001) is assigned to QSPI boot for these two devices. There is no common reserved value for all i.MX 6devices. Use b0010 for i.MX 6UL and 6ULL via compile time ifdef. Reported-by: NJoël Esponde <joel.esponde@honeywell.com> Signed-off-by: NStefan Agner <stefan.agner@toradex.com> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com> Tested-by: NJoël Esponde <joel.esponde@honeywell.com>
-
由 Christian Gmeiner 提交于
Signed-off-by: NChristian Gmeiner <christian.gmeiner@gmail.com>
-
由 Fabio Estevam 提交于
Remove the "Q" from the file guard symbol, so that it matches the file name. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
There is no need to add a 100us delay after the DDR initialization. Other imx6 boards do not have such delay either, so simply remove it. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
SPL is already selected via CONFIG_SPL=y, so there is no need to pass it inside CONFIG_SYS_EXTRA_OPTIONS. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
SPL is already selected via CONFIG_SPL=y, so there is no need to pass it inside CONFIG_SYS_EXTRA_OPTIONS. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
SPL is already selected via CONFIG_SPL=y, so there is no need to pass it inside CONFIG_SYS_EXTRA_OPTIONS. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
SPL is already selected via CONFIG_SPL=y, so there is no need to pass it inside CONFIG_SYS_EXTRA_OPTIONS. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
-
-
由 Masahiro Yamada 提交于
DTB is encoded in big endian. When we retrieve property values, we need to use fdt32_to_cpu (aka be32_to_cpu) for endian conversion. This is a bit error-prone, but sparse is useful to detect endian mismatch. We need to use (fdt32_t *) instead of (u32 *) for a pointer of a property value. Otherwise sparse warns "cast to restricted __be32". Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-