[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220630204433.hg2a2ws2zk5p73ld@soft-dev3-1.localhost>
Date: Thu, 30 Jun 2022 22:44:33 +0200
From: Horatiu Vultur <horatiu.vultur@...rochip.com>
To: Michael Walle <michael@...le.cc>
CC: "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
<UNGLinuxDriver@...rochip.com>, <netdev@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 0/4] net: lan966x: hardcode port count
The 06/30/2022 16:02, Michael Walle wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> 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.
It works also on LAN9662, but I didn't have time to send patches for
DTs. Then when I send patches for LAN9662, do I need to go in all dts
files to change the compatible string for the 'switch' node?
>
> 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
>
--
/Horatiu
Powered by blists - more mailing lists