linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle Hendry <kylehendrydev@gmail.com>
To: "Philipp Zabel" <p.zabel@pengutronix.de>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Fernández Rojas" <noltari@gmail.com>
Cc: Kyle Hendry <kylehendrydev@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] reset: bcm6345: add support for internal ephy resets on bcm63xx
Date: Tue, 15 Jul 2025 16:46:01 -0700	[thread overview]
Message-ID: <20250715234605.36216-1-kylehendrydev@gmail.com> (raw)

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. 

v2:
- Drop SoC specific patches since bits are sequential

v1: https://lore.kernel.org/all/20250709024740.194520-1-kylehendrydev@gmail.com/

Signed-off-by: Kyle Hendry <kylehendrydev@gmail.com>

Kyle Hendry (2):
  reset: bcm6345: add support for bcm63xx ephy control register
  dt-bindings: reset: add compatible for bcm63xx ephy control

 .../devicetree/bindings/reset/brcm,bcm6345-reset.yaml         | 4 +++-
 drivers/reset/reset-bcm6345.c                                 | 1 +
 2 files changed, 4 insertions(+), 1 deletion(-)

-- 
2.43.0


             reply	other threads:[~2025-07-15 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 23:46 Kyle Hendry [this message]
2025-07-15 23:46 ` [PATCH v2 1/2] reset: bcm6345: add support for bcm63xx ephy control register Kyle Hendry
2025-07-15 23:46 ` [PATCH v2 2/2] dt-bindings: reset: add compatible for bcm63xx ephy control Kyle Hendry

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=20250715234605.36216-1-kylehendrydev@gmail.com \
    --to=kylehendrydev@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noltari@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).