From: Stefan Wahren <wahrenst@gmx.net>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Frank Li <Frank.Li@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Aswath Govindraju <a-govindraju@ti.com>
Cc: Christoph Stoidner <c.stoidner@phytec.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-can@vger.kernel.org, linux-phy@lists.infradead.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Stefan Wahren <wahrenst@gmx.net>
Subject: [PATCH RFC 1/4] dt-bindings: arm: fsl: Add chargebyte Charge Control Y
Date: Tue, 18 Aug 2026 11:16:58 +0200 [thread overview]
Message-ID: <20260818091701.6441-2-wahrenst@gmx.net> (raw)
In-Reply-To: <20260818091701.6441-1-wahrenst@gmx.net>
Add device-tree bindings for chargebyte Charge Control Y board based on
the PHYTEC phyCORE-i.MX93 SoM (System-on-Module).
Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
---
Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
index 86876311ec59..a7a1dc6b0ea3 100644
--- a/Documentation/devicetree/bindings/arm/fsl.yaml
+++ b/Documentation/devicetree/bindings/arm/fsl.yaml
@@ -1633,6 +1633,7 @@ properties:
- description: PHYTEC phyCORE-i.MX93 SoM based boards
items:
- enum:
+ - chargebyte,imx93-charge-control-y # chargebyte Charge Control Y
- phytec,imx93-phyboard-nash # phyBOARD-Nash-i.MX93
- phytec,imx93-phyboard-segin # phyBOARD-Segin with i.MX93
- const: phytec,imx93-phycore-som # phyCORE-i.MX93 SoM
--
2.43.0
next prev parent reply other threads:[~2026-08-18 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 9:16 [PATCH RFC 0/4] arm64: dts: freescale: Add chargebyte Charge Control Y Stefan Wahren
2026-08-18 9:16 ` Stefan Wahren [this message]
2026-08-18 9:16 ` [PATCH RFC 2/4] dt-bindings: phy: ti,tcan104x-can: Document Microchip MCP2542 Stefan Wahren
2026-08-18 9:24 ` sashiko-bot
2026-08-18 9:26 ` [PATCH RFC 2/4] dt-bindings: phy: ti, tcan104x-can: " Marc Kleine-Budde
2026-08-18 16:23 ` [PATCH RFC 2/4] dt-bindings: phy: ti,tcan104x-can: " Frank Li
2026-08-18 9:17 ` [PATCH RFC 3/4] phy: phy-can-transceiver: Add support for " Stefan Wahren
2026-08-18 9:27 ` Marc Kleine-Budde
2026-08-18 9:17 ` [PATCH RFC 4/4] arm64: dts: freescale: Add chargebyte Charge Control Y Stefan Wahren
[not found] ` <20260818093147.E556C1F000E9@smtp.kernel.org>
2026-08-18 13:40 ` Stefan Wahren
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=20260818091701.6441-2-wahrenst@gmx.net \
--to=wahrenst@gmx.net \
--cc=Frank.Li@nxp.com \
--cc=a-govindraju@ti.com \
--cc=c.stoidner@phytec.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-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=vkoul@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