From: Jakub Kicinski <kuba@kernel.org>
To: Doug Berger <opendmb@gmail.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Maarten Vanraes <maarten@rmail.be>,
netdev@vger.kernel.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Phil Elwell <phil@raspberrypi.com>
Subject: Re: [PATCH] net: bcmgenet: Reset RBUF on first open
Date: Tue, 5 Mar 2024 07:13:21 -0800 [thread overview]
Message-ID: <20240305071321.4f522fe8@kernel.org> (raw)
In-Reply-To: <f189f3c9-0ea7-4863-aba7-1c7d0fe11ee2@gmail.com>
On Mon, 26 Feb 2024 15:13:57 -0800 Doug Berger wrote:
> I agree that the Linux driver expects the GENET core to be in a "quasi
> power-on-reset state" and it seems likely that in both Maxime's case and
> the one identified here that is not the case. It would appear that the
> Raspberry Pi bootloader and/or "firmware" are likely not disabling the
> GENET receiver after loading the kernel image and before invoking the
> kernel. They may be disabling the DMA, but that is insufficient since
> any received data would likely overflow the RBUF leaving it in a "bad"
> state which this patch apparently improves.
>
> So it seems likely these issues are caused by improper
> bootloader/firmware behavior.
>
> That said, I suppose it would be nice if the driver were more robust.
> However, we both know how finicky the receive path of the GENET core can
> be about its initialization. Therefore, I am unwilling to "bless" this
> change for upstream without more due diligence on our side.
The patch has minor formatting issues (using spaces to indent).
Once you've gain sufficient confidence that it doesn't cause issues -
please mend that and repost.
--
pw-bot: cr
next prev parent reply other threads:[~2024-03-05 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 23:53 [PATCH] net: bcmgenet: Reset RBUF on first open Maarten Vanraes
2024-02-26 17:34 ` Florian Fainelli
2024-02-26 19:14 ` Maarten
2024-02-26 23:13 ` Doug Berger
2024-02-27 12:53 ` Paolo Abeni
2024-03-05 15:13 ` Jakub Kicinski [this message]
2024-03-05 20:36 ` Maarten
2024-03-05 21:07 ` Jakub Kicinski
2024-03-06 8:03 ` Maarten
2024-03-16 11:53 ` Maarten
2024-03-19 16:56 ` Florian Fainelli
2024-03-19 21:11 ` Maarten
2024-03-19 21:50 ` 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=20240305071321.4f522fe8@kernel.org \
--to=kuba@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=maarten@rmail.be \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=phil@raspberrypi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.