package/kernel/ath10k-ct/patches/130-ath10k-activate-user-space-firmware-loading-again.patch

   1 From c0cc00f250e19c717fc9cdbdb7f55aaa569c7498 Mon Sep 17 00:00:00 2001
   2 From: Hauke Mehrtens <hauke@hauke-m.de>
   3 Date: Thu, 24 Aug 2017 23:06:41 +0200
   4 Subject: [PATCH] ath10k: activate user space firmware loading again
   5
   6 In commit 9f5bcfe93315 ("ath10k: silence firmware file probing
   7 warnings") the firmware loading was changed from request_firmware() to
   8 request_firmware_direct() to silence some warnings in case it fails.
   9 request_firmware_direct() directly searches in the file system only and
  10 does not send a hotplug event to user space in case it could not find
  11 the firmware directly.
  12 In LEDE we use a user space script to extract the calibration data from
  13 the flash memory which gets triggered by the hotplug event. This way the
  14 firmware gets extracted from some vendor specific partition when the
  15 driver requests this firmware. This mechanism does not work any more
  16 after this change.
  17
  18 Fixes: 9f5bcfe93315 ("ath10k: silence firmware file probing warnings")
  19 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
  20 Cc: Michal Kazior <michal.kazior@tieto.com>
  21 Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
  22 ---
  23  ath10k-4.13/core.c | 2 +-
  24  1 file changed, 1 insertion(+), 1 deletion(-)
  25
  26 --- a/ath10k-4.13/core.c
  27 +++ b/ath10k-4.13/core.c
  28 @@ -556,7 +556,7 @@ static const struct firmware *ath10k_fet
  29                 dir = ".";
  30
  31         snprintf(filename, sizeof(filename), "%s/%s", dir, file);
  32 -       ret = request_firmware_direct(&fw, filename, ar->dev);
  33 +       ret = request_firmware(&fw, filename, ar->dev);
  34         ath10k_dbg(ar, ATH10K_DBG_BOOT, "boot fw request '%s': %d\n",
  35                    filename, ret);
  36