[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <128467d6-8249-9f25-21a7-777fff9854d9@axis.com>
Date: Thu, 27 Oct 2022 08:35:17 +0200
From: Camel Guo <camelg@...s.com>
To: Andrew Lunn <andrew@...n.ch>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
CC: Camel Guo <Camel.Guo@...s.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Florian Fainelli <f.fainelli@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Russell King <linux@...linux.org.uk>,
Vivien Didelot <vivien.didelot@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Rob Herring <robh@...nel.org>, kernel <kernel@...s.com>
Subject: Re: [RFC net-next 2/2] net: dsa: Add driver for Maxlinear GSW1XX
switch
On 10/25/22 16:56, Andrew Lunn wrote:
>> > +EXPORT_SYMBOL(gsw1xx_shutdown);
>>
>> 1. EXPORT_SYMBOL_GPL
>> 2. Why do you do it in the first place? It's one driver, no need for
>> building two modules. Same applies to other places.
>
> At some point, there is likely to be SPI and UART support. The
> communication with the chip and the core driver will then be in
> separate modules. But i agree this is not needed at the moment when it
> is all linked into one.
Do you suggest that currently we put the content of gsw1xx_core.c and
gsw1xx_mdio.c into one file and split them later at the time when
another management mode (e,g: spi) is added?
Actually I kinda hope this piece of code (gsw1xx_core.c) can be reused
in lantiq_gswip in short future.
I tried to use the logic in lantiq_gswip directly on the gsw145 chip.
Unfortunately it did not work. It seems that the GSWIP part changes a lot.
>
> Andrew
Powered by blists - more mailing lists