[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <30b05289-2cd6-6ca9-51fd-0af351506b6e@pengutronix.de>
Date: Mon, 20 Jan 2020 10:50:01 +0100
From: Oleksij Rempel <o.rempel@...gutronix.de>
To: Andrew Lunn <andrew@...n.ch>
Cc: Fabio Estevam <festevam@...il.com>, netdev@...r.kernel.org,
Sascha Hauer <s.hauer@...gutronix.de>,
linux-kernel@...r.kernel.org, linux-imx@....com,
kernel@...gutronix.de, Shawn Guo <shawnguo@...nel.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v1] ARM i.MX6q: make sure PHY fixup for KSZ9031 is applied
only on one board
On 09.12.19 18:51, Andrew Lunn wrote:
>> Yes. all of them are broken.
>> I just trying to not wake all wasp at one time. Most probably there are
>> board working by accident. So, it will be good to have at least separate
>> patches for each fixup.
>
> I agree about a patch per fixup. Can you try to generate such patches?
> See if there is enough history in git to determine which boards
> actually need these fixups?
After some attempts to make it and more discussions, I tend to provide a Kconfig to
disable/enable this fixups. This will provide an option for users with old devicetree
and possibility to continue development on clean setup.
What do you think about this way and what default state it should be? FIXUPS default on or
off?
Kind regards,
Oleksij Rempel
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists