[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221130021216.1052230-1-xiaolei.wang@windriver.com>
Date: Wed, 30 Nov 2022 10:12:15 +0800
From: Xiaolei Wang <xiaolei.wang@...driver.com>
To: andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, f.fainelli@...il.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [v3][net-next][PATCH 0/1] net: phy: Add link between phy dev and mac dev
Compared with v2, the comment of phydev->devlink is added, and the net-next tree is specified
If the external phy used by current mac interface is
managed by another mac interface, it means that this
network port cannot work independently, especially
when the system suspends and resumes, the following
trace may appear, so we should create a device link
between phy dev and mac dev.
WARNING: CPU: 0 PID: 24 at drivers/net/phy/phy.c:983 phy_error+0x20/0x68
Modules linked in:
CPU: 0 PID: 24 Comm: kworker/0:2 Not tainted 6.1.0-rc3-00011-g5aaef24b5c6d-dirty #34
Hardware name: Freescale i.MX6 SoloX (Device Tree)
Workqueue: events_power_efficient phy_state_machine
unwind_backtrace from show_stack+0x10/0x14
show_stack from dump_stack_lvl+0x68/0x90
dump_stack_lvl from __warn+0xb4/0x24c
__warn from warn_slowpath_fmt+0x5c/0xd8
warn_slowpath_fmt from phy_error+0x20/0x68
phy_error from phy_state_machine+0x22c/0x23c
phy_state_machine from process_one_work+0x288/0x744
process_one_work from worker_thread+0x3c/0x500
worker_thread from kthread+0xf0/0x114
kthread from ret_from_fork+0x14/0x28
Exception stack(0xf0951fb0 to 0xf0951ff8)
Xiaolei Wang (1):
net: phy: Add link between phy dev and mac dev
drivers/net/phy/phy_device.c | 12 ++++++++++++
include/linux/phy.h | 4 ++++
2 files changed, 16 insertions(+)
--
2.25.1
Powered by blists - more mailing lists