devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: vtpieter@gmail.com
To: devicetree@vger.kernel.org, woojung.huh@microchip.com,
	UNGLinuxDriver@microchip.com, netdev@vger.kernel.org
Cc: o.rempel@pengutronix.de, Pieter Van Trappen <pieter.van.trappen@cern.ch>
Subject: [PATCH 0/4] net: dsa: microchip: ksz8795: add Wake on LAN support
Date: Wed, 17 Jul 2024 21:37:21 +0200	[thread overview]
Message-ID: <20240717193725.469192-1-vtpieter@gmail.com> (raw)

From: Pieter Van Trappen <pieter.van.trappen@cern.ch>

Add WoL support for KSZ8795 family of switches. This code was tested
with a KSZ8794 chip.

Strongly based on existing KSZ9477 code but there's too many
differences, such as the indirect register access, to generalize this
code to ksz_common. Some registers names have been changed to increase
standardization between those code bases.

In addition to the device-tree addition and the actual code, there's
two more patches to correct the erratum workaround application using
the now available indirect register read and a minor correction of
existing KSZ9477 function comments.

Pieter Van Trappen (4):
  dt-bindings: net: dsa: microchip: add microchip,pme-active-high flag
  net: dsa: microchip: ksz8795: add Wake on LAN support
  net: dsa: microchip: check erratum workaround through indirect
    register read
  net: dsa: microchip: ksz9477: correct description of WoL functions

 .../bindings/net/dsa/microchip,ksz.yaml       |   5 +
 drivers/net/dsa/microchip/ksz8.h              |   5 +
 drivers/net/dsa/microchip/ksz8795.c           | 230 +++++++++++++++++-
 drivers/net/dsa/microchip/ksz8795_reg.h       |  17 +-
 drivers/net/dsa/microchip/ksz9477.c           |   8 +-
 drivers/net/dsa/microchip/ksz_common.c        |   5 +
 drivers/net/dsa/microchip/ksz_common.h        |   1 +
 7 files changed, 258 insertions(+), 13 deletions(-)


base-commit: 51835949dda3783d4639cfa74ce13a3c9829de00
-- 
2.43.0


             reply	other threads:[~2024-07-17 19:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 19:37 vtpieter [this message]
2024-07-17 19:37 ` [PATCH 1/4] dt-bindings: net: dsa: microchip: add microchip,pme-active-high flag vtpieter
2024-07-17 19:37   ` [PATCH 2/4] net: dsa: microchip: ksz8795: add Wake on LAN support vtpieter
2024-07-17 19:37     ` [PATCH 3/4] net: dsa: microchip: check erratum workaround through indirect register read vtpieter
2024-07-17 19:37       ` [PATCH 4/4] net: dsa: microchip: ksz9477: correct description of WoL functions vtpieter
2024-07-19 13:52         ` Oleksij Rempel
2024-07-18  2:24       ` [PATCH 3/4] net: dsa: microchip: check erratum workaround through indirect register read Andrew Lunn
2024-07-18 13:45         ` Pieter
2024-07-19 13:46     ` [PATCH 2/4] net: dsa: microchip: ksz8795: add Wake on LAN support Oleksij Rempel
2024-07-20 12:44       ` Pieter
2024-07-19 12:36   ` [PATCH 1/4] dt-bindings: net: dsa: microchip: add microchip,pme-active-high flag Oleksij Rempel
2024-07-23  2:42   ` Rob Herring (Arm)

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=20240717193725.469192-1-vtpieter@gmail.com \
    --to=vtpieter@gmail.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pieter.van.trappen@cern.ch \
    --cc=woojung.huh@microchip.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).