Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: linux-m68k@lists.linux-m68k.org
Cc: Greg Ungerer <gerg@linux-m68k.org>
Subject: [PATCH 03/13] net: fec: add device tree support for ColdFire FEC
Date: Tue, 18 Feb 2025 22:46:23 +1000	[thread overview]
Message-ID: <20250218125124.2692982-4-gerg@linux-m68k.org> (raw)
In-Reply-To: <20250218125124.2692982-1-gerg@linux-m68k.org>

The FEC hardware module used in most Freescale ColdFire SoC parts is a
simpler version of that used on the iMX family of parts. Add a devicetree
compatible entry they can use.

Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
---
 Documentation/devicetree/bindings/net/fsl,fec.yaml | 1 +
 drivers/net/ethernet/freescale/fec_main.c          | 5 +++++
 2 files changed, 6 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/fsl,fec.yaml b/Documentation/devicetree/bindings/net/fsl,fec.yaml
index 24e863fdbdab..33f73057903a 100644
--- a/Documentation/devicetree/bindings/net/fsl,fec.yaml
+++ b/Documentation/devicetree/bindings/net/fsl,fec.yaml
@@ -24,6 +24,7 @@ properties:
           - fsl,imx6q-fec
           - fsl,mvf600-fec
           - fsl,s32v234-fec
+          - fsl,m5208-fec
       - items:
           - enum:
               - fsl,imx53-fec
diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
index f7c4ce8e9a26..a0a13afe5b7c 100644
--- a/drivers/net/ethernet/freescale/fec_main.c
+++ b/drivers/net/ethernet/freescale/fec_main.c
@@ -179,6 +179,10 @@ static const struct fec_devinfo fec_s32v234_info = {
 		  FEC_QUIRK_HAS_MDIO_C45,
 };
 
+static const struct fec_devinfo fec_m5208_info = {
+	.quirks = FEC_QUIRK_MIB_CLEAR | FEC_QUIRK_HAS_FRREG,
+};
+
 static struct platform_device_id fec_devtype[] = {
 	{
 		/* keep it for coldfire */
@@ -201,6 +205,7 @@ static const struct of_device_id fec_dt_ids[] = {
 	{ .compatible = "fsl,imx8mq-fec", .data = &fec_imx8mq_info, },
 	{ .compatible = "fsl,imx8qm-fec", .data = &fec_imx8qm_info, },
 	{ .compatible = "fsl,s32v234-fec", .data = &fec_s32v234_info, },
+	{ .compatible = "fsl,m5208-fec", .data = &fec_m5208_info, },
 	{ /* sentinel */ }
 };
 MODULE_DEVICE_TABLE(of, fec_dt_ids);
-- 
2.43.0


  parent reply	other threads:[~2025-02-18 12:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 12:46 [PATCH 00/13] m68k: coldfire: proof-of-concept devicetree Greg Ungerer
2025-02-18 12:46 ` [PATCH 01/13] serial: mcf: convert to use proper platform resources Greg Ungerer
2025-02-18 12:46 ` [PATCH 02/13] serial: mcf: add devicetree support Greg Ungerer
2025-02-18 12:46 ` Greg Ungerer [this message]
2025-02-19  7:05   ` [PATCH 03/13] net: fec: add device tree support for ColdFire FEC Krzysztof Kozlowski
2025-02-19 13:25     ` Greg Ungerer
2025-02-18 12:46 ` [PATCH 04/13] m68k: coldfire: enable common clock framework Greg Ungerer
2025-02-18 12:46 ` [PATCH 05/13] m68k: coldfire: support devicetree binding for intc-simr Greg Ungerer
2025-02-18 12:46 ` [PATCH 06/13] m68k: coldfire: support devicetree binding for intc controller Greg Ungerer
2025-02-18 12:46 ` [PATCH 07/13] m68k: coldfire: support devicetree binding for intc-2 controller Greg Ungerer
2025-02-18 12:46 ` [PATCH 08/13] m68k: coldfire: add devicetree for mcf5208-evb platform Greg Ungerer
2025-02-18 12:46 ` [PATCH 09/13] m68k: coldfire: add devicetree for mcf5475-evb platform Greg Ungerer
2025-02-19  7:06   ` Krzysztof Kozlowski
2025-02-19  8:23     ` Greg Ungerer
2025-02-19  8:26       ` Krzysztof Kozlowski
2025-02-19 21:58         ` Greg Ungerer
2025-02-18 12:46 ` [PATCH 10/13] m68k: implement an embedded devicetree for nonmmu Greg Ungerer
2025-02-20 14:06   ` Geert Uytterhoeven
2025-02-23 14:25     ` Greg Ungerer
2025-02-18 12:46 ` [PATCH 11/13] m68k: implement an embedded devicetree for mm targets Greg Ungerer
2025-02-18 12:46 ` [PATCH 12/13] m68k: coldfire: disable platform device tree entries Greg Ungerer
2025-02-18 12:46 ` [PATCH 13/13] m68k: coldfire: enable devicetree use Greg Ungerer

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=20250218125124.2692982-4-gerg@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.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