From: Shawn Guo <shawnguo@kernel.org>
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Markus Niebel <Markus.Niebel@ew.tq-group.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: arm: fsl: add TQ-Systems boards based on i.MX6Q/QP/DL
Date: Mon, 6 Dec 2021 08:58:38 +0800 [thread overview]
Message-ID: <20211206005838.GI4216@dragon> (raw)
In-Reply-To: <20211122113740.2348-1-matthias.schiffer@ew.tq-group.com>
On Mon, Nov 22, 2021 at 12:37:38PM +0100, Matthias Schiffer wrote:
> The TQ-Systems MBa6x mainboard can be used with TQMa6 variants with
> i.MX6Q/QP/DL SoCs (TQMa6Q/QP/DL). The TQMa6Q and DL exist in two variants:
> The newer variants "A" have a hardware workaround for Erratum ERR006687,
> while variants "B" are missing such a workaround, so it needs to be
> handled in software. The erratum was fixed in i.MX6QP, so no "A" variant
> of the TQMa6QP exists.
>
> Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
Applied all, thanks!
prev parent reply other threads:[~2021-12-06 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 11:37 [PATCH v3 1/3] dt-bindings: arm: fsl: add TQ-Systems boards based on i.MX6Q/QP/DL Matthias Schiffer
2021-11-22 11:37 ` [PATCH v3 2/3] ARM: dts: imx6qdl-tqma6: add ERR006687 hardware workaround for "a" variant Matthias Schiffer
2021-11-22 11:37 ` [PATCH v3 3/3] ARM: dts: imx6qdl: add TQ-Systems MBa6x device trees Matthias Schiffer
2021-12-06 0:58 ` Shawn Guo [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=20211206005838.GI4216@dragon \
--to=shawnguo@kernel.org \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).