From: "Stefan Dösinger" <stefandoesinger@gmail.com>
To: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Stefan Dösinger" <stefandoesinger@gmail.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Lee Jones" <lee@kernel.org>, "Ulf Hansson" <ulfh@kernel.org>,
"Vinod Koul" <vkoul@kernel.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Agustin Santiago Isasmendi" <isasmendi.agus@gmail.com>,
"Navid Ghahremani" <ghahramani.navid@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mfd@lists.linux.dev,
linux-pm@vger.kernel.org, linux-phy@lists.infradead.org
Subject: [PATCH 2/6] mfd: zx297520v3: Add socsys to the mfd host driver
Date: Fri, 20 Nov 2026 22:20:51 +0300 [thread overview]
Message-ID: <20261120-zx29usb-v1-2-b0433258e51b@gmail.com> (raw)
In-Reply-To: <20261120-zx29usb-v1-0-b0433258e51b@gmail.com>
This patch adds the parts of the zx297520v3 socsys controller, that can
be exposed via established driver APIs to the MFD host driver, so that
drivers in the respective subsystems can consume them. For now these are
a reset controller for Ethernet and maybe more, and a power domain
controller for USB, GSM and possibly a cryptographic engine.
Signed-off-by: Stefan Dösinger <stefandoesinger@gmail.com>
---
This series does not contain a driver for the reset child, as
implementing Ethernet is beyond the scope of the series and needs other
prerequisites (namely pincontrol).
---
drivers/mfd/zte-zx297520v3-crm.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/drivers/mfd/zte-zx297520v3-crm.c b/drivers/mfd/zte-zx297520v3-crm.c
index 7c29a860be3f..3d542e3dd7b8 100644
--- a/drivers/mfd/zte-zx297520v3-crm.c
+++ b/drivers/mfd/zte-zx297520v3-crm.c
@@ -23,6 +23,7 @@ enum zx_device_type {
TYPE_TOPCRM,
TYPE_MATRIXCRM,
TYPE_LSPCRM,
+ TYPE_SOCSYS,
};
static const struct mfd_cell zx297520v3_topcrm_cells[] = {
@@ -42,6 +43,11 @@ static const struct mfd_cell zx297520v3_lspcrm_cells[] = {
MFD_CELL_NAME("zx297520v3-lspreset"),
};
+static const struct mfd_cell zx297520v3_socsys_cells[] = {
+ MFD_CELL_NAME("zx297520v3-socsys-reset"),
+ MFD_CELL_NAME("zx297520v3-socsys-power"),
+};
+
static int zx297520v3_crm_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
@@ -77,6 +83,11 @@ static int zx297520v3_crm_probe(struct platform_device *pdev)
"Failed to deassert reset control\n");
break;
+ case TYPE_SOCSYS:
+ cells = zx297520v3_socsys_cells;
+ num_cells = ARRAY_SIZE(zx297520v3_socsys_cells);
+ break;
+
default:
return -ENODEV;
}
@@ -88,6 +99,7 @@ static const struct of_device_id of_match_zx297520v3_crm[] = {
{ .compatible = "zte,zx297520v3-topcrm", .data = (void *)TYPE_TOPCRM },
{ .compatible = "zte,zx297520v3-matrixcrm", .data = (void *)TYPE_MATRIXCRM },
{ .compatible = "zte,zx297520v3-lspcrm", .data = (void *)TYPE_LSPCRM },
+ { .compatible = "zte,zx297520v3-socsys", .data = (void *)TYPE_SOCSYS },
{ }
};
MODULE_DEVICE_TABLE(of, of_match_zx297520v3_crm);
--
2.56.1
next prev parent reply other threads:[~2026-11-20 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 19:20 [PATCH 0/6] ZTE zx297520v3 USB support Stefan Dösinger
2026-11-20 19:20 ` [PATCH 1/6] dt-bindings: soc: zte: Document zx297520v3 socsys controller Stefan Dösinger
2026-11-20 19:38 ` sashiko-bot
2026-11-20 19:20 ` Stefan Dösinger [this message]
2026-11-20 19:20 ` [PATCH 3/6] pmdomain: zte: Add a zx297520v3 power domain driver Stefan Dösinger
2026-11-20 19:51 ` sashiko-bot
2026-11-20 19:20 ` [PATCH 4/6] phy: zte: Add a zx29 USB PHY driver Stefan Dösinger
2026-11-20 19:47 ` sashiko-bot
2026-11-20 19:20 ` [PATCH 5/6] ARM: dts: zte: Declare nodes to enable the board's dwc2 controller Stefan Dösinger
2026-11-20 19:20 ` [PATCH 6/6] ARM: dts: zte: Declare the HSIC controller node Stefan Dösinger
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=20261120-zx29usb-v1-2-b0433258e51b@gmail.com \
--to=stefandoesinger@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ghahramani.navid@gmail.com \
--cc=isasmendi.agus@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=ulfh@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