From: Daniel Thompson <daniel.thompson@linaro.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Tom Rini <trini@konsulko.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
conor+dt@kernel.org, Caleb Connolly <caleb.connolly@linaro.org>,
neil.armstrong@linaro.org, Ramon Fried <rfried.dev@gmail.com>,
Dzmitry Sankouski <dsankouski@gmail.com>,
Peng Fan <peng.fan@nxp.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>,
Stephan Gerhold <stephan@gerhold.net>,
Marek Vasut <marex@denx.de>,
u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Boot Architecture Mailman List
<boot-architecture@lists.linaro.org>
Subject: Re: [PATCH 00/21] Qualcomm generic board support
Date: Mon, 4 Dec 2023 11:00:25 +0000 [thread overview]
Message-ID: <20231204110025.GA27965@aspen.lan> (raw)
In-Reply-To: <CAFA6WYMLUD9cnkr=R0Uur+1UeTMkKjM2zDdMJtXb3nmrLk+pDg@mail.gmail.com>
On Mon, Dec 04, 2023 at 11:02:57AM +0530, Sumit Garg wrote:
> + Linux kernel DT bindings maintainers, EBBR ML
>
> On Thu, 30 Nov 2023 at 20:05, Tom Rini <trini@konsulko.com> wrote:
> > On Thu, Nov 30, 2023 at 01:02:25PM +0530, Sumit Garg wrote:
> > > On Wed, 29 Nov 2023 at 22:06, Neil Armstrong <neil.armstrong@linaro.org> wrote:
> > > > > I've been thinking about and hacking on this for the last week or so,
> > > > > sorry for the delayed reply here.
> > > > >
> > > > > The value is in preventing any of the existing bindings from regressing,
> > >
> > > That is actually best addressed in Linux by checking the DTS against
> > > yaml DT bindings. We don't have that testing available in u-boot and
> > > only depend on careful reviews.
> >
> > I would absolutely love for someone to make another attempt at updating
> > our kbuild infrastucture so that we can run the validation targets.
> >
>
> Given that EBBR requires [1] the platform (firmware/bootloader) and
> not OS to supply the devicetree, it becomes evident that
> firmware/bootloaders import DTS from Linux kernel (where it is
> maintained).
>
> But currently u-boot doesn't have a proper way to validate those DTS
> against DT bindings (maintained in Linux kernel). Although there are
> Devicetree schema tools available here [2], there isn't a versioned
> release package of DT bindings which one should use to validate DTS
> files.
The kernel is regularly released in multiple forms (including git
tags and tarball). Why isn't the kernel itself sufficient to be a
versioned release of the DT bindings directory?
Daniel.
next prev parent reply other threads:[~2023-12-04 11:00 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 17:09 [PATCH 00/21] Qualcomm generic board support Caleb Connolly
2023-11-21 17:09 ` [PATCH 01/21] arm: init: export prev_bl_fdt_addr Caleb Connolly
2023-11-21 19:06 ` Tom Rini
2023-11-21 17:09 ` [PATCH 02/21] arm: allow CONFIG_LINUX_KERNEL_IMAGE_HEADER to be set in defconfig Caleb Connolly
2023-11-21 19:07 ` Tom Rini
2023-11-21 20:17 ` Caleb Connolly
2023-11-21 20:22 ` Tom Rini
2023-11-21 17:09 ` [PATCH 03/21] usb: dwc3-generic: support external vbus regulator Caleb Connolly
2023-11-21 17:09 ` [PATCH 04/21] mmc: msm_sdhci: use modern clock handling Caleb Connolly
2023-11-21 17:09 ` [PATCH 05/21] dt-bindings: drop msm_sdhci binding Caleb Connolly
2023-11-21 17:09 ` [PATCH 06/21] clk/qcom: use upstream compatible properties Caleb Connolly
2023-11-21 17:09 ` [PATCH 07/21] serial: msm: add debug UART Caleb Connolly
2023-11-21 17:09 ` [PATCH 08/21] serial: msm: fix clock handling Caleb Connolly
2023-11-21 17:09 ` [PATCH 09/21] configs: add dragonboard410c_chainloaded_defconfig Caleb Connolly
2023-11-21 19:08 ` Tom Rini
2023-11-21 20:21 ` Caleb Connolly
2023-11-21 22:11 ` Simon Glass
2023-11-21 17:09 ` [PATCH 10/21] dts: dragonboard410c: fix compatible and clocks Caleb Connolly
2023-11-21 17:09 ` [PATCH 11/21] board: dragonboard410c: import board code from mach-snapdragon Caleb Connolly
2023-11-21 17:09 ` [PATCH 12/21] board: dragonboard820c: use LINUX_KERNEL_IMAGE_HEADER Caleb Connolly
2023-11-21 17:09 ` [PATCH 13/21] mach-snapdragon: generalise board support Caleb Connolly
2023-11-21 17:09 ` [PATCH 14/21] mach-snapdragon: dynamic load addresses Caleb Connolly
2023-11-21 19:24 ` Tom Rini
2023-11-21 20:47 ` Caleb Connolly
2023-11-21 17:09 ` [PATCH 15/21] mach-snapdragon: generate fdtfile automatically Caleb Connolly
2023-11-21 17:09 ` [PATCH 16/21] doc: board/qualcomm: document generic targets Caleb Connolly
2023-11-21 17:09 ` [PATCH 17/21] dts: sdm845: import DT from Linux Caleb Connolly
2023-11-21 17:09 ` [PATCH 18/21] dts: msm8916: " Caleb Connolly
2023-11-21 19:21 ` Stephan Gerhold
2023-12-07 19:11 ` Caleb Connolly
2023-12-07 21:37 ` Stephan Gerhold
2023-11-21 17:09 ` [PATCH 19/21] dts: msm8996: " Caleb Connolly
2023-11-21 17:09 ` [PATCH 20/21] dts: qcs404-evb: " Caleb Connolly
2023-11-21 17:09 ` [PATCH 21/21] MAINTAINERS: Qualcomm: add some missing paths Caleb Connolly
2023-11-21 19:31 ` Tom Rini
2023-11-22 6:21 ` [PATCH 00/21] Qualcomm generic board support Sumit Garg
2023-11-22 14:01 ` Tom Rini
2023-11-22 14:14 ` Sumit Garg
2023-11-22 14:27 ` Tom Rini
2023-11-22 16:04 ` Caleb Connolly
2023-11-23 7:04 ` Sumit Garg
2023-11-29 15:34 ` Caleb Connolly
2023-11-29 16:36 ` Neil Armstrong
2023-11-29 17:01 ` Dennis Gilmore
2023-11-30 7:40 ` Sumit Garg
2023-11-30 7:32 ` Sumit Garg
2023-11-30 14:24 ` Caleb Connolly
2023-11-30 14:35 ` Tom Rini
2023-12-04 5:32 ` Sumit Garg
2023-12-04 10:06 ` ff
2023-12-04 11:00 ` Daniel Thompson [this message]
2023-12-04 13:24 ` Sumit Garg
2023-12-04 13:33 ` Krzysztof Kozlowski
2023-12-04 15:01 ` ff
2023-12-04 14:38 ` ff
2023-12-04 14:45 ` Krzysztof Kozlowski
2023-12-04 17:01 ` Rob Herring
2023-12-05 7:13 ` Sumit Garg
2023-12-05 7:28 ` Krzysztof Kozlowski
2023-12-05 9:45 ` Sumit Garg
2023-12-05 10:09 ` Krzysztof Kozlowski
2023-12-06 5:05 ` Sumit Garg
2023-12-06 20:42 ` Rob Herring
2023-12-07 8:08 ` ff
2023-12-07 18:51 ` Rob Herring
2023-12-07 20:24 ` ff
2023-12-07 20:31 ` Conor Dooley
2023-12-08 9:39 ` ff
2023-12-08 15:12 ` Conor Dooley
2023-12-07 13:37 ` Sumit Garg
2023-12-10 18:55 ` Tom Rini
2023-12-05 10:36 ` ff
2023-12-05 12:48 ` Daniel Thompson
2023-12-05 15:29 ` ff
2023-12-09 22:03 ` Tom Rini
2023-12-12 5:47 ` Sumit Garg
2023-12-12 20:21 ` Rob Herring
2023-12-06 10:44 ` Ilias Apalodimas
2023-12-06 11:50 ` Caleb Connolly
2023-12-10 16:05 ` Tom Rini
2023-12-05 0:52 ` Simon Glass
2023-12-05 7:44 ` Sumit Garg
2023-12-05 10:55 ` Caleb Connolly
2023-12-06 3:53 ` Simon Glass
2023-12-06 3:53 ` Simon Glass
2023-12-06 7:05 ` Sumit Garg
2023-12-06 13:00 ` Caleb Connolly
2023-11-22 7:26 ` Sumit Garg
2023-12-06 10:31 ` Ilias Apalodimas
2023-12-06 11:00 ` Mark Kettenis
2023-12-06 11:38 ` Ilias Apalodimas
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=20231204110025.GA27965@aspen.lan \
--to=daniel.thompson@linaro.org \
--cc=boot-architecture@lists.linaro.org \
--cc=caleb.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dsankouski@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=jorge.ramirez.ortiz@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=peng.fan@nxp.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=rfried.dev@gmail.com \
--cc=robh+dt@kernel.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=stephan@gerhold.net \
--cc=sumit.garg@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.