| Message ID | 20191120040725.32207-5-jerry.huang@nxp.com |
|---|---|
| State | Superseded |
| Headers | show |
| Series | new board ls1028ardb introduced | expand |
> diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > index 70d36fff73..6896d9a7aa 100644 > --- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > @@ -95,6 +95,15 @@ endif > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS = all > > +RCW_BOOT_MODE = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BOOT_MODE)) > +ifneq ($(RCW_BOOT_MODE),) > +RCW_PATH = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BIN)) > +RCW_FILE = $(lastword $(subst /, ,$(RCW_PATH))) > +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BOOT_MODE=$(RCW_BOOT_MODE) RCW=$(BINARIES_DIR)/$(RCW_FILE) > +ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += pbl > +ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw > +endif > + > ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP),y) > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += fip > ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-openssl Hi Jerry and all, Here arm-trusted-firmware build is modified when some host package with specific configuration is enabled in board config. Shouldn't it be the other way around ? To be more specific: another Config.in option for arm-trusted-firmware which pulls required build time dependencies, e.g. see Marvell DDR options or FIP options. Regards, Sergey
Thanks a lot for your reply. My comment in lines. Best Regards Jerry Huang > -----Original Message----- > From: Sergey Matyukevich <geomatsi@gmail.com> > Sent: Wednesday, November 20, 2019 3:50 PM > To: Jerry Huang <jerry.huang@nxp.com> > Cc: buildroot@busybox.net > Subject: [EXT] Re: [Buildroot] [PATCH 4/9] boot/arm-trusted-firmware: Add RCW > support > > Caution: EXT Email > > > diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > index 70d36fff73..6896d9a7aa 100644 > > --- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > @@ -95,6 +95,15 @@ endif > > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS = all > > > > +RCW_BOOT_MODE = $(call > qstrip,$(BR2_PACKAGE_HOST_RCW_BOOT_MODE)) > > +ifneq ($(RCW_BOOT_MODE),) > > +RCW_PATH = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BIN)) > > +RCW_FILE = $(lastword $(subst /, ,$(RCW_PATH))) > > +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += > BOOT_MODE=$(RCW_BOOT_MODE) > > +RCW=$(BINARIES_DIR)/$(RCW_FILE) > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += > > +pbl ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw endif > > + > > ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP),y) > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += fip > > ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-openssl > > Hi Jerry and all, > > Here arm-trusted-firmware build is modified when some host package with > specific configuration is enabled in board config. > > Shouldn't it be the other way around ? To be more specific: another Config.in > option for arm-trusted-firmware which pulls required build time dependencies, > e.g. see Marvell DDR options or FIP options. 1. If use another Config.in option for arm-trusted-firmware like Marvell DDR , need to mv package/rcw to boot/ directory. 2. Refer to FIP, add option like this BR2_PACKAGE_HOST_RCW_ATF in package/rcw/Config.in.host. How do you think about the second way? > Regards, > Sergey
> > > diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > index 70d36fff73..6896d9a7aa 100644 > > > --- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > @@ -95,6 +95,15 @@ endif > > > > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS = all > > > > > > +RCW_BOOT_MODE = $(call > > qstrip,$(BR2_PACKAGE_HOST_RCW_BOOT_MODE)) > > > +ifneq ($(RCW_BOOT_MODE),) > > > +RCW_PATH = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BIN)) > > > +RCW_FILE = $(lastword $(subst /, ,$(RCW_PATH))) > > > +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += > > BOOT_MODE=$(RCW_BOOT_MODE) > > > +RCW=$(BINARIES_DIR)/$(RCW_FILE) > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += > > > +pbl ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw endif > > > + > > > ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP),y) > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += fip > > > ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-openssl > > > > Hi Jerry and all, > > > > Here arm-trusted-firmware build is modified when some host package with > > specific configuration is enabled in board config. > > > > Shouldn't it be the other way around ? To be more specific: another Config.in > > option for arm-trusted-firmware which pulls required build time dependencies, > > e.g. see Marvell DDR options or FIP options. > 1. If use another Config.in option for arm-trusted-firmware like Marvell DDR , need to mv package/rcw to boot/ directory. > 2. Refer to FIP, add option like this BR2_PACKAGE_HOST_RCW_ATF in package/rcw/Config.in.host. > How do you think about the second way? Hi Jerry, Thomas, and all I think Marvell DDR was not a good example. In this case ATF does not need any sources from RCW package, only its binary. So what about the same approach as for BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33 ? The idea is not to check whether RCW host package was selected, but to request RCW as a build dependency and then use its binary. To be more specific, instead of checking BR2_PACKAGE_HOST_RCW_BOOT_MODE, just add BR2_TARGET_ARM_TRUSTED_FIRMWARE_FSL_QORIQ_RCW_BOOT_MODE and do the following in arm-trusted-firmware.mk: ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FSL_QORIQ_RCW_BOOT_MODE),y) ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += pbl ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BOOT_MODE=... CW=... endif IIUC, you don't need to move host-rcw package to boot directory. Or you need more flexibility when selecting boot mode and CW params ? Thoughts ? Comments ? Regards, Sergey
Hi, Sergey Best Regards Jerry Huang > -----Original Message----- > From: Sergey Matyukevich <geomatsi@gmail.com> > Sent: Thursday, November 21, 2019 4:03 PM > To: Jerry Huang <jerry.huang@nxp.com> > Cc: buildroot@busybox.net > Subject: Re: [EXT] Re: [Buildroot] [PATCH 4/9] boot/arm-trusted-firmware: Add > RCW support > > Caution: EXT Email > > > > > diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > > b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > > index 70d36fff73..6896d9a7aa 100644 > > > > --- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > > +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > > @@ -95,6 +95,15 @@ endif > > > > > > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS = all > > > > > > > > +RCW_BOOT_MODE = $(call > > > qstrip,$(BR2_PACKAGE_HOST_RCW_BOOT_MODE)) > > > > +ifneq ($(RCW_BOOT_MODE),) > > > > +RCW_PATH = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BIN)) > > > > +RCW_FILE = $(lastword $(subst /, ,$(RCW_PATH))) > > > > +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += > > > BOOT_MODE=$(RCW_BOOT_MODE) > > > > +RCW=$(BINARIES_DIR)/$(RCW_FILE) > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += > > > > +pbl ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw endif > > > > + > > > > ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP),y) > > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += fip > > > > ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-openssl > > > > > > Hi Jerry and all, > > > > > > Here arm-trusted-firmware build is modified when some host package > > > with specific configuration is enabled in board config. > > > > > > Shouldn't it be the other way around ? To be more specific: another > > > Config.in option for arm-trusted-firmware which pulls required build > > > time dependencies, e.g. see Marvell DDR options or FIP options. > > 1. If use another Config.in option for arm-trusted-firmware like Marvell DDR , > need to mv package/rcw to boot/ directory. > > 2. Refer to FIP, add option like this BR2_PACKAGE_HOST_RCW_ATF in > package/rcw/Config.in.host. > > How do you think about the second way? > > Hi Jerry, Thomas, and all > > I think Marvell DDR was not a good example. In this case ATF does not need any > sources from RCW package, only its binary. So what about the same approach as > for BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33 ? > The idea is not to check whether RCW host package was selected, but to request > RCW as a build dependency and then use its binary. Agree with you, now I added option BR2_PACKAGE_HOST_RCW_ATF=y to select ATF for RCW. > To be more specific, instead of checking > BR2_PACKAGE_HOST_RCW_BOOT_MODE, just add > BR2_TARGET_ARM_TRUSTED_FIRMWARE_FSL_QORIQ_RCW_BOOT_MODE > and do the following in arm-trusted-firmware.mk: > > ifeq > ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FSL_QORIQ_RCW_BOOT_MODE) > ,y) > ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += pbl > ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BOOT_MODE=... CW=... > endif Because there are different boot mode: sd, emmc, flexspi_nor, flexspi_nand, So I define the option BR2_PACKAGE_HOST_RCW_BOOT_MODE to indicate it. RCW=xxx is to indicate the location of RCW binary needed by ATF. > IIUC, you don't need to move host-rcw package to boot directory. > Or you need more flexibility when selecting boot mode and CW params ? I plan to move package/rcw into package/freescale-qoriq/ > Thoughts ? Comments ? > > Regards, > Sergey
Post the new codes: ifeq ($(BR2_PACKAGE_HOST_RCW_ATF),y) RCW_BOOT_MODE = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BOOT_MODE)) RCW_PATH = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BIN)) RCW_FILE = $(lastword $(subst /, ,$(RCW_PATH))) ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BOOT_MODE=$(RCW_BOOT_MODE) RCW=$(BINARIES_DIR)/$(RCW_FILE) ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += pbl ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-fsl-qoriq-rcw endif Best Regards Jerry Huang > -----Original Message----- > From: Jerry Huang > Sent: Thursday, November 21, 2019 4:38 PM > To: Sergey Matyukevich <geomatsi@gmail.com> > Cc: buildroot@busybox.net > Subject: RE: [EXT] Re: [Buildroot] [PATCH 4/9] boot/arm-trusted-firmware: Add > RCW support > > Hi, Sergey > > Best Regards > Jerry Huang > > > -----Original Message----- > > From: Sergey Matyukevich <geomatsi@gmail.com> > > Sent: Thursday, November 21, 2019 4:03 PM > > To: Jerry Huang <jerry.huang@nxp.com> > > Cc: buildroot@busybox.net > > Subject: Re: [EXT] Re: [Buildroot] [PATCH 4/9] > > boot/arm-trusted-firmware: Add RCW support > > > > Caution: EXT Email > > > > > > > diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > > > b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > > > index 70d36fff73..6896d9a7aa 100644 > > > > > --- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > > > +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk > > > > > @@ -95,6 +95,15 @@ endif > > > > > > > > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS = all > > > > > > > > > > +RCW_BOOT_MODE = $(call > > > > qstrip,$(BR2_PACKAGE_HOST_RCW_BOOT_MODE)) > > > > > +ifneq ($(RCW_BOOT_MODE),) > > > > > +RCW_PATH = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BIN)) > > > > > +RCW_FILE = $(lastword $(subst /, ,$(RCW_PATH))) > > > > > +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += > > > > BOOT_MODE=$(RCW_BOOT_MODE) > > > > > +RCW=$(BINARIES_DIR)/$(RCW_FILE) > > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += > > > > > +pbl ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw endif > > > > > + > > > > > ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP),y) > > > > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += fip > > > > > ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-openssl > > > > > > > > Hi Jerry and all, > > > > > > > > Here arm-trusted-firmware build is modified when some host package > > > > with specific configuration is enabled in board config. > > > > > > > > Shouldn't it be the other way around ? To be more specific: > > > > another Config.in option for arm-trusted-firmware which pulls > > > > required build time dependencies, e.g. see Marvell DDR options or FIP > options. > > > 1. If use another Config.in option for arm-trusted-firmware like > > > Marvell DDR , > > need to mv package/rcw to boot/ directory. > > > 2. Refer to FIP, add option like this BR2_PACKAGE_HOST_RCW_ATF in > > package/rcw/Config.in.host. > > > How do you think about the second way? > > > > Hi Jerry, Thomas, and all > > > > I think Marvell DDR was not a good example. In this case ATF does not > > need any sources from RCW package, only its binary. So what about the > > same approach as for > BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33 ? > > The idea is not to check whether RCW host package was selected, but to > > request RCW as a build dependency and then use its binary. > Agree with you, now I added option BR2_PACKAGE_HOST_RCW_ATF=y to select > ATF for RCW. > > > To be more specific, instead of checking > > BR2_PACKAGE_HOST_RCW_BOOT_MODE, just add > > BR2_TARGET_ARM_TRUSTED_FIRMWARE_FSL_QORIQ_RCW_BOOT_MODE > > and do the following in arm-trusted-firmware.mk: > > > > ifeq > > > ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FSL_QORIQ_RCW_BOOT_MODE) > > ,y) > > ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw > > ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += pbl > > ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BOOT_MODE=... CW=... > > endif > Because there are different boot mode: sd, emmc, flexspi_nor, flexspi_nand, So I > define the option BR2_PACKAGE_HOST_RCW_BOOT_MODE to indicate it. > RCW=xxx is to indicate the location of RCW binary needed by ATF. > > > IIUC, you don't need to move host-rcw package to boot directory. > > Or you need more flexibility when selecting boot mode and CW params ? > I plan to move package/rcw into package/freescale-qoriq/ > > > Thoughts ? Comments ? > > > > Regards, > > Sergey
diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk b/boot/arm-trusted-firmware/arm-trusted-firmware.mk index 70d36fff73..6896d9a7aa 100644 --- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk @@ -95,6 +95,15 @@ endif ARM_TRUSTED_FIRMWARE_MAKE_TARGETS = all +RCW_BOOT_MODE = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BOOT_MODE)) +ifneq ($(RCW_BOOT_MODE),) +RCW_PATH = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_BIN)) +RCW_FILE = $(lastword $(subst /, ,$(RCW_PATH))) +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BOOT_MODE=$(RCW_BOOT_MODE) RCW=$(BINARIES_DIR)/$(RCW_FILE) +ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += pbl +ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-rcw +endif + ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP),y) ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += fip ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-openssl
NXP Layerscape platforms use RCW (Reset Configure Word) to setup clocking and IO allocations and then launches the next stage of boot. RCW needs ATF as well as uboot. BR2_PACKAGE_HOST_RCW_BOOT_MODE is used to determine if ATF is used for RCW. Signed-off-by: Changming Huang <jerry.huang@nxp.com> --- boot/arm-trusted-firmware/arm-trusted-firmware.mk | 9 +++++++++ 1 file changed, 9 insertions(+)