From: Frieder Schrempf <frieder@fris.de>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Frank Li <Frank.Li@nxp.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
imx@lists.linux.dev, Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>
Cc: Annette Kobou <annette.kobou@kontron.de>,
Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: [PATCH v3 0/2] Kontron i.MX8MP OSM Devicetree Fixups
Date: Mon, 9 Mar 2026 09:57:41 +0100 [thread overview]
Message-ID: <20260309085749.25747-1-frieder@fris.de> (raw)
From: Frieder Schrempf <frieder.schrempf@kontron.de>
This contains three fixes and one cosmetic change for
the Kontron i.MX8MP OSM devices.
Changes for v3:
* Drop applied patches
* Add missing bindings patch for RV3028 RTC
Changes for v2:
* Add Frank's R-b tags (thanks)
* Enhance commit message of patch 2
Annette Kobou (1):
arm64: dts: imx8mp-kontron: Fix boot order for PMIC and RTC
Frieder Schrempf (1):
dt-bindings: rtc: microcrystal,rv3028: Allow to specify vdd-supply
.../devicetree/bindings/rtc/microcrystal,rv3028.yaml | 2 ++
arch/arm64/boot/dts/freescale/imx8mp-kontron-osm-s.dtsi | 6 ++++++
2 files changed, 8 insertions(+)
--
2.53.0
next reply other threads:[~2026-03-09 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 8:57 Frieder Schrempf [this message]
2026-03-09 8:57 ` [PATCH v3 1/2] dt-bindings: rtc: microcrystal,rv3028: Allow to specify vdd-supply Frieder Schrempf
2026-03-09 15:14 ` Krzysztof Kozlowski
2026-03-09 8:57 ` [PATCH v3 2/2] arm64: dts: imx8mp-kontron: Fix boot order for PMIC and RTC Frieder Schrempf
2026-03-09 14:59 ` [PATCH v3 0/2] Kontron i.MX8MP OSM Devicetree Fixups Frank Li
2026-03-13 9:28 ` (subset) " Alexandre Belloni
2026-03-23 23:18 ` Frank Li
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=20260309085749.25747-1-frieder@fris.de \
--to=frieder@fris.de \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=annette.kobou@kontron.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--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=linux-rtc@vger.kernel.org \
--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