From: Petko Manolov <petko.manolov@konsulko.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: u-boot@lists.u-boot-project.org, trini@konsulko.com, uboot-imx@nxp.com
Subject: Re: [PATCH v1 1/1] arm: draeger: Dräger M48 on NXP i.MX6(Q) and Intel/Altera SoCFPGA Cyclone V devicetree.
Date: Thu, 20 Aug 2026 09:19:12 +0300 [thread overview]
Message-ID: <20260820061912.GD24421@carbon.k.g> (raw)
In-Reply-To: <CAOMZO5B-Q6R652_wp=AWXURBSP8Npr_AwJUvaw=CYSL7=bJKKg@mail.gmail.com>
On 26-08-19 13:43:26, Fabio Estevam wrote:
> Hi Petko,
>
> On Wed, Aug 19, 2026 at 12:30 PM Petko Manolov
> <petko.manolov@konsulko.com> wrote:
> >
> > Signed-off-by: Petko Manolov <petko.manolov@konsulko.com>
> > ---
> > arch/arm/dts/Makefile | 3 +
> > arch/arm/dts/imx6dl-draeger-m48.dts | 24 ++
> > arch/arm/dts/imx6q-draeger-m48.dts | 24 ++
> > arch/arm/dts/imx6qdl-draeger-m48-u-boot.dtsi | 20 +
> > arch/arm/dts/imx6qdl-draeger-m48.dtsi | 369 ++++++++++++++++++
> > arch/arm/dts/imx6qp-draeger-m48.dts | 78 ++++
>
> Sorry if I wasn't clear, but what I meant in my previous comment is that you
> need to upstream these DTS to Linux first.
Unfortunately this board runs QNX, not Linux, so upstreaming them doesn't make
sense.
> That's where the real DTS review happens. Make sure the new devicetree files
> pass dt-schema validation.
>
> You should send the i.MX and SoCFPGA patches separately to the Linux folks for
> review.
>
> In U-Boot, we want to use the DTS directly from the upstream Linux repo.
Can i use some sort of DT validation tool that pass kernel's requirements?
Petko
prev parent reply other threads:[~2026-08-20 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 15:30 [PATCH v1 0/1] arm: draeger: Add devicetrees for Draeger's M48 board Petko Manolov
2026-08-19 15:30 ` [PATCH v1 1/1] arm: draeger: Dräger M48 on NXP i.MX6(Q) and Intel/Altera SoCFPGA Cyclone V devicetree Petko Manolov
2026-08-19 16:43 ` Fabio Estevam
2026-08-20 6:19 ` Petko Manolov [this message]
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=20260820061912.GD24421@carbon.k.g \
--to=petko.manolov@konsulko.com \
--cc=festevam@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
--cc=uboot-imx@nxp.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 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.