From: Michael Walle <michael@walle.cc>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Walle <michael@walle.cc>
Subject: [PATCH net-next 0/4] net: lan966x: hardcode port count
Date: Thu, 30 Jun 2022 16:02:33 +0200 [thread overview]
Message-ID: <20220630140237.692986-1-michael@walle.cc> (raw)
Don't rely on the device tree to count the number of physical port. Instead
introduce a new compatible string which the driver can use to select the
correct port count.
This also hardcodes the generic compatible string to 8. The rationale is
that this compatible string was just used for the LAN9668 for now and I'm
not even sure the current driver would support the LAN9662.
Michael Walle (4):
net: lan966x: hardcode the number of external ports
dt-bindings: net: lan966x: add specific compatible string
net: lan966x: add new compatible microchip,lan9668-switch
ARM: dts: lan966x: use new microchip,lan9668-switch compatible
.../net/microchip,lan966x-switch.yaml | 5 +++-
arch/arm/boot/dts/lan966x.dtsi | 2 +-
.../ethernet/microchip/lan966x/lan966x_main.c | 24 +++++++++++++------
3 files changed, 22 insertions(+), 9 deletions(-)
--
2.30.2
next reply other threads:[~2022-06-30 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 14:02 Michael Walle [this message]
2022-06-30 14:02 ` [PATCH net-next 1/4] net: lan966x: hardcode the number of external ports Michael Walle
2022-06-30 14:02 ` [PATCH net-next 2/4] dt-bindings: net: lan966x: add specific compatible string Michael Walle
2022-06-30 14:02 ` [PATCH net-next 3/4] net: lan966x: add new compatible microchip,lan9668-switch Michael Walle
2022-06-30 14:02 ` [PATCH net-next 4/4] ARM: dts: lan966x: use new microchip,lan9668-switch compatible Michael Walle
2022-06-30 19:18 ` Krzysztof Kozlowski
2022-06-30 20:44 ` [PATCH net-next 0/4] net: lan966x: hardcode port count Horatiu Vultur
2022-06-30 20:56 ` Michael Walle
2022-06-30 21:21 ` Horatiu Vultur
2022-06-30 21:08 ` Andrew Lunn
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=20220630140237.692986-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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