mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Wang, Xiaolei" <xiaolei.wang@windriver.com>,
	Andrew Lunn <andrew@lunn.ch>
Cc: hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v2][PATCH 1/1] net: phy: Add link between phy dev and mac dev
Date: Sun, 27 Nov 2022 12:30:43 -0800	[thread overview]
Message-ID: <45a8283b-64ee-599d-3ec6-abe2b2f96920@gmail.com> (raw)
In-Reply-To: <6b50524f-4f24-d14e-9d3f-f03f25ca549b@windriver.com>



On 11/25/2022 5:41 PM, Wang, Xiaolei wrote:
> add Florian
> 
> thanks
> 
> xiaolei
> 
> On 11/26/2022 5:43 AM, Andrew Lunn wrote:
>> CAUTION: This email comes from a non Wind River email account!
>> Do not click links or open attachments unless you recognize the sender 
>> and know the content is safe.
>>
>> On Fri, Nov 25, 2022 at 12:12:06PM +0800, Xiaolei Wang wrote:
>>> 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 suspend and resume, 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)
>>>
>>> Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com>
>> This needs Florians review, since for v1 he thinks it will cause
>> regressions.

Please give me until Tuesday to give this patch some proper testing, thanks!
-- 
Florian

  reply	other threads:[~2022-11-27 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25  4:12 [v2][PATCH 0/1] " Xiaolei Wang
2022-11-25  4:12 ` [v2][PATCH 1/1] " Xiaolei Wang
2022-11-25 21:43   ` Andrew Lunn
2022-11-26  1:41     ` Wang, Xiaolei
2022-11-27 20:30       ` Florian Fainelli [this message]
2022-11-28  3:18         ` Wang, Xiaolei
2022-11-28 21:05   ` Florian Fainelli
2022-11-29  3:00     ` Jakub Kicinski
2022-11-29  3:02       ` Florian Fainelli
2022-11-29 11:50   ` Paolo Abeni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45a8283b-64ee-599d-3ec6-abe2b2f96920@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xiaolei.wang@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®