From: Neil Armstrong <narmstrong@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Geraldo Nascimento <geraldogabriel@gmail.com>
Cc: arnd@arndb.de, bjorn.andersson@linaro.org,
linux-amlogic@lists.infradead.org
Subject: Re: Regression, bisected: meson-dwmac8b never loads, no ethernet
Date: Tue, 21 Sep 2021 08:57:25 +0200 [thread overview]
Message-ID: <274de82d-74f7-ad8b-2707-c424ecb6811f@baylibre.com> (raw)
In-Reply-To: <CAFBinCC+7sgtqr2rQPP3OX9v7yss3nm0eCjpx4qan5_BQJ1eHg@mail.gmail.com>
Hi Geraldo,
Thanks for the report
On 21/09/2021 07:31, Martin Blumenstingl wrote:
> Hi Geraldo,
>
> On Tue, Sep 21, 2021 at 4:09 AM Geraldo Nascimento
> <geraldogabriel@gmail.com> wrote:
>>
>> Sorry to add further noise to this, as there's still 6 release candidates to solve this regression, but the correct name of the driver is meson8b-dwmac.
>>
>> You see, git bisecting the kernel had my head spinning so much that I apparently switched the proper driver name.
>>
>> Speaking of which, I swear I ran git bisect every time telling it good when where's good and vice-versa. And was I left with a qcom general device tree commit that also merges qcom 5.14-rc3 into 5.15 because of a regression in USB apparently?
> Which board/SoC are you referring to?
> I can confirm that dwmac-meson8b still works fine on an Odroid-C1
> (Meson8b SoC) with 5.15-rc2
> Newer (arm64) SoCs additionally use an MDIO mux driver:
> - mdio-mux-mmioreg on GXL, GXM
> - mdio-mux-meson-g12a on G12A, G12B, SM1
Indeed it's an issue with mdio muxes, a similar issue had been reported by Marek at https://lore.kernel.org/all/0a2c4106-7f48-2bb5-048e-8c001a7c3fda@samsung.com/
and it concerns commit cf4b94c8530d ("of: property: fw_devlink: Add support for "phy-handle" property")
It may be the same issue here.
Neil
>
>
> Best regards,
> Martin
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2021-09-21 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 23:43 Geraldo Nascimento
[not found] ` <CAEsQvctayUAp4Cx=TaqjUu90VNZa1itqyfqMNzDrDGfr--aSQg@mail.gmail.com>
2021-09-21 5:31 ` Martin Blumenstingl
2021-09-21 6:57 ` Neil Armstrong [this message]
2021-09-21 7:22 ` Geraldo Nascimento
2021-09-21 7:22 ` Arnd Bergmann
2021-09-21 7:26 ` Geraldo Nascimento
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=274de82d-74f7-ad8b-2707-c424ecb6811f@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=geraldogabriel@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.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
all inboxes | Powered by JetHome®