From: Lukasz Majewski <lukma@denx.de>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: 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>,
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 v11 3/3] ARM: dts: mxs: Add descriptions for imx287 based btt3-[012] devices
Date: Mon, 9 Dec 2024 12:16:19 +0100 [thread overview]
Message-ID: <20241209121619.623886a4@wsk> (raw)
In-Reply-To: <c8fd371f-fd36-48c4-ad49-1e8f8db01383@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Hi Stefan,
> Am 19.11.24 um 16:52 schrieb Lukasz Majewski:
> > Dear Community,
> >
> >> 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.
> >>
> > Are there any more comments / suggestions for this patch set?
> I've send my RB for this patch on October 31th for V10, but it didn't
> made it into V11.
Sorry, I've just noticed it.
When the yaml patches are applied/accepted, I will either resend the
dts patches with your Reviewed-by or maybe this tag can be added when
applying the code by the maintainer (Shawn).
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-12-09 11:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 8:57 [PATCH v11 1/3] dt-bindings: display: Add powertip,{st7272|hx8238a} as DT Schema description Lukasz Majewski
2024-11-07 8:57 ` [PATCH v11 2/3] dt-bindings: arm: Document the btt3 i.MX28 based board Lukasz Majewski
2025-02-17 10:06 ` Shawn Guo
2024-11-07 8:57 ` [PATCH v11 3/3] ARM: dts: mxs: Add descriptions for imx287 based btt3-[012] devices Lukasz Majewski
2024-11-19 15:52 ` Lukasz Majewski
2024-12-09 8:46 ` Shawn Guo
2025-02-06 9:27 ` Lukasz Majewski
2025-02-12 8:52 ` Lukasz Majewski
2024-12-09 10:32 ` Stefan Wahren
2024-12-09 11:16 ` Lukasz Majewski [this message]
2024-12-09 9:52 ` [PATCH v11 1/3] dt-bindings: display: Add powertip,{st7272|hx8238a} as DT Schema description Lukasz Majewski
2024-12-20 10:29 ` Lukasz Majewski
2025-01-09 14:37 ` Lukasz Majewski
2025-01-09 15:12 ` Fabio Estevam
2025-01-09 15:32 ` Lukasz Majewski
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=20241209121619.623886a4@wsk \
--to=lukma@denx.de \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wahrenst@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).