diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2024-04-20 06:43:17 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2024-04-20 06:43:17 +0300 |
| commit | a9176f7c66f0f438dfd9a1a6c86ca7b73280a494 (patch) | |
| tree | 93edc3d2dafbe3efe1399c41839b4da12107728a /drivers/net/usb/qmi_wwan.c | |
| parent | 9f898fc2c31fbf0ac5ecd289f528a716464cb005 (diff) | |
| parent | 773501d01e6bc3f2557882a25679392d982d5f3e (diff) | |
| download | linux-a9176f7c66f0f438dfd9a1a6c86ca7b73280a494.tar.xz | |
Merge branch 'mlxsw-fixes'
Petr Machata says:
====================
mlxsw: Fixes
This patchset fixes the following issues:
- During driver de-initialization the driver unregisters the EMAD
response trap by setting its action to DISCARD. However the manual
only permits TRAP and FORWARD, and future firmware versions will
enforce this.
In patch #1, suppress the error message by aligning the driver to the
manual and use a FORWARD (NOP) action when unregistering the trap.
- The driver queries the Management Capabilities Mask (MCAM) register
during initialization to understand if certain features are supported.
However, not all firmware versions support this register, leading to
the driver failing to load.
Patches #2 and #3 fix this issue by treating an error in the register
query as an indication that the feature is not supported.
v2:
- Patch #2:
- Make mlxsw_env_max_module_eeprom_len_query() void
====================
Link: https://lore.kernel.org/r/cover.1713446092.git.petrm@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/usb/qmi_wwan.c')
0 files changed, 0 insertions, 0 deletions