From: Renaud Barbier <renaud.barbier@ametek.com>
To: barebox@lists.infradead.org
Cc: Renaud Barbier <renaud.barbier@ametek.com>
Subject: [PATCH v3 0/4] net: expand gianfar support to ls1021a
Date: Tue, 10 Feb 2026 12:52:21 +0000 [thread overview]
Message-ID: <20260210125225.981725-1-renaud.barbier@ametek.com> (raw)
This patch adds limited support for the Ethernet controller on the NXP
LS1021A:
* Only one port has been tested i.e enet1.
* The PHY negotiation has been limited to 100Mbits-FD.
In this version 3, remove code that was meant to make the difference
between the mdio register offset between PPC and ARM if retrieved from
the device tree. However, the PPC platform does not support DTBs and the
mdio offset is already taken into account into the mdio access functions.
Hence, the clean up.
Renaud Barbier (4):
net: gianfar: disable link information
gianfar: apply checkpatch recommendations
net:gianfar: add device tree support
ARM: ls1021a: initial Ethernet and mdio configuration
arch/arm/boards/ls1021aiot/board.c | 35 +++
arch/arm/configs/layerscape_v7_defconfig | 7 +
arch/arm/dts/fsl-ls1021a-iot.dts | 16 ++
arch/powerpc/include/asm/dma.h | 34 +++
drivers/net/Kconfig | 2 +-
drivers/net/gianfar.c | 310 ++++++++++++++++++-----
drivers/net/gianfar.h | 32 ++-
7 files changed, 367 insertions(+), 69 deletions(-)
--
2.43.0
next reply other threads:[~2026-02-10 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 12:52 Renaud Barbier [this message]
2026-02-10 12:52 ` [PATCH v3 1/4] net: gianfar: disable link information Renaud Barbier
2026-02-10 12:52 ` [PATCH v3 2/4] gianfar: apply checkpatch recommendations Renaud Barbier
2026-02-10 12:52 ` [PATCH v3 3/4] net:gianfar: add device tree support Renaud Barbier
2026-02-10 12:52 ` [PATCH v3 4/4] ARM: ls1021a: initial Ethernet and mdio configuration Renaud Barbier
2026-02-11 9:35 ` [PATCH v3 0/4] net: expand gianfar support to ls1021a Sascha Hauer
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=20260210125225.981725-1-renaud.barbier@ametek.com \
--to=renaud.barbier@ametek.com \
--cc=barebox@lists.infradead.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