[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYcvRSqr=6zc5etNn3=LSc8h2Uw=C8GNw6YgdTvsYGV+A@mail.gmail.com>
Date: Fri, 10 Nov 2017 09:16:04 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, Roman Yeryomin <roman@...em.lv>,
Vivien Didelot <vivien.didelot@...oirfairelinux.com>,
netdev@...r.kernel.org,
Antti Seppälä <a.seppala@...il.com>,
Colin Leitner <colin.leitner@...glemail.com>,
Gabor Juhos <juhosg@...nwrt.org>
Subject: Re: [PATCH 4/4] RFC: net: dsa: realtek-smi: Add Realtek SMI driver
On Thu, Nov 9, 2017 at 7:08 PM, Florian Fainelli <f.fainelli@...il.com> wrote:
> if you are thinking about converting existing swconfig
> drivers from OpenWrt/LEDE into DSA, please do it! The conversion is
> reasonably simple even if the APIs do not exactly match.
I can confirm this :)
It's exactly what I did for this Realtek thingie and it wasn't
that hard.
> Quite a lot of
> swconfig driers in OpenWrt/LEDE are implemented as phy_device, and the
> conversion for that is to use a proper mdio_device (see
> drivers/net/dsa/b53/b53_mdio.c for an example).
I found a nice split here with the DSA device forking off some
MDIO children, it's really neat and works well.
I just had to patch in some IRQ (link change) support as it
was relying on polling. I'm working in getting
that in shape so we can move ahead with it, as you can see
I took the approach of letting the DSA device present an irqchip
that the PHY can pick an IRQ from and it works like a charm.
Yours,
Linus Walleij
Powered by blists - more mailing lists