From: Conor Dooley <conor.dooley@microchip.com>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"Conor Dooley" <conor.dooley@microchip.com>
Subject: [net-next PATCH RESEND 0/2] PolarFire SoC macb reset support
Date: Fri, 1 Jul 2022 07:58:30 +0100 [thread overview]
Message-ID: <20220701065831.632785-1-conor.dooley@microchip.com> (raw)
Hey all,
Jakub requested that these patches be split off from the series
adding the reset controller itself that I sent yesterday [0].
The Cadence MACBs on PolarFire SoC (MPFS) have reset capability and are
compatible with the zynqmp's init function. I have removed the zynqmp
specific comments from that function & renamed it to reflect what it
does, since it is no longer zynqmp only.
MPFS's MACB had previously used the generic binding, so I also added
the required specific binding.
Thanks,
Conor.
0 - https://lore.kernel.org/all/20220630080532.323731-1-conor.dooley@microchip.com/
Conor Dooley (2):
dt-bindings: net: cdns,macb: document polarfire soc's macb
net: macb: add polarfire soc reset support
.../devicetree/bindings/net/cdns,macb.yaml | 1 +
drivers/net/ethernet/cadence/macb_main.c | 25 +++++++++++++------
2 files changed, 19 insertions(+), 7 deletions(-)
--
2.36.1
next reply other threads:[~2022-07-01 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 6:58 Conor Dooley [this message]
2022-07-01 6:58 ` [net-next PATCH RESEND 1/2] dt-bindings: net: cdns,macb: document polarfire soc's macb Conor Dooley
2022-07-01 20:35 ` Rob Herring
2022-07-01 6:58 ` [net-next PATCH RESEND 2/2] net: macb: add polarfire soc reset support Conor Dooley
2022-07-01 7:47 ` Claudiu.Beznea
2022-07-01 7:55 ` Conor.Dooley
2022-07-01 8:06 ` Conor.Dooley
2022-07-02 15:34 ` Conor.Dooley
2022-07-04 7:07 ` Claudiu.Beznea
2022-07-04 7:31 ` Conor.Dooley
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=20220701065831.632785-1-conor.dooley@microchip.com \
--to=conor.dooley@microchip.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.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