netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Justin Chen <justin.chen@broadcom.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
	rafal@milecki.pl, linux@armlinux.org.uk, hkallweit1@gmail.com,
	bcm-kernel-feedback-list@broadcom.com, opendmb@gmail.com,
	conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
	pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
	davem@davemloft.net, andrew+netdev@lunn.ch,
	florian.fainelli@broadcom.com
Subject: Re: [PATCH net-next 3/5] net: bcmasp: Remove support for asp-v2.0
Date: Tue, 22 Apr 2025 19:32:35 +0100	[thread overview]
Message-ID: <20250422183235.GN2843373@horms.kernel.org> (raw)
In-Reply-To: <20250416224815.2863862-4-justin.chen@broadcom.com>

On Wed, Apr 16, 2025 at 03:48:13PM -0700, Justin Chen wrote:
> The SoC that supported asp-v2.0 never saw the light of day. asp-v2.0 has
> quirks that makes the logic overly complicated. For example, asp-v2.0 is
> the only revision that has a different wake up IRQ hook up. Remove asp-v2.0
> support to make supporting future HW revisions cleaner.
> 
> Signed-off-by: Justin Chen <justin.chen@broadcom.com>
> ---
>  drivers/net/ethernet/broadcom/asp2/bcmasp.c   | 98 ++-----------------
>  drivers/net/ethernet/broadcom/asp2/bcmasp.h   | 45 ++-------
>  .../ethernet/broadcom/asp2/bcmasp_ethtool.c   | 21 +---
>  .../net/ethernet/broadcom/asp2/bcmasp_intf.c  |  2 +-
>  .../ethernet/broadcom/asp2/bcmasp_intf_defs.h |  3 +-
>  5 files changed, 23 insertions(+), 146 deletions(-)
> 
> diff --git a/drivers/net/ethernet/broadcom/asp2/bcmasp.c b/drivers/net/ethernet/broadcom/asp2/bcmasp.c

...

>  static const struct bcmasp_plat_data v21_plat_data = {
> -	.init_wol = bcmasp_init_wol_shared,
> -	.enable_wol = bcmasp_enable_wol_shared,
> -	.destroy_wol = bcmasp_wol_irq_destroy_shared,
>  	.core_clock_select = bcmasp_core_clock_select_one,
> -	.hw_info = &v21_hw_info,
> +	.eee_fixup = NULL;

	.eee_fixup = NULL,

>  };

...

  reply	other threads:[~2025-04-22 18:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 22:48 [PATCH net-next 0/5] net: bcmasp: Add v3.0 and remove v2.0 Justin Chen
2025-04-16 22:48 ` [PATCH net-next 1/5] dt-bindings: net: brcm,asp-v2.0: " Justin Chen
2025-04-17  5:52   ` Krzysztof Kozlowski
2025-04-17 17:40     ` Justin Chen
2025-04-16 22:48 ` [PATCH net-next 2/5] dt-bindings: net: brcm,unimac-mdio: " Justin Chen
2025-04-16 22:48 ` [PATCH net-next 3/5] net: bcmasp: Remove support for asp-v2.0 Justin Chen
2025-04-22 18:32   ` Simon Horman [this message]
2025-04-22 20:20     ` Russell King (Oracle)
2025-04-16 22:48 ` [PATCH net-next 4/5] net: bcmasp: Add support for asp-v3.0 Justin Chen
2025-04-17 18:13   ` Florian Fainelli
2025-04-16 22:48 ` [PATCH net-next 5/5] net: phy: mdio-bcm-unimac: Add asp-v3.0 and remove asp-v2.0 Justin Chen

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=20250422183235.GN2843373@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=hkallweit1@gmail.com \
    --cc=justin.chen@broadcom.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=opendmb@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=rafal@milecki.pl \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).