From: kernel test robot <lkp@intel.com>
To: Shengyu Qu <wiagn233@outlook.com>,
nbd@nbd.name, lorenzo@kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, sean.wang@mediatek.com,
kvalo@kernel.org, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com,
chui-hao.chiu@mediatek.com, emmanuel.grumbach@intel.com,
StanleyYP.Wang@mediatek.com, meichia.chiu@mediatek.com,
johannes.berg@intel.com, quic_adisi@quicinc.com,
allen.ye@mediatek.com, bo.jiao@mediatek.com,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: oe-kbuild-all@lists.linux.dev, Shengyu Qu <wiagn233@outlook.com>,
Sujuan Chen <sujuan.chen@mediatek.com>
Subject: Re: [PATCH v5] wifi: mt76: mt7915: add wds support when wed is enabled
Date: Sun, 4 Aug 2024 10:43:33 +0800 [thread overview]
Message-ID: <202408041039.BqVRJOqp-lkp@intel.com> (raw)
In-Reply-To: <TY3P286MB2611CB2F4F5FA27D782AA80A98BC2@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
Hi Shengyu,
kernel test robot noticed the following build errors:
[auto build test ERROR on wireless-next/main]
[also build test ERROR on wireless/main linus/master v6.11-rc1 next-20240802]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Shengyu-Qu/wifi-mt76-mt7915-add-wds-support-when-wed-is-enabled/20240803-231632
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link: https://lore.kernel.org/r/TY3P286MB2611CB2F4F5FA27D782AA80A98BC2%40TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM
patch subject: [PATCH v5] wifi: mt76: mt7915: add wds support when wed is enabled
config: x86_64-buildonly-randconfig-003-20240804 (https://download.01.org/0day-ci/archive/20240804/202408041039.BqVRJOqp-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240804/202408041039.BqVRJOqp-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202408041039.BqVRJOqp-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/wireless/mediatek/mt76/mt7915/mcu.c: In function 'mt7915_mcu_init_firmware':
>> drivers/net/wireless/mediatek/mt76/mt7915/mcu.c:2363:67: error: 'struct mtk_wed_device' has no member named 'rev_id'
2363 | dev->mt76.mmio.wed.rev_id, 0);
| ^
vim +2363 drivers/net/wireless/mediatek/mt76/mt7915/mcu.c
2322
2323 int mt7915_mcu_init_firmware(struct mt7915_dev *dev)
2324 {
2325 int ret;
2326
2327 /* force firmware operation mode into normal state,
2328 * which should be set before firmware download stage.
2329 */
2330 mt76_wr(dev, MT_SWDEF_MODE, MT_SWDEF_NORMAL_MODE);
2331
2332 ret = mt7915_driver_own(dev, 0);
2333 if (ret)
2334 return ret;
2335 /* set driver own for band1 when two hif exist */
2336 if (dev->hif2) {
2337 ret = mt7915_driver_own(dev, 1);
2338 if (ret)
2339 return ret;
2340 }
2341
2342 ret = mt7915_load_firmware(dev);
2343 if (ret)
2344 return ret;
2345
2346 set_bit(MT76_STATE_MCU_RUNNING, &dev->mphy.state);
2347 ret = mt7915_mcu_fw_log_2_host(dev, MCU_FW_LOG_WM, 0);
2348 if (ret)
2349 return ret;
2350
2351 ret = mt7915_mcu_fw_log_2_host(dev, MCU_FW_LOG_WA, 0);
2352 if (ret)
2353 return ret;
2354
2355 if (mtk_wed_device_active(&dev->mt76.mmio.wed)) {
2356 if (is_mt7915(&dev->mt76) ||
2357 !mtk_wed_get_rx_capa(&dev->mt76.mmio.wed))
2358 ret = mt7915_mcu_wa_cmd(dev, MCU_WA_PARAM_CMD(CAPABILITY),
2359 0, 0, 0);
2360 else
2361 ret = mt7915_mcu_wa_cmd(dev, MCU_WA_PARAM_CMD(SET),
2362 MCU_WA_PARAM_WED_VERSION,
> 2363 dev->mt76.mmio.wed.rev_id, 0);
2364 if (ret)
2365 return ret;
2366 }
2367
2368 ret = mt7915_mcu_set_mwds(dev, 1);
2369 if (ret)
2370 return ret;
2371
2372 ret = mt7915_mcu_set_muru_ctrl(dev, MURU_SET_PLATFORM_TYPE,
2373 MURU_PLATFORM_TYPE_PERF_LEVEL_2);
2374 if (ret)
2375 return ret;
2376
2377 ret = mt7915_mcu_init_rx_airtime(dev);
2378 if (ret)
2379 return ret;
2380
2381 return mt7915_mcu_set_red(dev, mtk_wed_device_active(&dev->mt76.mmio.wed));
2382 }
2383
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-04 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 7:58 [PATCH v5] wifi: mt76: mt7915: add wds support when wed is enabled Shengyu Qu
2024-08-04 2:43 ` kernel test robot [this message]
2024-08-04 9:28 ` Shengyu Qu
2024-08-04 9:56 ` Kalle Valo
2024-08-04 12:17 ` Shengyu Qu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202408041039.BqVRJOqp-lkp@intel.com \
--to=lkp@intel.com \
--cc=StanleyYP.Wang@mediatek.com \
--cc=allen.ye@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bo.jiao@mediatek.com \
--cc=chui-hao.chiu@mediatek.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=meichia.chiu@mediatek.com \
--cc=nbd@nbd.name \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_adisi@quicinc.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=sujuan.chen@mediatek.com \
--cc=wiagn233@outlook.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).