Thread (13 messages) 13 messages, 4 authors, 2021-09-17

Re: [PATCH v2 0/6] fw_devlink improvements

From: Marek Szyprowski <m.szyprowski@samsung.com>
Date: 2021-09-17 09:20:39
Also in: linux-acpi, lkml

Hi,

On 15.09.2021 18:44, Saravana Kannan wrote:
On Wed, Sep 15, 2021 at 1:44 AM Marek Szyprowski
[off-list ref] wrote:
quoted
On 15.09.2021 10:11, Saravana Kannan wrote:
quoted
Patches ready for picking up:
Patch 1 fixes a bug in fw_devlink.
Patch 2-4 are meant to make debugging easier
Patch 5 and 6 fix fw_devlink issues with PHYs and networking
Is this patchset supposed to fix the PHY related issues I've experienced
or does it also require the Andrew's patch for 'mdio-parent-bus'? If the
first, then applying only this patchset on top of today's linux-next
doesn't fix the ethernet issue on my Amlogic SoC based test boards.
Marek,

The issue you hit was actually a general issue with fw_devlink and
that's fixed by Patch 1. But I also needed to revert the phy-handle
patch for other reasons (see commit text) and that fixes the issue you
were hitting without needing the 'mdio-parent-bus' patch.
https://lore.kernel.org/lkml/20210915081933.485112-1-saravanak@google.com/ (local)

When I eventually bring back phy-handle support, I'll need the
'mdio-parent-bus' to not break your use case.

Hope that clarifies things.
Okay, I missed the fact that you have sent the revert of the phy-handle 
patch. Now I see it in the linux-next, so everything is fine.

Best regards

-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help