[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20160511.193658.976667252714550868.davem@davemloft.net>
Date: Wed, 11 May 2016 19:36:58 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: andrew@...n.ch
Cc: vivien.didelot@...oirfairelinux.com, f.fainelli@...il.com,
netdev@...r.kernel.org
Subject: Re: [PATCH v1 net-next 0/7] More enabler patches for DSA probing
From: Andrew Lunn <andrew@...n.ch>
Date: Tue, 10 May 2016 23:27:18 +0200
> The complete set of patches for the reworked DSA probing is too big to
> post as once. These subset contains some enablers which are easy to
> review.
>
> Eventually, the Marvell driver will instantiate its own internal MDIO
> bus, rather than have the framework do it, thus allows devices on the
> bus to be listed in the device tree. Initialize the main mutex as soon
> as it is created, to avoid lifetime issues with the mdio bus.
>
> A previous patch renamed all the DSA probe functions to make room for
> a true device probe. However the recent merging of all the Marvell
> switch drivers resulted in mv88e6xxx going back to the old probe
> name. Rename it again, so we can have a driver probe function.
>
> Add minimum support for the Marvell switch driver to probe as an MDIO
> device, as well as an DSA driver. Later patches will then register
> this device with the new DSA core framework.
>
> Move the GPIO reset code out of the DSA code. Different drivers may
> need different reset mechanisms, e.g. via a reset controller for
> memory mapped devices. Don't clutter up the core with this. Let each
> driver implement what it needs.
>
> master_dev is no longer needed in the switch drivers, since they have
> access to a device pointer from the probe function. Remove it.
>
> Let the switch parse the eeprom length from its one device tree
> node. This is required with the new binding when the central DSA
> platform device no longer exists.
Series applied, thanks Andrew.
Powered by blists - more mailing lists