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 v7 2/2] ARM: dts: mxs: Add descriptions for imx287 based btt3-[012] devices
Date: Mon, 7 Oct 2024 12:57:57 +0200 [thread overview]
Message-ID: <752dfca1-327e-48b9-8065-3aca7a4b4420@gmx.net> (raw)
In-Reply-To: <20241007115336.393f0696@wsk>
Hi Lukasz,
Am 07.10.24 um 11:53 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.
> Gentle ping on this patch series...
unfortunately most of my comments in V6 were silently ignored :(
Regards
next prev parent reply other threads:[~2024-10-07 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 14:31 [PATCH v7 1/2] dt-bindings: arm: Document the btt3 i.MX28 based board Lukasz Majewski
2024-09-25 14:31 ` [PATCH v7 2/2] ARM: dts: mxs: Add descriptions for imx287 based btt3-[012] devices Lukasz Majewski
2024-10-07 9:53 ` Lukasz Majewski
2024-10-07 10:57 ` Stefan Wahren [this message]
2024-10-08 11:35 ` Lukasz Majewski
2024-09-25 14:57 ` [PATCH v7 1/2] dt-bindings: arm: Document the btt3 i.MX28 based board Conor Dooley
2024-09-26 2:42 ` Rob Herring (Arm)
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=752dfca1-327e-48b9-8065-3aca7a4b4420@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