From: Andrew Lunn <andrew@lunn.ch>
To: Michael Walle <michael@walle.cc>
Cc: "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>,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] net: lan966x: hardcode port count
Date: Thu, 30 Jun 2022 23:08:32 +0200 [thread overview]
Message-ID: <Yr4Q0G4w9waIx7Ux@lunn.ch> (raw)
In-Reply-To: <20220630140237.692986-1-michael@walle.cc>
On Thu, Jun 30, 2022 at 04:02:33PM +0200, Michael Walle wrote:
> 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.
Does the silicon have an ID register which identifies what the device
is?
Andrew
prev parent reply other threads:[~2022-06-30 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 14:02 [PATCH net-next 0/4] net: lan966x: hardcode port count Michael Walle
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 [this message]
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=Yr4Q0G4w9waIx7Ux@lunn.ch \
--to=andrew@lunn.ch \
--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=michael@walle.cc \
--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;
as well as URLs for NNTP newsgroup(s).