diff options
author | Michael Chan <michael.chan@broadcom.com> | 2023-04-16 23:58:18 -0700 |
---|---|---|
committer | Paolo Abeni <pabeni@redhat.com> | 2023-04-18 12:27:15 +0200 |
commit | e8b51a1a15d5a3cce231e0669f6a161dc5bb9b75 (patch) | |
tree | cfdb097b6443f2655c3063428874356c133389e9 /lib/kfifo.c | |
parent | e50b9b9e8610d47b7c22529443e45a16b1ea3a15 (diff) | |
download | linux-stable-e8b51a1a15d5a3cce231e0669f6a161dc5bb9b75.tar.gz linux-stable-e8b51a1a15d5a3cce231e0669f6a161dc5bb9b75.tar.bz2 linux-stable-e8b51a1a15d5a3cce231e0669f6a161dc5bb9b75.zip |
bnxt_en: Do not initialize PTP on older P3/P4 chips
The driver does not support PTP on these older chips and it is assuming
that firmware on these older chips will not return the
PORT_MAC_PTP_QCFG_RESP_FLAGS_HWRM_ACCESS flag in __bnxt_hwrm_ptp_qcfg(),
causing the function to abort quietly.
But newer firmware now sets this flag and so __bnxt_hwrm_ptp_qcfg()
will proceed further. Eventually it will fail in bnxt_ptp_init() ->
bnxt_map_ptp_regs() because there is no code to support the older chips.
The driver will then complain:
"PTP initialization failed.\n"
Fix it so that we abort quietly earlier without going through the
unnecessary steps and alarming the user with the warning log.
Fixes: ae5c42f0b92c ("bnxt_en: Get PTP hardware capability from firmware")
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'lib/kfifo.c')
0 files changed, 0 insertions, 0 deletions