From: Elmar Psilog <epsi@gmx.de>
To: Marek Vasut <marex@denx.de>, u-boot@lists.denx.de
Cc: rfried.dev@gmail.com
Subject: Re: [PATCH v3] Let the EQoS in imx8mp handle fixed-phy too.
Date: Sun, 19 Mar 2023 21:02:00 +0100 [thread overview]
Message-ID: <fcbb2de7-85b3-d971-cf29-bb58f85172d1@gmx.de> (raw)
In-Reply-To: <d4625ebf-0f96-5f90-d856-966cb2a7ae7c@denx.de>
Am 19.03.23 um 18:21 schrieb Marek Vasut:
> On 3/19/23 11:43, Elmar Psilog wrote:
>>> Without that patch it lost track to the node to scan
>>> speed and duplex.
>>> Patch was created by Marek Vasut, just tested by me.
>>>
>>> Signed-off-by: Elmar Psilog <epsi at gmx.de>
>>> Reviewed-by: Marek Vasut <marex at denx.de>
>>> ---
>>> changes v2: fix format issues
>>> changes v3: remove {} around single if, add reviewd..
>>>
>>> drivers/net/dwc_eth_qos.c | 18 +++++++++++++++---
>>> 1 file changed, 15 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/net/dwc_eth_qos.c b/drivers/net/dwc_eth_qos.c
>>> index 112deb546d..b9de205b8a 100644
>>> --- a/drivers/net/dwc_eth_qos.c
>>> +++ b/drivers/net/dwc_eth_qos.c
>>> @@ -788,9 +788,21 @@ static int eqos_start(struct udevice *dev)
>>> */
>>> if (!eqos->phy) {
>>> int addr = -1;
>>> - addr = eqos_get_phy_addr(eqos, dev);
>>> - eqos->phy = phy_connect(eqos->mii, addr, dev,
>>> - eqos->config->interface(dev));
>>> + ofnode fixed_node;
>>> +
>>> + if (IS_ENABLED(CONFIG_PHY_FIXED)) {
>>> + fixed_node = ofnode_find_subnode(dev_ofnode(dev),
>>> + "fixed-link");
>>> + if (ofnode_valid(fixed_node))
>>> + eqos->phy = fixed_phy_create(dev_ofnode(dev));
>>> + }
>>> +
>>> + if (!eqos->phy) {
>>> + addr = eqos_get_phy_addr(eqos, dev);
>>> + eqos->phy = phy_connect(eqos->mii, addr, dev,
>>> + eqos->config->interface(dev));
>>> + }
>>> +
>>> if (!eqos->phy) {
>>> pr_err("phy_connect() failed");
>>> goto err_stop_resets;
>>> --
>>> 2.34.1
>>
>>
>> I would give a short reminder about the patch. Reviewed by Marek, ok for
>> Ramon. Would be glad to see it in 2023.04.
>
> We're already in 2023.04-rc4 , this is material for v2023.07 , i.e.
> for u-boot/next branch .
Ok, but does it change anything for the patch itself? As source isn't
touched in last weeks it is still needed. Other way asked: Any action
(from my side) needed? I just afraid your (@Marek) and my work gets
lost. I would expect either an "accepted" or "rejected" (for a reason).
next prev parent reply other threads:[~2023-03-19 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 15:03 [PATCH v3] Let the EQoS in imx8mp handle fixed-phy too Elmar Psilog
2023-03-19 10:43 ` Elmar Psilog
2023-03-19 17:21 ` Marek Vasut
2023-03-19 20:02 ` Elmar Psilog [this message]
2023-03-19 22:58 ` Marek Vasut
2023-05-06 14:54 ` Tom Rini
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=fcbb2de7-85b3-d971-cf29-bb58f85172d1@gmx.de \
--to=epsi@gmx.de \
--cc=marex@denx.de \
--cc=rfried.dev@gmail.com \
--cc=u-boot@lists.denx.de \
/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