From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: hauke@hauke-m.de, andrew@lunn.ch, vivien.didelot@gmail.com,
f.fainelli@gmail.com, olteanv@gmail.com, davem@davemloft.net,
kuba@kernel.org, linux@armlinux.org.uk, robh+dt@kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Aleksander Jan Bajkowski <olek2@wp.pl>
Subject: [PATCH v4 0/3] net: dsa: lantiq: add support for xRX300 and xRX330
Date: Mon, 22 Mar 2021 21:37:14 +0100 [thread overview]
Message-ID: <20210322203717.20616-1-olek2@wp.pl> (raw)
Changed since v3:
* fixed last compilation warning
Changed since v2:
* fixed compilation warnings
* removed example bindings for xrx330
* patches has been refactored due to upstream changes
Changed since v1:
* gswip_mii_mask_cfg() can now change port 3 on xRX330
* changed alowed modes on port 0 and 5 for xRX300 and xRX330
* moved common part of phylink validation into gswip_phylink_set_capab()
* verify the compatible string against the hardware
Aleksander Jan Bajkowski (3):
net: dsa: lantiq: allow to use all GPHYs on xRX300 and xRX330
net: dsa: lantiq: verify compatible strings against hardware
dt-bindings: net: dsa: lantiq: add xRx300 and xRX330 switch bindings
.../bindings/net/dsa/lantiq-gswip.txt | 4 +
drivers/net/dsa/lantiq_gswip.c | 162 ++++++++++++++----
2 files changed, 136 insertions(+), 30 deletions(-)
--
2.20.1
next reply other threads:[~2021-03-22 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 20:37 Aleksander Jan Bajkowski [this message]
2021-03-22 20:37 ` [PATCH v4 1/3] net: dsa: lantiq: allow to use all GPHYs on xRX300 and xRX330 Aleksander Jan Bajkowski
2021-03-22 20:37 ` [PATCH v4 2/3] net: dsa: lantiq: verify compatible strings against hardware Aleksander Jan Bajkowski
2021-03-22 20:37 ` [PATCH v4 3/3] dt-bindings: net: dsa: lantiq: add xRx300 and xRX330 switch bindings Aleksander Jan Bajkowski
2021-03-22 23:40 ` [PATCH v4 0/3] net: dsa: lantiq: add support for xRX300 and xRX330 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=20210322203717.20616-1-olek2@wp.pl \
--to=olek2@wp.pl \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@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).