public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: "René Rebe" <rene@exactco.de>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] net: sunhme: Fix sbus regression
Date: Thu, 5 Feb 2026 20:41:11 -0500	[thread overview]
Message-ID: <cc269d9f-9a06-6623-e412-d04ecb7b4f74@gmail.com> (raw)
In-Reply-To: <20260205.170959.89574674688839340.rene@exactco.de>

On 2/5/26 11:09, René Rebe wrote:
> Commit cc216e4b44ce ("net: sunhme: Switch SBUS to devres") changed
> explicit sized of_ioremap with BMAC_REG_SIZEs to
> devm_platform_ioremap_resource mapping all the resource. However,
> this does not work on my Sun Ultra 2 with SBUS HMEs:
> 
> hme f0072f38: error -EBUSY: can't request region for resource [mem 0x1ffe8c07000-0x1ffe8c0701f]
> hme f0072f38: Cannot map TCVR registers.
> hme f0072f38: probe with driver hme failed with error -16
> hme f007ab44: error -EBUSY: can't request region for resource [mem 0x1ff28c07000-0x1ff28c0701f]
> hme f007ab44: Cannot map TCVR registers.
> hme f007ab44: probe with driver hme failed with error -16
> 
> Turns out the open-firmware resources overlap, at least on this
> machines and PROM version:
> 
> hexdump /proc/device-tree/sbus@1f,0/SUNW,hme@2,8c00000/reg:
> 00 00 00 02 08 c0 00 00  00 00 01 08
> 00 00 00 02 08 c0 20 00  00 00 20 00
> 00 00 00 02 08 c0 40 00  00 00 20 00
> 00 00 00 02 08 c0 60 00  00 00 20 00
> 00 00 00 02 08 c0 70 00  00 00 00 20
> 
> And the driver previously explicitly mapped way smaller mmio regions:
> 
> /proc/iomem:
> 1ff28c00000-1ff28c00107 : HME Global Regs
> 1ff28c02000-1ff28c02033 : HME TX Regs
> 1ff28c04000-1ff28c0401f : HME RX Regs
> 1ff28c06000-1ff28c0635f : HME BIGMAC Regs
> 1ff28c07000-1ff28c0701f : HME Tranceiver Regs
> 
> Quirk this specific issue by truncating the previous resource to not
> overlap into the TCVR registers.
> 
> Fixes: cc216e4b44ce ("net: sunhme: Switch SBUS to devres")
> Signed-off-by: René Rebe <rene@exactco.de>
> ---
> Tested on Sun Ultra 2 running T2/Linux.
> Alternatively we could explicitly size all regions, or check overlap
> in startup code (I also already have a patch for that, too).

What does this look like?

> ---
> 
> --- linux-6.18/drivers/net/ethernet/sun/sunhme.c.vanilla	2026-02-05 11:50:33.288906134 +0100
> +++ linux-6.18/drivers/net/ethernet/sun/sunhme.c	2026-02-05 11:55:22.541384377 +0100
> @@ -2551,6 +2551,9 @@
>   		goto err_out_clear_quattro;
>   	}
>   
> +	/* BIGMAC may have bogus sizes */
> +	if ((op->resource[3].end - op->resource[3].start) >= BMAC_REG_SIZE)
> +		op->resource[3].end = op->resource[3].start + BMAC_REG_SIZE - 1;
>   	hp->bigmacregs = devm_platform_ioremap_resource(op, 3);
>   	if (IS_ERR(hp->bigmacregs)) {
>   		dev_err(&op->dev, "Cannot map BIGMAC registers.\n");
> 

Reviewed-by: Sean Anderson <seanga2@gmail.com>

  reply	other threads:[~2026-02-06  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 16:09 [PATCH] net: sunhme: Fix sbus regression René Rebe
2026-02-06  1:41 ` Sean Anderson [this message]
2026-02-06  9:05   ` René Rebe
2026-02-06 14:49     ` Sean Anderson
2026-02-10 11:57       ` Paolo Abeni
2026-02-10 12:10 ` patchwork-bot+netdevbpf

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=cc269d9f-9a06-6623-e412-d04ecb7b4f74@gmail.com \
    --to=seanga2@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rene@exactco.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