From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, fugang.duan@nxp.com,
cphealy@gmail.com, dkarr@vyex.com
Subject: Re: [PATCH v2] net: fec: fix MDIO probing for some FEC hardware blocks
Date: Fri, 30 Oct 2020 11:53:04 +0100 [thread overview]
Message-ID: <20201030105304.GA37786@workstation.tuxnet> (raw)
In-Reply-To: <20201028052232.1315167-1-gerg@linux-m68k.org>
On Wed, Oct 28, 2020 at 03:22:32PM +1000, Greg Ungerer wrote:
> Some (apparently older) versions of the FEC hardware block do not like
> the MMFR register being cleared to avoid generation of MII events at
> initialization time. The action of clearing this register results in no
> future MII events being generated at all on the problem block. This means
> the probing of the MDIO bus will find no PHYs.
>
> Create a quirk that can be checked at the FECs MII init time so that
> the right thing is done. The quirk is set as appropriate for the FEC
> hardware blocks that are known to need this.
>
> Fixes: f166f890c8f0 ("net: ethernet: fec: Replace interrupt driven MDIO with polled IO")
> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
> ---
> drivers/net/ethernet/freescale/fec.h | 6 +++++
> drivers/net/ethernet/freescale/fec_main.c | 29 +++++++++++++----------
> 2 files changed, 22 insertions(+), 13 deletions(-)
>
> v2: use quirk for imx28 as well
>
> Resending for consideration based on Andy's last comment that this fix
> is enough on its own for all hardware types.
>
> diff --git a/drivers/net/ethernet/freescale/fec.h b/drivers/net/ethernet/freescale/fec.h
> index 832a2175636d..c527f4ee1d3a 100644
> --- a/drivers/net/ethernet/freescale/fec.h
> +++ b/drivers/net/ethernet/freescale/fec.h
> @@ -456,6 +456,12 @@ struct bufdesc_ex {
> */
> #define FEC_QUIRK_HAS_FRREG (1 << 16)
>
> +/* Some FEC hardware blocks need the MMFR cleared at setup time to avoid
> + * the generation of an MII event. This must be avoided in the older
> + * FEC blocks where it will stop MII events being generated.
> + */
> +#define FEC_QUIRK_CLEAR_SETUP_MII (1 << 17)
> +
> struct bufdesc_prop {
> int qid;
> /* Address of Rx and Tx buffers */
> diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
> index fb37816a74db..65784d3e54a5 100644
> --- a/drivers/net/ethernet/freescale/fec_main.c
> +++ b/drivers/net/ethernet/freescale/fec_main.c
> @@ -100,14 +100,14 @@ static const struct fec_devinfo fec_imx27_info = {
> static const struct fec_devinfo fec_imx28_info = {
> .quirks = FEC_QUIRK_ENET_MAC | FEC_QUIRK_SWAP_FRAME |
> FEC_QUIRK_SINGLE_MDIO | FEC_QUIRK_HAS_RACC |
> - FEC_QUIRK_HAS_FRREG,
> + FEC_QUIRK_HAS_FRREG | FEC_QUIRK_CLEAR_SETUP_MII,
> };
>
> static const struct fec_devinfo fec_imx6q_info = {
> .quirks = FEC_QUIRK_ENET_MAC | FEC_QUIRK_HAS_GBIT |
> FEC_QUIRK_HAS_BUFDESC_EX | FEC_QUIRK_HAS_CSUM |
> FEC_QUIRK_HAS_VLAN | FEC_QUIRK_ERR006358 |
> - FEC_QUIRK_HAS_RACC,
> + FEC_QUIRK_HAS_RACC | FEC_QUIRK_CLEAR_SETUP_MII,
> };
>
> static const struct fec_devinfo fec_mvf600_info = {
> @@ -119,7 +119,8 @@ static const struct fec_devinfo fec_imx6x_info = {
> FEC_QUIRK_HAS_BUFDESC_EX | FEC_QUIRK_HAS_CSUM |
> FEC_QUIRK_HAS_VLAN | FEC_QUIRK_HAS_AVB |
> FEC_QUIRK_ERR007885 | FEC_QUIRK_BUG_CAPTURE |
> - FEC_QUIRK_HAS_RACC | FEC_QUIRK_HAS_COALESCE,
> + FEC_QUIRK_HAS_RACC | FEC_QUIRK_HAS_COALESCE |
> + FEC_QUIRK_CLEAR_SETUP_MII,
> };
>
> static const struct fec_devinfo fec_imx6ul_info = {
> @@ -127,7 +128,7 @@ static const struct fec_devinfo fec_imx6ul_info = {
> FEC_QUIRK_HAS_BUFDESC_EX | FEC_QUIRK_HAS_CSUM |
> FEC_QUIRK_HAS_VLAN | FEC_QUIRK_ERR007885 |
> FEC_QUIRK_BUG_CAPTURE | FEC_QUIRK_HAS_RACC |
> - FEC_QUIRK_HAS_COALESCE,
> + FEC_QUIRK_HAS_COALESCE | FEC_QUIRK_CLEAR_SETUP_MII,
> };
>
> static struct platform_device_id fec_devtype[] = {
> @@ -2114,15 +2115,17 @@ static int fec_enet_mii_init(struct platform_device *pdev)
> if (suppress_preamble)
> fep->phy_speed |= BIT(7);
>
> - /* Clear MMFR to avoid to generate MII event by writing MSCR.
> - * MII event generation condition:
> - * - writing MSCR:
> - * - mmfr[31:0]_not_zero & mscr[7:0]_is_zero &
> - * mscr_reg_data_in[7:0] != 0
> - * - writing MMFR:
> - * - mscr[7:0]_not_zero
> - */
> - writel(0, fep->hwp + FEC_MII_DATA);
> + if (fep->quirks & FEC_QUIRK_CLEAR_SETUP_MII) {
> + /* Clear MMFR to avoid to generate MII event by writing MSCR.
> + * MII event generation condition:
> + * - writing MSCR:
> + * - mmfr[31:0]_not_zero & mscr[7:0]_is_zero &
> + * mscr_reg_data_in[7:0] != 0
> + * - writing MMFR:
> + * - mscr[7:0]_not_zero
> + */
> + writel(0, fep->hwp + FEC_MII_DATA);
> + }
>
> writel(fep->phy_speed, fep->hwp + FEC_MII_SPEED);
>
> --
> 2.25.1
>
This fixes the problem on i.MX6Q!
Tested-by: Clemens Gruber <clemens.gruber@pqgruber.com>
Best regards,
Clemens
prev parent reply other threads:[~2020-10-30 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 5:22 [PATCH v2] net: fec: fix MDIO probing for some FEC hardware blocks Greg Ungerer
2020-10-28 5:28 ` [EXT] " Andy Duan
2020-10-30 0:02 ` Andrew Lunn
2020-10-30 15:26 ` Jakub Kicinski
2020-10-30 10:53 ` Clemens Gruber [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=20201030105304.GA37786@workstation.tuxnet \
--to=clemens.gruber@pqgruber.com \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=dkarr@vyex.com \
--cc=fugang.duan@nxp.com \
--cc=gerg@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).