Devicetree
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>,
	Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v5 2/5] include: linux: phy: Add phy attribute "type" and associated helpers
Date: Tue, 4 Aug 2026 22:22:20 +0000	[thread overview]
Message-ID: <anJhN9-4dOtDqncs@vbox> (raw)
In-Reply-To: <5zgabwyhxu65hacpr53cwktwe4npu2ndzgvt3uulja5lejnmi4@bj4uxp5wlb7l>

On Sun, Jul 26, 2026, Dmitry Baryshkov wrote:
> On Thu, Jul 23, 2026 at 04:09:05PM +0530, Krishna Kurapati wrote:
> > In cases like USB High-speed phys which can be either USB2 or EUSB2, it is
> > required to know the type of phy (rather than the operating mode).
> 
> Why?

Perhaps Krishna should expand on this in the commit message. See patch
5/5 for the reason.

> 
> > Add
> > support to cache the PHY_TYPE and add the following helpers:
> > 
> > - phy_set_type() for the phy drivers (like m31_eusb2 or snps-eusb2) to
> > declare what type of PHY they are (in this case PHY_TYPE_EUSB2).
> 
> PHY type is usually coveyed through the PHY cells in DT. Why do you need
> to set it from the driver?

PHY_TYPE_* via phy cells is typically used for combo PHYs for multiple
protocols where cell arg selects the lane. In this case, the eusb2 phy
is a single protocol phy with #phy-cells = <0>. Adding a cell arg just
for the type would require updating all the eusb2 phy bindings and every
dts file referencing it. Introducing a new interface and setting it from
the phy driver is IMHO a cleaner approach.

BR,
Thinh

> 
> > 
> > - phy_get_type() for the consumers (like USB controllers) to query the
> > type of phy connected to them.
> > 
> > Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
> > ---
> >  include/linux/phy/phy.h | 27 +++++++++++++++++++++++++++
> >  1 file changed, 27 insertions(+)
> > 
> 
> -- 
> With best wishes
> Dmitry

  reply	other threads:[~2026-08-04 22:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 10:39 [PATCH v5 0/5] Modify interrupt handling for eUSB2 Phy targets Krishna Kurapati
2026-07-23 10:39 ` [PATCH v5 1/5] dt-bindings: phy: Add PHY_TYPE_EUSB2 definition Krishna Kurapati
2026-07-26 20:36   ` Dmitry Baryshkov
2026-07-27  7:11   ` Krzysztof Kozlowski
2026-07-23 10:39 ` [PATCH v5 2/5] include: linux: phy: Add phy attribute "type" and associated helpers Krishna Kurapati
2026-07-26 20:36   ` Dmitry Baryshkov
2026-08-04 22:22     ` Thinh Nguyen [this message]
2026-07-23 10:39 ` [PATCH v5 3/5] phy: snps-eusb2: Set phy type to EUSB2 Krishna Kurapati
2026-07-24 21:51   ` Sebastian Reichel
2026-07-26 17:08     ` Krishna Kurapati
2026-08-04 22:28       ` Thinh Nguyen
2026-08-05  0:43         ` Sebastian Reichel
2026-08-04 21:42   ` Thinh Nguyen
2026-07-23 10:39 ` [PATCH v5 4/5] phy: qcom: m31-eusb2: " Krishna Kurapati
2026-08-04 21:46   ` Thinh Nguyen
2026-07-23 10:39 ` [PATCH v5 5/5] usb: dwc3: qcom: Modify interrupt handling for eUSB2 Phy targets Krishna Kurapati
2026-07-23 11:31   ` sashiko-bot
2026-08-04 22:01   ` Thinh Nguyen

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=anJhN9-4dOtDqncs@vbox \
    --to=thinh.nguyen@synopsys.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=krishna.kurapati@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --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