On Sat, 2 Mar 2019 at 06:27, Peng Fan peng.fan@nxp.com wrote:
On Mon, 4 Feb 2019 at 10:05, Chris Spencer spencercw@gmail.com wrote:
From: Chris Spencer christopher.spencer@sea.co.uk
The Ethernet controller is not able to initialise correctly without the pinctrl driver.
This config setting was enabled in the initial version of this file, but was removed by a savedefconfig resync because the parameter did not actually exist at that point.
Fixes: 1bac199e8c87 ("configs: Resync with savedefconfig") Signed-off-by: Chris Spencer christopher.spencer@sea.co.uk Reviewed-by: Fabio Estevam festevam@gmail.com
Depends on this patch:
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpat
chwork.ozlabs.org%2Fpatch%2F1031817%2F&data=02%7C01%7Cpeng.f an%40n
xp.com%7Cffae7c0ab2494a20159008d69e40ed2d%7C686ea1d3bc2b4c6fa92 cd99c5c
301635%7C0%7C0%7C636870399030578148&sdata=0tJenqE8zP4dFhLs HJJ5WO3n
Tmiyz%2FAZWeclKFp8wso%3D&reserved=0
Changes in v2:
- Added Fabio's Reviewed-by.
- Corrected From address.
Since there hasn't been any activity on the i.MX8MM patch series for a while, I wonder if the pinctrl driver [1] could be committed in isolation? This patch could then be applied so we can get the Ethernet working on the i.MX8MQ.
The blocking issue for i.MX8MM is clock part, for the pinctrl that could be reused by i.MX8MQ, I think it could be committed, but need Stefano to decide.
Regards, Peng.
Any thoughts on this, Stefano? Would be good to get the pinctrl driver + defconfig change into 2019.04 if we can.
Thanks, Chris