From: Jérôme Pouiller <jerome.pouil...@silabs.com>

Currently, the driver explicitly exclude support for chip with version
number it does not know. However, it unlikely that any futur hardware
change would break the driver. Therefore, we prefer to invert the test
and only exclude the versions we know the driver does not support.

Signed-off-by: Jérôme Pouiller <jerome.pouil...@silabs.com>
---
 drivers/staging/wfx/fwio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/wfx/fwio.c b/drivers/staging/wfx/fwio.c
index 9d61082c1e6c..e2f914296677 100644
--- a/drivers/staging/wfx/fwio.c
+++ b/drivers/staging/wfx/fwio.c
@@ -360,7 +360,7 @@ int wfx_init_device(struct wfx_dev *wdev)
        dev_dbg(wdev->dev, "initial config register value: %08x\n", reg);
 
        hw_revision = FIELD_GET(CFG_DEVICE_ID_MAJOR, reg);
-       if (hw_revision == 0 || hw_revision > 2) {
+       if (hw_revision == 0) {
                dev_err(wdev->dev, "bad hardware revision number: %d\n",
                        hw_revision);
                return -ENODEV;
-- 
2.26.1

_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to