netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Beckmeyer <beb@eks-engel.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <netdev@vger.kernel.org>
Subject: Re: DSA with MV88E6321 and imx28
Date: Thu, 6 Jun 2019 11:39:33 +0200	[thread overview]
Message-ID: <f451fe3b-307f-fb1e-da34-8ff85a9d8243@eks-engel.de> (raw)
In-Reply-To: <20190605184724.GB19590@lunn.ch>

>> I removed all phy-handle for the internal ports and in the mdio part 
>> is only port 2 and 6 by now. But the Serdes ports are still not be
>> recognized. So maybe there is still something wrong?
> What do you mean by SERDES? Do you mean they are connected to an SFP
> cage? If so, you need to add an SFP node. Take a look at
> vf610-zii-dev-rev-c.dts for an example.
>
> 	Andrew

Hey Andrew,
I've looked into the device tree. Why do they reference to i2c? We have
1x8 SFF tranceivers. Should I just add an i2c entry for it, because the 
value is required?

Now I don't have anything in the mdio part but the serdes ports are not 
recognized. Do I have to activate them in any kind? When I read the PHY
0 register of the serdes port 0 (SMI address 0xc) it is in power down mode.
Is there a problem with the mapping? Internally these serdes port PHYs are
at 0x0c and 0x0d but mapped to 0x0 and 0x1, for me this can be a reason 
why it won't be found. Is there a switch comparable to this mapping?
Maybe I'm totally wrong and misunderstanding something here?

Do you know which switch chip they use in the  vf610-zii-dev-rev-c?

Benjamin


  reply	other threads:[~2019-06-06  9:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 13:07 DSA with MV88E6321 and imx28 Benjamin Beckmeyer
2019-06-04 13:50 ` Andrew Lunn
2019-06-05  4:52   ` Benjamin Beckmeyer
2019-06-05 12:24     ` Andrew Lunn
2019-06-05 13:12       ` Benjamin Beckmeyer
2019-06-05 13:31         ` Andrew Lunn
2019-06-05 13:54           ` Benjamin Beckmeyer
2019-06-05 18:47             ` Andrew Lunn
2019-06-06  9:39               ` Benjamin Beckmeyer [this message]
     [not found]               ` <c27f2b9b-90d7-db63-f01c-2dfaef7a014b@eks-engel.de>
     [not found]                 ` <20190606122437.GA20899@lunn.ch>
2019-06-06 13:27                   ` Benjamin Beckmeyer
2019-06-06 13:35                     ` Andrew Lunn
2019-06-06 13:47                       ` Benjamin Beckmeyer
2019-06-06 13:59                         ` Andrew Lunn
2019-06-07  9:41                           ` Benjamin Beckmeyer
2019-06-07 12:47                             ` Andrew Lunn
2019-06-11  7:36                               ` Benjamin Beckmeyer
2019-06-11 12:19                                 ` Andrew Lunn
2019-06-11 13:09                                   ` Benjamin Beckmeyer
2019-06-11 13:27                                     ` Andrew Lunn
2019-06-12  9:05                                       ` Benjamin Beckmeyer

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=f451fe3b-307f-fb1e-da34-8ff85a9d8243@eks-engel.de \
    --to=beb@eks-engel.de \
    --cc=andrew@lunn.ch \
    --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).