From: Heiner Kallweit <hkallweit1@gmail.com>
To: Chris Healy <cphealy@gmail.com>,
andrew@lunn.ch, linux@armlinux.org.uk, davem@davemloft.net,
neil.armstrong@linaro.org, khilman@baylibre.com,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
jeremy.wang@amlogic.com
Cc: Chris Healy <healych@amazon.com>
Subject: Re: [PATCH v2] net: phy: meson-gxl: Add generic dummy stubs for MMD register access
Date: Mon, 30 Jan 2023 21:16:10 +0100 [thread overview]
Message-ID: <0489ac03-ff79-adf1-104d-72523ace9701@gmail.com> (raw)
In-Reply-To: <20230130200352.462548-1-cphealy@gmail.com>
On 30.01.2023 21:03, Chris Healy wrote:
> From: Chris Healy <healych@amazon.com>
>
> The Meson G12A Internal PHY does not support standard IEEE MMD extended
> register access, therefore add generic dummy stubs to fail the read and
> write MMD calls. This is necessary to prevent the core PHY code from
> erroneously believing that EEE is supported by this PHY even though this
> PHY does not support EEE, as MMD register access returns all FFFFs.
>
> Fixes: 5c3407abb338 ("net: phy: meson-gxl: add g12a support")
> Signed-off-by: Chris Healy <healych@amazon.com>
> ---
>
> Change in v2:
> * Add fixes tag
>
Reviewed-by: Heiner Kallweit <hkallweit1@gmail.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2023-01-30 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 20:03 [PATCH v2] net: phy: meson-gxl: Add generic dummy stubs for MMD register access Chris Healy
2023-01-30 20:16 ` Heiner Kallweit [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=0489ac03-ff79-adf1-104d-72523ace9701@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=davem@davemloft.net \
--cc=healych@amazon.com \
--cc=jeremy.wang@amlogic.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=neil.armstrong@linaro.org \
--cc=netdev@vger.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