This patch adds the infrastructure to define different config headers
with different configurations and default environment for the baseboards
that can now be selected via Kconfig. The new configuration for the
theadorable-x86-conga-qa3-e3845 is also added. Also the new defconfig
file for this new
This defconfig uses the PCIe x4 binary blobs from the congatec BIOS.
Signed-off-by: Stefan Roese
Cc: Simon Glass
Cc: Bin Meng
---
v4:
- Remove Gigadevice and Macronix flash support
v3:
- New patch
Hi Simon,
On Sun, Aug 6, 2017 at 1:16 PM, Simon Glass wrote:
> Hi Bin,
>
> On 3 August 2017 at 18:17, Bin Meng wrote:
>> Hi Simon,
>>
>> On Thu, Aug 3, 2017 at 11:24 PM, Simon Glass wrote:
>>> Hi Bin,
>>>
>>> On 1 August 2017 at 17:33,
Hi Stefan,
On Sun, Aug 6, 2017 at 1:13 PM, Stefan Roese wrote:
> Hi Bin,
>
>
> On 06.08.2017 02:48, Bin Meng wrote:
>>
>> On Sun, Aug 6, 2017 at 12:49 AM, Stefan Roese wrote:
>>>
>>> This patch adds the infrastructure to define different config headers
>>> with
On Sun, Aug 6, 2017 at 1:16 AM, Simon Glass wrote:
> Hi Rob,
>
> On 3 August 2017 at 10:48, Rob Clark wrote:
>> Similar to CONFIG_OF_BOARD, but in this case the fdt is still built by
>> u-boot build. This allows the board to patch the fdt, etc.
>>
>> In
On Sun, Aug 6, 2017 at 1:16 AM, Simon Glass wrote:
> Hi Rob,
>
> On 3 August 2017 at 13:36, Rob Clark wrote:
>> On Thu, Aug 3, 2017 at 3:10 PM, Brüns, Stefan
>> wrote:
>>> On Donnerstag, 3. August 2017 18:54:30 CEST Rob Clark
On Sun, Aug 6, 2017 at 1:16 AM, Simon Glass wrote:
> On 4 August 2017 at 07:16, Bin Meng wrote:
>> Hi Rob,
>>
>> On Fri, Aug 4, 2017 at 8:51 PM, Rob Clark wrote:
>>> stdin might not be set, which would cause iomux_doenv() to fail
>>>
Hi Rob,
On Sun, Aug 6, 2017 at 6:41 PM, Rob Clark wrote:
> On Sun, Aug 6, 2017 at 1:16 AM, Simon Glass wrote:
>> On 4 August 2017 at 07:16, Bin Meng wrote:
>>> Hi Rob,
>>>
>>> On Fri, Aug 4, 2017 at 8:51 PM, Rob Clark
This works (roughly) the same way as linux's, but we currently always
print lower-case (ie. we just keep %pUB and %pUL for compat with linux),
mostly just because that is what uuid_bin_to_str() supports.
%pUb: 01020304-0506-0708-090a-0b0c0d0e0f10
%pUl: 04030201-0605-0807-090a-0b0c0d0e0f10
On Sun, Aug 6, 2017 at 1:16 AM, Simon Glass wrote:
> On 4 August 2017 at 07:16, Bin Meng wrote:
>> Hi Rob,
>>
>> On Fri, Aug 4, 2017 at 8:51 PM, Rob Clark wrote:
>>> stdin might not be set, which would cause iomux_doenv() to fail
>>>
> On 06 Aug 2017, at 07:15, Simon Glass wrote:
>
> On 26 July 2017 at 04:28, Philipp Tomsich
> wrote:
>> On the RK3399, SPI3 is special (it's configured via PMUGRF). The
>> implementation of the clock-setup for SPI3 was never supported
On Sun, Aug 06, 2017 at 11:34:15AM -0400, Rob Clark wrote:
> On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark wrote:
> >
> > I've started trying to hack up test_efi_loader.py to add a test that
> > loads OpenBSD's bootloader.. kinda muddling through it at this point,
> > since not
> With SPL and TPL support for the RK3368 in place, mark SPL and TPL as
> supported from Kconfig for the RK3368. As this is primarily tested on
> the RK3368-uQ7, we'll leave it to board's individual defconfig to
> enable.
>
> Also enable DEBUG_UART_BOARD_INIT for the RK3368, so we get output
>
> To allow for a finer-grained control of features for TPL and SPL
> builds all modules/boot-methods/etc. need to be consistently selected
> based on the $(SPL_TPL_) macros.
>
> This allows splitting the associated config-options in Kconfig: we
> don't split the Kconfig options here and now, as
> Even though there's now a TPL_DM configuration option, the spl logic
> still checks for SPL_DM and thus does not pick up the proper config
> option.
>
> This introduces the use of CONFIG_IS_ENABLED(DM) in spl.c to always
> pick up the desired configuration option instead of having a
>
> The utility functions in sdram_common.c will be useful both for some
> SPL implementations (and if unused, the linked will discard these
> anyway) and for the full U-Boot stage.
>
> This changes selects sdram_common.o through the $(SPL_TPL_) macro to
> allow better control of its inclusion
> SPL_REGMAP and SPL_SYSCON were marked as depending on DM, when a
> stricter dependency of SPL_DM was possible. This commit makes the
> prereq more specific.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
>
> To use it with the DM timer driver in SPL and TPL, timer0 needs to be
> marked as pre-reloc.
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> Changes in v2:
> - add 'clock-frequency' prop to timer in the
> As SPI support may be useful in the boot-flow, this adds support for
> configuring the SPI controller's clocks in the RK3368 clock driver.
>
> Reviewed-by: Simon Glass
> Signed-off-by: Philipp Tomsich
> ---
>
> Changes in v4: None
>
> This splits the compilation of code modules for TPL and SPL for
> OF_CONTROL (and related) features between TPL and SPL. The typical
> use-case of this is a TPL stage that uses OF_PLATDATA at TPL and
> provides full OF_CONTROL at SPL (e.g. on the RK3368).
>
> Signed-off-by: Philipp Tomsich
> With the RK3368's limited TPL size, we'll want to use OF_PLATFDATA for
> the SPL stage. This implements support for OF_PLATDATA in the clock
> driver for the RK3368.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
>
> To simplify drivers/Makefile a bit when using TPL/SPL, we consistently
> use the $(SPL_TPL_) macro to test for drivers that have separate
> configuration symbols for the full U-boot, SPL and TPL stages.
> Instead of explicitly repeating them in two separate if-guarded
> sections of the Makefile,
On Sun, Aug 6, 2017 at 1:28 PM, Mark Kettenis wrote:
>> From: Rob Clark
>> Date: Sun, 6 Aug 2017 11:34:15 -0400
>>
>> On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark wrote:
>> >
>> > I've started trying to hack up test_efi_loader.py
On Sun, Aug 6, 2017 at 2:37 PM, Mark Kettenis wrote:
>> Date: Sun, 6 Aug 2017 20:21:45 +0200 (CEST)
>> From: Mark Kettenis
>>
>> > Mind sending me or pastebin'ing your u-boot .config? There are some
>> > different device-path construction
Hi Christophe,
On 05/08/2017 14:58, christophe leroy wrote:
Le 14/07/2017 à 23:45, Angelo Dureghello a écrit :
Signed-off-by: Angelo Dureghello
---
arch/m68k/Kconfig | 5 +
board/sysam/stmark2/Kconfig | 15 +++
board/sysam/stmark2/MAINTAINERS
Hi Bin,
On 05/08/2017 15:19, Bin Meng wrote:
Hi Angelo,
On Sat, Jul 15, 2017 at 5:45 AM, Angelo Dureghello wrote:
Signed-off-by: Angelo Dureghello
Can you please write something about your board in the commit message?
sure, sending patch v2.
---
On Sun, Aug 6, 2017 at 9:16 AM, Mark Kettenis wrote:
>> From: Rob Clark
>> Date: Sat, 5 Aug 2017 11:36:25 -0400
>>
>> On Sat, Aug 5, 2017 at 11:24 AM, Rob Clark wrote:
>> > On Sat, Aug 5, 2017 at 11:10 AM, Heinrich Schuchardt
Spotted this debugging OpenBSD's bootloader in qemu. (Wouldn't really
fix anything, the problem was not having any disks, but we should
probably return the correct error code.)
Signed-off-by: Rob Clark
---
lib/efi_loader/efi_boottime.c | 3 +++
1 file changed, 3
> The RK3368 GRF header was still defines with a shifted-mask but with
> non-shifted function selectors for the IOMUX defines. As the RK3368
> support is still fresh enough to allow a quick change, we do this now
> before having more code use this.
>
> Signed-off-by: Philipp Tomsich
> Adds SPL support for the RK3368 (assuming that our TPL stage has
> initialised DRAM and set up the memory firewall).
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> ---
>
> Changes in v4: None
> Changes in v3: None
> From: Klaus Goger
>
> prefix the bl31 firmware needed to build uboot.itb so it can coexist in
> the build area with ATFs from other boards (i.e. lion_rk3368)
>
> Signed-off-by: Klaus Goger
>
> Reviewed-by: Simon Glass
> To add GMAC (Gigabit Ethernet) support (limited to RGMII only at this
> point), we need support for additional pin-configuration. This commit
> adds the pinctrl support for GMAC in RGMII mode:
> * adds a PERIPH_ID_GMAC and the mapping from IRQ number to PERIPH_ID
> * configures the RGMII pins
> This adds the TPL support for the RK3368, including the u-boot-tpl.lds.
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> Changes in v4: None
> Changes in v3:
> - removes the '#define DEBUG'
> - uses the syscon
> To implement pinctrl support for the RK3368, we need to add the
> bit-definitions to configure the IOMUX and tie these into the
> pinctrl framework. This also adds the mapping from the IRQ# back
> onto the periheral id for the SPI devices.
>
> Signed-off-by: Philipp Tomsich
> TPL builds today don't need to call into firmware or set up the MMU
> (if this changes, it should be controlled through a config option
> whether to include this or not), but include the needed support code
> for this anyway. By moving these unused low-level functions into
> seperate
> From: Rob Clark
> Date: Sat, 5 Aug 2017 11:36:25 -0400
>
> On Sat, Aug 5, 2017 at 11:24 AM, Rob Clark wrote:
> > On Sat, Aug 5, 2017 at 11:10 AM, Heinrich Schuchardt
> > wrote:
> >> On 08/05/2017 04:35 PM, Rob Clark wrote:
> >>>
Hi Stefan,
On 08/04/2017 04:38 PM, Stefan Agner wrote:
From: Stefan Agner
This series adds NXP's Serial Download Protocol (SDP) support via
USB for SPL/U-Boot. It allows to download U-Boot via USB from a
(recovered) SPL using the same tools used to download SPL
On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark wrote:
>
> I've started trying to hack up test_efi_loader.py to add a test that
> loads OpenBSD's bootloader.. kinda muddling through it at this point,
> since not a py expert or too familiar w/ u-boot's test framework. But
> I'll
Update igep00x0 code with the following features:
- Add board and revision detection for the boards:
- IGEP0020-RF
- IGEP0020-RC
- IGEP0030-RG
- IGEP0030-RE
- Merge IGEP0020 and IGEP0030 mux tables
- Add suport to use GPIO_126, GPIO_127 and GPIO_129
- board_name environment variable
> For the bringup of the RK3368, we need to support TPL and SPL running
> from different addresses... which requires both stages to use a
> distinct TEXT_BASE.
>
> This commit adds support for having a separate LDSCRIPT for TPL (which
> is expected to make use of the TPL_MAX_SIZE define) and for
> Now that we have split up SPL_LDSCRIPT into a SPL and TPL variant and
> have started to use the TPL-variant for the RK3368, it's time to clean
> up behind ourselves: move both variants into Kconfig and remove them
> from the whitelist.
>
> Signed-off-by: Philipp Tomsich
> The BootROM of the RK3368 Boot ROM does not initialise cntfrq_el0.
> This change defines COUNTER_FREQUENCY, which is used by the AArch64 init
> code in arch/arm/cpu/armv8/start.S to set up cntfrq_el0.
>
> If the counter-frequency is not correctly set up, the calculation of
> delays using the
> We will to drop device security temporarily (until the ATF initialises
> it fully) from the TPL/SPL stage: this requires access to some
> registers in the SGRF.
>
> This adds the sgrf node to the rk3368.dtsi, so we can then bind a
> syscon device onto it and access its memory ranges.
>
>
> For the RK3368, we can reuse the SPI driver (although we'll have to
> eventually investigate whether it can be merged with the
> designware_spi.c driver) also used for the RK3288 and RK3399.
> This adds the necessary compatible string to support the RK3368.
>
> Note that the assumption that
> When using DM timers w/ the timer0 block within the RK3368, we no
> longer depend on the ARMv8 generic timer counting. This allows us to
> drop the secure timer initialisation from the TPL and SPL stages.
>
> The secure timer will later be set up by ATF, which starts the ARMv8
> generic timer.
> The timer-uclass depends on full OF_CONTROL through its interrogation
> of /chosen and the code to determine the clock-frequency.
>
> For the OF_PLATDATA case, these code-paths are disabled and it becomes
> the timer driver's responsibility to correctly set the clock-frequency
> in the uclass
> There is no real reason to keep the bit-definitions for the IOMUX in
> the grf header file (which defines the register layout of the GRF block):
> these should only be used by our pinctrl driver (with the possible
> exception of early debug-init code in TPL/SPL).
>
> This moves the relevant
> This commit adds support for RK3368 SoC in mkimage.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> ---
>
> Changes in v4: None
> Changes in v3: None
> Changes in v2: None
>
> tools/rkcommon.c | 1 +
> 1 file
Spotted this debugging OpenBSD's bootloader in qemu. (Wouldn't really
fix anything, the problem was not having any disks, but we should
probably return the correct error code.)
Signed-off-by: Rob Clark
---
v2: early-return in the EFI_NOT_FOUND case, as suggested by Heinrich
> Date: Sun, 6 Aug 2017 20:21:45 +0200 (CEST)
> From: Mark Kettenis
>
> > Mind sending me or pastebin'ing your u-boot .config? There are some
> > different device-path construction depending on legacy vs
> > CONFIG_DM+CONFIG_BLK (the legacy case *looks* right to me, and
Signed-off-by: Rob Clark
---
Kinda works, but since we don't have an 'exit' command like grub, we
have to reboot, which leaves the "board" in a bad state (I guess,
since the next test fails). I haven't tackled the travis bits to get
travis to download OpenBSD's bootloader,
> This adds a device-model driver for the timer block in the RK3368 (and
> similar devices that share the same timer block, such as the RK3288) for
> the down-counting (i.e. non-secure) timers.
>
> This allows us to configure U-Boot for the RK3368 in such a way that
> we can run with the secure
> The RK3368 has two SD/MMC controllers that can be used from U-Boot
> both during SPL and for booting an OS from the full bootloader stage.
> While both are configured to (mostly) sensible settings from the BROM,
> additional configuration for the MMC controller is needed to configure
> it to
> The ITS file generated warnings due to @ designations in the naming
> which cause DTC to complain as follows:
> Warning (unit_address_vs_reg): Node /images/uboot@1 has a unit name, but no
> reg property
> Warning (unit_address_vs_reg): Node /images/atf@1 has a unit name, but no
> reg
> On the RK3368 we use a TPL-stage similar to Rockchip's DDR init
> (i.e. it initialises DRAM, leaves some info for the next stage and
> returns to the BootROM). To allow compatibility with Rockchip's DDR
> init code, we use the same register os_reg2 in pmugrf for passing
> this info (i.e. DRAM
> The RK3368 option in Kconfig referred to the RK3328 (copy-and-paste)
> and had a few typos and unnecessarily used UTF-8 characters. While
> fixing this, I also reformatted and further clarified the text
> (e.g. made the grouping into a a big and little cluster of 4 cores
> each explicit).
>
>
> On he RK3368, we need to temporarily disable security on the DMA
> engines during TPL and SPL to allow the MMC host to DMA into DRAM. To
> do so, we need to reset the two DMA engines, which in turn requires
> the DMA1_SRST_REQ and DMA2_SRST_REQ constants to refer to the
> appropriate bits in
> We can finally drop TPL_STACK, TPL_TEXT_BASE and TPL_MAX_SIZE off the
> whitelist (this time it's really happening!) and migrate the setting
> (only used on the RK3368-uQ7 so far) into Kconfig.
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> Handling TPL and SPL in the Makefile for mach-rockchip was based on
> nested if checks and/or if-else-if paths. This can be simplified and
> made more readable by using $(SPL_TPL_) and by introducing
> intermediate variables for the aggregation of SPL and TPL features.
>
> Signed-off-by:
> To implement a TPL stage (incl. its DRAM controller setup) for the
> RK3368, we'll want to configure the DPLL (DRAM PLL).
>
> This commit implements setting the DPLL (CLK_DDR) and provides PLL
> configuration details for the common DRAM operating speeds found on
> RK3368 boards.
>
>
> For the RK3368, we want to use OF_PLATDATA in TPL, but full OF_CONTROL
> in SPL: this requires the introduction of a new family of
> configuration options to decouple SPL_OF_CONTROL and SPL_OF_PLATDATA
> from TPL.
>
> Consequently, Makefile.spl needs to be adjusted to test for these
>
> This change introduces TPL variants of the REGMAP and SYSCON config
> options (i.e. TPL_REGMAP and TPL_SYSCON in analogy to SPL_REGMAP and
> SPL_SYSCON) in preparation of a finer-grained feature selection for
> building feature-rich TPL variants.
>
> Signed-off-by: Philipp Tomsich
On Sun, Aug 6, 2017 at 6:49 PM, Rob Clark wrote:
> On Sun, Aug 6, 2017 at 1:28 PM, Mark Kettenis wrote:
>>> From: Rob Clark
>>> Date: Sun, 6 Aug 2017 11:34:15 -0400
>>>
>>> On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark
On 4 August 2017 at 14:52, Philipp Tomsich
wrote:
> With the hierarchical defaults set up, we remove these from the header
> files. To do so, I've run moveconfig on SPL_LDSCRIPT and this commits
> the changes.
>
> Signed-off-by: Philipp Tomsich
On 26 July 2017 at 05:22, Philipp Tomsich
wrote:
> With both an imply from CMD_USB to USB_FUNCTION_MASS_STORAGE and with
> USB_FUNCTION_MASS_STORAGE moved to Kconfig, we can now run moveconfig.
>
> Signed-off-by: Philipp Tomsich
Hi Philipp,
On 4 August 2017 at 14:52, Philipp Tomsich
wrote:
> With SPL_LDSCRIPT moved to Kconfig (and this being a 'string' config
> node), all the lingering definitions in header files will cause errors
> due to the redefinition of the configuration
On 08/06/2017 05:34 PM, Rob Clark wrote:
> On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark wrote:
>>
>> I've started trying to hack up test_efi_loader.py to add a test that
>> loads OpenBSD's bootloader.. kinda muddling through it at this point,
>> since not a py expert or too
> As the debug uart is marked as dm-pre-reloc, the pinctrl driver
> will handle the correct iomux setting.
>
> Signed-off-by: Andy Yan
> Acked-by: Philipp Tomsich
> Reviewed-by: Philipp Tomsich
> Device drivers like debug serial, dmc should be enabled before
> relocation, so add u-boot.dtsi files to contain devices that
> should be marked as dm-pre-reloc.
>
> Signed-off-by: Andy Yan
> Reviewed-by: Philipp Tomsich
>
> The RK3368-uQ7 (codenamed 'Lion') is a micro-Qseven (40mm x 70mm,
> MXM-230 edge connector compatible with the Qseven specification)
> form-factor system-on-module based on the octo-core Rockchip RK3368.
> It is designed, supported and manufactured by Theobroma Systems.
>
> It provides the
> The RK3368 TRM recommends to configure the bandwith adjustment (CON2)
> for PLLs to NF/2. This implements this for all reconfigurations of
> PLLs and removes the 'has_bwadj' flag (as the RK3368 always has the
> bandwidth-adjustment feature according to its manual).
>
> Signed-off-by: Philipp
> Introduce TPL_CLK to allow finer-grained selection of TPL features
> for feature-rich (i.e. DM-based) TPL stages.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> Reviewed-by: Tom Rini
> ---
>
>
> To allow a TPL and SPL to run from different addresses/memories, we
> need to split setup of the TPL and SPL stacks. To do so, we introduce
> CONFIG_TPL_STACK (not listed in Kconfig) which can be used to override
> the initial stack pointer for TPL.
>
> To provide backward compatibility for
> The original clock support for MMC/SD cards on the RK3368 suffered
> from a tendency to select a divider less-or-equal to the the one
> giving the requested clock-rate: this can lead to higher-than-expected
> (or rather: higher than supported) clock rates for the MMC/SD
> communiction.
>
> This
> With the changes to split SPL/TPL for the RK3368, I apparently missed
> some needed adjustments to the RK3188 Kconfig and rock_defconfig.
>
> This fixes build-issues for the rock board after applying the RK3368
> enablement (and SPL/TPL) set that resulted from TPL_SERIAL_SUPPORT,
>
> For full SPL support, including DRAM initialisation, we need a few
> nodes from the DTS: this commit adds the DMC (DRAM controller) node,
> the service_msch (memory scheduler) node and marks GRF, PMUGRF and CRU
> as 'u-boot,dm-pre-reloc'. In addition to this, we also include the
> dt-binding
> This adds the TPL_DRIVER_MISC_SUPPORT option to allow activation of
> DRIVER_MISC_SUPPORT for devices that need it in the TPL stage.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> Reviewed-by: Tom Rini
> With the clock support in rk3368_clk_set_rate() conditionalized on
> various feature definitions, 'priv' can remain unused (e.g. in the
> SPL build when only MMC is enabled).
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
On Sun, Aug 06, 2017 at 12:00:21AM -0500, Derald D. Woods wrote:
> This patch brings the OMAP3 EVM to a bootable state, on master, as of
> v2017.09-rc1.
>
> Signed-off-by: Derald D. Woods
>
Reviewed-by: Tom Rini
--
Tom
signature.asc
> In TPL we will need to configure security in the SGRF of the RK3368.
> This change adds support for the SGRF as a syscon device, so we can
> retrieve its address range through the syscon API in TPL (and can
> avoid having to hard-code the address).
>
> Signed-off-by: Philipp Tomsich
> This adds a DRAM controller driver for the RK3368 and places it in
> drivers/ram/rockchip (where the other DM-enabled DRAM controller
> drivers for rockchip devices should also be moved eventually).
>
> At this stage, only the following feature-set is supported:
> - DDR3
> - 32-bit
> To enable the GMAC on the RK3368, we need to set up the clocking
> appropriately to generate a tx_clk for the MAC.
>
> This adds an implementation that implements the use of the <_gmac>
> clock (i.e. an external 125MHz clock for RGMII provided by the PHY).
> This is the clock setup used by the
> With SPL_LDSCRIPT moved to Kconfig (and this being a 'string' config
> node), all the lingering definitions in header files will cause errors
> due to the redefinition of the configuration item.
>
> As we don't want to pollute the defconfig files (and values should
> usually be identical for
> Set TPL_LDSCRIPT in Kconfig, so we don't have to pollute our
> header file.
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> Changes in v4:
> - (added) sets TPL_LDSCRIPT via Kconfig
>
> Changes in v3: None
>
> From: Rob Clark
> Date: Sun, 6 Aug 2017 11:34:15 -0400
>
> On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark wrote:
> >
> > I've started trying to hack up test_efi_loader.py to add a test that
> > loads OpenBSD's bootloader.. kinda muddling through it at
> To fully support DM timer in SPL and TPL, we need a few things cleaned
> up and normalised:
> - inclusion of the uclass and drivers should be an all-or-nothing
> decision for each stage and under control of $(SPL_TPL_)TIMER
> instead of having the two-level configuration with TIMER and
>
> In order to reuse the support for the u-boot,spl-boot-order property
> from the rk3399, we split it into a reusable module that can be
> included by the SPL code for any of our boards.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> This commit models the dependency from SPL_RAM to SPL_DM in Kconfig.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> Reviewed-by: Tom Rini
> ---
>
> Changes in v4: None
> Changes in v3: None
>
> There is no reasonably robust way (this will be needed so early that
> diagnostics will be limited) to specify the base-address of the secure
> timer through the DTS for TPL and SPL. In order to allow us a cleaner
> way to structure our SPL and TPL stage, we now move to a DM timer
> driver.
>
> Let's clean up behind ourselves and move the (newly defined)
> TPL_STACK, TPL_MAX_SIZE and TPL_TEXT_BASE into Kconfig. Given that
> 0x0 might be considered to be valid values for TPL_TEXT_BASE and
> TPL_STACK, we need to introduce helper config options
> ("TPL_NEEDS_SEPARATE_...") to indicate
> SPL_CLK should also depend on SPL_DM (and not just on CLK).
> Add the additional dependency.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> Reviewed-by: Tom Rini
> ---
>
> Changes in v4: None
>
> From: Rob Clark
> Date: Sun, 6 Aug 2017 13:49:43 -0400
>
> On Sun, Aug 6, 2017 at 1:28 PM, Mark Kettenis wrote:
> >> From: Rob Clark
> >> Date: Sun, 6 Aug 2017 11:34:15 -0400
> >>
> >> On Sun, Aug 6, 2017 at 10:45 AM, Rob
> The back-to-bootrom option is rather unfortunately named
> CONFIG_ROCKCHIP_SPL_BACK_TO_BOOTROM
> instead of
> CONFIG_SPL_ROCKCHIP_BACK_TO_BOOTROM
>
> To make is selectable through CONFIG_IS_ENABLED(ROCKCHIP_BACK_TO_BOOTROM),
> we need to rename it. At the same time, we introduce a TPL_
> On the RK3368, we want our TPL to use the 'return to bootrom' boot
> method (to have the bootrom load up the SPL stage) and then continue
> with different boot methods (MMC, SPI, etc.) from SPL.
>
> This adds the config option needed to control the availabily of the
> 'return to bootrom'
> TPL_NAND_SUPPORT, TPL_SERIAL_SUPPORT, TPL_SPI_FLASH_SUPPORT and
> TPL_SPI_SUPPORT refer to SPL in their help text. This fixes up
> the description to correctly reference TPL.
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> With the finer-grained control over LIBGENERIC_SUPPORT for TPL/SPL (i.e.
> with the newly introduced distinction between TPL_LIBGENERIC_SUPPORT and
> SPL_LIBGENERIC_SUPPORT), we can simplify the #ifdef-check to simply use
> CONFIG_IS_ENABELD.
>
> Signed-off-by: Philipp Tomsich
> To allow finer grained selection of features for TPL, we introduce
> TPL_RAM (in analogy to SPL_RAM).
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> Reviewed-by: Tom Rini
> ---
>
> Changes in
> Now that TPL_STACK has been moved off the whitelist (ok, I'm lying:
> the 'moving off the whitelist' part comes in once moveconfig
> runs... which will be a few commits down the line) and added to
> Kconfig, we need to test CONFIG_TPL_NEEDS_SEPARATE_STACK to see
> whether the value from
> The RK3368 has both a limited TPL size (just 0x7000 bytes) and the
> added challenge of booting in AArch64, which increases the code size
> for TPL (particularily when using the LP64 programming model). For
> this reason we expect the RK3368 to always use OF_PLATDATA for its
> TPL stage.
>
>
> For the RK3368, we use a multi-stage boot-process consisting of the
> following:
> 1. TPL: initalises DRAM, returns to boot-ROM (which then loads
>the next stage and transfers control to it)
> 2. SPL: a full-features SPL stage including OF_CONTROL and FIT
>image
1 - 100 of 131 matches
Mail list logo