From: "Heiko Stübner" <heiko@sntech.de>
To: u-boot@lists.denx.de, bmeng.cn@gmail.com, rick@andestech.com,
anup.patel@wdc.com, atish.patra@wdc.com, hs@denx.de
Cc: cyril.jean@microchip.com, lewis.hanly@microchip.com,
conor.dooley@microchip.com, daire.mcnamara@microchip.com,
ivan.griffin@microchip.com,
valentina.fernandezalanis@microchip.com,
Padmarao Begari <padmarao.begari@microchip.com>,
Padmarao Begari <padmarao.begari@microchip.com>
Subject: Re: macb clock handling (Was: [PATCH v1 4/5] net: macb: Compatible as per device tree)
Date: Thu, 25 Nov 2021 20:32:51 +0100 [thread overview]
Message-ID: <1771149.Og9QhtiVRx@diego> (raw)
In-Reply-To: <4033485.bJdaIYV4bU@diego>
Hi,
Am Donnerstag, 11. November 2021, 10:41:46 CET schrieb Heiko Stübner:
> not wanting to hijack this too much, but does the mac driver also need
> some sort of clock handling?
>
> Because on the Icicle I have here, I'm running into "TX timeout" errors:
>
> RISC-V # dhcp
> ethernet@20112000: PHY present at 9
> ethernet@20112000: Starting autonegotiation...
> ethernet@20112000: Autonegotiation complete
> ethernet@20112000: link up, 1000Mbps full-duplex (lpa: 0x3800)
> BOOTP broadcast 1
> ethernet@20112000: TX timeout
> BOOTP broadcast 2
> ethernet@20112000: TX timeout
> BOOTP broadcast 3
> ethernet@20112000: TX timeout
> BOOTP broadcast 4
> ethernet@20112000: TX timeout
>
> The sifive variant of the macb distinguishes between speeds in its
> cllk_init callback, so I guess the Icicle might need that as well?
just for "the archive", i.e. when people read this in the future:
I got this solved by updating the HSS to a recent release (2021.11
in this case).
So now I do have working network in u-boot.
Heiko
> Am Freitag, 22. Oktober 2021, 10:56:47 CET schrieb Padmarao Begari:
> > Update compatible as per Microchip PolarFire SoC ethernet
> > device node.
> >
> > Signed-off-by: Padmarao Begari <padmarao.begari@microchip.com>
> > ---
> > drivers/net/macb.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/macb.c b/drivers/net/macb.c
> > index 8c6461e717..1b867bd5c2 100644
> > --- a/drivers/net/macb.c
> > +++ b/drivers/net/macb.c
> > @@ -1502,7 +1502,7 @@ static const struct udevice_id macb_eth_ids[] = {
> > { .compatible = "cdns,zynq-gem" },
> > { .compatible = "sifive,fu540-c000-gem",
> > .data = (ulong)&sifive_config },
> > - { .compatible = "microchip,mpfs-mss-gem",
> > + { .compatible = "microchip,mpfs-gem",
> > .data = (ulong)µchip_config },
> > { }
> > };
> >
>
>
next prev parent reply other threads:[~2021-11-25 19:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 8:56 [PATCH v1 0/5] Update Microchip PolarFire SoC support Padmarao Begari
2021-10-22 8:56 ` [PATCH v1 1/5] riscv: dts: Split Microchip device tree Padmarao Begari
2021-11-01 8:34 ` Leo Liang
2021-11-01 8:41 ` Bin Meng
2021-11-02 9:52 ` Padmarao Begari
2021-10-22 8:56 ` [PATCH v1 2/5] riscv: Update Microchip MPFS Icicle Kit support Padmarao Begari
2021-11-01 8:36 ` Leo Liang
2021-11-01 8:43 ` Bin Meng
2021-11-02 10:38 ` Padmarao Begari
2021-10-22 8:56 ` [PATCH v1 3/5] i2c: Add Microchip PolarFire SoC I2C driver Padmarao Begari
2021-11-01 8:53 ` Leo Liang
2021-10-22 8:56 ` [PATCH v1 4/5] net: macb: Compatible as per device tree Padmarao Begari
2021-11-01 8:30 ` Leo Liang
2021-11-01 8:44 ` Bin Meng
2021-11-02 11:03 ` Padmarao Begari
2021-11-02 12:45 ` Bin Meng
2021-11-03 11:47 ` Padmarao Begari
2021-11-03 13:10 ` Padmarao Begari
2021-11-11 8:07 ` Bin Meng
2021-11-11 9:06 ` Padmarao Begari
2021-11-11 12:54 ` Michael Walle
2021-11-11 13:17 ` Ivan.Griffin
2021-11-12 1:28 ` Bin Meng
2021-11-12 9:36 ` Padmarao Begari
2021-11-11 13:20 ` Conor.Dooley
2021-11-11 9:41 ` macb clock handling (Was: [PATCH v1 4/5] net: macb: Compatible as per device tree) Heiko Stübner
2021-11-25 19:32 ` Heiko Stübner [this message]
2021-10-22 8:56 ` [PATCH v1 5/5] doc: board: Update Microchip MPFS Icicle Kit doc Padmarao Begari
2021-11-01 8:33 ` Leo Liang
2021-11-01 8:46 ` Bin Meng
2021-11-02 11:04 ` Padmarao Begari
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=1771149.Og9QhtiVRx@diego \
--to=heiko@sntech.de \
--cc=anup.patel@wdc.com \
--cc=atish.patra@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=hs@denx.de \
--cc=ivan.griffin@microchip.com \
--cc=lewis.hanly@microchip.com \
--cc=padmarao.begari@microchip.com \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=valentina.fernandezalanis@microchip.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