From: Jakub Kicinski Date: Tue, 30 May 2023 04:46:55 +0000 (-0700) Subject: Merge branch 'net-pcs-add-helpers-to-xpcs-and-lynx-to-manage-mdiodev' X-Git-Tag: v6.6.7~2536^2~214 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3ed018fb262801a1a1cdd7918ee3d7e7071bd252;p=platform%2Fkernel%2Flinux-starfive.git Merge branch 'net-pcs-add-helpers-to-xpcs-and-lynx-to-manage-mdiodev' Russell King says: ==================== net: pcs: add helpers to xpcs and lynx to manage mdiodev This morning, we have had two instances where the destruction of the MDIO device associated with XPCS and Lynx has been wrong. Rather than allowing this pattern of errors to continue, let's make it easier for driver authors to get this right by adding a helper. The changes are essentially: 1. Add two new mdio device helpers to manage the underlying struct device reference count. Note that the existing mdio_device_free() doesn't actually free anything, it merely puts the reference count. 2. Make the existing _create() and _destroy() PCS driver methods increment and decrement this refcount using these helpers. This results in no overall change, although drivers may hang on to the mdio device for a few cycles longer. 3. Add _create_mdiodev() which creates the mdio device before calling the existing _create() method. Once the _create() method has returned, we put the reference count on the mdio device. If _create() was successful, then the reference count taken there will "hold" the mdio device for the lifetime of the PCS (in other words, until _destroy() is called.) However, if _create() failed, then dropping the refcount at this point will free the mdio device. This is the exact behaviour we desire. 4. Convert users that create a mdio device and then call the PCS's _create() method over to the new _create_mdiodev() method, and simplify the cleanup. We also have DPAA2 and fmem_memac that look up their PCS rather than creating it. These could also drop their reference count on the MDIO device immediately after calling lynx_pcs_create(), which would then mean we wouldn't need lynx_get_mdio_device() and the associated complexity to put the device in dpaa2_pcs_destroy() and pcs_put(). Note that DPAA2 bypasses the mdio device's abstractions by calling put_device() directly. ==================== Link: https://lore.kernel.org/r/ZHCGZ8IgAAwr8bla@shell.armlinux.org.uk Signed-off-by: Jakub Kicinski --- 3ed018fb262801a1a1cdd7918ee3d7e7071bd252