mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Joseph Telaak <joseph@telaak.dev>
Cc: Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Chuanhong Guo <gch981213@gmail.com>,
	linux-mips@vger.kernel.org, linux-phy@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: phy: Add Siflower SF19A2890 USB 2.0 PHY
Date: Thu, 5 Nov 2026 19:18:13 +0000	[thread overview]
Message-ID: <20261105-shampoo-osmosis-6975c7cf734d@spud> (raw)
In-Reply-To: <CAPY4CJ5g+e4iu8p5s+Vf7XmEjB9cYX9xYyzHd0Fz8GEbmFm4hw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

On Wed, Nov 04, 2026 at 07:39:32PM -0500, Joseph Telaak wrote:
> > > +        reg = <0x19e0c040 0x60>;
> >
> > That's a weird offset and size.
> > What lies in the regions around this device?
> 
> It sits in the 1 KiB from 0x19e0c000 up to the next block at
> 0x19e0c400. At 0x0, 0x4 and 0xc are the reset, clock gate and bus output
> enable registers of the USB clock and reset manager, which the clk
> series describes as siflower,sf19a2890-usb-crm; 0x8 holds a value I
> have no documentation for. The OpenWrt port gives the PHY 0x40-0x9f,
> and its driver only uses 0x44, the PHY's sleep control. Read from
> U-Boot, registers between 0x40 and 0x8f hold non-zero values I have no
> documentation for either, and the rest reads as 0. The GMAC's
> configuration registers sit the same way, at 0x40 past its clock and
> reset manager at 0x19e04400.
> 
> If you'd prefer one node for the whole region, providing the clocks,
> resets and the PHY, I'll restructure it that way for v2.

No, not asking for that. Just making sure this wasn't some sort of
syscon being hidden by the offsets and size.
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-11-05 19:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  7:21 [PATCH 0/2] phy: Add the " Joseph Telaak via B4 Relay
2026-11-04  7:21 ` [PATCH 1/2] dt-bindings: phy: Add " Joseph Telaak via B4 Relay
2026-11-04 23:44   ` Conor Dooley
2026-11-05  0:39     ` Joseph Telaak
2026-11-05 19:18       ` Conor Dooley [this message]
2026-11-04  7:21 ` [PATCH 2/2] phy: siflower: Add SF19A2890 USB 2.0 PHY driver Joseph Telaak via B4 Relay
2026-11-05 13:14   ` Philipp Zabel
2026-11-05 21:00     ` Joseph Telaak

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=20261105-shampoo-osmosis-6975c7cf734d@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gch981213@gmail.com \
    --cc=joseph@telaak.dev \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=vkoul@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®