devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
	Matthew Hagan <mnhagan88@gmail.com>
Cc: Vladimir Oltean <olteanv@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
	Vivek Unune <npcomplete13@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] ARM: dts: NSP: Move USB3 PHY to internal MDIO bus
Date: Thu, 24 Jun 2021 15:34:56 -0700	[thread overview]
Message-ID: <20210624223456.1315572-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20210613094639.3242151-4-mnhagan88@gmail.com>

On Sun, 13 Jun 2021 10:46:37 +0100, Matthew Hagan <mnhagan88@gmail.com> wrote:
> This patch largely replicates Vivek Unune's patch "ARM: dts:
> BCM5301X:Make usb3 phy use mdio phy driver"[1] for the NSP platform,
> whereby we need to create an mdio-mux to facilitate switches
> configured via external MDIO, in this case on the Meraki MX65.
> 
> However in doing so, we are creating an overlap with usb3_phy's
> ccb-mii range. To resolve this, usb3_phy should be moved to a child
> node of the internal MDIO bus. The result is heavily based upon Vivek's
> patch. This has also been cross-referenced with Yendapally Reddy's
> earlier work which utilised the subsequently dropped brcm,nsp-usb3-phy
> driver: "[PATCH v2 4/4] arm: dts: nsp: Add USB nodes to device tree"
> [2]. Finally, this change provides conformance to the bcm-ns-usb3-phy
> documentation, utilising the required usb3-dmp-syscon property. Note
> that support for the deprecated ccb-mii bindings has been dropped as of
> "phy: phy-bcm-ns-usb3: drop support for deprecated DT binding"[3].
> 
> [1] https://lore.kernel.org/patchwork/patch/933971/
> [2] https://www.spinics.net/lists/arm-kernel/msg555132.html
> [3] https://lore.kernel.org/linux-devicetree/20201113113423.9466-1-zajec5@gmail.com/
> 
> Signed-off-by: Matthew Hagan <mnhagan88@gmail.com>
> ---

Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian

  reply	other threads:[~2021-06-24 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13  9:46 [PATCH 1/4] ARM: dts: NSP: disable qspi node by default Matthew Hagan
2021-06-13  9:46 ` [PATCH 2/4] ARM: dts: NSP: disable sp804 ccbtimers " Matthew Hagan
2021-06-13 16:22   ` Florian Fainelli
2021-06-13 19:46     ` Matthew Hagan
2021-06-13  9:46 ` [PATCH 3/4] ARM: dts: NSP: add MDIO bus controller node Matthew Hagan
2021-06-24 22:34   ` Florian Fainelli
2021-06-13  9:46 ` [PATCH 4/4] ARM: dts: NSP: Move USB3 PHY to internal MDIO bus Matthew Hagan
2021-06-24 22:34   ` Florian Fainelli [this message]
2021-06-24 22:33 ` [PATCH 1/4] ARM: dts: NSP: disable qspi node by default Florian Fainelli

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=20210624223456.1315572-1-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mnhagan88@gmail.com \
    --cc=npcomplete13@gmail.com \
    --cc=olteanv@gmail.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    /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).