From: Ezequiel Garcia <ezequiel@collabora.com>
To: netdev@vger.kernel.org, linux-rockchip@lists.infradead.org
Cc: Jose Abreu <joabreu@synopsys.com>,
Heiko Stuebner <heiko@sntech.de>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Peter Geis <pgwipeout@gmail.com>,
Ezequiel Garcia <ezequiel@collabora.com>,
kernel@collabora.com
Subject: [PATCH net-next 0/3] net: stmmac: RK3566/RK3568
Date: Tue, 13 Apr 2021 18:02:32 -0300 [thread overview]
Message-ID: <20210413210235.489467-1-ezequiel@collabora.com> (raw)
Add support for Rockchip RK3566 and RK3568 SoCs.
This has been tested on a Pine64 RK3566 Quartz64 Model B board,
DHCP and iperf are looking good.
While here, I'm adding a small patch from David Wu, for some
sanity checks for dwmac-rockchip-specific non-NULL ops.
Thanks!
David Wu (2):
net: stmmac: dwmac-rk: Check platform-specific ops
net: stmmac: Add RK3566/RK3568 SoC support
Ezequiel Garcia (1):
net: stmmac: Don't set has_gmac if has_gmac4 is set
.../bindings/net/rockchip-dwmac.txt | 2 +
.../net/ethernet/stmicro/stmmac/dwmac-rk.c | 179 +++++++++++++++++-
2 files changed, 178 insertions(+), 3 deletions(-)
--
2.30.0
next reply other threads:[~2021-04-13 21:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 21:02 Ezequiel Garcia [this message]
2021-04-13 21:02 ` [PATCH net-next 1/3] net: stmmac: Don't set has_gmac if has_gmac4 is set Ezequiel Garcia
2021-04-13 21:02 ` [PATCH net-next 2/3] net: stmmac: dwmac-rk: Check platform-specific ops Ezequiel Garcia
2021-04-13 21:02 ` [PATCH net-next 3/3] net: stmmac: Add RK3566/RK3568 SoC support Ezequiel Garcia
2021-04-13 22:51 ` Peter Geis
[not found] ` <1412-60762b80-423-d9eaa5@27901112>
2021-04-14 11:03 ` Peter Geis
2021-04-14 11:15 ` Heiko Stübner
2021-04-14 13:48 ` Ezequiel Garcia
2021-04-14 16:33 ` Chen-Yu Tsai
2021-04-14 16:35 ` Heiko Stübner
2021-04-14 16:44 ` Ezequiel Garcia
2021-04-14 13:48 ` Ezequiel Garcia
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=20210413210235.489467-1-ezequiel@collabora.com \
--to=ezequiel@collabora.com \
--cc=davem@davemloft.net \
--cc=heiko@sntech.de \
--cc=joabreu@synopsys.com \
--cc=kernel@collabora.com \
--cc=kuba@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pgwipeout@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).