From: Vinod Koul <vkoul@kernel.org>
To: Aleksandar Gerasimovski <Aleksandar.Gerasimovski@belden.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kishon@kernel.org" <kishon@kernel.org>
Subject: Re: [PATCH] phy/marvell/phy-mvebu-cp110-utmi: fix dr_mode property read from dts
Date: Thu, 15 Jan 2026 10:07:46 +0530 [thread overview]
Message-ID: <aWhvGn15591LtVXI@vaman> (raw)
In-Reply-To: <SA1PR18MB5692676E0E4617D560200305998FA@SA1PR18MB5692.namprd18.prod.outlook.com>
On 14-01-26, 09:58, Aleksandar Gerasimovski wrote:
> Hi Vinod,
Hi,
Please do not top post
Would you good to review the Documentation/process/ docs to understand
the process and expectations here.
>
> Thanks for looking into, can you be more specific with your comment?
Your email footer asked me to ignore, I have done that!
>
> Regards,
> Aleksandar
>
>
>
> From: Vinod Koul <vkoul@kernel.org>
> Sent: Wednesday, January 14, 2026 10:48 AM
> To: Aleksandar Gerasimovski <Aleksandar.Gerasimovski@belden.com>
> Cc: linux-kernel@vger.kernel.org; kishon@kernel.org
> Subject: Re: [PATCH] phy/marvell/phy-mvebu-cp110-utmi: fix dr_mode property read from dts
>
> On 06-01-26, 15: 06, Aleksandar Gerasimovski wrote: > The problem with the current implementation is that it does not consider > that the USB controller can have multiple PHY handles with different > arguments count, as for example we
>
> On 06-01-26, 15:06, Aleksandar Gerasimovski wrote:
> > The problem with the current implementation is that it does not consider
> > that the USB controller can have multiple PHY handles with different
> > arguments count, as for example we have in our cn9131 based platform:
> > "phys = <&cp0_comphy1 0>, <&cp0_utmi0>;".
> >
> > In such case calling "of_usb_get_dr_mode_by_phy" with -1 (no phy-cells)
> > leads to not proper phy detection, taking the "marvell,cp110-utmi-phy"
> > dts definition we can call the "of_usb_get_dr_mode_by_phy" with 0
> > (#phy-cells = <0>) and safely look for that phy.
> >
> > Signed-off-by: Aleksandar Gerasimovski <mailto:aleksandar.gerasimovski@belden.com>
> > ---
> > drivers/phy/marvell/phy-mvebu-cp110-utmi.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/phy/marvell/phy-mvebu-cp110-utmi.c b/drivers/phy/marvell/phy-mvebu-cp110-utmi.c
> > index 59903f86b13f..dd3e515a8e86 100644
> > --- a/drivers/phy/marvell/phy-mvebu-cp110-utmi.c
> > +++ b/drivers/phy/marvell/phy-mvebu-cp110-utmi.c
> > @@ -338,7 +338,7 @@ static int mvebu_cp110_utmi_phy_probe(struct platform_device *pdev)
> > return -ENOMEM;
> > }
> >
> > - port->dr_mode = of_usb_get_dr_mode_by_phy(child, -1);
> > + port->dr_mode = of_usb_get_dr_mode_by_phy(child, 0);
> > if ((port->dr_mode != USB_DR_MODE_HOST) &&
> > (port->dr_mode != USB_DR_MODE_PERIPHERAL)) {
> > dev_err(&pdev->dev,
> > --
> > 2.34.1
> >
> >
> > **********************************************************************
> > DISCLAIMER:
> > Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
>
>
> Okay destroyed!
>
> --
> ~Vinod
>
> **********************************************************************
> DISCLAIMER:
> Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
--
~Vinod
next prev parent reply other threads:[~2026-01-15 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:06 Aleksandar Gerasimovski
2026-01-06 15:28 ` Aleksandar Gerasimovski
2026-01-14 9:48 ` Vinod Koul
2026-01-14 9:58 ` Aleksandar Gerasimovski
2026-01-15 4:37 ` Vinod Koul [this message]
2026-01-15 10:42 ` Aleksandar Gerasimovski
2026-01-21 8:52 ` Vinod Koul
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=aWhvGn15591LtVXI@vaman \
--to=vkoul@kernel.org \
--cc=Aleksandar.Gerasimovski@belden.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.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®