All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Golle <daniel@makrotopia.org>
To: devicetree@vger.kernel.org, netdev@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	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>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Qingfang Deng <dqfext@gmail.com>,
	SkyLake Huang <SkyLake.Huang@mediatek.com>,
	Simon Horman <simon.horman@corigine.com>
Subject: [PATCH net-next v4 0/2] net: phy: add driver for MediaTek SoC built-in GE PHYs
Date: Thu, 11 May 2023 16:09:54 +0200	[thread overview]
Message-ID: <cover.1683813687.git.daniel@makrotopia.org> (raw)

Some of MediaTek's Filogic SoCs come with built-in gigabit Ethernet
PHYs which require calibration data from the SoC's efuse.
Despite the similar design the driver doesn't share any code with the
existing mediatek-ge.c, so add support for these PHYs by introducing a
new driver for only MediaTek's ARM64 SoCs.

As the PHYs integrated in the MT7988 SoC require reading the polarity
of the LEDs from the SoCs's boottrap also add dt-binding for that.

All LEDs are for now setup with default values, a follow up patch which
allows custom LED setups will be sent after the PHY LED framework is
more in shape.

Changes since v3:
 * fix spelling and reverse xmas tree
 * add dt-binding for mediatek,boottrap

Changes since v2:
 * remove everything related to PHY LEDs for now, LED support will
   be cleaned up and submitted once PHY LED framework is more ready

Changes since v1:
 * split-off SoC-specific driver from mediatek-ge.c as requested
 * address comments made by Heiner Kallweit
 * add pinctrl handling for PHY LED
 * remove calibration details not needed in production hardware

Daniel Golle (2):
  dt-bindings: arm: mediatek: add mediatek,boottrap binding
  net: phy: add driver for MediaTek SoC built-in GE PHYs

 .../arm/mediatek/mediatek,boottrap.yaml       |   37 +
 MAINTAINERS                                   |    9 +
 drivers/net/phy/Kconfig                       |   12 +
 drivers/net/phy/Makefile                      |    1 +
 drivers/net/phy/mediatek-ge-soc.c             | 1264 +++++++++++++++++
 drivers/net/phy/mediatek-ge.c                 |    3 +-
 6 files changed, 1325 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,boottrap.yaml
 create mode 100644 drivers/net/phy/mediatek-ge-soc.c


base-commit: 285b2a46953cecea207c53f7c6a7a76c9bbab303
-- 
2.40.0



             reply	other threads:[~2023-05-11 14:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 14:09 Daniel Golle [this message]
2023-05-11 14:10 ` [PATCH net-next v4 1/2] dt-bindings: arm: mediatek: add mediatek,boottrap binding Daniel Golle
2023-05-11 15:53   ` Andrew Lunn
2023-05-12  6:54     ` Krzysztof Kozlowski
2023-05-18  2:44       ` Daniel Golle
2023-05-18  2:44         ` Daniel Golle
2023-05-18  7:50         ` Krzysztof Kozlowski
2023-05-18  7:50           ` Krzysztof Kozlowski
2023-05-18 14:21           ` Krzysztof Kozlowski
2023-05-18 14:21             ` Krzysztof Kozlowski
2023-05-11 17:06   ` Krzysztof Kozlowski
2023-05-11 14:10 ` [PATCH net-next v4 2/2] net: phy: add driver for MediaTek SoC built-in GE PHYs Daniel Golle

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=cover.1683813687.git.daniel@makrotopia.org \
    --to=daniel@makrotopia.org \
    --cc=SkyLake.Huang@mediatek.com \
    --cc=andrew@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dqfext@gmail.com \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@kernel.org \
    --cc=simon.horman@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.