mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiaolei Wang <xiaolei.wang@windriver.com>
To: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Add link between phy dev and mac dev
Date: Wed, 16 Nov 2022 22:43:03 +0800	[thread overview]
Message-ID: <20221116144305.2317573-1-xiaolei.wang@windriver.com> (raw)

On imx6sx, there are two fec interfaces, but the external
phys can only be configured by fec0 mii_bus. That means
the fec1 can't work independently, it only work when the
fec0 is active. It is alright in the normal boot since the
fec0 will be probed first. But then the fec0 maybe moved
behind of fec1 in the dpm_list due to various device link.
So in system suspend and resume, we would get the following
warning when configuring the external phy of fec1 via the
fec0 mii_bus due to the inactive of fec0. In order to fix
this issue, we create a device link between phy dev and fec0.
This will make sure that fec0 is always active when fec1
is in active mode.

Therefore, in order to solve this kind of problem, an interface
function phy_mac_link_add is added to establish a link relationship
between phy dev and mac dev.

Xiaolei Wang (2):
  net: phy: Add netdev link when multiple phys share a mdio
  net: fec: net: fec: Create device link between fec0 and fec1

 drivers/net/ethernet/freescale/fec_main.c |  4 +++-
 drivers/net/phy/phy.c                     | 21 +++++++++++++++++++++
 include/linux/phy.h                       |  1 +
 3 files changed, 25 insertions(+), 1 deletion(-)

-- 
2.25.1


             reply	other threads:[~2022-11-16 14:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 14:43 Xiaolei Wang [this message]
2022-11-16 14:43 ` [PATCH 1/2] net: phy: " Xiaolei Wang
2022-11-16 23:11   ` kernel test robot
2022-11-16 23:22   ` Florian Fainelli
2022-11-17  4:39     ` Wang, Xiaolei
2022-11-17 19:28   ` kernel test robot
2022-11-16 14:43 ` [PATCH 2/2] net: fec: Create device " Xiaolei Wang
2022-11-16 15:07   ` Andrew Lunn
2022-11-16 23:27     ` Florian Fainelli
2022-11-16 23:57       ` Andrew Lunn
2022-11-17  0:21         ` Florian Fainelli
2022-11-17  4:40           ` Wang, Xiaolei
2022-11-17  4:40     ` Wang, Xiaolei

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=20221116144305.2317573-1-xiaolei.wang@windriver.com \
    --to=xiaolei.wang@windriver.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 \
    /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®