devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: paul.geurts@prodrive-technologies.com, f.fainelli@gmail.com,
	jonas.gorski@gmail.com, andrew@lunn.ch, olteanv@gmail.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH v2 0/2] net: dsa: b53: mdio: add support for BCM53134
Date: Fri, 24 Mar 2023 09:41:36 +0100	[thread overview]
Message-ID: <20230324084138.664285-1-noltari@gmail.com> (raw)
In-Reply-To: <20230323121804.2249605-1-noltari@gmail.com>

This is based on the initial work from Paul Geurts that was sent to the
incorrect linux development lists and recipients.
I've simplified his patches by adding BCM53134 to the is531x5() block since it
seems that the switch doesn't need a special RGMII config.

Paul Geurts (1):
  net: dsa: b53: mdio: add support for BCM53134

Álvaro Fernández Rojas (1):
  dt-bindings: net: dsa: b53: add BCM53134 support

 .../devicetree/bindings/net/dsa/brcm,b53.yaml     |  1 +
 drivers/net/dsa/b53/b53_common.c                  | 15 +++++++++++++++
 drivers/net/dsa/b53/b53_mdio.c                    |  5 ++++-
 drivers/net/dsa/b53/b53_priv.h                    |  7 +++++--
 4 files changed, 25 insertions(+), 3 deletions(-)

-- 
2.30.2


  parent reply	other threads:[~2023-03-24  8:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 12:18 [PATCH 0/2] net: dsa: b53: mdio: add support for BCM53134 Álvaro Fernández Rojas
2023-03-23 12:18 ` [PATCH 1/2] dt-bindings: net: dsa: b53: add BCM53134 support Álvaro Fernández Rojas
2023-03-23 16:34   ` Florian Fainelli
2023-03-25 11:15   ` Krzysztof Kozlowski
2023-03-23 12:18 ` [PATCH 2/2] net: dsa: b53: mdio: add support for BCM53134 Álvaro Fernández Rojas
2023-03-23 16:43   ` Florian Fainelli
2023-03-23 16:49     ` Álvaro Fernández Rojas
2023-03-23 16:57       ` Florian Fainelli
2023-03-23 20:10     ` Paul Geurts
2023-03-23 21:02       ` Florian Fainelli
2023-03-23 22:13         ` Álvaro Fernández Rojas
2023-03-24  8:29           ` Paul Geurts
2023-03-24  8:43             ` Álvaro Fernández Rojas
2023-03-23 22:12       ` Álvaro Fernández Rojas
2023-03-23 19:58 ` [PATCH 0/2] " Paul Geurts
2023-03-23 22:10   ` Álvaro Fernández Rojas
2023-03-24  8:41 ` Álvaro Fernández Rojas [this message]
2023-03-24  8:41   ` [PATCH v2 1/2] dt-bindings: net: dsa: b53: add BCM53134 support Álvaro Fernández Rojas
2023-03-25 11:15     ` Krzysztof Kozlowski
2023-03-24  8:41   ` [PATCH v2 2/2] net: dsa: b53: mdio: add support for BCM53134 Álvaro Fernández Rojas
2023-03-24 22:07     ` Florian Fainelli
2023-03-24 22:05   ` [PATCH v2 0/2] " Jakub Kicinski
2023-03-27  7:40   ` patchwork-bot+netdevbpf

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=20230324084138.664285-1-noltari@gmail.com \
    --to=noltari@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=jonas.gorski@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=paul.geurts@prodrive-technologies.com \
    --cc=robh+dt@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).