All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
	Baruch Siach <baruch@tkos.co.il>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	stable <stable@vger.kernel.org>, Soeren Moch <smoch@web.de>,
	Steve Twiss <stwiss.opensource@diasemi.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: imx: Fix the AR803X phy-mode
Date: Tue, 2 Apr 2019 08:06:22 -0300	[thread overview]
Message-ID: <CAOMZO5DWcckLSbAmAG2dc5oCgz6z54g4N1mqf3hYX8O7rDY+UQ@mail.gmail.com> (raw)
In-Reply-To: <20190402055252.j6yfbsk2rusujvyw@pengutronix.de>

Hi Michael,

On Tue, Apr 2, 2019 at 2:52 AM Michael Grzeschik <mgr@pengutronix.de> wrote:

> These use the KSZ9021. But the fix was obviously the right one
> after v5.0 making the network stable again. I did not dig deeper
> into the cause, after finding this diff solving the issue.

I was not aware that KSZ9021 PHYs are currently broken too.

This patch aims to fixing the i.MX boards with AR8031/AR8035 PHY.

The fix for KSZ9021 would require some explanation as to what commit
exposed or caused the issue and would be better to be on a separate
patch.

Could you please work on that?

Thanks

WARNING: multiple messages have this Message-ID (diff)
From: Fabio Estevam <festevam@gmail.com>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>, Baruch Siach <baruch@tkos.co.il>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	stable <stable@vger.kernel.org>, Soeren Moch <smoch@web.de>,
	Steve Twiss <stwiss.opensource@diasemi.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: imx: Fix the AR803X phy-mode
Date: Tue, 2 Apr 2019 08:06:22 -0300	[thread overview]
Message-ID: <CAOMZO5DWcckLSbAmAG2dc5oCgz6z54g4N1mqf3hYX8O7rDY+UQ@mail.gmail.com> (raw)
In-Reply-To: <20190402055252.j6yfbsk2rusujvyw@pengutronix.de>

Hi Michael,

On Tue, Apr 2, 2019 at 2:52 AM Michael Grzeschik <mgr@pengutronix.de> wrote:

> These use the KSZ9021. But the fix was obviously the right one
> after v5.0 making the network stable again. I did not dig deeper
> into the cause, after finding this diff solving the issue.

I was not aware that KSZ9021 PHYs are currently broken too.

This patch aims to fixing the i.MX boards with AR8031/AR8035 PHY.

The fix for KSZ9021 would require some explanation as to what commit
exposed or caused the issue and would be better to be on a separate
patch.

Could you please work on that?

Thanks

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-04-02 11:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 12:47 [PATCH] ARM: dts: imx: Fix the AR803X phy-mode Fabio Estevam
2019-04-01 12:47 ` Fabio Estevam
2019-04-01 17:55 ` Michael Grzeschik
2019-04-01 17:55   ` Michael Grzeschik
2019-04-01 19:47   ` Fabio Estevam
2019-04-01 19:47     ` Fabio Estevam
2019-04-02  5:52     ` Michael Grzeschik
2019-04-02  5:52       ` Michael Grzeschik
2019-04-02 11:06       ` Fabio Estevam [this message]
2019-04-02 11:06         ` Fabio Estevam
2019-04-02 13:21         ` Andrew Lunn
2019-04-02 13:21           ` Andrew Lunn
2019-04-03  6:40           ` Michael Grzeschik
2019-04-03  6:40             ` Michael Grzeschik
2019-04-08 10:44             ` Michael Grzeschik
2019-04-08 10:44               ` Michael Grzeschik
2019-04-02 15:48 ` Sasha Levin
2019-04-02 16:26   ` Fabio Estevam
2019-04-02 16:26     ` Fabio Estevam

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=CAOMZO5DWcckLSbAmAG2dc5oCgz6z54g4N1mqf3hYX8O7rDY+UQ@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=baruch@tkos.co.il \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux@armlinux.org.uk \
    --cc=mgr@pengutronix.de \
    --cc=mkl@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=smoch@web.de \
    --cc=stable@vger.kernel.org \
    --cc=stwiss.opensource@diasemi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.