U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "hs@denx.de" <hs@denx.de>, "festevam@gmail.com" <festevam@gmail.com>
Cc: "agust@denx.de" <agust@denx.de>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"uboot-imx@nxp.com" <uboot-imx@nxp.com>,
	"sbabic@denx.de" <sbabic@denx.de>,
	"Schweizer, Walter" <walter.schweizer@siemens.com>,
	"Leto, Enrico" <enrico.leto@siemens.com>,
	"trini@konsulko.com" <trini@konsulko.com>
Subject: Re: [PATCH v1 15/22] siemens: imx8-capricorn.dtsi: small adaptions
Date: Mon, 11 Nov 2024 10:36:20 +0000	[thread overview]
Message-ID: <cf5df90e974abd13e14bd623425fb1fa443b0dcc.camel@siemens.com> (raw)
In-Reply-To: <4dadf359-8113-08b7-f198-42a2111cef81@denx.de>

Hello Heiko, Fabio,

On Mon, 2024-11-11 at 06:52 +0100, Heiko Schocher wrote:
> > >    arch/arm/dts/imx8-capricorn.dtsi | 16 ++++++++++++++++
> > 
> > Are there any plans to upstream this dtsi and switch to OF_UPSTREAM?
> 
> Hmm... good question! Currently we work on U-Boot to get mainline ready
> for use in production, so we get rid from NXP code.
> 
> I do not know, if we can reach this with mainline linux too...
> 
> May the siemens guys can answer this...

speaking about the concrete file, or Siemens DTs in general,
currently we don't have plans to upstream them. We are currently in fact
quite far from being able to do this. Currently it's only me working in
this direction, but... We have about 1k patches in total, where roughly
a half of them are NXP BSP patches. Another half are our configs, our
DTs and our (and DENX ;-) fixes to, say, drivers. So I try at least
to reduce the diff on the drivers, both Siemens and DENX patches.

But I don't feel that we would be able to clean up this
legacy platform to the extent that we could enable OF_UPSTREAM.

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com

  parent reply	other threads:[~2024-11-11 10:36 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  5:21 [PATCH v1 00/22] imx8qxp: siemens board: updates / sync with mainline Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 01/22] wdt: imx8qxp: add option to control external PMIC wdt via IMX8 SCU Heiko Schocher
2024-11-08  7:19   ` Stefan Roese
2024-11-08 11:47     ` Sverdlin, Alexander
2024-11-08  5:21 ` [PATCH v1 02/22] net: fec_mxc: fix probing for imx8qxp Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 03/22] tools: imx8image: Improve error message Heiko Schocher
2024-11-11  8:03   ` Sverdlin, Alexander
2024-11-08  5:21 ` [PATCH v1 04/22] imx: imx_cntr_image.sh: prevent warning for missing spl Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 05/22] imx8qxp: Fix build when using SPL Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 06/22] siemens: capricorn: move to cxg3 reference project with deneb board Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 07/22] siemens: imx8qxp-capricorn-u-boot.dtsi: fix boot Heiko Schocher
2024-11-11  8:34   ` Sverdlin, Alexander
2024-11-08  5:21 ` [PATCH v1 08/22] siemens: capricorn: use DCD_SKIP entry Heiko Schocher
2024-11-11  8:35   ` Schweizer, Walter
2024-11-11  8:49     ` Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 09/22] siemens: imximage.cfg: correct comment Heiko Schocher
2024-11-11  8:41   ` Sverdlin, Alexander
2024-11-08  5:21 ` [PATCH v1 10/22] siemens: imximage.cfg: sync image names Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 11/22] siemens: imx8-capricorn-u-boot.dtsi: add fec2 Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 12/22] siemens: capricorn: add missing ARCH_MISC_INIT Heiko Schocher
2024-11-09 12:03   ` Fabio Estevam
2024-11-08  5:21 ` [PATCH v1 13/22] siemens: configs/capricorn_cxg3_defconfig: updates Heiko Schocher
2024-11-09 12:10   ` Fabio Estevam
2024-11-11 10:04   ` Sverdlin, Alexander
2024-11-08  5:21 ` [PATCH v1 14/22] siemens: capricorn: sync spl code with 8qxp-mek Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 15/22] siemens: imx8-capricorn.dtsi: small adaptions Heiko Schocher
2024-11-09 12:03   ` Fabio Estevam
2024-11-11  5:52     ` Heiko Schocher
2024-11-11  8:25       ` Leto, Enrico
2024-11-11  8:47         ` Heiko Schocher
2024-11-11  9:24           ` Leto, Enrico
2024-11-11 12:08           ` Sverdlin, Alexander
2024-11-11 10:36       ` Sverdlin, Alexander [this message]
2024-11-08  5:21 ` [PATCH v1 16/22] siemens: capricorn: board.c fixes Heiko Schocher
2024-11-09 16:38   ` Fabio Estevam
2024-11-11  6:01     ` Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 17/22] siemens: capricorn: add HW version information to boot log Heiko Schocher
2024-11-09 12:09   ` Fabio Estevam
2024-11-11  5:57     ` Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 18/22] siemens: capricorn: get ram size from system controller Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 19/22] siemens: capricorn: get module name from eeprom Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 20/22] siemens: add ddr full memory test Heiko Schocher
2024-11-09 12:06   ` Fabio Estevam
2024-11-11  5:55     ` Heiko Schocher
2024-11-11  8:48       ` Leto, Enrico
2024-11-08  5:21 ` [PATCH v1 21/22] siemens: add ddr signal integrity test Heiko Schocher
2024-11-08  5:21 ` [PATCH v1 22/22] siemens: capricorn: update maintainers Heiko Schocher
2024-11-08 11:51   ` Sverdlin, Alexander

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=cf5df90e974abd13e14bd623425fb1fa443b0dcc.camel@siemens.com \
    --to=alexander.sverdlin@siemens.com \
    --cc=agust@denx.de \
    --cc=enrico.leto@siemens.com \
    --cc=festevam@gmail.com \
    --cc=hs@denx.de \
    --cc=sbabic@denx.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.com \
    --cc=walter.schweizer@siemens.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