summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* fpga: Resync various CONFIG_FPGA_* symbolsTuomas Tynkkynen2018-02-059-11/+5
| | | | | | | | | | | | | These are declared in Kconfig, but some #defines have crept in. CONFIG_FPGA CONFIG_FPGA_ALTERA CONFIG_FPGA_CYCLON2 CONFIG_FPGA_SOCFPGA CONFIG_FPGA_XILINX CONFIG_FPGA_ZYNQMPPL Signed-off-by: Tuomas Tynkkynen <tuomas@tuxera.com>
* usb: dwc2: make casts of ep->dma_buf consistentTom Rini2018-02-051-1/+1
| | | | | | | | | | | | In most places in the code we cast this to an unsigned long, but in one place we cast to an unsigned int. For consistency and to fix a warning on 64bit targets, always cast this to unsigned long. For the long term we should however change the declaration of dma_buf. Cc: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Acked-by: Lukasz Majewski <lukma@denx.de> Acked-by: Marek Vasut <marex@denx.de> Signed-off-by: Tom Rini <trini@konsulko.com>
* MAINTAINERS: board: qcom: db410c, db820c: update email.Jorge Ramirez-Ortiz2018-02-042-2/+2
| | | | | | Update email address. Signed-off-by: Jorge Ramirez-Ortiz <jramirez@baylibre.com>
* travis.yml: run buildman with option -EDaniel Schwierzeck2018-02-041-1/+1
| | | | | | This forces all compiler warnings to be treated as errors. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
* travis.yml: fix 'set +e' in build scriptDaniel Schwierzeck2018-02-041-3/+2
| | | | | | | | The build script should not manipulate shell flags (especially '-e'). A non-zero exit value can also be catched with 'cmd || ret=$?'. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
* buildman: add option -E for treating compiler warnings as errorsDaniel Schwierzeck2018-02-044-2/+10
| | | | | | | Add a new option '-E' for treating all compiler warnings as errors. Eventually this will pass 'KCFLAGS=-Werror' to Kbuild. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
* README: add doc for how to supply user specific compiler flags to KbuildDaniel Schwierzeck2018-02-041-0/+5
| | | | | | | Probably not all users are aware of this possibility, thus add a pointer to the README. Also add a useful example. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
* MAINTAINERS: Update email address for Maxime RipardMaxime Ripard2018-02-042-4/+4
| | | | | | | Free Electrons is no more and is now known as Bootlin, change my email address accordingly. Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
* Merge git://git.denx.de/u-boot-dmTom Rini2018-02-0412-6/+351
|\
| * log: add category LOGC_EFIHeinrich Schuchardt2018-02-033-0/+3
| | | | | | | | | | | | | | | | | | The EFI implementation does not fit into any of the existing categories. Provide LOGC_EFI so that EFI related message can be filtered. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Simon Glass <sjg@chromium.org>
| * log: Add a way to log error-return valuesSimon Glass2018-02-034-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When functions return an error it propagates up the stack to the point where it is reported. Often the error code provides enough information about the root cause of the error that this is obvious what went wrong. However in some cases the error may be hard to trace. For example if a driver uses several devices to perform an operation, it may not be obvious which one failed. Add a log_ret() macro to help with this. This can be used to wrap any error-return value. The logging system will then output a log record when the original error is generated, making it easy to trace the call stack of the error. This macro can significantly impact code size, so its use is controlled by a Kconfig option, which is enabled for sandbox. Signed-off-by: Simon Glass <sjg@chromium.org>
| * log: Add documentation for commands and formattingSimon Glass2018-02-031-0/+27
| | | | | | | | | | | | Add some notes about recent new features. Signed-off-by: Simon Glass <sjg@chromium.org>
| * log: Add tests for the new log featuresSimon Glass2018-02-031-1/+27
| | | | | | | | | | | | | | | | Add a test of the 'log format' and 'log rec' commands. This also covers things like log_get_cat_by_name(), since they are used by these commands. Fix a style nit in the tests also. Signed-off-by: Simon Glass <sjg@chromium.org>
| * log: Add a command to output a log recordSimon Glass2018-02-031-1/+40
| | | | | | | | | | | | | | | | Add a 'log rec' command which allows a log record to be manually output. This is useful for scripts which want full control over what is logged. It also permits easy testing of the log system. Signed-off-by: Simon Glass <sjg@chromium.org>
| * log: Add a command to control the log output formatSimon Glass2018-02-031-0/+43
| | | | | | | | | | | | | | | | Add a 'log format' command which can display or change the log output format. This is useful for changing how much information is displayed. The ordering of the fields is fixed. Signed-off-by: Simon Glass <sjg@chromium.org>
| * log: Update log_console to honour the log formatSimon Glass2018-02-032-3/+28
| | | | | | | | | | | | | | At present this just outputs the message. Update it to output whatever the format requests. Signed-off-by: Simon Glass <sjg@chromium.org>
| * log: Add control over log formattingSimon Glass2018-02-033-0/+16
| | | | | | | | | | | | | | | | | | It is useful to be able to control the output format of log records on the console. As a starting point, add definitions for controlling which elements of the log record are displayed. Use function and message as the default, since these are the most useful fields. Signed-off-by: Simon Glass <sjg@chromium.org>
| * log: Add functions to convert IDs to/from namesSimon Glass2018-02-032-2/+104
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Category and level both use an enum for their ID values. Add functions to convert these IDs to strings and vice versa. This will allow the log to output the strings instead of the (inscrutable) values. At the same time, add a new 'driver-model' category, to cover core driver-model functions and fix an incorrect value for LOGL_MAX. Tests will be added with the new 'log' subcommands. Signed-off-by: Simon Glass <sjg@chromium.org> (Updated to correct clang warnings)
| * dm: core: Add a function to look up a uclass by nameSimon Glass2018-02-033-0/+31
| | | | | | | | | | | | | | | | | | Each uclass has a driver name which we can use to look up the uclass. This is useful for logging, where the uclass ID is used as the category. Add a function to handle this, as well as a test. Signed-off-by: Simon Glass <sjg@chromium.org>
* | Merge git://git.denx.de/u-boot-imxTom Rini2018-02-0486-969/+8262
|\ \ | |/ |/|
| * imx: mx7: run sec_init for CAAM RNGBryan O'Donoghue2018-02-041-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds a sec_init call into arch_misc_init(). Doing so in conjunction with the patch "drivers/crypto/fsl: assign job-rings to non-TrustZone" enables use of the CAAM in Linux when OPTEE/TrustZone is active. u-boot will initialise the RNG and assign ownership of the job-ring registers to a non-TrustZone context. With recent changes by Lukas Auer to fully initialize the RNG in sec_init() this means that u-boot will hand-off the CAAM in a state that Linux then can use the CAAM without touching the reserved DECO registers. This change is safe both for the OPTEE/TrustZone boot path and the regular non-OPTEE/TrustZone boot path. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Peng Fan <peng.fan@nxp.com> Cc: Marco Franchi <marco.franchi@nxp.com> Cc: Vanessa Maegima <vanessa.maegima@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Lukas Auer <lukas.auer@aisec.fraunhofer.de> Tested-by: Lukas Auer <lukas.auer@aisec.fraunhofer.de> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * drivers/crypto/fsl: assign job-rings to non-TrustZoneBryan O'Donoghue2018-02-042-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After enabling TrustZone various parts of the CAAM silicon become inaccessible to non TrustZone contexts. The job-ring registers are designed to allow non TrustZone contexts like Linux to still submit jobs to CAAM even after TrustZone has been enabled. The default job-ring permissions after the BootROM look like this for job-ring zero. ms=0x00008001 ls=0x00008001 The MS field is JRaMIDR_MS (job ring MID most significant). Referring to "Security Reference Manual for i.MX 7Dual and 7Solo Applications Processors, Rev. 0, 03/2017" section 8.10.4 we see that JROWN_NS controls whether or not a job-ring is accessible from non TrustZone. Bit 15 (TrustZone) is the logical inverse of bit 3 hence the above value of 0x8001 shows that JROWN_NS=0 and TrustZone=1. Clearly then as soon as TrustZone becomes active the job-ring registers are no longer accessible from Linux, which is not what we want. This patch explicitly sets all job-ring registers to JROWN_NS=1 (non TrustZone) by default and to the Non-Secure MID 001. Both settings are required to successfully assign a job-ring to non-secure mode. If a piece of TrustZone firmware requires ownership of job-ring registers it can unset the JROWN_NS bit itself. This patch in conjunction with a modification of the Linux kernel to skip HWRNG initialisation makes CAAM usable to Linux with TrustZone enabled. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Peng Fan <peng.fan@nxp.com> Cc: Alex Porosanu <alexandru.porosanu@nxp.com> Cc: Ruchika Gupta <ruchika.gupta@nxp.com> Cc: Aneesh Bansal <aneesh.bansal@nxp.com> Link: https://github.com/OP-TEE/optee_os/issues/1408 Link: https://tinyurl.com/yam5gv9a Tested-by: Lukas Auer <lukas.auer@aisec.fraunhofer.de>
| * i2c: imx: Take mx6dqp in consideration in the I2C_PADS_INFO macroEran Matityahu2018-02-041-2/+1
| | | | | | | | | | | | | | | | | | | | We should take the MX6DP and MX6QP options in consideration in the I2C_PADS_INFO macro. Based on a patch by Pierluigi Passaro <pierluigi.p@variscite.com> Signed-off-by: Eran Matityahu <eran.m@variscite.com> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * iomux-v3: Take mx6dqp in consideration for imx_iomux_v3_setup_pad()Eran Matityahu2018-02-041-1/+1
| | | | | | | | | | | | | | | | | | | | We should take the MX6DP and MX6QP options in consideration when defining imx_iomux_v3_setup_pad(). Based on a patch by Pierluigi Passaro <pierluigi.p@variscite.com> Signed-off-by: Eran Matityahu <eran.m@variscite.com> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * doc: mxc_hab: Improve the config option listFabio Estevam2018-02-041-6/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The original text is from the time that the config options were not converted to Kconfig. After the conversion to Kconfig only CONFIG_SECURE_BOOT and CONFIG_CMD_DEKBLOB need to be selected by the user. The other config options are automatically selected by the Kconfig logic. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Reviewed-by: Breno Lima <breno.lima@nxp.com>
| * arm: dts: imx6ull: move input include to base device treeStefan Agner2018-02-042-1/+1
| | | | | | | | | | | | | | The input keycode KEY_POWER is used in the imx6ull.dtsi file, hence include the input header where used. Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
| * mx6sabresd: Add fastboot supportFabio Estevam2018-02-041-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fastboot tool is a convenient way to flash the eMMC, so add support for it. Examples of usages: On the mx6sabresd: => fastboot 0 On the Linux PC connected via USB: $ sudo fastboot getvar bootloader-version -i 0x0525 bootloader-version: U-Boot 2018.01-00550-g7517cfe finished. total time: 0.000s $ sudo fastboot reboot -i 0x0525 (this causes the mx6sabresd to reboot) Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Tested-by: Shawn Guo <shawn.guo@linaro.org>
| * mx6sabresd: Select CONFIG_CMD_USB_MASS_STORAGEFabio Estevam2018-02-042-1/+1
| | | | | | | | | | | | Select CONFIG_CMD_USB_MASS_STORAGE so that the 'ums' can be used. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
| * mx6sabre_common: Allow building CONFIG_USB_FUNCTION_MASS_STORAGEFabio Estevam2018-02-041-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Selecting CONFIG_USB_FUNCTION_MASS_STORAGE=y in the defconfig leads to the following error: cmd/built-in.o: In function `do_usb_mass_storage': cmd/usb_mass_storage.c:217: undefined reference to `fsg_main_thread' cmd/usb_mass_storage.c:170: undefined reference to `fsg_init' CONFIG_USB_FUNCTION_MASS_STORAGE option is built only for the non-SPL case as per the logic in drivers/usb/gadget/Makefile, so remove the incorrect CONFIG_SPL ifdefery to fix the build failure. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Tested-by: Shawn Guo <shawn.guo@linaro.org>
| * board: tbs2910: add private imx configSoeren Moch2018-02-042-1/+116
| | | | | | | | | | | | | | Add board specific imx config file with recommended IPU Qos settings and adapted DDR configuration. Signed-off-by: Soeren Moch <smoch@web.de>
| * imx: mx25: Remove SION bit in all pin-mux that are safeMichael Trimarchi2018-02-041-281/+290
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SION bit should be used in the situation that we need to read back the value of a pin and should not be set by default macro. We get some malfunction as raised by following thread https://www.spinics.net/lists/linux-usb/msg162574.html As reported by this application note: https://www.nxp.com/docs/en/application-note/AN5078.pdf The software input on (SION) bit is an option to force an input path to be active regardless of the value driven by the corresponding module. It is used when the nature direction of a pin depending on selected alternative function is an output, but it is needed to read the real logic value on a pin. The SION bit can be used in: • Loopback: the module of a selected alternative function drives the pad and also receives the pad value as an input • GPIO capture: the module of a selected alternative function drives the pin and the value is captured by the GPIO SION bit is not necessary when the pin is configured as a peripheral apart specific silicon bug. If an application needs to have this set, this should be done in board file or in dts file Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com> Reviewed-by: Benoît Thébaudeau <benoit.thebaudeau.dev@gmail.com> Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * imx: mx7dsabresd: enable UHS and HS200Peng Fan2018-02-042-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable UHS and HS200 for mx7dsabresd. Read Speed improvement: Kingston SD10VG2/16GB SDHC 3.0 card 22.2MB/s -> 73.7MB/s eMMC5.0 MTFC8GACAEAM: 68MB/s -> 87MB/s Signed-off-by: Peng Fan <peng.fan@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com>
| * mmc: fsl_esdhc: support SDR104 and HS200Peng Fan2018-02-042-5/+405
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce SDR104 and HS200 support The implementation takes linux kernel sdhci.c and sdhci-esdhc-imx.c as reference. - Implement esdhc_change_pinstate to dynamically change pad settings - Implement esdhc_set_timing - Implement esdhc_set_voltage to switch voltage - Implement fsl_esdhc_execute_tuning to execute time process - Enlarge the cfg->f_max to 200MHz. - Parse fsl,tuning-step, fsl,tuning-start-tap and fsl,strobe-dll-delay-target from device tree. - Parse no-1-8-v property - Introduce esdhc_soc_data to indicate the flags and caps Signed-off-by: Peng Fan <peng.fan@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
| * ARM: dts: add pinmux and tuning settings for HS200/SDR104Peng Fan2018-02-041-0/+88
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The pinmux and tuning settings are from https://source.codeaurora.org/external/imx/linux-imx/tree/arch/ arm/boot/dts/imx7s.dtsi?h=imx_4.9.11_1.0.0_ga https://source.codeaurora.org/external/imx/linux-imx/tree/arch/ arm/boot/dts/imx7d-sdb.dts?h=imx_4.9.11_1.0.0_ga To support HS200 and SDR104, we need change pinmux settings dynamically. And configure tuning step and start tuning tap, otherwise you may see tuning failure. Signed-off-by: Peng Fan <peng.fan@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com>
| * mmc: fsl_esdhc: add strobe and tuning entryPeng Fan2018-02-041-8/+12
| | | | | | | | | | | | | | | | | | | | | | | | Add entries that will be used for tuning control. The whole layout not changed, just expand reserved3[84] and rename other reservedx in sequence. Signed-off-by: Peng Fan <peng.fan@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
| * mx6memcal: fix comment in board header fileEric Nelson2018-02-041-3/+2
| | | | | | | | | | | | | | | | The board header file included a reference to the starting point from nitrogen6x.h, but since so much changed, the file bears little resemblance to that file. Signed-off-by: Eric Nelson <eric@nelint.com>
| * mx6memcal: enable SDP supportEric Nelson2018-02-043-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | The initial implementation of mx6memcal reset the CPU after running the memory calibration procedure because the generic board has no information about which boot devices are available. Now that we have SDP support in SPL, use it to allow a full U-Boot to be uploaded (i.e. to use "mtest"). Signed-off-by: Eric Nelson <eric@nelint.com> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * mx6memcal: launder through savedefconfigEric Nelson2018-02-041-5/+4
| | | | | | | | | | | | | | | | | | This patch just changes the order of configuration items in mx6memcal_defconfig to match the Kconfig layout, making it easier to track changes made using menuconfig. Signed-off-by: Eric Nelson <eric@nelint.com> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * arm: imx: mx53loco: remove usage of mx53_dram_sizePatrick Bruenn2018-02-042-39/+1
| | | | | | | | | | | | | | | | | | | | | | Static variables are not available during board_init_f(). 'static uint32_t mx53_dram_size[2];' was used in board specific dram_init(), dram_init_banksize() and get_effective_memsize() to avoid multiple calls to get_ram_size(). Reused dram initialization functions from arch/arm/mach-imx/mx5/mx53_dram.c Signed-off-by: Patrick Bruenn <p.bruenn@beckhoff.com>
| * arm: imx: m53evk: remove usage of mx53_dram_sizePatrick Bruenn2018-02-042-39/+1
| | | | | | | | | | | | | | | | | | | | | | Static variables are not available during board_init_f(). 'static uint32_t mx53_dram_size[2];' was used in board specific dram_init(), dram_init_banksize() and get_effective_memsize() to avoid multiple calls to get_ram_size(). Reused dram initialization functions from arch/arm/mach-imx/mx5/mx53_dram.c Signed-off-by: Patrick Bruenn <p.bruenn@beckhoff.com>
| * arm: imx: cx9020: move dram init into common placePatrick Bruenn2018-02-043-35/+48
| | | | | | | | | | | | | | | | Move dram_init(), dram_init_banksize() and get_effective_memsize() to arch/arm/mach-imx/mx5/mx53_dram.c, where it can be reused by m53evk and mx53loco. Signed-off-by: Patrick Bruenn <p.bruenn@beckhoff.com>
| * arm: imx: cx9020: remove usage of mx53_dram_sizePatrick Bruenn2018-02-041-9/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Static variables are not available during board_init_f(). 'static uint32_t mx53_dram_size[2];' was used in board specific dram_init(), dram_init_banksize() and get_effective_memsize() to avoid multiple calls to get_ram_size(). However multiple calls are better than undefined behavior... This fixes: https://lists.denx.de/pipermail/u-boot/2017-November/313214.html https://lists.denx.de/pipermail/u-boot/2017-December/314480.html Signed-off-by: Patrick Bruenn <p.bruenn@beckhoff.com>
| * board,ge,bx50v3 - rtc time validationNandor Han2018-02-043-1/+9
| | | | | | | | | | | | | | | | | | | | Validate the time at startup: - in case rtc error add to kernel command line RTC_ERROR - clamp date to 1-Jan-2036 Signed-off-by: Nandor Han <nandor.han@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
| * configs: ge_bx50v3: automatic partition selection and video output failure ↵Ian Ray2018-02-041-29/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | message The exact definition of a successful boot is defined by user-space. Determine the boot partition automatically. A partition is selected if file `/boot/bootcause/firstboot' exists (meaning that the partition has freshly installed software) OR if file `/boot/fitImage' exists. When userspace determines that new software was successfully installed, it must (1) delete `/boot/fitImage' on the _inactive_ partition and (2) remove `/boot/bootcause/firstboot'. Enable video, but do not display logos or other version information. Silence kernel console logging by default. Print a message to VGA screen in case of boot failure and reset bootcount to allow the user to attempt boot again. Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
| * board: ge: bx50v3: mount rootfs read-onlyHannu Lounento2018-02-041-1/+1
| | | | | | | | | | | | | | | | | | Change the kernel command line to mount the root filesystem read-only in order to be able to run filesystem check on it on boot. Signed-off-by: Hannu Lounento <hannu.lounento@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
| * configs: ge_bx50v3: enable bootcountIan Ray2018-02-041-0/+8
| | | | | | | | | | | | | | | | Enable bootcount using an EXT file. Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
| * config: ge_bx50v3: read boot scriptIan Ray2018-02-041-6/+6
| | | | | | | | | | | | | | | | Read boot script from shared partition, if available. Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
| * board: ge: bx50v3: Support FIT and select configuration based on VPDIan Ray2018-02-045-83/+20
| | | | | | | | | | | | | | | | | | | | Modify configuration to support FIT. Set variable `confidx' from VPD, in order to load the correct device tree. Modify/simplify U-Boot environment to support loading FIT image. Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
| * board: ge: bx50v3: Enable hardware watchdogMartyn Welch2018-02-042-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable the hardware watchdog on bx50v3 to cause it to reset in the event the board hangs. Configure GPIO_9 pin as WDOG1_B so that a watchdog timeout results in a full system reset. The watchdog is used and reconfigured by systemd approximately 1.7 seconds into boot. Adding a few seconds for U-Boot and a few more seconds as a safety margin. Note that the PCIe controller is _not_ put back into a safe state prior to board reset. This is a problem if board reset is implemented as CPU reset. Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
| * board: ge: bx50v3: program MAC address to I210Hannu Lounento2018-02-041-1/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are two I210s on the b850v3 and one on the b450v3 and b650v3. One is connected to Marvell 88e6240 which is already programmed. Follow the flow documented in doc/README.enetaddr: set the enet[0-9]*addr environment variable and let the driver program the hardware. The mapping from the driver's index to the environment variable's name is documented in README: Note for Redundant Ethernet Interfaces. It is assumed that eth_devices for the controllers on the board are always indexed in the same order. The environment variables are removed after programming the hardware because the variables seem to influence MAC addresses also after U-Boot. Specifically the MAC address of FEC (MC interface) would be incorrectly set: 'ethaddr', which maps to the first I210 chip and is set to I210's default address read from the driver by eth_write_hwaddr in eth_legacy.c because the variable is undefined (not set even by bx50v3.c), would result in the eth0 interface's MAC address to be set to I210's default address. Signed-off-by: Hannu Lounento <hannu.lounento@ge.com> Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
View Lorry Controller Status