diff options
| author | Mian Yousaf Kaukab <ykaukab@suse.de> | 2021-04-14 13:33:58 +0300 |
|---|---|---|
| committer | Priyanka Jain <priyanka.jain@nxp.com> | 2021-06-16 15:44:08 +0300 |
| commit | 864c3dbc0affea081264ff31c229232fbd45945a (patch) | |
| tree | b0a5522830c1f5a984618548e7398723567682d1 /drivers/net/pfe_eth | |
| parent | 2bf4658b8c5e5f4f43dc1888fe39ea61e6eeba64 (diff) | |
| download | u-boot-864c3dbc0affea081264ff31c229232fbd45945a.tar.xz | |
ls1012a: net: pfe: remove pfe stop from bootcmd
When using bootefi to boot a EFI binary, u-boot is supposed to
provide networking service for EFI application. Currently, 'pfe stop'
command is called from bootcmd before running bootefi. As a result
network stops working for EFI applications and console is flooded with
"Rx pkt not on expected port" messages.
Implement board_quiesce_devices() for ls1012a boards and call
pfe_command_stop() from it instead of calling 'pfe stop' from
*_bootcmd and bootcmd.
Tested-by: Anji Jagarlmudi <anji.jagarlmudi@nxp.com>
Signed-off-by: Mian Yousaf Kaukab <ykaukab@suse.de>
Reviewed-by: Ramon Fried <rfried.dev@gmail.com>
[Fixed checkpatch space error]
Signed-off-by: Priyanka Jain <priyanka.jain@nxp.com>
Diffstat (limited to 'drivers/net/pfe_eth')
| -rw-r--r-- | drivers/net/pfe_eth/pfe_cmd.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/pfe_eth/pfe_cmd.c b/drivers/net/pfe_eth/pfe_cmd.c index 1e69525cb7..364750f65c 100644 --- a/drivers/net/pfe_eth/pfe_cmd.c +++ b/drivers/net/pfe_eth/pfe_cmd.c @@ -418,7 +418,7 @@ static void send_dummy_pkt_to_hif(void) writel(buf, TMU_PHY_INQ_PKTINFO); } -static void pfe_command_stop(int argc, char *const argv[]) +void pfe_command_stop(int argc, char *const argv[]) { int pfe_pe_id, hif_stop_loop = 10; u32 rx_status; |