From: Stefan Wahren <stefan.wahren@i2se.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Michael Heimpold <michael.heimpold@in-tech.com>,
jimmy.shen@vertexcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH RFC V2 0/4] add Vertexcom MSE102x support
Date: Sat, 4 Dec 2021 14:17:47 +0100 [thread overview]
Message-ID: <1638623871-21805-1-git-send-email-stefan.wahren@i2se.com> (raw)
This patch series adds support for the Vertexcom MSE102x Homeplug GreenPHY
chips [1]. They can be connected either via RGMII, RMII or SPI to a host CPU.
These patches handles only the last one, with an Ethernet over SPI protocol
driver.
The code has been tested only on Raspberry Pi boards, but should work
on other platforms.
Any comments about the code are welcome.
Changes in V2:
- improve lock handling for RX & TX path
- add new patch to introduce IF_PORT_HOMEPLUG as suggested by Andrew Lunn
- address all the comments by Jakub Kicinski, Andrew Lunn, Kernel test robot
[1] - http://www.vertexcom.com/p_homeplug_plc_en.html
Stefan Wahren (4):
dt-bindings: add vendor Vertexcom
dt-bindings: net: add Vertexcom MSE102x support
net: introduce media selection IF_PORT_HOMEPLUG
net: vertexcom: Add MSE102x SPI support
.../devicetree/bindings/net/vertexcom-mse102x.yaml | 71 ++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
drivers/net/ethernet/Kconfig | 1 +
drivers/net/ethernet/Makefile | 1 +
drivers/net/ethernet/vertexcom/Kconfig | 25 +
drivers/net/ethernet/vertexcom/Makefile | 6 +
drivers/net/ethernet/vertexcom/mse102x.c | 770 +++++++++++++++++++++
include/uapi/linux/netdevice.h | 3 +-
8 files changed, 878 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/net/vertexcom-mse102x.yaml
create mode 100644 drivers/net/ethernet/vertexcom/Kconfig
create mode 100644 drivers/net/ethernet/vertexcom/Makefile
create mode 100644 drivers/net/ethernet/vertexcom/mse102x.c
--
2.7.4
next reply other threads:[~2021-12-04 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 13:17 Stefan Wahren [this message]
2021-12-04 13:17 ` [PATCH RFC V2 1/4] dt-bindings: add vendor Vertexcom Stefan Wahren
2021-12-04 13:17 ` [PATCH RFC V2 2/4] dt-bindings: net: add Vertexcom MSE102x support Stefan Wahren
2021-12-04 13:17 ` [PATCH RFC V2 3/4] net: introduce media selection IF_PORT_HOMEPLUG Stefan Wahren
2021-12-06 19:29 ` Jakub Kicinski
2021-12-08 16:55 ` Stefan Wahren
2021-12-04 13:17 ` [PATCH RFC V2 4/4] net: vertexcom: Add MSE102x SPI support Stefan Wahren
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=1638623871-21805-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jimmy.shen@vertexcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.heimpold@in-tech.com \
--cc=netdev@vger.kernel.org \
--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).