Re: [PATCH v5 00/11] An effort to bring DT bindings compliance within U-Boot
On Tue, 6 Feb 2024 at 18:30, Tom Rini wrote: > > On Tue, Feb 06, 2024 at 10:57:12AM +0530, Sumit Garg wrote: > > Hi Tom, > > > > On Fri, 2 Feb 2024 at 23:32, Tom Rini wrote: > > > > > > On Fri, Feb 02, 2024 at 06:35:23PM +0530, Sumit Garg wrote: > > > > > > > Changes in v5: > > > > -- > > > > - Rebased on tip of master (050a9b981d6a835133521b599be3ae189ce70f41) > > > > - Created v5_dt branch for testing purposes: > > > > https://github.com/b49020/u-boot/tree/v5_dt > > > > - Patch #6: Added support to cherry-pick fixes in subtree update script. > > > > Also, used https:// instead of git://. > > > > - Patch #7: Fixed inappropriate documentation update. > > > > - Patch #8: Document how to cherry-pick fixes from devicetree-rebasing > > > > tree. > > > > > > OK, for v6 please push this through CI. I've started a run now to check > > > other things, but just sandbox currently fails to build right now. > > > > Yeah it looks like patch#3 rework in v4 has broken EFI capsule .dtsi > > file generation logic which should be fixed by add-on fix [1] for > > patch#3. The github CI passes [2] with that included. I suppose the > > gitlab CI should be fine too. If its fine for your testing as well > > then I will incorporate it in v6. > > > > [1] > > https://github.com/u-boot/u-boot/pull/484/commits/d796c34307cd363674e0d0d2e31618643ac8e76c > > [2] https://github.com/u-boot/u-boot/pull/484 > > Yup, if Azure passes GitLab should pass too. I think you should wait to > repost v6 until you and Marek agree about how we are (and perhaps > aren't) handling fixes to dts files. > Although I haven't received any further feedback/comments but will wait for a few more days before posting v6. -Sumit > -- > Tom
Re: [PATCH v5 00/11] An effort to bring DT bindings compliance within U-Boot
On Tue, Feb 06, 2024 at 10:57:12AM +0530, Sumit Garg wrote: > Hi Tom, > > On Fri, 2 Feb 2024 at 23:32, Tom Rini wrote: > > > > On Fri, Feb 02, 2024 at 06:35:23PM +0530, Sumit Garg wrote: > > > > > Changes in v5: > > > -- > > > - Rebased on tip of master (050a9b981d6a835133521b599be3ae189ce70f41) > > > - Created v5_dt branch for testing purposes: > > > https://github.com/b49020/u-boot/tree/v5_dt > > > - Patch #6: Added support to cherry-pick fixes in subtree update script. > > > Also, used https:// instead of git://. > > > - Patch #7: Fixed inappropriate documentation update. > > > - Patch #8: Document how to cherry-pick fixes from devicetree-rebasing > > > tree. > > > > OK, for v6 please push this through CI. I've started a run now to check > > other things, but just sandbox currently fails to build right now. > > Yeah it looks like patch#3 rework in v4 has broken EFI capsule .dtsi > file generation logic which should be fixed by add-on fix [1] for > patch#3. The github CI passes [2] with that included. I suppose the > gitlab CI should be fine too. If its fine for your testing as well > then I will incorporate it in v6. > > [1] > https://github.com/u-boot/u-boot/pull/484/commits/d796c34307cd363674e0d0d2e31618643ac8e76c > [2] https://github.com/u-boot/u-boot/pull/484 Yup, if Azure passes GitLab should pass too. I think you should wait to repost v6 until you and Marek agree about how we are (and perhaps aren't) handling fixes to dts files. -- Tom signature.asc Description: PGP signature
Re: [PATCH v5 00/11] An effort to bring DT bindings compliance within U-Boot
Hi Tom, On Fri, 2 Feb 2024 at 23:32, Tom Rini wrote: > > On Fri, Feb 02, 2024 at 06:35:23PM +0530, Sumit Garg wrote: > > > Changes in v5: > > -- > > - Rebased on tip of master (050a9b981d6a835133521b599be3ae189ce70f41) > > - Created v5_dt branch for testing purposes: > > https://github.com/b49020/u-boot/tree/v5_dt > > - Patch #6: Added support to cherry-pick fixes in subtree update script. > > Also, used https:// instead of git://. > > - Patch #7: Fixed inappropriate documentation update. > > - Patch #8: Document how to cherry-pick fixes from devicetree-rebasing > > tree. > > OK, for v6 please push this through CI. I've started a run now to check > other things, but just sandbox currently fails to build right now. > Yeah it looks like patch#3 rework in v4 has broken EFI capsule .dtsi file generation logic which should be fixed by add-on fix [1] for patch#3. The github CI passes [2] with that included. I suppose the gitlab CI should be fine too. If its fine for your testing as well then I will incorporate it in v6. [1] https://github.com/u-boot/u-boot/pull/484/commits/d796c34307cd363674e0d0d2e31618643ac8e76c [2] https://github.com/u-boot/u-boot/pull/484 -Sumit > -- > Tom
Re: [PATCH v5 00/11] An effort to bring DT bindings compliance within U-Boot
On Fri, Feb 02, 2024 at 06:35:23PM +0530, Sumit Garg wrote: > Changes in v5: > -- > - Rebased on tip of master (050a9b981d6a835133521b599be3ae189ce70f41) > - Created v5_dt branch for testing purposes: > https://github.com/b49020/u-boot/tree/v5_dt > - Patch #6: Added support to cherry-pick fixes in subtree update script. > Also, used https:// instead of git://. > - Patch #7: Fixed inappropriate documentation update. > - Patch #8: Document how to cherry-pick fixes from devicetree-rebasing > tree. OK, for v6 please push this through CI. I've started a run now to check other things, but just sandbox currently fails to build right now. -- Tom signature.asc Description: PGP signature
[PATCH v5 00/11] An effort to bring DT bindings compliance within U-Boot
Changes in v5: -- - Rebased on tip of master (050a9b981d6a835133521b599be3ae189ce70f41) - Created v5_dt branch for testing purposes: https://github.com/b49020/u-boot/tree/v5_dt - Patch #6: Added support to cherry-pick fixes in subtree update script. Also, used https:// instead of git://. - Patch #7: Fixed inappropriate documentation update. - Patch #8: Document how to cherry-pick fixes from devicetree-rebasing tree. Changes in v4: -- - Switched subtree to be imported as dts/upstream sub-directory rather than devicetree-rebasing sub-directory to better suite U-Boot directory structure. - Since we now have v6.7-dts tag available now, so switch subtree to that from its beginning. - Patch #2: Incorporate build fix to adjust Bindings Makefile rules to old U-Boot Kbuild infrastructure. - Patch #3: Incorporate fix to resolve rk3399 migration issue reported by Simon. - Patch #4: New patch to reuse upstream DT includes by U-Boot as per Brian's use-case for TI K3 SoCs. - Patch #5: Added a note to OF_UPSTREAM Kconfig option. - Patch #6: New patch to add script dts/update-dts-subtree.sh as per Rob's comments. - Patch #7: Separate patch to align documentation to use Kconfig symbols instead. - Patch #8: Clarify subtree uprev schedule as a separate documentation section. Also, fixed documentation typos. - Patch #9: Added commit description. Changes in v3: -- - Patch #4: Minor commit message update - Patch #5: Replace CONFIG_* with Kconfig options - Patch #7: Dropped Makefile portion and enabled OF_UPSTREAM for SoC instead. - Patch #1, #3, #6 and #8: Picked up review tags Changes in v2: -- - Patch #1: excluded gitab CI config check and added commit description. - Patch #3: s/UBOOT_DTSI_LOC/u_boot_dtsi_loc/ - Patch #4: s/DEVICE_TREE_LOC/dt_dir/ and s/U-boot/U-Boot/ - Patch #5: s/U-boot/U-Boot/ - Patch #6 and #7: Picked up review tags Prerequisite This patch series requires devicetree-rebasing git repo to be added as a subtree to the main U-Boot repo via: $ git subtree add --prefix dts/upstream \ https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git \ v6.7-dts --squash Background -- This effort started while I was reviewing patch series corresponding to Qcom platforms [1] which was about to import modified devicetree source files from Linux kernel. I suppose keeping devicetree files sync with Linux kernel without any DT bindings schema validation has been a pain for U-Boot SoC/platform maintainers. There has been past discussions about a single DT repo but that hasn't come up and Linux kernel remained the place where DT source files as well as bindings are placed and maintained. However, Linux kernel DT maintainers proposed [2] for U-Boot to rather use devicetree-rebasing repo [3] which is a forked copy from Linux kernel for DT source files as well as bindings. It is tagged at every Linux kernel major release or intermideate release candidates. So here I have tried to reuse that to bring DT bingings compliance as well as a standard way to maintain a regular sync of DT source files with Linux kernel. In order to maintain devicetree files sync, U-Boot will maintains a Git subtree for devicetee-rebasing repo as `dts/upstream` sub-directory. U-Boot will regularly sync `dts/upstream/` subtree whenever the next window opens with the next available kernel major release. `dts/update-dts-subtree.sh` script provides a wrapper around git subtree pull command, usage from the top level U-Boot source tree, run: $ ./dts/update-dts-subtree.sh pull If required it is also possible to cherry-pick fixes from devicetree-rebasing tree prior to next sync, usage: $ ./dts/update-dts-subtree.sh pick The RFC/prototype for this series has been discussed with Linux DT maintainers as well as U-Boot maintainers here [4]. Now we would like to reach out to wider U-Boot community to seek feedback. [1] https://lore.kernel.org/all/CAFA6WYMLUD9cnkr=r0uur+1uetmkkjm2zddmjtxb3nmrlk+...@mail.gmail.com/ [2] https://lore.kernel.org/all/cal_jsqkejv2tsgmt+0zio7_qbbfhtycbgnhjhypkdfzfo9j...@mail.gmail.com/ [3] https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/ [4] https://github.com/u-boot/u-boot/pull/451 Changes --- Traditionally, U-Boot placed copies of devicetree source files from Linux kernel into `arch//dts/.dts` which can be selected via setting "" when prompted for `DEFAULT_DEVICE_TREE` by Kconfig. SoC/board maintainers are encouraged to migrate to use synced copies from `dts/upstream/src//`. To do that enable `OF_UPSTREAM` for the SoC being used via Kconfig and set up "/" when prompted for `DEFAULT_DEVICE_TREE` by Kconfig. An example have been shown for Amlogic meson-gxbb SoC and corresponding derived boards via patch #10 and #11. Devicetree bindings schema checks - With devicetee-rebasing Git subtree, the devicetree bindings are
