From: Philipp Zabel <p.zabel@pengutronix.de>
To: "Kyle Hendry" <kylehendrydev@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Fernández Rojas" <noltari@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] reset: bcm6345: add support for internal ephy resets on bcm63xx
Date: Thu, 14 Aug 2025 12:57:16 +0200 [thread overview]
Message-ID: <0af65202bca6ef30ee6530703db303e81ec190eb.camel@pengutronix.de> (raw)
In-Reply-To: <20250709024740.194520-1-kylehendrydev@gmail.com>
On Di, 2025-07-08 at 19:47 -0700, Kyle Hendry wrote:
> bcm63xx SoCs have a register in the gpio controller that controls some
> of the phy functionality. Some of the bits reset individual phys and
> need a driver to set.
>
> The other fields in the register configure phy power and will be set
> by the network device driver.
>
> Kyle Hendry (6):
> reset: bcm6345: add support for bcm63xx ephy control register
> dt-bindings: reset: add compatible for bcm63xx ephy control
[...]
Applied patches 1 and 2 to reset/next (in inverse order), thanks!
[2/6] dt-bindings: reset: add compatible for bcm63xx ephy control
https://git.pengutronix.de/cgit/pza/linux/commit/?id=a341bcfbfa74
[1/6] reset: bcm6345: add support for bcm63xx ephy control register
https://git.pengutronix.de/cgit/pza/linux/commit/?id=6e273caeacf0
Do you agree that patches 2-6 are not necessary?
regards
Philipp
prev parent reply other threads:[~2025-08-14 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 2:47 Kyle Hendry
2025-07-09 2:47 ` [PATCH 1/6] reset: bcm6345: add support for bcm63xx ephy control register Kyle Hendry
2025-08-14 11:12 ` Krzysztof Kozlowski
2025-07-09 2:47 ` [PATCH 2/6] dt-bindings: reset: add compatible for bcm63xx ephy control Kyle Hendry
2025-07-10 21:53 ` Rob Herring (Arm)
2025-08-14 11:13 ` Krzysztof Kozlowski
2025-07-09 2:47 ` [PATCH 3/6] dt-bindings: reset: add BCM63268 ephy reset definitions Kyle Hendry
2025-07-10 21:54 ` Rob Herring
2025-07-09 2:47 ` [PATCH 4/6] dt-bindings: reset: add BCM6318 " Kyle Hendry
2025-07-09 2:47 ` [PATCH 5/6] dt-bindings: reset: add BCM6362 " Kyle Hendry
2025-07-09 2:47 ` [PATCH 6/6] dt-bindings: reset: add BCM6328 " Kyle Hendry
2025-08-14 10:57 ` Philipp Zabel [this message]
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=0af65202bca6ef30ee6530703db303e81ec190eb.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kylehendrydev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=robh@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
all inboxes | Powered by JetHome®