From: Tobias Schramm <t.schramm@manjaro.org>
To: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Heiko Stuebner <heiko@sntech.de>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
David Wu <david.wu@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Tobias Schramm <t.schramm@manjaro.org>
Subject: [PATCH 0/3] Add support for RK3308 gmac
Date: Fri, 14 May 2021 13:38:10 +0200 [thread overview]
Message-ID: <20210514113813.2093534-1-t.schramm@manjaro.org> (raw)
The Rockchip RK3308 SoC features an internal gmac. Only the signals
required for RMII are exposed so it is limited to 10/100 Mbit/s operation.
This patchset adds support for it.
I've tested the patchset on a Rock Pi S, works fine.
Cheers,
Tobias
Tobias Schramm (3):
dt-bindings: net: rockchip-dwmac: add rk3308 gmac compatible
net: stmmac: dwmac-rk: add support for rk3308 gmac
arm64: dts: rockchip: add gmac to rk3308 dts
.../bindings/net/rockchip-dwmac.yaml | 2 +
arch/arm64/boot/dts/rockchip/rk3308.dtsi | 22 +++++++++
.../net/ethernet/stmicro/stmmac/dwmac-rk.c | 49 +++++++++++++++++++
3 files changed, 73 insertions(+)
--
2.31.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-05-14 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 11:38 Tobias Schramm [this message]
2021-05-14 11:38 ` [PATCH 1/3] dt-bindings: net: rockchip-dwmac: add rk3308 gmac compatible Tobias Schramm
2021-05-14 11:38 ` [PATCH 2/3] net: stmmac: dwmac-rk: add support for rk3308 gmac Tobias Schramm
2021-05-14 11:38 ` [PATCH 3/3] arm64: dts: rockchip: add gmac to rk3308 dts Tobias Schramm
2021-05-14 22:20 ` [PATCH 0/3] Add support for RK3308 gmac patchwork-bot+netdevbpf
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=20210514113813.2093534-1-t.schramm@manjaro.org \
--to=t.schramm@manjaro.org \
--cc=davem@davemloft.net \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).