[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2344b1ea-f8bc-7491-4662-b8a3e94fb94e@gmail.com>
Date: Tue, 4 Apr 2017 21:21:26 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
netdev@...r.kernel.org
Subject: Re: [PATCH v2 00/13] ftgmac100: Rework batch 1 - Link & Interrupts
Salut Benjamin,
Le 04/04/17 à 19:28, Benjamin Herrenschmidt a écrit :
> This is version 2 of the first batch of updates to the
> ftgmac100 driver.
>
> Essentially:
>
> - A few misc cleanups
> - Fixing link speed & duplex handling (including dealing with
> an Aspeed requirement to double reset the controller when
> the speed changes)
> - And addition of a reset task workqueue which will be used
> for delaying the re-initialization of the controller
> - Fixing a number of issues with how interrupts and NAPI
> are dealt with.
>
> Subsequent batches will rework and improve the rx path, the
> tx path, and add a bunch of features and fixes.
>
> Version 2 addresses some review comments to patches 5 and 10
> (see version history in the respective emails).
>
This looks pretty good to me, two minor things:
- most drivers keep track of the old status/duplex/pause/link variables
instead of the current one which is already available within struct
phy_device, any particular reason for not doing like the other drivers?
- the need to reset the HW during link changes is just ... well too bad
With that:
Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
--
Florian
Powered by blists - more mailing lists