From: Greg KH <gregkh@linuxfoundation.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: stable@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH linux-5.4.y] bgmac: fix *initial* chip reset to support BCM5358
Date: Fri, 7 Jul 2023 17:56:39 +0200 [thread overview]
Message-ID: <2023070731-boxcar-pointed-d73f@gregkh> (raw)
In-Reply-To: <20230706111346.20234-1-zajec5@gmail.com>
On Thu, Jul 06, 2023 at 01:13:46PM +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> commit f99e6d7c4ed3be2531bd576425a5bd07fb133bd7 upstream.
>
> While bringing hardware up we should perform a full reset including the
> switch bit (BGMAC_BCMA_IOCTL_SW_RESET aka SICF_SWRST). It's what
> specification says and what reference driver does.
>
> This seems to be critical for the BCM5358. Without this hardware doesn't
> get initialized properly and doesn't seem to transmit or receive any
> packets.
>
> Originally bgmac was calling bgmac_chip_reset() before setting
> "has_robosw" property which resulted in expected behaviour. That has
> changed as a side effect of adding platform device support which
> regressed BCM5358 support.
>
> Fixes: f6a95a24957a ("net: ethernet: bgmac: Add platform device support")
> Cc: Jon Mason <jdmason@kudzu.us>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> Link: https://lore.kernel.org/r/20230227091156.19509-1-zajec5@gmail.com
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> Upstream commit wasn't backported to 5.4 (and older) because it couldn't
> be cherry-picked cleanly. There was a small fuzz caused by a missing
> commit 8c7da63978f1 ("bgmac: configure MTU and add support for frames
> beyond 8192 byte size").
>
> I've manually cherry-picked fix for BCM5358 to the linux-5.4.x.
> ---
> drivers/net/ethernet/broadcom/bgmac.c | 8 ++++++--
> drivers/net/ethernet/broadcom/bgmac.h | 2 ++
> 2 files changed, 8 insertions(+), 2 deletions(-)
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-07-07 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 11:13 [PATCH linux-5.4.y] bgmac: fix *initial* chip reset to support BCM5358 Rafał Miłecki
2023-07-07 15:56 ` Greg KH [this message]
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=2023070731-boxcar-pointed-d73f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=zajec5@gmail.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.