netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
	olteanv@gmail.com, davem@davemloft.net, linux@armlinux.org.uk,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] net: dsa: mv88e6xxx: serdes link without phy
Date: Wed, 14 Oct 2020 17:35:33 -0700	[thread overview]
Message-ID: <20201014173533.75137c09@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20201013021858.20530-1-chris.packham@alliedtelesis.co.nz>

On Tue, 13 Oct 2020 15:18:56 +1300 Chris Packham wrote:
> This small series gets my hardware into a working state. The key points are to
> make sure we don't force the link and that we ask the MAC for the link status.
> I also have updated my dts to say `phy-mode = "1000base-x";` and `managed =
> "in-band-status";`

Russell, Andrew, PHY folks - does this look good to you?

      parent reply	other threads:[~2020-10-15  0:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  2:18 [PATCH 0/2] net: dsa: mv88e6xxx: serdes link without phy Chris Packham
2020-10-13  2:18 ` [PATCH 1/2] net: dsa: mv88e6xxx: Don't force link when using in-band-status Chris Packham
2020-10-18 16:00   ` Andrew Lunn
2020-10-13  2:18 ` [PATCH 2/2] net: dsa: mv88e6xxx: Support serdes ports on MV88E6097 Chris Packham
2020-10-18 16:16   ` Andrew Lunn
2020-10-18 20:09     ` Chris Packham
2020-10-18 20:25       ` Andrew Lunn
2020-10-18 21:15         ` Chris Packham
2020-10-18 22:08           ` Andrew Lunn
2020-10-18 22:31             ` Chris Packham
2020-10-19  2:45               ` Chris Packham
2020-10-15  0:35 ` Jakub Kicinski [this message]

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=20201014173533.75137c09@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=vivien.didelot@gmail.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;
as well as URLs for NNTP newsgroup(s).