From: Shawn Guo <shawnguo@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.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-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCHv3 0/3] Support for GE B1x5v2 and B1x5Pv2
Date: Sat, 12 Jun 2021 12:22:37 +0800 [thread overview]
Message-ID: <20210612042236.GU29138@dragon> (raw)
In-Reply-To: <20210526152243.51059-1-sebastian.reichel@collabora.com>
On Wed, May 26, 2021 at 05:22:40PM +0200, Sebastian Reichel wrote:
> Hi,
>
> This series adds support for another General Electric patient
> monitor series (similar to existing Bx50v3), which is based on
> i.MX6DL using Congatec's QMX6 module.
>
> This series has a runtime dependency on two commits, that have
> already been merged to linux-next:
>
> 1. Any imx6dl-qmx6 based boards without f765e349c3e1 ("rtc: m41t80:
> add support for fixed clock") and CONFIG_RTC_DRV_M41T80 enabled
> will result in unstable system. Because the kernel will disable
> one of the CPU clocks.
>
> 2. Booting B155(P)v2 additionally requires 94dfec48fca7 ("drm/imx:
> Add 8 pixel alignment fix") to avoid boot hanging indefinitely.
>
> Changes since PATCHv2:
> * https://lore.kernel.org/lkml/20210428222953.235280-1-sebastian.reichel@collabora.com/
> * Add Acked-by from Rob Herring to patch DT binding patches
> * Drop RTC and DRM patch (applied)
> * order DT Makefile entries alphabetically
> * order DT nodes alphabetically
> * Remove a couple of superfluous status = 'okay';
> * Move compatible property to start of nodes
> * Move status property to end of nodes (but before sub-nodes)
> * Drop useless fsl,spi-num-chipselects property
> * Update pinctrl config for audio pins fixing noise issue affecting some boards
> * rebased to v5.13-rc1
>
> Changes since PATCHv1:
> * https://lore.kernel.org/lkml/20210222171247.97609-1-sebastian.reichel@collabora.com/
> * drop patch 5 (applied)
> * instead of using 'protected-clocks' in RTC node, add fixed-clock
> node as suggested by Saravana Kannan
> * rebased to current master (68a32ba14177)
>
> Thanks,
>
> -- Sebastian
>
> Sebastian Reichel (3):
> dt-bindings: vendor-prefixes: add congatec
> dt-bindings: arm: fsl: add GE B1x5pv2 boards
> ARM: dts: imx6: Add GE B1x5v2
Applied all, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-12 4:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 15:22 [PATCHv3 0/3] Support for GE B1x5v2 and B1x5Pv2 Sebastian Reichel
2021-05-26 15:22 ` [PATCHv3 1/3] dt-bindings: vendor-prefixes: add congatec Sebastian Reichel
2021-05-26 15:22 ` [PATCHv3 2/3] dt-bindings: arm: fsl: add GE B1x5pv2 boards Sebastian Reichel
2021-05-26 15:22 ` [PATCHv3 3/3] ARM: dts: imx6: Add GE B1x5v2 Sebastian Reichel
2021-06-12 4:22 ` 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=20210612042236.GU29138@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@collabora.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).