Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Lukasz Majewski <lukma@denx.de>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 4/4] ARM: dts: mxs: Add descriptions for imx287 based btt3-[012] devices
Date: Thu, 31 Oct 2024 11:06:33 +0100	[thread overview]
Message-ID: <1a851c21-18d2-472f-95ae-b4121ffded4f@gmx.net> (raw)
In-Reply-To: <20241022133040.686562-4-lukma@denx.de>

Am 22.10.24 um 15:30 schrieb Lukasz Majewski:
> The btt3 device' HW revisions from 0 to 2 use imx287 SoC and are to
> some extend similar to already upstreamed XEA devices, hence are
> using common imx28-lwe.dtsi file.
>
> New, imx28-btt3.dtsi has been added to embrace common DTS
> properties for different HW revisions for this device.
>
> As a result - changes introduced in imx28-btt3-[012].dts are
> minimal.
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>

Assuming that Rob's comment wouldn't result in fundamental changes here:

Reviewed-by: Stefan Wahren <wahrenst@gmx.net>

      parent reply	other threads:[~2024-10-31 10:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 13:30 [PATCH v10 1/4] dt-bindings: display: Add powertip,st7272 as DT Schema description Lukasz Majewski
2024-10-22 13:30 ` [PATCH v10 2/4] dt-bindings: display: Add powertip,hx8238a " Lukasz Majewski
2024-10-22 21:01   ` Rob Herring
2024-10-22 13:30 ` [PATCH v10 3/4] dt-bindings: arm: Document the btt3 i.MX28 based board Lukasz Majewski
2024-10-22 13:30 ` [PATCH v10 4/4] ARM: dts: mxs: Add descriptions for imx287 based btt3-[012] devices Lukasz Majewski
2024-10-31  8:42   ` Lukasz Majewski
2024-10-31 10:10     ` Stefan Wahren
2024-10-31 10:34       ` Lukasz Majewski
2024-10-31 10:57         ` Stefan Wahren
2024-10-31 11:36           ` Lukasz Majewski
2024-11-06 10:57     ` Lukasz Majewski
2024-11-06 19:26       ` Stefan Wahren
2024-10-31 10:06   ` Stefan Wahren [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=1a851c21-18d2-472f-95ae-b4121ffded4f@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukma@denx.de \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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