netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sriram Chadalavada <sriram.chadalavada@mindleap.ca>
To: netdev@vger.kernel.org
Subject: Information on DSA driver initialization
Date: Thu, 5 Mar 2020 17:24:47 -0500	[thread overview]
Message-ID: <CAOK2joFxzSETFgHX7dRuhWPVSSEYswJ+-xfSxbPr5n3LcsMHzw@mail.gmail.com> (raw)

Is there information in kernel documentation or elsewhere about DSA
initialization process starting from the device tree parse to the
Marvell switch being detected?

The specific problem I'm facing is that while I see this:
root@SDhub:/# dmesg | grep igb
[ 1.314324] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[ 1.314332] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.314679] igb 0000:03:00.0: enabling device (0140 -> 0142)
[ 1.343926] igb 0000:03:00.0: added PHC on eth0
[ 1.343938] igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 1.343949] igb 0000:03:00.0: eth0: (PCIe:2.5Gb/s:Width x1) c4:48:38:00:63:eb
[ 1.344019] igb 0000:03:00.0: eth0: PBA No: 000300-000
[ 1.344030] igb 0000:03:00.0: Using MSI-X interrupts. 4 rx queue(s), 4
tx queue(s)
[ 1.344464] libphy: igb_enet_mii_bus: probed

I do NOT see this in the log:
[ 1.505474] libphy: mdiobus_find: mii bus [igb_enet_mii_bus] found
[ 1.645075] igb 0000:03:00.0 eth0: [0]: detected a Marvell 88E6176 switch
[ 24.341748] igb 0000:03:00.0 eth0: igb_enet_mii_probe starts
[ 24.344928] igb 0000:03:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps
Full Duplex, Flow Control: RX/TX

Any suggestions/speculations what may be going on here?

             reply	other threads:[~2020-03-05 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 22:24 Sriram Chadalavada [this message]
2020-03-05 22:51 ` Information on DSA driver initialization Andrew Lunn
2020-03-12 22:38   ` Sriram Chadalavada
2020-03-13  9:47     ` Andrew Lunn
2020-03-13 21:04       ` Sriram Chadalavada

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=CAOK2joFxzSETFgHX7dRuhWPVSSEYswJ+-xfSxbPr5n3LcsMHzw@mail.gmail.com \
    --to=sriram.chadalavada@mindleap.ca \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).