From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@amd.com>, michal.simek@xilinx.com
Cc: luca@lucaceresoli.net, giulio.benetti@benettiengineering.com,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: transition to tarballs
Date: Wed, 04 May 2022 08:49:09 +0200 [thread overview]
Message-ID: <87h7653i8q.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220503152425.1069617-2-neal.frager@amd.com> (Neal Frager's message of "Tue, 3 May 2022 09:24:25 -0600")
>>>>> "Neal" == Neal Frager <neal.frager@amd.com> writes:
> This patch migrates configs/zynqmp_zcu106_defconfig to tarballs for TF-A, u-boot and Linux.
> This patch has zero change in code running on the device.
> The goal is to improve build speed and align with the zynq_xxx_defconfigs.
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Committed, thanks.
Notice: I'm still seeing noisy warnings from the kernel during boot, did
you hear back from Michal abot that?
[ 4.384715] zynqmp-display fd4a0000.display: vtc bridge property not present
[ 4.393156] ------------[ cut here ]------------
[ 4.397776] More than allowed devices are using the vpll_int, which is forbidden
[ 4.405204] WARNING: CPU: 1 PID: 7 at drivers/clk/zynqmp/pll.c:200 zynqmp_pll_set_rate+0x198/0x200
[ 4.414160] Modules linked in:
[ 4.417208] CPU: 1 PID: 7 Comm: kworker/u8:0 Not tainted 5.15.19 #1
[ 4.423465] Hardware name: ZynqMP ZCU106 RevA (DT)
[ 4.428250] Workqueue: events_unbound deferred_probe_work_func
[ 4.434081] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 4.441033] pc : zynqmp_pll_set_rate+0x198/0x200
[ 4.445642] lr : zynqmp_pll_set_rate+0x198/0x200
[ 4.450251] sp : ffffffc009523660
[ 4.453558] x29: ffffffc009523660 x28: ffffff887f7f6458 x27: ffffff8801d8b810
[ 4.460694] x26: 000000000000b61b x25: ffffff88014e7600 x24: 0000000000000060
[ 4.467828] x23: 0000000001fca055 x22: ffffff88014e7600 x21: ffffff88014e7680
[ 4.474963] x20: 000000000169cfa1 x19: 0000000059682ef1 x18: 0000000000000030
[ 4.482098] x17: 6962726f66207369 x16: 206863696877202c x15: 746e695f6c6c7076
[ 4.489233] x14: 2065687420676e69 x13: 6e6564646962726f x12: ffffffc00936b9b0
[ 4.496368] x11: 0000000000000141 x10: 6c6c707620656874 x9 : 00000000fffff7ff
[ 4.503503] x8 : ffffffc0093979b0 x7 : 000000000000bfe8 x6 : 80000000fffff800
[ 4.510638] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
[ 4.517773] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff880009ad80
[ 4.524909] Call trace:
[ 4.527348] zynqmp_pll_set_rate+0x198/0x200
[ 4.531609] clk_change_rate+0x148/0x2c0
[ 4.535523] clk_core_set_rate_nolock+0x154/0x240
[ 4.540220] clk_set_rate+0x38/0x150
[ 4.543787] xilinx_dp_codec_probe+0xd4/0x1f0
[ 4.548136] platform_probe+0x68/0xe0
[ 4.551790] really_probe.part.0+0x9c/0x310
[ 4.555965] __driver_probe_device+0x98/0x150
[ 4.560314] driver_probe_device+0x44/0x120
> ---
> configs/zynqmp_zcu106_defconfig | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
> diff --git a/configs/zynqmp_zcu106_defconfig b/configs/zynqmp_zcu106_defconfig
> index c8b507f0db..96b15eea81 100644
> --- a/configs/zynqmp_zcu106_defconfig
> +++ b/configs/zynqmp_zcu106_defconfig
> @@ -3,9 +3,8 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_15=y
> BR2_ROOTFS_POST_BUILD_SCRIPT="board/zynqmp/post-build.sh"
> BR2_ROOTFS_POST_IMAGE_SCRIPT="board/zynqmp/post-image.sh"
> BR2_LINUX_KERNEL=y
> -BR2_LINUX_KERNEL_CUSTOM_GIT=y
> -BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/Xilinx/linux-xlnx.git"
> -BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="xlnx_rebase_v5.15_LTS_2022.1"
> +BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,Xilinx,linux-xlnx,xlnx_rebase_v5.15_LTS_2022.1)/xlnx_rebase_v5.15_LTS_2022.1.tar.gz"
> BR2_LINUX_KERNEL_DEFCONFIG="xilinx_zynqmp"
> BR2_LINUX_KERNEL_DTS_SUPPORT=y
> BR2_LINUX_KERNEL_INTREE_DTS_NAME="xilinx/zynqmp-zcu106-revA"
> @@ -14,16 +13,14 @@ BR2_TARGET_ROOTFS_EXT2=y
> BR2_TARGET_ROOTFS_EXT2_4=y
> # BR2_TARGET_ROOTFS_TAR is not set
> BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
> -BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
> -BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://github.com/Xilinx/arm-trusted-firmware.git"
> -BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="xlnx_rebase_v2.6_2022.1"
> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL=y
> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL_LOCATION="$(call github,Xilinx,arm-trusted-firmware,xlnx_rebase_v2.6_2022.1)/xlnx_rebase_v2.6_2022.1.tar.gz"
> BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="zynqmp"
> BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31_UBOOT=y
> BR2_TARGET_UBOOT=y
> BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> -BR2_TARGET_UBOOT_CUSTOM_GIT=y
> -BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/Xilinx/u-boot-xlnx.git"
> -BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xlnx_rebase_v2022.01_2022.1"
> +BR2_TARGET_UBOOT_CUSTOM_TARBALL=y
> +BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,Xilinx,u-boot-xlnx,xlnx_rebase_v2022.01_2022.1)/xlnx_rebase_v2022.01_2022.1.tar.gz"
> BR2_TARGET_UBOOT_BOARD_DEFCONFIG="xilinx_zynqmp_virt"
> BR2_TARGET_UBOOT_CONFIG_FRAGMENT_FILES="board/zynqmp/zcu106/uboot.fragment"
> BR2_TARGET_UBOOT_NEEDS_DTC=y
> --
> 2.17.1
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-04 6:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 15:24 [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: transition to tarballs Neal Frager via buildroot
2022-05-03 15:24 ` [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2022-05-04 6:49 ` Peter Korsgaard [this message]
[not found] ` <edddb58b-dee7-21aa-05b8-3a94c3e2c4d1@xilinx.com>
2022-05-04 7:18 ` Peter Korsgaard
[not found] ` <86b8666c-4427-32c6-c015-f9b67e963195@xilinx.com>
2022-05-04 7:39 ` Peter Korsgaard
2022-05-04 8:53 ` Neal Frager
2022-05-04 9:12 ` Luca Ceresoli
2022-05-04 9:24 ` Neal Frager
2022-05-04 9:34 ` Neal Frager
[not found] ` <a430617e-f535-75c5-a848-2384c774368d@xilinx.com>
2022-05-04 9:53 ` Luca Ceresoli
[not found] ` <5dd71ac6-35a1-1d34-0964-66390cbb94ba@xilinx.com>
2022-05-04 12:45 ` Neal Frager
[not found] ` <87d7438b-6b9d-a837-c6b9-0e2f6086b8c7@xilinx.com>
2022-05-04 13:09 ` Neal Frager
2022-05-11 9:10 ` Peter Korsgaard
[not found] ` <08d36a3f-8c9b-173d-f965-fa2aef9a8c77@xilinx.com>
2022-05-11 10:08 ` Peter Korsgaard
2022-05-11 11:06 ` Neal Frager
2022-05-11 13:41 ` Neal Frager
2022-05-11 15:54 ` Peter Korsgaard
2022-05-12 14:38 ` Luca Ceresoli
2022-05-12 16:09 ` Neal Frager
2022-05-12 19:32 ` Peter Korsgaard
2022-05-13 4:21 ` Neal Frager
2022-05-13 7:17 ` Luca Ceresoli
2022-05-13 8:40 ` Neal Frager
2022-05-13 9:06 ` Neal Frager
2022-05-13 10:48 ` Neal Frager
2022-05-17 7:42 ` Luca Ceresoli
2022-05-17 7:50 ` Neal Frager
2022-05-17 7:58 ` Peter Korsgaard
2022-08-01 13:59 ` Frager, Neal via buildroot
2022-08-02 15:01 ` Luca Ceresoli via buildroot
2022-08-02 15:06 ` Frager, Neal via buildroot
2022-08-17 17:23 ` Frager, Neal via buildroot
2022-08-18 16:13 ` Luca Ceresoli via buildroot
2022-05-28 8:37 ` Peter Korsgaard
2022-05-04 6:46 ` [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: " Peter Korsgaard
2022-05-28 8:37 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7653i8q.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca@lucaceresoli.net \
--cc=michal.simek@xilinx.com \
--cc=neal.frager@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox