devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcus Carlberg <marcus.carlberg@axis.com>
To: <lxu@maxlinear.com>, <andrew@lunn.ch>
Cc: <linux-kernel@vger.kernel.org>, <kernel@axis.com>,
	Marcus Carlberg <marcus.carlberg@axis.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	<devicetree@vger.kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/2] net: phy: mxl-gpy: Add mode for 2 leds
Date: Tue, 20 Sep 2022 17:14:09 +0200	[thread overview]
Message-ID: <20220920151411.12523-1-marcus.carlberg@axis.com> (raw)

GPY211 phy default to using all four led pins.
Hardwares using only two leds where led0 is used as the high
network speed led and led1 the low network speed led will not
get the correct behaviour since 1Gbit and 2.5Gbit will not be
represented at all in the existing leds.


Marcus Carlberg (2):
  dt-bindings: net: Add mxl,gpy
  net: phy: mxl-gpy: Add mode for 2 leds

 .../devicetree/bindings/net/mxl,gpy.yaml      | 39 ++++++++++++++++
 .../devicetree/bindings/vendor-prefixes.yaml  |  2 +
 MAINTAINERS                                   |  1 +
 drivers/net/phy/mxl-gpy.c                     | 45 +++++++++++++++++++
 4 files changed, 87 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/net/mxl,gpy.yaml

--
2.20.1


             reply	other threads:[~2022-09-20 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 15:14 Marcus Carlberg [this message]
2022-09-20 15:14 ` [PATCH net-next 1/2] dt-bindings: net: Add mxl,gpy Marcus Carlberg
2022-09-25 23:27   ` kernel test robot
2022-09-20 15:14 ` [PATCH net-next 2/2] net: phy: mxl-gpy: Add mode for 2 leds Marcus Carlberg
2022-09-22  8:05 ` [PATCH net-next 0/2] " Michael Walle
2022-09-22 12:00   ` Andrew Lunn

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=20220920151411.12523-1-marcus.carlberg@axis.com \
    --to=marcus.carlberg@axis.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kernel@axis.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lxu@maxlinear.com \
    --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;
as well as URLs for NNTP newsgroup(s).