| <?xml version="1.0" encoding="utf-8"?><manifest revision="124432165cd6d5608f5ca0ea559638be152a0f8d"> |
| <notice>Your sources have been sync'd successfully.</notice> |
| <remote alias="cros" fetch="https://chromium.googlesource.com/" name="chromium"/> |
| <remote fetch="https://chromium.googlesource.com" name="cros" review="https://chromium-review.googlesource.com"/> |
| <default remote="cros" revision="refs/heads/master" sync-j="8"/> |
| <project name="chromium/deps/libmtp" path="chromium/src/third_party/libmtp" revision="0680a2d0c4cec58f8163fe115de80cff8852fd8b" upstream="refs/heads/master"/> |
| <project name="chromium/src/third_party/hwcplus" revision="e66a31e54e12906e86dc59f95b458889f025c505" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromium/tools/depot_tools" revision="3add4b62b8fc420ba5a6cc0c8bddcf152c00a970"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/chromite" path="chromite" revision="b84aa9a3b60d269db57845cddb1cd4d6c142d511" upstream="refs/heads/master"> |
| <copyfile dest="AUTHORS" src="AUTHORS"/> |
| <copyfile dest="LICENSE" src="LICENSE"/> |
| </project> |
| <project name="chromiumos/manifest" path="manifest" revision="c708999bdbc3fd6f26eac3cf790156039a7a5fb6" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/board-overlays" path="src/overlays" revision="86cc85b7bd54527c0d71342c3da454067ecaef4b" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="6314f79a834f121b7edf7e068aa8069c286f0ef3" sync-c="true" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/eclass-overlay" path="src/third_party/eclass-overlay" revision="3a2c975087dbe6aa72ffabf55133d402f85c09e2" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/portage-stable" path="src/third_party/portage-stable" revision="b28340845fc5cbb02c79b6ef075903ffc178fe6a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/assets" path="src/platform/assets" revision="135c7bd2056cd5773c2074d257c3895dc7a3bfe1" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/audiotest" path="src/platform/audiotest" revision="82278ee760fc1eb19f0719cdef626dca157cd533" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/battery_updater" path="src/platform/battery_updater" revision="32463c6de8e8c98d4b1711937bc7678afc121a85" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bmpblk" path="src/platform/bmpblk" revision="580140574963688c0adb1ea5710481dbca1b775a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bootcache" path="src/platform/bootcache" revision="ebe3a0995e90026433ffc62b7aeed6cad1f28694" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/btsocket" path="src/platform/btsocket" revision="1b65449a647c99556511df30b8ab660b98acce7f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chameleon" path="src/platform/chameleon" revision="d92645c7e5610a21b83954ba0f24465be79bb9fd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chromiumos-assets" path="src/platform/chromiumos-assets" revision="05ce8d3c59a2d8e765b3beb2e1a69e7fcf59e5ba" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/crostestutils" path="src/platform/crostestutils" revision="8544657d8bcb5741ef6864ff3de60c94619119aa" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/crosutils" path="src/scripts" revision="b94781849e3e0f690f0543838f9645fd20aa7303" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="606a3272893c07a2644fe8cb5a2bf4c0e4cf8123" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="c1a8222ef1f6b10ae69d5fb0208d49c83ba627eb" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/dm-verity" path="src/platform/verity" revision="c4df284b32558f631862f79c75fc03af4f5ca68a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/drm-tests" path="src/platform/drm-tests" revision="842bd998c3bc34cf044c70584305a4aa373896fe" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/ec" path="src/platform/ec" revision="dbc03d1bf9f7831f4e0aae12c3ff4297a54b2c45" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory" path="src/platform/factory" revision="d9a1af5485b9686b1708d9e5ad2e96cc64ce1a7f" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory_installer" path="src/platform/factory_installer" revision="37ff411373c39c236a56fea1ef3fb2a33b2ec206" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/firmware" path="src/platform/firmware" revision="70f79da7a3bd18c942fa65a6b21fea589bbb5516" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/frecon" path="src/platform/frecon" revision="5f6742f036cc0783209fa564cca16b037acb25c5" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/gestures" path="src/platform/gestures" revision="88ce928bf7e9f1364a140efd7d726026a27cbca1" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/glbench/images" path="src/platform2/glbench/images" revision="5fd5ce655833f65d46b1950bec4eedeb4e96959b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/go-seccomp" path="src/platform/go-seccomp" revision="0280326e5bd212fcfbe3696e113730045debae74" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/google-breakpad" path="src/third_party/breakpad" revision="139693446b857a6b11e5255d5db23c50061c4226" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/initramfs" path="src/platform/initramfs" revision="1a710721263b8b93ab49af6a6f749a778483f3df" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/inputcontrol" path="src/platform/inputcontrol" revision="ae0b15dc322bab9bf6d7c4fcd5f77d488766a275" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/jabra_vold" path="src/platform/jabra_vold" revision="5ee665e7c68856d3b6ce8bb0f610d43503e603af" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/libevdev" path="src/platform/libevdev" revision="61f882f395b9f39478d7164209e7134cccdcb72b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/memento_softwareupdate" path="src/platform/memento_softwareupdate" revision="202f42a36d8b9d8b2bf4ba870d15599c9462d1ce" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/microbenchmark" path="src/platform/microbenchmark" revision="d5ea30febe406c5b486325dfae926564f3a46efd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/minigbm" path="src/platform/minigbm" revision="e04c9b50d4f50ed661f06db883e77c8b56acf386" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/monitor_reconfig" path="src/platform/monitor_reconfig" revision="f022d19d84f232290b596beeb26347f62442e7eb" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mosys" path="src/platform/mosys" revision="0fa54157eb932c0626eb15fe8fd34fa82ed3cfce" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtpd" path="src/platform/mtpd" revision="d5b6d854f8bfd775673341e98cbbd476c8fb42e3" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtplot" path="src/platform/mtplot" revision="5e4f631e633384751f582bd9db5f4d6eb2112494" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mttools" path="src/platform/mttools" revision="906f3a0a929968a8725e6a2dae7fe1b5f39f02c4" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/punybench" path="src/platform/punybench" revision="5a230ee17756dc43ff732932dcb52899c06a4d09" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/system_api" path="src/platform/system_api" revision="7b49ad4f2528207d4cdc8f9b999ee0aa3350753a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_firmware_test" path="src/platform/touch_firmware_test" revision="a9400e80d2577cead7300e926f5ca0715910e9ae" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_noise_filter" path="src/platform/touch_noise_filter" revision="6b0aba12a385f4d3a7a47641a3a919018032f6f8" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_updater" path="src/platform/touch_updater" revision="15b02fd7a45b0e49420d1dc0682c5ef7529da5b9" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchbot" path="src/platform/touchbot" revision="658a4244256e4dec1ad5e12cb2fc8c77c188beaf" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchpad-tests" path="src/platform/touchpad-tests" revision="c2217b861b79ce92b053f8d9fe9da6e0a1cd30dc" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tpm" path="src/third_party/tpm" revision="0cba6cadd1bea1ce3717779201d594c4c9131dc2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tpm_lite" path="src/platform/tpm_lite" revision="066c7f963b3ef733716251b666e0af0afd03b4fe" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/trunks" path="src/platform/trunks" revision="92dbe8c9e7fcf8acf67805fd5e25e85aa371f673" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/uboot-env" path="src/platform/uboot-env" revision="108ebbfac4d13d11e1940216434c368384ee0c0b" upstream="refs/heads/master"/> |
| <project groups="buildtools" name="chromiumos/platform/vboot" path="src/platform/vboot" revision="2d30a2f5b1c81eb61de4bf82180a910d45f22e81" upstream="refs/heads/master"/> |
| <project groups="buildtools" name="chromiumos/platform/vboot_reference" path="src/platform/vboot_reference" revision="65f61f90ccae5f0b5f37ea3bdf86735bc58709a0" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/vpd" path="src/platform/vpd" revision="b2bc97f7c89b0ca5f90aebfb57bc072922b95472" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/webplot" path="src/platform/webplot" revision="bbd5ea22ef9f8e109e363b26958d9a2fc8921f0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/wireless_automation" path="src/platform/wireless_automation" revision="d7177dbd464f2952e10309bf1eef56bb31a7f8ad" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/workarounds" path="src/platform/workarounds" revision="76475bb60c7fa2c2522c27e2c63c9dbbe5de73d7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xf86-input-cmt" path="src/platform/xf86-input-cmt" revision="3f2ffc921952e57a4343463b0679d90b80b51fc7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xorg-conf" path="src/platform/xorg-conf" revision="4cfa67817a9e71385431a20fa721070967ade5a2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform2" path="src/platform2" revision="12e79d86a53a5b351a45335fb24fff0f802ebb9c" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/repohooks" path="src/repohooks" revision="7a610e823d287f3a1f796100b2a3d11da83de89e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/adhd" path="src/third_party/adhd" revision="63499640f9f6ca22d86740d3c6d300403eb88920" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/android_mtdutils" path="src/third_party/android_mtdutils" revision="9bcfc3ee238f16925e9aaa4573129784ebb397e7" upstream="chromeos"/> |
| <project name="chromiumos/third_party/arm-trusted-firmware" path="src/third_party/arm-trusted-firmware" revision="195d29f399759813cd42ea2b8d3133ba426e2ba2"> |
| <annotation name="branch-mode" value="create"/> |
| </project> |
| <project name="chromiumos/third_party/atheros" path="src/third_party/atheros" revision="52a5bdaa8930c14ee42518354de3e5ec09911c6b" upstream="refs/heads/master"/> |
| <project groups="buildtools" name="chromiumos/third_party/autotest" path="src/third_party/autotest/files" revision="70c30198f336186e460dd6fdd3ed214c7a3d31ac" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bluez" path="src/third_party/bluez" revision="dac51d02485dd5d9c0634887397340b41c37860c" upstream="refs/heads/chromeos-5.37"/> |
| <project name="chromiumos/third_party/bootstub" path="src/third_party/bootstub" revision="5ac54e8d3d305c2c6c7297e8e54d3cf7e4629b29" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/broadcom" path="src/third_party/broadcom" revision="4070e7161f2f1a1a22027a744eb868500688f0b6" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cbootimage" path="src/third_party/cbootimage" revision="b7d5b2d6a6dd05874d86ee900ff441d261f9034c" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/chrontel" path="src/third_party/chrontel" revision="7bcd0328d0eeef6a0539bd0ba80cd9a545e6cf4a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/coreboot" path="src/third_party/coreboot" revision="1d13e967addb5cd31e6196e32541cda97ae00257" upstream="refs/heads/chromeos-2016.02"/> |
| <project name="chromiumos/third_party/coreboot/blobs" path="src/third_party/coreboot/3rdparty/blobs" revision="9ba07035ed0acb28902cce826ea833cf531d57c1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cypress-tools" path="src/third_party/cypress-tools" revision="043fba1c35f89cce95f804bf6d4f01cfc23a6c21" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/daisydog" path="src/third_party/daisydog" revision="3182aa85c087446e4358370549adc45db21ec124" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/dbus-cplusplus" path="src/third_party/dbus-c++" revision="f140c0aa430e1db1c0f31d23d3eb2397d47f209e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/dbus-spy" path="src/third_party/dbus-spy" revision="0e04421c73b24536de7fcc1886da469d8b7a2a41" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/third_party/dpkt" path="chromite/third_party/dpkt" revision="f5259728b1294412bee945df9708efba09ea9160"> |
| <annotation name="branch-mode" value="pin"/> |
| </project> |
| <project name="chromiumos/third_party/edk2" path="src/third_party/edk2" revision="0aa39d284043be61b5f1222afdffd39a5abaf3aa" upstream="refs/heads/chromeos-2014.04"/> |
| <project name="chromiumos/third_party/em100" path="src/third_party/em100" revision="6e60dbae5bf62cd0ffffb9fc5ca9ba93e831ee88" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/flashmap" path="src/third_party/flashmap" revision="aaaf66654dba797f152066df4d1dc4144b492c66" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/flashrom" path="src/third_party/flashrom" revision="4af3f82cda5dd10c2648468a1a6627e2084e7c64" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gcc" path="src/third_party/gcc" revision="2d511e935a49006ef2e3ce505f0639c49d13f501" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/third_party/gdata" path="chromite/third_party/gdata" revision="fe7e5c90a9827feb66ed446b2d297a1618b25272" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gdmwimax" path="src/third_party/gdmwimax" revision="e8236b4b2d66b1972e4f84955a238134acd7f6a1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gobi3k-sdk" path="src/third_party/gobi3k-sdk" revision="69702c400e274984a24d08fcaefe3952d5dcb36e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/grub2" path="src/third_party/grub2" revision="df6034c59cb2d847f9e780cf2def30c5c9b8305f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hdctools" path="src/third_party/hdctools" revision="e571a0dfc03d271a7b157d5b82b6014f94827b83" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant" revision="e595cbd52dff1e84b5e4854386872e7490ccc411" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hwcplus-drm" path="src/third_party/hwcplus-drm" revision="7376a8da1c961115a61d7a3cb23bb13e4153583d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ibus-chewing" path="src/third_party/ibus-chewing/files" revision="7a9514a0844eb5eb90ab96f62484a6af9e4a0d6d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ibus-xkb-layouts" path="src/third_party/ibus-xkb-layouts/files" revision="6af015110aa92dc2eed88a9f704634c3eff53b14" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.8" revision="ab96a12cf5d5ea499b3c67ac80421020bee60652" upstream="refs/heads/chromeos-3.8"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.10" revision="1378d100fcf5f679a343dfbd10239d095372d481" upstream="refs/heads/chromeos-3.10"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.14" revision="8adc652b658f40a3fc66186de4ddab91cc29b851" upstream="refs/heads/chromeos-3.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="ee39fa3656760223e32496587901cccb02acadbf" upstream="refs/heads/chromeos-3.18"/> |
| <project name="chromiumos/third_party/kernel-next" path="src/third_party/kernel/v4.4-experimental" revision="72e321277a9ceb06c855b9326f69ab7c4eef18f8" upstream="refs/heads/chromeos-4.4"/> |
| <project name="chromiumos/third_party/khronos" path="src/third_party/khronos" revision="dceee6ef99b968fd11d9c6058448202db835bc0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libc-bench" path="src/third_party/libc-bench" revision="76793dd4b09191a78a78180012718e72d792717f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libdrm" path="src/third_party/libdrm" revision="2c25afb719347a151657f8637ad62a5df42e247e" upstream="refs/heads/chromeos-2.4.66"/> |
| <project name="chromiumos/third_party/libmbim" path="src/third_party/libmbim" revision="c4e2949edeed01ca3b810729a7af0d265c49629b" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libqmi" path="src/third_party/libqmi" revision="a436c551cf226af66cdb3dd74ee3971d0b1dae04" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libresample" path="src/third_party/libresample" revision="cc9f20f439396b7d45e94b8301edd95d33f26a46" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libscrypt" path="src/third_party/libscrypt" revision="b45c53f9418a6eff2c8ed98703a55f96029304b1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libsigrok" path="src/third_party/libsigrok" revision="199fe31115c76231746f5953271795d58679561c" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrok-cli" path="src/third_party/sigrok-cli" revision="c9edfa218e5a5972531b6f4a3ece8d33a44ae1b5" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrokdecode" path="src/third_party/libsigrokdecode" revision="3279c2825684c7009775b731d0a9e37815778282" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libv4lplugins" path="src/third_party/libv4lplugins" revision="07f7a81118f74a8a7bc4ef5b81ee651aa12b8adb" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/linux-firmware" path="src/third_party/linux-firmware" revision="53b86eee34a9a2ec2812d81d344eb7e252aff5fc" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ltp" path="src/third_party/ltp" revision="4290bd545748cae9e3abad8113dcf4f6dc82e840" upstream="refs/heads/chromeos-20150119"/> |
| <project name="chromiumos/third_party/marvell" path="src/third_party/marvell" revision="f3a48ad1a911ce0bc8110279e314d718e2fa54a8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/memtest" path="src/third_party/memtest" revision="3d4be6e3bfd819856e38a82e35c206fec4551851" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa" revision="3dc2630e457155a4e8c8613911fe178bc4adf743" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa-img" revision="129178893b2260df22db96327c5ca9c2ce7db046" upstream="refs/heads/mesa-img"/> |
| <project name="chromiumos/third_party/minifakedns" path="src/third_party/miniFakeDns" revision="6184bea119dea53da539727fe8c2a116f98cef24" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mmc-utils" path="src/third_party/mmc-utils" revision="c2faa3df83d679cb01b553d567b16ecc2299f134" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/modemmanager-next" path="src/third_party/modemmanager-next" revision="b263d6a8f1f16d433e7b2279d00a5d8d6f6ac797" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/opencryptoki" path="src/third_party/opencryptoki" revision="b67690aeeb4174b2253db18a9c1b19eeb219a4ef" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ply-image" path="src/third_party/ply-image" revision="6cf4e4cd968bb72ade54e423e2b97eb3a80c6de9" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/third_party/pyelftools" path="chromite/third_party/pyelftools" revision="19b3e610c86fcadb837d252c794cb5e8008826ae" upstream="refs/heads/master-0.22"/> |
| <project groups="project_sdk" name="chromiumos/third_party/rootdev" path="src/third_party/rootdev" revision="5d7d7ff513315abd103d0c95e92ae646c1a7688c" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/seabios" path="src/third_party/seabios" revision="3004147dd3707e600772ec6c5d37beac7f4b8eb4" upstream="refs/heads/chromeos-2014.11.03"/> |
| <project name="chromiumos/third_party/sysbios" path="src/third_party/sysbios" revision="33e1db34b8162de72a5e9bbbc44e6bce38978396" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegra-power-query" path="src/third_party/tegra-power-query" revision="66f1f0d949f4ca4836c1a65b622629205240e37a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegrastats" path="src/third_party/tegrastats" revision="1be161a89525d840e1f6d1f21b3f45645a7dedb3" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tlsdate" path="src/third_party/tlsdate" revision="ab36a75379f1cfaa7a803cb6f8b33ad31e49fcbf" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm-emulator" path="src/third_party/tpm-emulator" revision="310a21ef24ace14b4d6e8095172445494f54ff25" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm2" path="src/third_party/tpm2" revision="24f8b1918812346e57274ed6a377954fe58b7bc0" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/third_party/trousers" path="src/third_party/trousers" revision="416d30f74a9c1dc08b95b907d8b7e81edf6c9db0" upstream="refs/heads/master-0.3.13"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/files" revision="020ddef0473ed6bafa1a30d935bcb382bcfd6fb4" upstream="refs/heads/chromeos-v2013.06"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/next" revision="b30f38206f17aa73cda0a2fdaf4dc705527315ba" upstream="refs/heads/chromeos-v2015.07-rc1"/> |
| <project name="chromiumos/third_party/xf86-video-armsoc" path="src/third_party/xf86-video-armsoc" revision="30370e9dbf7ba0e457ee7de297d2ad6c269a00be" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="external/swarming.client" path="chromite/third_party/swarming.client" revision="715861067a7cc8d20d2d629b6d76d796c004feb4"/> |
| <project name="linux-syscall-support" path="src/third_party/breakpad/src/third_party/lss" revision="9292030109847793f7a6689adac1ddafb412fe14"/> |
| <repo-hooks enabled-list="pre-upload" in-project="chromiumos/repohooks"/> |
| <pending_commit branch="chromeos-3.18" change_id="I4e5ad46f8acfcec17551cb3de482162976eb876b" commit="6a5bb47e3c992dd22a0afd827253645dd9dc2ffe" commit_message="UPSTREAM: ath10k: suppress 'failed to process fft' warning messages When using DFS channels on Ath10k, kernel log has repeated warning message 'failed to process fft: -22' typically under medium/heavy traffic. This patch switches the warnings to driver debug (WMI events) mode only thus reducing log file noise. DFS and spectral scan share underlying HW mechanisms and enabling one (DFS) enables the other (spectral scan) as far as event reporting from firmware to driver is concerned. Spectral scan events take no part in processing of DFS radar pulses which are delivered as distinct events, so the fft (spectral event) warning is harmless and DFS interference detection/protection still occurs. Symptoms seen & fix tested in both debug & non-debug modes on TP-Link Archer C7 v2 platform. (cherry picked from commit 3413e97dbbae8561e01ac28ccb0d4bbe7ce933f4) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I4e5ad46f8acfcec17551cb3de482162976eb876b Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333457 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333457" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/57/333457/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I3a199dffa5cdca9ee8aedff5015afb91a348cb01" commit="78d7e7ea5e34edea424a75929b015185f032b7f5" commit_message="UPSTREAM: ath10k: Improve performance by reducing tx_lock contention During tx completion, tx_lock is held for longer than required, preventing efficient refill of htt->pending_tx. Refactor the code so that only MSDU related operations are protected by the lock. Improves downstream performance on a dual-core ARM Freescale LS1024A (f.k.a. Mindspeed Comcerto 2000) AP with a 3x3 client from 495 to 580 Mbps. Other CPU bound multicore systems may also benefit. (cherry picked from commit 005fb161310f72070ad5f4352d6b81ffaca8a11e) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I3a199dffa5cdca9ee8aedff5015afb91a348cb01 Signed-off-by: Denton Gentry <dgentry@google.com> Signed-off-by: Avery Pennarun <apenwarr@google.com> [mfaltesek@google.com: removed conflicting code for tracking msdu_ids.] Signed-off-by: Marty Faltesek <mfaltesek@google.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333458 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333458" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/58/333458/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Iec82208c8946cf118e1548029e2c142cd88ce952" commit="2d38939e7b6f15aa96f83a9f0f07a5563e9b8487" commit_message="UPSTREAM: ath10k: enable raw encap mode and software crypto engine This patch enables raw Rx/Tx encap mode to support software based crypto engine. This patch introduces a new module param 'cryptmode'. cryptmode: 0: Use hardware crypto engine globally with native Wi-Fi mode TX/RX encapsulation to the firmware. This is the default mode. 1: Use sofware crypto engine globally with raw mode TX/RX encapsulation to the firmware. Known limitation: A-MSDU must be disabled for RAW Tx encap mode to perform well when heavy traffic is applied. Testing: (by Michal Kazior <michal.kazior@tieto.com>) a) Performance Testing cryptmode=1 ap=qca988x sta=killer1525 killer1525 -> qca988x 194.496 mbps [tcp1 ip4] killer1525 -> qca988x 238.309 mbps [tcp5 ip4] killer1525 -> qca988x 266.958 mbps [udp1 ip4] killer1525 -> qca988x 477.468 mbps [udp5 ip4] qca988x -> killer1525 301.378 mbps [tcp1 ip4] qca988x -> killer1525 297.949 mbps [tcp5 ip4] qca988x -> killer1525 331.351 mbps [udp1 ip4] qca988x -> killer1525 371.528 mbps [udp5 ip4] ap=killer1525 sta=qca988x qca988x -> killer1525 331.447 mbps [tcp1 ip4] qca988x -> killer1525 328.783 mbps [tcp5 ip4] qca988x -> killer1525 375.309 mbps [udp1 ip4] qca988x -> killer1525 403.379 mbps [udp5 ip4] killer1525 -> qca988x 203.689 mbps [tcp1 ip4] killer1525 -> qca988x 222.339 mbps [tcp5 ip4] killer1525 -> qca988x 264.199 mbps [udp1 ip4] killer1525 -> qca988x 479.371 mbps [udp5 ip4] Note: - only open network tested for RAW vs nwifi performance comparison - killer1525 (qca6174 hw2.2) is 2x2 device (hence max 866mbps) - used iperf - OTA, devices a few cm apart from each other, no shielding - tcpX/udpX, X - means number of threads used Overview: - relative Tx performance drop is seen but is within reasonable and expected threshold (A-MSDU must be disabled with RAW Tx) b) Connectivity Testing cryptmode=1 ap=iwl6205 sta1=qca988x crypto=open topology-1ap1sta OK ap=iwl6205 sta1=qca988x crypto=wep1 topology-1ap1sta OK ap=iwl6205 sta1=qca988x crypto=wpa topology-1ap1sta OK ap=iwl6205 sta1=qca988x crypto=wpa-ccmp topology-1ap1sta OK ap=qca988x sta1=iwl6205 crypto=open topology-1ap1sta OK ap=qca988x sta1=iwl6205 crypto=wep1 topology-1ap1sta OK ap=qca988x sta1=iwl6205 crypto=wpa topology-1ap1sta OK ap=qca988x sta1=iwl6205 crypto=wpa-ccmp topology-1ap1sta OK ap=iwl6205 sta1=qca988x crypto=open topology-1ap1sta2br OK ap=iwl6205 sta1=qca988x crypto=wep1 topology-1ap1sta2br OK ap=iwl6205 sta1=qca988x crypto=wpa topology-1ap1sta2br OK ap=iwl6205 sta1=qca988x crypto=wpa-ccmp topology-1ap1sta2br OK ap=qca988x sta1=iwl6205 crypto=open topology-1ap1sta2br OK ap=qca988x sta1=iwl6205 crypto=wep1 topology-1ap1sta2br OK ap=qca988x sta1=iwl6205 crypto=wpa topology-1ap1sta2br OK ap=qca988x sta1=iwl6205 crypto=wpa-ccmp topology-1ap1sta2br OK ap=iwl6205 sta1=qca988x crypto=open topology-1ap1sta2br1vlan OK ap=iwl6205 sta1=qca988x crypto=wep1 topology-1ap1sta2br1vlan OK ap=iwl6205 sta1=qca988x crypto=wpa topology-1ap1sta2br1vlan OK ap=iwl6205 sta1=qca988x crypto=wpa-ccmp topology-1ap1sta2br1vlan OK ap=qca988x sta1=iwl6205 crypto=open topology-1ap1sta2br1vlan OK ap=qca988x sta1=iwl6205 crypto=wep1 topology-1ap1sta2br1vlan OK ap=qca988x sta1=iwl6205 crypto=wpa topology-1ap1sta2br1vlan OK ap=qca988x sta1=iwl6205 crypto=wpa-ccmp topology-1ap1sta2br1vlan OK Note: - each test takes all possible endpoint pairs and pings - each pair-ping flushes arp table - ip6 is used c) Testbed Topology: 1ap1sta: [ap] ---- [sta] endpoints: ap, sta 1ap1sta2br: [veth0] [ap] ---- [sta] [veth2] | | | | [veth1] | \ [veth3] \ / \ / [br0] [br1] endpoints: veth0, veth2, br0, br1 note: STA works in 4addr mode, AP has wds_sta=1 1ap1sta2br1vlan: [veth0] [ap] ---- [sta] [veth2] | | | | [veth1] | \ [veth3] \ / \ / [br0] [br1] | | [vlan0_id2] [vlan1_id2] endpoints: vlan0_id2, vlan1_id2 note: STA works in 4addr mode, AP has wds_sta=1 Credits: Thanks to Michal Kazior <michal.kazior@tieto.com> who helped find the amsdu issue, contributed a workaround (already squashed into this patch), and contributed the throughput and connectivity tests results. (cherry picked from commit ccec9038c7217e537f5ae5e3ac5af8293a21bbfd) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Iec82208c8946cf118e1548029e2c142cd88ce952 Signed-off-by: David Liu <cfliu.tw@gmail.com> Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Tested-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333459 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333459" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/59/333459/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ica77eafb2e1a4a348960b360180f1199f2befeb3" commit="ed7957af763459fe4d970157665b184fe5ea3c29" commit_message="UPSTREAM: ath10k: fix memory alloc failure in qca99x0 during wmi svc rdy event Host memory required for firmware is allocated while handling wmi service ready event. Right now, wmi service ready is handled in tasklet context and it calls dma_alloc_coherent() with atomic flag (GFP_ATOMIC) to allocate memory in host needed for firmware. The problem is, dma_alloc_coherent() with GFP_ATOMIC fails in the platform (at least in AP platform) where it has less atomic pool memory (< 2mb). QCA99X0 requires around 2 MB of host memory for one card, having additional QCA99X0 card in the same platform will require similarly amount of memory. So, it's not guaranteed that all the platform will have enough atomic memory pool. Fix this issue, by handling wmi service ready event in workqueue context and calling dma_alloc_coherent() with GFP_KERNEL. mac80211 work queue will not be ready at the time of handling wmi service ready. So, it can't be used to handle wmi service ready. Also, register work gets scheduled during insmod in existing ath10k_wq and waits for wmi service ready to completed. Both workqueue can't be used for this purpose. New auxiliary workqueue is added to handle wmi service ready. (cherry picked from commit c8ecfc1c33979054fb631d2066745d03ce322b6f) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ica77eafb2e1a4a348960b360180f1199f2befeb3 Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333460 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333460" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/60/333460/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ifc494afdda91d91320a74b52fb6acfc6be99abde" commit="68adba3d72d709eb7b737f998d447363650aba55" commit_message="UPSTREAM: ath10k: increase max client to 512 in qca99x0 When max client was set to 512 in qca99x0, there was host memory alloc failure during wmi service ready event handling. This issue got resolved now, increasing max client limit from 256 to 512. (cherry picked from commit 1201844e6ddc4e13dfc1a7ffbba0cfd180944679) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ifc494afdda91d91320a74b52fb6acfc6be99abde Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333461 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333461" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/61/333461/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I5b848544fac83cddd9acc97f9e6aaacff2d0af7f" commit="af0afd77687f93606c39e1ebbf713866f7fa88dd" commit_message="UPSTREAM: ath10k: add QCA99X0 to supported device list Add vendor/device id of QCA99X0 V2.0 to pci id table and QCA99X0_HW_2_0_CHIP_ID_REV to ath10k_pci_supp_chips[] for QCA99X0 to get detected by the driver. kvalo: now QCA99X0 family of chipsets is supported by ath10k. Tested client, AP and monitor mode with QCA9990. (cherry picked from commit 8a055a8adc875768223be2dfc33de5dc70212756) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I5b848544fac83cddd9acc97f9e6aaacff2d0af7f Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333462 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333462" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/62/333462/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="If459d89649fea524dfc8a2167511a644895fe315" commit="b34c32b19c8ab1b395795907688e7eefc65dc862" commit_message="UPSTREAM: ath10k: initialize msdu ext. descriptor before use Initial QCA99X0 support has a known issue with TCP Tx throughput. All other path such as UDP Tx/Rx and TCP Rx meet their expectation (> 900Mbps), but TCP Tx marked as low as 5Mbps when single pair is used on iperf. The root cause is turned out because TSO flag is not initialized properly so that firmware configures TSO in wrong way. TSO flags in msdu extension descriptor is required to be reset to indicate firmware there is no TSO is enabled, otherwise it could act as TSO is enabled which causes huge throughput drop. In fact, it's enough by resetting TSO flags only to prevent the unexpected behavior, but initializing whole msdu ext. descriptor will help to clear uncertainty of firmware could bring on as it constantly updated. (cherry picked from commit ae7d3821a769a4ac64d4c244b5cd8b134768d452) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: If459d89649fea524dfc8a2167511a644895fe315 Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333463 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333463" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/63/333463/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I3840e79e602b44427fed0f35121e0d455b6a3338" commit="67eb67d7d5ffe626d22d0bc60f0f84e0ccdfdcaf" commit_message="UPSTREAM: ath10k: remove futile fragmentation threshold config Commit 1010ba4c5d1c ("ath10k: unregister and remove frag_threshold callback") didn't remove all instances of (futile) fragmentation threshold configuration. No known firmware supports the parameter so don't even bother setting it. (cherry picked from commit 4dca0e6edd14e0c8afa19c8ad90f711f1563b52e) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I3840e79e602b44427fed0f35121e0d455b6a3338 Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333464 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333464" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/64/333464/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Iaa697a13526c1a8d987b47e399b7a966665e99ce" commit="c410e381bc93f9972c3c3ff5e2bcbd88bbf50651" commit_message="UPSTREAM: ath10k: reject 11b tx fragmentation configuration Even though there's a WMI enum for fragmentation threshold no known firmware actually implements it. Moreover it is not possible to rely frame fragmentation to mac80211 because firmware clears the "more fragments" bit in frame control making it impossible for remote devices to reassemble frames. Hence implement a dummy callback just to say fragmentation isn't supported. This effectively prevents mac80211 from doing frame fragmentation in software. This fixes Tx becoming broken after setting fragmentation threshold. Fixes: 1010ba4c5d1c ("ath10k: unregister and remove frag_threshold callback") (cherry picked from commit 92092fe528e79c9bd25784ca0ef341d5a1d1b642) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Iaa697a13526c1a8d987b47e399b7a966665e99ce Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333465 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333465" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/65/333465/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Iedcaa3fdca850ec683fe062d3494c61d78cc8732" commit="5935db5a227aabfa3f4ccd18b64253e9a6c603bd" commit_message="UPSTREAM: ath10k: Support different txbf configuration schemes qca61x4 uses the vdev param as a sole sufficient configuration for txbf while qca99x0 enables txbf during peer assoc by combining the vdev param value with peer assoc's vht capabilities This patch gets the appropriate txbf configuration scheme before passing the wmi command to enable the same in the firmware. (cherry picked from commit 08e75ea84cb595c52f140049fcf6362679473592) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Iedcaa3fdca850ec683fe062d3494c61d78cc8732 Signed-off-by: Vivek Natarajan <nataraja@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333466 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333466" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/66/333466/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ib35e34121c33beb5a209dcf4104ce5f8bf8579b4" commit="c02428a3328ecd67e1e0c8498153217ef18fbd39" commit_message="UPSTREAM: ath10k: Enable MU MIMO txbf support for QCA99X0 This patch enables MU-MIMO transmit beamforming support for QCA99X0 chipsets. (cherry picked from commit a48e2cc8992a13a58cff04e54e05f959d418554b) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ib35e34121c33beb5a209dcf4104ce5f8bf8579b4 Signed-off-by: Vivek Natarajan <nataraja@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333467 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333467" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/67/333467/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ic78fb99ca2c5053146fccfc013b5613ffc7f61fd" commit="9029a1396e8455b33b6f2b640940b5ffe28a3813" commit_message="UPSTREAM: ath10k: initialize fw_features var If firmware did not have any feature flags set the var would be left with values found on the stack (i.e. garbage) yielding print string like this: (...) features \xffffffa6m:^R\xfffffffb\xffffffc4^E Fixes: b27bc5a40f91 ("ath10k: dump fw features during probing") (cherry picked from commit 84e3df60f0daba5b1e7874101502d0b030afb867) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ic78fb99ca2c5053146fccfc013b5613ffc7f61fd Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333468 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333468" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/68/333468/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I5c2e34f2af3f18cc15a4053e4f44e6108aa6901a" commit="7c201fd2762fb274eec7e5441f64bbc4c798f8a4" commit_message="UPSTREAM: ath10k: fix hw reconfig on wow failure When WoWLAN resume fails with retval 1 mac80211 will attempt to reconfig the device in a similar manner when hw restart is requested. This wasn't handled properly and yielded call trace warnings and the device ended up not working. (cherry picked from commit 6f7429c29b9979d64d067543caec940bbc023340) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I5c2e34f2af3f18cc15a4053e4f44e6108aa6901a Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333469 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333469" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/69/333469/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ia1d83d7cc15d931c89e04b2d8a5d204a231ca8ef" commit="d2201a16e9ce2ec07456ef48a6d967c09250da27" commit_message="UPSTREAM: ath10k: don't remove peer that doesn't exist If peer creation failed during offchannel Tx the driver attempted to delete the peer nonetheless. This caused the ar->num_peers counter to be incorrectly decremented. This subsequently could cause the counter to drop below 0 and also eventually lead to firmware crash because host would think there are less peer entries created in firmware then there really were. (cherry picked from commit adaeed74bc085bc59991cd6e23ee7f720b6c6aab) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ia1d83d7cc15d931c89e04b2d8a5d204a231ca8ef Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333470 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333470" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/70/333470/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I1a7e32ebaec79d547a714d541877ac1b9fb916fd" commit="94addbeeaeb2e4cab3bf6e4a18e00f1e23c34837" commit_message="UPSTREAM: ath10k: fix peer limit enforcement Firmware peer entries are involved in internal firmware vdev structures. This was not accounted for and could lead firmware to crash due to asking it to do more than it could. Fixes: 039a0051ec1a ("ath10k: allocate fw resources for iface combinations") (cherry picked from commit e04cafbc38c70af2aad3810ce24ab0eba8114779) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I1a7e32ebaec79d547a714d541877ac1b9fb916fd Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333471 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333471" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/71/333471/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I97d68782d7362d94d41b28561a156b0ac30c34b1" commit="4f4cbe584532cc9ed965fbd91f4252d8beef5c09" commit_message="UPSTREAM: ath10k: wake up offchannel queue properly Once HTT Tx queue got full offchannel queue was stopped and never woken up again. This broke, e.g. P2P. This could be reproduced after running a lot of traffic enough to saturate 100% of the driver Tx queue and then trying to send offchannel traffic. Fixes: 96d828d45e16 ("ath10k: rework tx queue locking") (cherry picked from commit 3a73d1a6f22bf13044056543ad43b2a304ee0022) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I97d68782d7362d94d41b28561a156b0ac30c34b1 Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333472 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333472" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/72/333472/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I10d13918247ceb56c2c27c780c8c57e7491ce3f4" commit="6615100d3515471d8c11bd871e3baf3dc931c90d" commit_message="UPSTREAM: ath10k: wake up queue upon vif creation Vif's vdev_id is used as queue number. However due to the tx pausing design in ath10k it was possible for a new interface to be created with its tx queue stopped (via ieee80211_stop_queues). This could in turn leave the interface inoperable until ath10k_mac_tx_unlock() was called. This problem only affected multi-vif scenarios when new interfaces were created some time later after other interfaces have been running for some time and had Tx queue full at some point prior. Possible manifestation of the bug was authentication timeout for a client vif. Fixes: 96d828d45e16 ("ath10k: rework tx queue locking") (cherry picked from commit 6d2d51ecfff13f5f6ffc476dccf4d5b2668072eb) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I10d13918247ceb56c2c27c780c8c57e7491ce3f4 Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333473 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333473" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/73/333473/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ib9af0775d67cf4445bc53548c48a25ff90fa5fa6" commit="1356a1a0ee0be26bb7e55bea6cae7c4841c5a871" commit_message="UPSTREAM: ath10k: fix invalid survey reporting for QCA99X0 There are three WMI_CHAN_INFO events reported per channel in QCA99X0 firmware. First one is a notification at the begining of the channel dwell time with cmd_flag as CHAN_INFO_START(cmd_flag = 0), second one is a notification at the end of the dwell time with cmd_flag CHAN_INFO_PRE_COMPLETE (cmd_flag = 2) and the third is the indication with CHAN_INFO_COMPLETE (cmd_flag = 1) which is the last indication for the channel. Since there is a new state before the completion, the handler is to fixed so that the counts are deducted from the ones reported with CHAN_INFO_START rather than the ones reported with CHAN_INFO_PRE_COMPLETE. Without this fix there will be lots of 0 msecs reported as active and busy time. (cherry picked from commit 3d2a2e293e9578f59b182c8e5ad7b54ec4e28318) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ib9af0775d67cf4445bc53548c48a25ff90fa5fa6 Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333474 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333474" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/74/333474/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ia2aa501c633a026a646b74ba23090f72cf1c09c7" commit="23bad0e2e8559a5ac7a6c4c411c1a748906b6d4c" commit_message="UPSTREAM: ath10k: add cycle/rx_clear counters frequency to hw_params The frequency at which cycle/rx_clear counters are running might change from one target type to another. QCA99X0 is running the counters at 150Mhz while QCA9888X and QCA6174 are running at 88Mhz. Add a new entry to hw_params to store the target specific frequency and use it in msecs conversion. This change fixes inconsistent channel active/busy time. (cherry picked from commit 9c8fb548fb242b462657151eb9c5dd6b6def5b62) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ia2aa501c633a026a646b74ba23090f72cf1c09c7 Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333475 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333475" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/75/333475/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I89f19516b9e276b7727fdd716021949e7c66162a" commit="45c30bbafdb68a3d28b231efd88631c5b7b5b4e1" commit_message="UPSTREAM: ath10k: split ap/ibss wep key install process Apparently it's not safe to install both pairwise and groupwise keys on AP vdevs as it can cause traffic to stop working in some multi-vif (WPA+WEP) cases. Fixes: ce90b27128c2 ("ath10k: fix multiple key static wep with ibss") (cherry picked from commit 8674d909fabf49140e266f124af68daa3ac93ab3) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I89f19516b9e276b7727fdd716021949e7c66162a Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333476 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333476" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/76/333476/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I72034595da627fe4dbe48809a7037f8ab2d6de8c" commit="2ffa1ef017cc0f3de75953b59df818bd7b1b8cde" commit_message="UPSTREAM: ath10k: refactor phyerr event handlers Existing phyerr event handlers directly uses phyerr header format (ie, struct wmi_phyerr and struct wmi_phyerr_event) in the code exactly on how firmware packs it. This is the problem in 10.4 fw specific phyerr event handling where it uses different phyerror header format. Before adding 10.4 specific handler, little bit of refactor is done in existing phyerr handlers. Two new abstracted structures (struct wmi_phyerr_ev_hdr_arg and struct wmi_phyerr_ev_arg) are introduced to remove dependency of using firmware specific header format in the code. So that firmware specific phyerror handlers can populate values to abstracted structures and the following code can use abstracted struct for further operation. .pull_phyerr_hdr is added newly to pull common phyerr header info like tsf, buf_len, number of phyerr packed. Existing .pull_phyerr handler is changed and called to parse every sub phyerrs in the event. Validated these refactoring on qca988x hw2.0 using fw 10.2.4 version. (cherry picked from commit 991adf71a6cd993c3e6a1a0d8ea9f88b2fa51b95) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I72034595da627fe4dbe48809a7037f8ab2d6de8c Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333477 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333477" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/77/333477/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="If5e9163eafe75af44baa9bff9e9d45156a72166f" commit="a0be8f33847f8e14434dafdf75648bd3bd95e2a0" commit_message="UPSTREAM: ath10k: handle 10.4 firmware phyerr event Header format of 10.4 firmware phyerr event is not alligned with pre 10.4 firmware. Introduce new wmi handlers to parse 10.4 firmware specific phyerror event header. With changes covered in this patch, radar detection works on qca9x0 hw 2.0 which uses 10.4 firmware. (cherry picked from commit 2b0a2e0d7c2f12d06575fdc2a0f5cc04b131202d) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: If5e9163eafe75af44baa9bff9e9d45156a72166f Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333478 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333478" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/78/333478/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I028329ecc99afdad8e79c3110c3c34414d8bfb8c" commit="899a6f4bfc066747032c2633dc04e732cc7199af" commit_message="UPSTREAM: ath10k: fill in wmi 10.4 command handlers for addba/delba debug commands WMI 10.4 uses the same command interface as QCA988X for addba/delba debug wmi commands. Fill wmi_10_4_ops table with the functions used for QCA988X for these commands. With this change, the following debugfs entries can be used to configure the aggregation mode and to send addba request, addba response and delba respectively in manual aggregation mode for QCA99X0 chip. /sys/kernel/debug/ieee80211/phyX/netdev:wlanX/stations/XX:XX:XX:XX:XX:XX/aggr_mode /sys/kernel/debug/ieee80211/phyX/netdev:wlanX/stations/XX:XX:XX:XX:XX:XX/addba /sys/kernel/debug/ieee80211/phyX/netdev:wlanX/stations/XX:XX:XX:XX:XX:XX/addba_resp /sys/kernel/debug/ieee80211/phyX/netdev:wlanX/stations/XX:XX:XX:XX:XX:XX/delba (cherry picked from commit b2887410f0d00f376b250f78d34654b4ac093900) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I028329ecc99afdad8e79c3110c3c34414d8bfb8c Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333479 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333479" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/79/333479/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ief265d4e30b9e98bc538d16d4efd8a69c7dfd9fe" commit="0a8528184cdff9680d7b0f18f4615b53c72914cf" commit_message="UPSTREAM: ath10k: ensure pktlog disable cmd reaches fw before pdev suspend Found incorrect sequence in ath10k_core_stop() where wmi pktlog disable cmd is passed from ath10k_debug_stop() to firmware immediately after wmi pdev suspend cmd. Firmware will not accept any wmi cmd after receiving wmi pdev suspend cmd. Fix this issue in ath10k_core_stop() by moving ath10k_debug_stop() just before sending pdev suspend cmd. So that pktlog disable cmd will get passed before pdev suspend cmd. (cherry picked from commit f1ee2682ef8dffe6d6ec6f7788d6bf33d6bab7a6) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ief265d4e30b9e98bc538d16d4efd8a69c7dfd9fe Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333480 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333480" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/80/333480/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ib726ee0546eb2f42ff817cb808c78b5de16299be" commit="df2438c78fa77a83405ed19df8613cc2660a5891" commit_message="UPSTREAM: ath10k: free collected fw stats memory if .pull_fw_stats fails If .pull_fw_stats() fails for some reason while processing fw stats event, collected pdev/vdev/peer stats just before the failure should be freed. This is unlikely to happen, just code review catch. (cherry picked from commit 5db879aefa0ef6dea4fdda268dd94016bc165f3d) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ib726ee0546eb2f42ff817cb808c78b5de16299be Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333481 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333481" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/81/333481/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ib475ead0f16f37e3f4c3418642e2802d5afdea02" commit="389296f6226b9f9934a6e2acf887148bbbd5bc8e" commit_message="UPSTREAM: ath10k: add missing mutex unlock on failpath Kernel would complain about leaving a held lock after going back to userspace and would subsequently deadlock. Fixes: e04cafbc38c7 ("ath10k: fix peer limit enforcement") (cherry picked from commit 503422d95248c1d9698735bb5803b70aa51b18ef) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ib475ead0f16f37e3f4c3418642e2802d5afdea02 Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333482 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333482" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/82/333482/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ic85fa48a3063905d611bd5022cbc678646436469" commit="fba4d7291bb12e59bb61f79c3e7f906099da8a95" commit_message="UPSTREAM: ath10k: fix dma_mapping_error() handling The function returns 1 when DMA mapping fails. The driver would return bogus values and could possibly confuse itself if DMA failed. Fixes: 767d34fc67af ("ath10k: remove DMA mapping wrappers") (cherry picked from commit 5e55e3cbd1042cffa6249f22c10585e63f8a29bf) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ic85fa48a3063905d611bd5022cbc678646436469 Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333483 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333483" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/83/333483/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie429342df14bc37330f02d5fc84148b600a39fb9" commit="a2d8b45ccb9e89c2662ed0d7d4c82632c7c3ba40" commit_message="UPSTREAM: ath10k: add spectral scan support for 10.4 fw To enable/configure spectral scan parameters in 10.4 firmware, existing wmi spectral related functions can be reused. Link those functions in 10.4 wmi ops table. In addition, adjust bin size (only when size is 68 bytes) before reporting bin samples to user space. The background for this adjustment is that qca99x0 reports bin size as 68 bytes (64 bytes + 4 bytes) in report mode 2. First 64 bytes carries in-band tones (-32 to +31) and last 4 byte carries band edge detection data (+32) mainly used in radar detection purpose. Additional last 4 bytes are stripped to make bin size valid one. This bin size adjustment will happen only for qca99x0, all other chipsets will report proper bin sizes (64/128) without extra 4 bytes being added at the end. The changes are validated in qca99x0 using 10.4 firmware. (cherry picked from commit 4535edbd4214ce21328655434c0b75da404e29b7) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Ie429342df14bc37330f02d5fc84148b600a39fb9 Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333484 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333484" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/84/333484/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I35b5256d5df6031c943c645d52d43a45edcf3196" commit="b00cbe79662a67328267917c361677a5c3182bab" commit_message="UPSTREAM: ath10k: add qca6164 support This adds additional 0x0041 PCI Device ID definition to ath10k for QCA6164 which is a 1 spatial stream sibling of the QCA6174 (which is 2 spatial stream chip). The QCA6164 needs a dedicated board.bin file which is different than the one used for QCA6174. If the board.bin is wrong the device will crash early while trying to boot firmware. The register dump will look like this: ath10k_pci 0000:02:00.0: firmware register dump: ath10k_pci 0000:02:00.0: [00]: 0x05010000 0x000015B3 0x000A012D 0x00955B31 ... Note the value 0x000A012D. Special credit goes to Alan Liu <alanliu@qca.qualcomm.com> for providing support help which enabled me to come up with this patch. (cherry picked from commit 36582e5d4daeccf68a8a3cef9bc37b60fb7d45b9) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I35b5256d5df6031c943c645d52d43a45edcf3196 Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333485 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333485" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/85/333485/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6e375a04e870b269be1c427a95d7386457205f9c" commit="6b9e368d55ac1759a62a65833923e4005a9749ca" commit_message="UPSTREAM: ath10k: fix compilation warnings in wmi phyerr pull function Below compilation warnings are observed in gcc version 4.8.2. Even though it's not seen in bit older gcc versions (for ex, 4.7.3), It's good to fix it by changing format specifier from %d to %zd in wmi pull phyerr functions. wmi.c: In function 'ath10k_wmi_op_pull_phyerr_ev': wmi.c:3567:8: warning: format '%d' expects argument of type 'int', but argument 4 has type 'long unsigned int' [-Wformat=] left_len, sizeof(*phyerr)); ^ wmi.c: In function 'ath10k_wmi_10_4_op_pull_phyerr_ev': wmi.c:3612:8: warning: format '%d' expects argument of type 'int', but argument 4 has type 'long unsigned int' [-Wformat=] left_len, sizeof(*phyerr)); ^ Fixes: 991adf71a6cd ("ath10k: refactor phyerr event handlers") Fixes: 2b0a2e0d7c2f ("ath10k: handle 10.4 firmware phyerr event") (cherry picked from commit ee92a2099f79d47e1d6d4857ab308f5b15a00549) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: I6e375a04e870b269be1c427a95d7386457205f9c Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333486 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333486" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/86/333486/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Icd19ef8561bcc7273f2806b7718c16c7af6de653" commit="4a03ae6ee4f5307957a334eaae88b4d8da59c2e3" commit_message="UPSTREAM: ath10k: fix mu-mimo rx status reporting MU-MIMO Rx involves different interpretation of the VHT-SIG-A compared to SU-MIMO. The incorrect interpretation led ath10k to report VHT MCS values greater than 9 which subsequently prompted mac80211 to drop such frames. This effectively broke Rx with MU-MIMO in many cases and manifested with a kernel warning in the log which looked like this: [ 14.552520] WARNING: CPU: 2 PID: 0 at net/mac80211/rx.c:3578 ieee80211_rx+0x26c/0x940 [mac80211]() [ 14.552522] Rate marked as a VHT rate but data is invalid: MCS: 10, NSS: 2 ... call trace follows ... (cherry picked from commit 6986fdd699f9be57cc1478c738ea6347e3d52547) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: Icd19ef8561bcc7273f2806b7718c16c7af6de653 Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333487 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333487" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/87/333487/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="If2b00b2f6a82f0a7fdcde300b18c59e537b85571" commit="a0c015c2f2c2548bcdb387123c20a67f3c8b7faa" commit_message="UPSTREAM: ath10k: fix DMA alloc failure for target requested memory chunks During long hours of stress testing like AP interface up/down along with continuous ping flood from a station doing connect/disconnect, it is observed that the system is not able to allocate DMA consistent memory of size > 512KB chunks as requested by firmware in WMI_SERVICE_EVENTID. With the system memory getting fragmented during the run based on the size of the memory requested, the failure to return physically continguous memory of high order can happen. Once the system gets to this situation, bringing up the wifi interface will fail and a system reboot may be needed to make it work again. This problem is obseved with QCA99X0. To fix this issue, allocate the DMA memory requested by firmware during device probe time and keep it during the life time of the device. WMI service ready event handler is changed to allocate the memory chunks if it is not already allocated or if the memory allocated for the previous ready event is not same as the current requested ones. After this patch the memory usage when wifi is inactive will be inceased by few 100KB to 3MB based on the target type. Failure happens with the following stack trace [29557.488773] kworker/u4:1: page allocation failure: order:8, mode:0xd0 [29557.494297] CPU: 0 PID: 8402 Comm: kworker/u4:1 Not tainted 3.14.43 #7 [29557.500793] Workqueue: ath10k_aux_wq ath10k_wmi_event_service_ready_work [ath10k_core] [29557.508602] [<c021e9b0>] (unwind_backtrace) from [<c021ba90>] (show_stack+0x10/0x14) [29557.516580] [<c021ba90>] (show_stack) from [<c03bdddc>] (dump_stack+0x88/0xcc) [29557.523612] [<c03bdddc>] (dump_stack) from [<c0290e34>] (warn_alloc_failed+0xdc/0x108) [29557.531515] [<c0290e34>] (warn_alloc_failed) from [<c0292d88>] (__alloc_pages_nodemask+0x4f0/0x654) [29557.540485] [<c0292d88>] (__alloc_pages_nodemask) from [<c0222b48>] (__dma_alloc_buffer.isra.20+0x2c/0x104) [29557.550260] [<c0222b48>] (__dma_alloc_buffer.isra.20) from [<c0222c34>] (__alloc_remap_buffer.isra.23+0x14/0xb8) [29557.560413] [<c0222c34>] (__alloc_remap_buffer.isra.23) from [<c022305c>] (__dma_alloc+0x224/0x2b8) [29557.569490] [<c022305c>] (__dma_alloc) from [<c0223208>] (arm_dma_alloc+0x84/0x90) [29557.577010] [<c0223208>] (arm_dma_alloc) from [<bf5159d0>] (ath10k_wmi_event_service_ready_work+0x2f8/0x420 [ath10k_core]) [29557.588055] [<bf5159d0>] (ath10k_wmi_event_service_ready_work [ath10k_core]) from [<c024260c>] (process_one_work+0x20c/0x328) [29557.599305] [<c024260c>] (process_one_work) from [<c02432d0>] (worker_thread+0x228/0x360) [29557.607470] [<c02432d0>] (worker_thread) from [<c0247f88>] (kthread+0xd8/0xec) [29557.614750] [<c0247f88>] (kthread) from [<c0208d18>] (ret_from_fork+0x14/0x3c) [29557.712751] Normal: 696*4kB (UEMR) 512*8kB (UEMR) 367*16kB (UEMR) 404*32kB (UEMR) 455*64kB (UEMR) 424*128kB (UEMR) 379*256kB (UMR) 327*512kB (UMR) 1*1024kB (R) 0*2048kB 0*4096kB = 374544kB (cherry picked from commit a925a3763982799460b9e9b5299520172652b785) BUG=chrome-os-partner:49260 TEST=built ath10k modules for x86 Change-Id: If2b00b2f6a82f0a7fdcde300b18c59e537b85571 Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/333488 Commit-Ready: Grant Grundler <grundler@chromium.org> Tested-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> " fail_count="0" gerrit_number="333488" owner_email="c_mkenna@qti.qualcomm.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/88/333488/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I7a21c66325399d1f0d69f7e5e74f9580166f7148" commit="cee3debe1ff7ccd2127e33236880d3b41cf3e676" commit_message="cros-board: add smaug-kasan board BUG=chromium:596063 TEST=none Change-Id: I7a21c66325399d1f0d69f7e5e74f9580166f7148 Signed-off-by: Alexander Potapenko <glider@google.com> Reviewed-on: https://chromium-review.googlesource.com/333941 Commit-Ready: Alexander Potapenko <glider@chromium.org> Tested-by: Alexander Potapenko <glider@chromium.org> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="0" gerrit_number="333941" owner_email="glider@chromium.org" pass_count="0" patch_number="1" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/41/333941/1" remote="cros" total_fail_count="0"/><lkgm version="8101.0.0-rc1"/></manifest> |
