From: Conor Dooley <mail@conchuod.ie>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Conor.Dooley@microchip.com
Cc: palmer@rivosinc.com, apatel@ventanamicro.com,
netdev@vger.kernel.org, Nicolas.Ferre@microchip.com,
Claudiu.Beznea@microchip.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux-riscv@lists.infradead.org
Subject: Re: riscv defconfig CONFIG_PM/macb/generic PHY regression in v5.18-rc1
Date: Tue, 5 Apr 2022 17:58:50 +0100 [thread overview]
Message-ID: <0415ff44-34fd-2f00-833d-fbcea3a967cb@conchuod.ie> (raw)
In-Reply-To: <Ykxl4m1uPPDktZnD@shell.armlinux.org.uk>
On 05/04/2022 16:53, Russell King (Oracle) wrote:
> On Tue, Apr 05, 2022 at 01:05:12PM +0000, Conor.Dooley@microchip.com wrote:
>> Hey,
>> I seem to have come across a regression in the default riscv defconfig
>> between riscv-for-linus-5.18-mw0 (bbde015227e8) & v5.18-rc1, exposed by
>> c5179ef1ca0c ("RISC-V: Enable RISC-V SBI CPU Idle driver for QEMU virt
>> machine") which causes the ethernet phy to not come up on my Icicle kit:
>> [ 3.179864] macb 20112000.ethernet eth0: validation of sgmii with support 0000000,00000000,00006280 and advertisement 0000000,00000000,00004280 failed: -EINVAL
>> [ 3.194490] macb 20112000.ethernet eth0: Could not attach PHY (-22)
>
> I don't think that would be related to the idle driver. This looks like
> the PHY hasn't filled in the supported mask at probe time - do you have
> the driver for the PHY built-in or the PHY driver module loaded?
Hey Russel,
The idle stuff enabled CONFIG_PM=y though in the default riscv
defconfig, so it is not confined to just QEMU.
I am not sure what the symbol for the generic phy & I am not at work
to properly check, so I hope this is the relevant part of the config:
CONFIG_PHYLINK=y
CONFIG_PHYLIB=y
CONFIG_SWPHY=y
CONFIG_FIXED_PHY=y
If it isn't, you should be able to generate the config I used to cause
the error with:
make ARCH=RISCV defconfig
If you look at my response to Andrew [1] you'll see that my problems
are not isolated to just the Generic PHY driver as a builtin Vitesse
driver has issues too (although validation appears to have passed).
Thanks,
Conor.
[1]
https://lore.kernel.org/linux-riscv/60fd1eb7-a2ce-9084-c567-721e975e7e86@microchip.com/
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-04-05 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 13:05 riscv defconfig CONFIG_PM/macb/generic PHY regression in v5.18-rc1 Conor.Dooley
2022-04-05 13:25 ` Andrew Lunn
2022-04-05 14:18 ` Conor.Dooley
2022-04-05 14:41 ` Conor.Dooley
2022-04-05 14:49 ` Andrew Lunn
2022-04-05 14:56 ` Andrew Lunn
2022-04-05 15:04 ` Andrew Lunn
2022-04-05 16:25 ` Conor Dooley
2022-04-06 8:36 ` Conor.Dooley
2022-04-07 14:30 ` Conor.Dooley
2022-04-05 15:53 ` Russell King (Oracle)
2022-04-05 16:56 ` Palmer Dabbelt
2022-04-05 17:23 ` Conor Dooley
2022-04-05 18:06 ` Andrew Lunn
2022-04-05 18:35 ` Conor Dooley
2022-04-05 16:58 ` Conor Dooley [this message]
2022-04-05 18:55 ` Russell King (Oracle)
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=0415ff44-34fd-2f00-833d-fbcea3a967cb@conchuod.ie \
--to=mail@conchuod.ie \
--cc=Claudiu.Beznea@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=andrew@lunn.ch \
--cc=apatel@ventanamicro.com \
--cc=hkallweit1@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=palmer@rivosinc.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