| <?xml version="1.0" encoding="utf-8"?><manifest revision="12286b5c3b2b7e0fc0b8a91ffc934962f4ee8b1a"> |
| <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="b6795643ec0305ba2ff862fcd0f450756aa5e58c"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/chromite" path="chromite" revision="f83692cb5a663d9d817a6c8ebe9f4c298f5932e3" upstream="refs/heads/master"> |
| <copyfile dest="AUTHORS" src="AUTHORS"/> |
| <copyfile dest="LICENSE" src="LICENSE"/> |
| </project> |
| <project name="chromiumos/manifest" path="manifest" revision="60d0de0f26feea2c8c63895e576990cc21115c17" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/board-overlays" path="src/overlays" revision="8ce05afbec16671e4feb75ee3c6e46f51fa77472" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="3137a138f72a49bfa825a7ac68d5008ed76d58f8" sync-c="true" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/eclass-overlay" path="src/third_party/eclass-overlay" revision="475609d0d82476d9162498e238df000eed27ff36" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/portage-stable" path="src/third_party/portage-stable" revision="f21c9ee135e8b46016083f644c75ff115db6446b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/assets" path="src/platform/assets" revision="48950c9cb35671c59f9f63316683357c8792b79d" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/audiotest" path="src/platform/audiotest" revision="3fb17a505c9dae6dbac84c98f8cd8f30941b6eef" 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/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="06e2b418bd604b362d3c245562a068f619b2b1bf" 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="c0ed34f476aeecf52ac9bfea4750ac4fb8a539c4" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/crosutils" path="src/scripts" revision="948dba96f358f9da6baaf28cba2f6969d7db2de9" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="0cb2fe940bd5cf0a9beb8d553e9b52c994a4dffd" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="ba4e00f161e55bd7967e154aba7755f96470e935" 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="987a60f5ae48541c1df1aab8a01560446b712f76" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/ec" path="src/platform/ec" revision="49d4254bd40a81b8f37014400bf5a50e7e581e4d" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory" path="src/platform/factory" revision="190aa4addbc9a286ace2aaaba0401a91a48700c9" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory_installer" path="src/platform/factory_installer" revision="f90b5268a73704d68700a782d170261d546fd85a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/firmware" path="src/platform/firmware" revision="8b14a26ccaaac20c33535a38199273c0acecb33f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/frecon" path="src/platform/frecon" revision="38917fe2b121610c487570bb41f97167a76132ce" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/gestures" path="src/platform/gestures" revision="05325e18158f8519f853e086e92c04504e2b87aa" 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/platform/google-breakpad" revision="cf5b98e801bcf0218dfe19ac722c5fa600814678" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/initramfs" path="src/platform/initramfs" revision="7efff0e164437b46def2b2f556d822827e29a0be" 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="0b6e7be80034cbede5e111108c46bb75bb5942dd" 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="dc94b474288cec3c8c9ca55e0f0b5ee2d681f2e7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/monitor_reconfig" path="src/platform/monitor_reconfig" revision="c02c806dfe581dcff530f75f7b73847f7c3dc229" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mosys" path="src/platform/mosys" revision="46479afc8eb9d0801e2ee066ec6b1842d8ab8290" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtpd" path="src/platform/mtpd" revision="9f9c6bf080b3f75f6249fadf62aeb9591a1915a4" 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="7cde658e97d6a00cf0d43f0478544e71ffd2e2d2" 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="e1517ab9becc2b8525a4352943febc794d107b7f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_firmware_test" path="src/platform/touch_firmware_test" revision="63e30ba7c02484a99e4f7757fccf049e2880c029" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_noise_filter" path="src/platform/touch_noise_filter" revision="322345ed0b1ab6e42ec2710ef5c904464b0dc218" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_updater" path="src/platform/touch_updater" revision="abbaca628034dc25bca7f8a6c0015a8c21154d10" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchbot" path="src/platform/touchbot" revision="c3c6ea92a02cb6bba18175c713cdedec18309d28" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchpad-tests" path="src/platform/touchpad-tests" revision="35468240e94dd74577f06dbeca5aac88e4c0b8ef" 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="03382e68603e99b0fdc81e2f3500448c47ba2396" 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_reference" path="src/platform/vboot_reference" revision="b491bc8bb1499452536eb140c22f749d1c9f9fc3" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/vpd" path="src/platform/vpd" revision="f07e3dfe1be57bc778d84657bf051ff50443cf56" 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="48a42e96e26edd12bf295ea13b50bcdd40c068e3" 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="2389885e788815f7d44b6cd3160c4085da7e689e" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform2" path="src/platform2" revision="ecb08355b44f255feb0bdaa0d19ab2af56c0df4b" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/repohooks" path="src/repohooks" revision="81d07144f3790a66819ecd320101bfdf51dd15f8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/adhd" path="src/third_party/adhd" revision="bc573a33370cf0a323cb7c5dd4fe2956a0141e2f" 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="f57e2db6ef4b86a6af57891a2d7a90266ad6c033" upstream="refs/heads/master"/> |
| <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="253f5dcc1e6d89bf64482d5d59b949d629d8748e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/binutils" path="src/third_party/binutils" revision="ff847b57d425687df548c860b48851f090bd79e2" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bluez" path="src/third_party/bluez" revision="3cc29b0281e14f1bb5b36e9a569c663cc54db970" upstream="refs/heads/master"/> |
| <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/bsdiff" path="src/third_party/bsdiff" revision="8c17bdc0d759c8e6da90c5f72b052ba2605a0a3a" 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="92568c630c48446b1ad9d4f22056f22e0679970c" upstream="refs/heads/chromeos-2015.07"/> |
| <project name="chromiumos/third_party/coreboot/blobs" path="src/third_party/coreboot/3rdparty/blobs" revision="612cd24575ab8bb77260e22f3665f46b77794ffe" 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="96c67aab12f53380342a6eeabf8954eac02a7911" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gcc" path="src/third_party/gcc" revision="b6125c702850488ac3bfb1079ae5c9db89989406" 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="3703700655a062ba9f4a5ba30af2208636d5eb09" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant" revision="88126a88e240ab18730163ea0f5d0b775247ac23" 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="f40dc81315226652baad6bd18d1b515597a95b5a" upstream="refs/heads/chromeos-3.8"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.10" revision="d200a34f72072cd531f08bba1b5d7e32d6b65e7a" upstream="refs/heads/chromeos-3.10"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.14" revision="56f6936d88d42112625e6c506337667af902f99d" upstream="refs/heads/chromeos-3.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="9b4152659fbc08548de1925d8e26420f6734c0c7" upstream="refs/heads/chromeos-3.18"/> |
| <project name="chromiumos/third_party/khronos" path="src/third_party/khronos" revision="c4932bd57b6edfc42773b4527180a219b9af9ca4" 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/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="0ece365f95c0b1a81dc9b768504c5994202798c8" 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="f1684f7174aad3f4249416a3e9049899d05824ba" 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="c2a0600d5b0645533ba442b5ab879b23c2564a4d" 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="52fbe37e5d78011366eec0033d5374a0c8950f0e" 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="7d5367e2a8618718e90274ae920bc6f406b59b9e" 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="a49f9129735985d8851e38da0f2ca4380a51e388" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/third_party/trousers" path="src/third_party/trousers" revision="4ca78880022107e61481a0e2e053acc82b2e5090" upstream="refs/heads/master-0.3.13"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/files" revision="b6e27ea40d24cd4273143eeab741a39704ee47fe" upstream="refs/heads/chromeos-v2013.06"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/next" revision="04cfc2000cdc6a27b8a33e3b112e97c33e22f318" 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="0ec868bc7a6a72ca40e3cb508898e4e07f109ae1"/> |
| <repo-hooks enabled-list="pre-upload" in-project="chromiumos/repohooks"/> |
| <pending_commit branch="chromeos-3.14" change_id="I567770fb8d59e5f161410375e1785cb0cad99eda" commit="23e046076866c3080677d9f967de7ab1fcb1b2d7" commit_message="UPSTREAM: ath10k: advertise 10.4 fw ap and sta iface combination to mac80211 10.4 fw supports upto 16 interface in ap mode and 1 interface in station mode, overall total interfaces supported are 16 interfaces. Populate this limit in wiphy->iface_combinations. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit cf36fef08a85c815d9358e1571d3d83da02474f7) TEST=none BUG=none Change-Id: I567770fb8d59e5f161410375e1785cb0cad99eda Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307300 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307300" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/00/307300/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I2bb1cef99f6612a7f23a25da080bb44be40d090b" commit="5fce18e468cae4048174fd3b7856942554593e85" commit_message="UPSTREAM: ath10k: set max spatial stream to 4 for 10.4 fw 10.4 fw supports upto 4 spatial stream. Limit max spatial stream to 4 for 10.4 firmware and to 3 for non 10.4 firmware. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 5c8726eca3e4080615f09328d1f28013b6e5c837) TEST=none BUG=none Change-Id: I2bb1cef99f6612a7f23a25da080bb44be40d090b Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307301 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307301" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/01/307301/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I708b21eba737156f3effd8e7a6ae1f3d97bc7d3b" commit="98ded7d2c6df8ef348d873b14b848599ba5017cc" commit_message="UPSTREAM: ath10k: configure frag desc memory to target for qca99X0 Pre qca99X0 chipsets follows the model where dynamically allocate memory for frag desc on getting new skb for TX. But, this is not going to be the case in qca99X0. It expects frag desc memory to be allocated at boot time and let the driver to reuse allocated memory after every TX completion. So there won't be any dynamic frag memory memory allocation in qca99X0 during data transmission. qca99X0 hardware doesn't need fragment desc address to be programmed in msdu descriptor for every data transaction. It needs to know only starting address of fragment descriptor at the time of the boot. During data transmission, qca99X0 hardware can retrieve corresponding frag addr by adding programmed frag desc base addr + msdu id. Allocate continuous fragment descriptor memory (same size as number of descriptor) at the time of target initialization and configure allocated dma address to the target via HTT_H2T_MSG_TYPE_FRAG_DESC_BANK_CFG. How this is allocated continuous memory is going to be used is not covered in this patch. It just allocates memory and hand over to firmware. If we don't do it at init time, qca99X0 will stall when firmware tries to do TX. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit d9156b5f6849a1b1185ac62790f36df013b1ade6) TEST=none BUG=none Change-Id: I708b21eba737156f3effd8e7a6ae1f3d97bc7d3b Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307302 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307302" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/02/307302/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I8af56a6d15606dd4de3859194d1b1e346eab6ae9" commit="a50e541222f7fd1c7c36cb2a6fbda5bc3cd22d6c" commit_message="UPSTREAM: ath10k: fix QCA61X4 boot up commit a521ee983d312db7 ("ath10k: Add new reg_address/mask to hw register table") broke QCA61x4 support by providing wrong fw_indicator_address, which should have been 0x0003a028 instead of 0x00009028. User experience was a failing boot up sequence (crashing device during initialization): [ 181.663874] ath10k_pci 0000:02:00.0: enabling device (0000 -> 0002) [ 181.664787] ath10k_pci 0000:02:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [ 181.688886] ath10k_pci 0000:02:00.0: device has crashed during init [ 181.688897] ath10k_pci 0000:02:00.0: failed to wait for target after cold reset: -70 [ 181.688902] ath10k_pci 0000:02:00.0: failed to reset chip: -70 [ 181.689774] ath10k_pci: probe of 0000:02:00.0 failed with error -70 Fix it by updating the address with correct value. Fixes: a521ee983d31 ("ath10k: Add new reg_address/mask to hw register table") Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit a052158aa981ca470673f49c636b289ee16894ea) TEST=none BUG=none Change-Id: I8af56a6d15606dd4de3859194d1b1e346eab6ae9 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307303 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307303" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/03/307303/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I4ea5fa4b00d3fcc02b43bd6402f766254ff30b39" commit="c29638cdce479d4493bc7c8279a56e9c5b2ff92d" commit_message="UPSTREAM: ath10k: Fix target to cpu address conversion logic In commit 418ca5992e2f ("ath10k: Make target cpu address to CE address conversion chip specific") mask 0x7fff is added by mistake instead of 0x7ff. Fix this regression. Fixes: 418ca5992e2f ("ath10k: Make target cpu address to CE address conversion chip specific") Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 3c7e256a6de378e01098147527082abae05b146e) TEST=none BUG=none Change-Id: I4ea5fa4b00d3fcc02b43bd6402f766254ff30b39 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307304 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307304" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/04/307304/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I518329eb8c4233614df0222da84c69f0c414fb65" commit="7524dbf21e834a76adc4fdef54495fbd27b46025" commit_message="UPSTREAM: ath10k: don't set cck/ofdm scan flags mac80211 already does provide complete IEs for Probe Requests for hw scan and ath10k firmware was appending duplicate Supported Rates IEs unnecessarily. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 835d56a10c1fcfb0fee28bb6aceb722e1a6f643a) TEST=none BUG=none Change-Id: I518329eb8c4233614df0222da84c69f0c414fb65 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307305 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307305" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/05/307305/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="Icc97a1ac0d948ea79774c76fcc9591dcd5a603a1" commit="28c3c4dd711ca219b6ea93c44aed5811ac326565" commit_message="UPSTREAM: ath10k: limit multi-vif ps more aggresivelly Further testing proved that multi-channel AP+STA on QCA6174 with RM.2.0-00088 should have powersave force-disabled to avoid beacon misses/skipping on either side which in turn could disrupt communication. Since AP never has arvif->ps don't even bother checking it. Other combinations may be broken as well so disallow powersave with multivif outright unless firmware advertises otherwise. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 424f26301467daf241a4afe4b6fe82750d4ac624) TEST=none BUG=none Change-Id: Icc97a1ac0d948ea79774c76fcc9591dcd5a603a1 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307306 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307306" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/06/307306/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I7568502704b8fbb2c381cc552bada02c97d3360d" commit="aef70ed8afd4782124aa4d356101090c229ad7b0" commit_message="UPSTREAM: ath10k: fix hw roc expiration notifcation The expiration function must not be called when roc is explicitly cancelled by mac80211. However since fcf9844636be ("ath10k: fix hw roc expiration") the notification was never sent when roc actually expired. This fixes some P2P connection setup issues. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit d710e75d1050cb66fbf6e906addb4a661e444729) TEST=none BUG=none Change-Id: I7568502704b8fbb2c381cc552bada02c97d3360d Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307307 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307307" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/07/307307/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I2cdb0be4ef93e4cf750fe5e63e6bf154a042197c" commit="e3ad762fff0f8a9406c87e6984deb971b4c4b9b3" commit_message="UPSTREAM: ath10k: update vdev ps state on start Psmode can be forcefully enabled when vdev isn't started. It isn't guaranteed that mac80211 will re-issue psmode setting after vdev is started unless actual bss_conf.ps value has changed. Even if this doesn't fix any problems now it may prevent future breakage. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit f23e587e55f3607741e29a789efa61ea999f13f8) TEST=none BUG=none Change-Id: I2cdb0be4ef93e4cf750fe5e63e6bf154a042197c Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307308 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307308" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/08/307308/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I929803f3b0de7e81fc6ae185284af90a462f171e" commit="0722cda03a3b94716d2a5f0ee4601a552fb78770" commit_message="UPSTREAM: ath10k: fix per-vif queue locking Whenever any vdev was supposed to be paused all Tx queues were stopped (except offchannel) instead of only these associated with the given vdev. This caused subtle issues with multi-channel/multi-vif scenarios, e.g. authentication of station vif could sometimes fail depending on fw tx pause request timing. Fixes: b4aa539dd8f2 ("ath10k: implement tx pause wmi event") Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit acd0b27bb13a09dd0a56d4562d3eb4137a7318b2) TEST=none BUG=none Change-Id: I929803f3b0de7e81fc6ae185284af90a462f171e Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307309 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307309" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/09/307309/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I880704f627a66158bd14711af555aec38e3cb460" commit="451fdcc408774b4b6711f83cab0e9408d2ab0adb" commit_message="UPSTREAM: ath10k: tweak interface combinations Concurrent AP/GO operation on different channels isn't really supported well by the firmware so it's better to remove it from being advertised. Also tune the way station and p2p client interface limits are expressed to allow station + 2x p2p client or station + p2p client + p2p go. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit ed25b113a955e62aeaba49a3ec71faea4f25bf34) TEST=none BUG=none Change-Id: I880704f627a66158bd14711af555aec38e3cb460 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307310 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307310" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/10/307310/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="Id07af08e134c4253b52ee6298d475b98c6760c24" commit="dcc01dcc44a1cdac5dfb65ce325d9d11b7b1cc11" commit_message="UPSTREAM: ath9k: DFS - consider ext_channel pulses only in HT40 mode The chip reports radar pulses on extension channel even if operating in HT20 mode. This patch adds a sanity check for HT40 mode before it feeds pulses on extension channel to the pattern detector. Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 8f010d9ca88f9023650b2e54b74c84ab63a19d02) TEST=none BUG=none Change-Id: Id07af08e134c4253b52ee6298d475b98c6760c24 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307311 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307311" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/11/307311/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="Ib78223f4e4f1f2d26b4ff49920431be570e8b661" commit="68e8ae34b5f3adb5a9672f8e9a02ebaa1999b714" commit_message="UPSTREAM: ath9k: DFS - add pulse chirp detection for FCC FCC long pulse radar (type 5) requires pulses to be checked for chirping. This patch implements chirp detection based on the FFT data provided for long pulses. A chirp is detected when a set of criteria defined by FCC pulse characteristics is met, including * have at least 4 FFT samples * max_bin index moves equidistantly between samples * the gradient is within defined range The chirp detection has been tested with reference radar generating devices and proved to work reliably. Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 8fc2b61a36fe17f744b445a26599a6cac9e6c1c0) TEST=none BUG=none Change-Id: Ib78223f4e4f1f2d26b4ff49920431be570e8b661 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307312 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307312" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/12/307312/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I66779fc8caa6549d7dedf8418520062b921e9208" commit="5db3d773759197610a42175dc9cdefa9567c7b6f" commit_message="UPSTREAM: ath9k: make DMA stop related messages debug-only A long time ago, ath9k had issues during reset where the DMA engine would stay active and could potentially corrupt memory. To debug those issues, the driver would print warnings whenever they occur. Nowadays, these issues are gone and the primary cause of these messages is if the MAC is stuck during reset or busy processing a long transmission. This is fairly harmless, yet these messages continue to worry users. To reduce the number of bogus bug reports, turn these messages into debug messages and count their occurence in the "reset" debugfs file. Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit e60ac9c7a4c8776b2503892dfd01f1b4d651245d) TEST=none BUG=none Change-Id: I66779fc8caa6549d7dedf8418520062b921e9208 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307313 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307313" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/13/307313/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I76b5bbdede45f48d24bf480544ee5ca11f2189c8" commit="858f2eee9401b2b4c7e270758c5beae6e3f5dc15" commit_message="UPSTREAM: ath9k: fix moredata flag endianness in cabq tx While compiling ath9k with some extra flags I've found that: ath9k/xmit.c +2473 ## 16: warning: restricted __le16 degrades to integer ath9k/xmit.c +2474 ## 36: warning: invalid assignment: &= ath9k/xmit.c +2474 ## 36: left side has type restricted __le16 ath9k/xmit.c +2474 ## 36: right side has type int There's no way for frame ftype/stype to be mistreated as the offending 'moredata' flag when considering cab queue. This could've however theoretically led sometimes to increased power consumption on connected stations as they would keep their Rx active waiting for frames that would never come. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 92cd40322848a12f1f3ef2d7804233b93030c532) TEST=none BUG=none Change-Id: I76b5bbdede45f48d24bf480544ee5ca11f2189c8 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307314 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307314" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/14/307314/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I47cb8cdee823184db6e71d2ce9ebac22a0729b83" commit="3224cd305b8bb2ddd499a3cdfe841f1d0fd57929" commit_message="UPSTREAM: ath9k: Fix register definitions for QCA956x Signed-off-by: Miaoqing Pan <miaoqing@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit fa5b8c8a5ae4088a590d59fffb022da3ea17bd15) TEST=none BUG=none Change-Id: I47cb8cdee823184db6e71d2ce9ebac22a0729b83 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307315 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307315" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/15/307315/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I5c6d335569e6126f920872ee449848b519e19c31" commit="9879b0b44b4fc77880ef956645987d620d69cba2" commit_message="UPSTREAM: ath9k: export HW random number generator We measured the FFT-based entropy in 3 ways, Shannon entropy, collision entropy, and directly measured min-entropy. Just to be conservative, we recommend the estimated min-Entropy to be 10 bits per 16-bit value. Analysis was done by Jacobson,David(djacobso@qti.qualcomm.com). Signed-off-by: Miaoqing Pan <miaoqing@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 6301566e0b2dafa7d6779598621bca867962a0a2) TEST=none BUG=none Change-Id: I5c6d335569e6126f920872ee449848b519e19c31 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307316 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307316" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/16/307316/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I6ee239c8f3a03d1d34670988abe7e3f12ae8150e" commit="c6e902415114beeb0d620c426b8227235a754b6e" commit_message="UPSTREAM: ath10k: delay device access after cold reset It is observed that during cold reset pcie access right after a write operation to SOC_GLOBAL_RESET_ADDRESS causes Data Bus Error and system hard lockup. The reason for bus error is that pcie needs some time to get back to stable state for any transaction during cold reset. Add delay of 20 msecs after write of SOC_GLOBAL_RESET_ADDRESS to fix this issue. This patch is tested on QCA988X. This is also tested on QCA99X0 which is WIP. Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit acd195800ffca556e9c78c51d1efe534d71dd236) TEST=none BUG=none Change-Id: I6ee239c8f3a03d1d34670988abe7e3f12ae8150e Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307317 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307317" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/17/307317/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="Ifd361762991ede23b0139e8b2e847bf8df661a73" commit="9861b2ab7d320e875589081550bc2b4411ab21f3" commit_message="UPSTREAM: ath10k: update tx path to support QCA99X0 Since QCA99X0 uses fragmentation descriptor differently from other ones on tx path, we need to handle it separately. QCA99X0 is using 48 bits for address and 16 bits for length out of 2 dword and each values have to be programmed by frag desc base addr + msdu id, so that hardware can retrieve corresponding frag data. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit fbc03a466fd48bc8be2e675be948001feea29e4d) TEST=none BUG=none Change-Id: Ifd361762991ede23b0139e8b2e847bf8df661a73 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307318 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307318" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/18/307318/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I2c49b09b57b1d78312afddf50e8420ef9c3e109a" commit="8e7e046f53de1f24969a5fd33a60974eada7e163" commit_message="UPSTREAM: ath10k: redefine rx_ppdu_end_common structure to cover qca99x0 rx_ppdu_end_common structure is valid for both of qca998x and qca6174, but not for qca99x0 since it has new additional members. Hence update the common structure to cover qca99x0 as well. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 05a2cb0daa49af4e240834ff3736fd35ba83320f) TEST=none BUG=none Change-Id: I2c49b09b57b1d78312afddf50e8420ef9c3e109a Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307319 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307319" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/19/307319/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I5aa7dac00558e0bbbd546cd930c849862b2c3e3b" commit="4d5110b0568a7cb1898a773d3b71c28eb53c02d3" commit_message="UPSTREAM: ath10k: add support for qca99x0 Rx descriptors QCA99X0 chip has an extra 4 bytes in rx_msdu_start, 20 bytes in rx_msdu_end and 20 bytes in rx_ppdu_end structure which are used in htt_rx_desc and HTT Rx ring offset setup. This is necessary for correct Rx for QCA99X0 or Rx descriptors will be overwritten and corrupted. With this patch QCA988X and QCA6174 will have extra 44 bytes padding in Rx descriptor layout which is harmless. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 1f5dbfbb64c92e1c22305ac2b3951d6e3cf7a9a7) TEST=none BUG=none Change-Id: I5aa7dac00558e0bbbd546cd930c849862b2c3e3b Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307320 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307320" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/20/307320/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I4606ecbd04e516758a8d74218b7aa7d7c8ce3387" commit="94faf47fe283b91bf56bb764ba501a3bec921f94" commit_message="UPSTREAM: ath10k: fix wrong initialization of struct channel chandef is initialized with NULL and on the very next line, we are using it to get channel, which is not correct. Channel should be initialized after obtaining chandef. Found by cppcheck: ath/ath10k/mac.c:839]: (error) Possible null pointer dereference: chandef Signed-off-by: Maninder Singh <maninder1.s@samsung.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 19be9e9a7ac7e6050eab426283d2a87593cf6e82) TEST=none BUG=none Change-Id: I4606ecbd04e516758a8d74218b7aa7d7c8ce3387 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307321 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307321" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/21/307321/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I9110b3ee13198424ef638d2ba995632bdfb29dc8" commit="0cd37311a31e599ab368192bfa12fb6738dde41e" commit_message="UPSTREAM: ath10k: add TCP/UDP Checksum offload support for QCA99x0 The patch adds support to offload TCP/UDP checksum calculations for QCA99x0. Signed-off-by: Manikanta Pubbisetty <c_mpubbi@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit b963519509644f52eaaddcc1fa484e28ac74c750) TEST=none BUG=none Change-Id: I9110b3ee13198424ef638d2ba995632bdfb29dc8 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307322 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307322" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/22/307322/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I3a34c4724c8d1fba9d7e9fe7f07cfb759edebf4a" commit="ce3ba93c37f2c3a14a97e312d765606568cce947" commit_message="UPSTREAM: ath10k: extend struct htt_mgmt_tx_dec for qca99x0 HTT_H2T_MSG_TYPE_MGMT_TX msg in 10.4 firmware carries additional 4 byte in htt_mgmt_tx_desc where it tells to firmware that at what rate mgmt frame has to go out in the air. It's an optional parameter, setting this field to zero will force firmware to choose auto rate and send the frame out. Those 4 byte info is missed out in the current code and 10.4 firmware ended up reading some junk in those 4 byte and sometime malfunctioning. Fix it by adding 4 byte in struct htt_mgmt_tx_desc. Non 10.4 firmware will not process those four byte. So, adding 4 byte at the end of struct htt_mgmt_tx_desc will not create any impact on other chipset. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 1d0088f8c1d8b9541ed01f2cc52606fbf8baf50c) TEST=none BUG=none Change-Id: I3a34c4724c8d1fba9d7e9fe7f07cfb759edebf4a Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307323 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307323" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/23/307323/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I4e5ad46f8acfcec17551cb3de482162976eb876b" commit="7d302460682f9eb167899a804ea7524edd2b1c4a" 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. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 3413e97dbbae8561e01ac28ccb0d4bbe7ce933f4) TEST=none BUG=none Change-Id: I4e5ad46f8acfcec17551cb3de482162976eb876b Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307324 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307324" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/24/307324/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I3a199dffa5cdca9ee8aedff5015afb91a348cb01" commit="7a85f8286c4b20b15eacff0e8cd2183f0dab0312" 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. 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> (cherry picked from commit 005fb161310f72070ad5f4352d6b81ffaca8a11e) TEST=none BUG=none Change-Id: I3a199dffa5cdca9ee8aedff5015afb91a348cb01 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307325 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307325" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/25/307325/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="Iec82208c8946cf118e1548029e2c142cd88ce952" commit="e1931b367451a3dd5fbbe87e6e69d8c48c5ff25d" 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. 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> (cherry picked from commit ccec9038c7217e537f5ae5e3ac5af8293a21bbfd) TEST=none BUG=none Change-Id: Iec82208c8946cf118e1548029e2c142cd88ce952 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307326 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307326" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/26/307326/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="Ica77eafb2e1a4a348960b360180f1199f2befeb3" commit="d837eb643d8b5b9f301943b351ecfd17852cf908" 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. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit c8ecfc1c33979054fb631d2066745d03ce322b6f) TEST=none BUG=none Change-Id: Ica77eafb2e1a4a348960b360180f1199f2befeb3 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307327 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307327" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/27/307327/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="Ifc494afdda91d91320a74b52fb6acfc6be99abde" commit="53c71557c3ab46634c73ca073fd363fd14345b99" 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. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 1201844e6ddc4e13dfc1a7ffbba0cfd180944679) TEST=none BUG=none Change-Id: Ifc494afdda91d91320a74b52fb6acfc6be99abde Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307328 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307328" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/28/307328/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I5b848544fac83cddd9acc97f9e6aaacff2d0af7f" commit="e38375df1cce66c1b719c83f01e13ce5ee90637e" 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. Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 8a055a8adc875768223be2dfc33de5dc70212756) TEST=none BUG=none Change-Id: I5b848544fac83cddd9acc97f9e6aaacff2d0af7f Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307329 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307329" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/29/307329/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="If459d89649fea524dfc8a2167511a644895fe315" commit="a6c44bb1bde764a86aa90bbf8a6d8058a185fc4a" 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. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit ae7d3821a769a4ac64d4c244b5cd8b134768d452) TEST=none BUG=none Change-Id: If459d89649fea524dfc8a2167511a644895fe315 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307330 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307330" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/30/307330/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I159054597513038ada145223246cfeb66faffe31" commit="a3e1b7531b77b63694cffe3a9f6b23a92d6a0d0e" commit_message="Revert "UPSTREAM: ath9k: export HW random number generator" This reverts commit 6301566e0b2dafa7d6779598621bca867962a0a2. Oleksij Rempel noticed that the randomness doesn't look to be good enough and Stephan Mueller commented: "I would say that the discussed RNG does not seem fit for hooking it up with the hwrandom framework." http://lkml.kernel.org/g/3945775.m5HblJPgiO@tauon.atsec.com So let's the revert the patch until we are sure that we can trust this random generator. Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 360d9bb5ee2db4d409448667de606c05b3914d53) TEST=none BUG=none Change-Id: I159054597513038ada145223246cfeb66faffe31 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307331 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307331" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/31/307331/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I20d440e689a5a27e01b3a40921829aab1998cc56" commit="e3bbbf19eba94c577f5f7107923e8ad6d4a605a6" commit_message="UPSTREAM: ath9k: advertise p2p dev support when chanctx Advertise p2p device support when ath9k loaded with use_chanctx=1. This will fix problem, when first interface is an AP and next we would like to run p2p_find. Before p2p find (scan phase) failed with EOPNOTSUPP. Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit eb61f9f623f78f463ec08b1c4a1defea9b511312) TEST=none BUG=none Change-Id: I20d440e689a5a27e01b3a40921829aab1998cc56 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307332 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307332" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/32/307332/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I1d92721a820540c29efea18773763801e9972c68" commit="36ec2da48fd2ec4eecca270cd6efe400e2634066" commit_message="UPSTREAM: ath9k: handle RoC cancel correctly In case we will get ROC cancel from mac80211 we should not call ieee80211_remain_on_channel_expired(). In other case I hit such warning on MIPS and p2p negotiation failed (tested with use_chanctx=1). ath: phy0: Starting RoC period ath: phy0: Channel definition created: 2412 MHz ath: phy0: Assigned next_chan to 2412 MHz ath: phy0: Offchannel duration for chan 2412 MHz : 506632 ath: phy0: ath_chanctx_set_next: current: 2412 MHz, next: 2412 MHz ath: phy0: Stopping current chanctx: 2412 ath: phy0: Flush timeout: 200 ath: phy0: ath_chanctx_set_next: Set channel 2412 MHz ath: phy0: Set channel: 2412 MHz width: 0 ath: phy0: Reset to 2412 MHz, HT40: 0 fastcc: 0 ath: phy0: cur_chan: 2412 MHz, event: ATH_CHANCTX_EVENT_TSF_TIMER, state: ATH_CHANCTX_STATE_IDLE ath: phy0: ath_offchannel_channel_change: offchannel state: ATH_OFFCHANNEL_ROC_START ath: phy0: cur_chan: 2412 MHz, event: ATH_CHANCTX_EVENT_SWITCH, state: ATH_CHANCTX_STATE_IDLE ath: phy0: Cancel RoC ath: phy0: RoC aborted ath: phy0: RoC request on vif: 00:03:7f:4e:a0:cd, type: 1 duration: 500 ath: phy0: Starting RoC period ath: phy0: Channel definition created: 2412 MHz ath: phy0: Assigned next_chan to 2412 MHz ath: phy0: Offchannel duration for chan 2412 MHz : 506705 ath: phy0: ath_chanctx_set_next: current: 2412 MHz, next: 2412 MHz ath: phy0: ath_offchannel_channel_change: offchannel state: ATH_OFFCHANNEL_ROC_START ath: phy0: cur_chan: 2412 MHz, event: ATH_CHANCTX_EVENT_SWITCH, state: ATH_CHANCTX_STATE_IDLE ------------[ cut here ]------------ WARNING: CPU: 0 PID: 3312 at drivers/net/wireless-4.2/ath/ath9k/main.c:2319 Modules linked in: ath9k ath9k_common ath9k_hw ath mac80211 cfg80211 Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit d83520b7cd6e8c5399b1bd0d2f6f9ce733b10454) TEST=none BUG=none Change-Id: I1d92721a820540c29efea18773763801e9972c68 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307333 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307333" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/33/307333/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I0093f9d48c18f31b36af906bd9aa188f21dc445b" commit="945be5def6d38e0614762b5e4fa4a01c95f66a23" commit_message="UPSTREAM: ath9k: setup rxfilter for all chanctx While mac80211 setup this per HW, set same rxfilter configuration for all chanctx. Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit f3771c08282afa1354c2e5a2fdade587f30db4fd) TEST=none BUG=none Change-Id: I0093f9d48c18f31b36af906bd9aa188f21dc445b Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307334 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307334" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/34/307334/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I1cbc553f3cca3d965501c3bb65cbb839e3d7ed3d" commit="9e6882e326d65ab11008f2012fa1ae6d42ab7b87" commit_message="UPSTREAM: ath9k: setup rxfilter when offchannel Setup rxfiler correctly for offchannel ctx. This fix problem we didn't configure rxfilter, next didn't receive probe requests and next failed p2p_find. This was seen when ath9k loaded with use_chanctx=1 Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 1738203ee7291b5e93670d19a663fae03155aebc) TEST=none BUG=none Change-Id: I1cbc553f3cca3d965501c3bb65cbb839e3d7ed3d Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307335 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307335" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/35/307335/2" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I650f636e23435c4f8e9a26b09a39ef378cd94068" commit="bf64435d9258f07de877cdd5495b00514597dbd4" commit_message="power_LoadTest: Open trap window for auto loaded tabs There's a tab that opens on first login for Chromebooks for free offers. Since every login for power_LoadTest is a first login (since the state is cleared), open a window to catch that tab (and any others) which will be closed by the test later. BUG=None TEST=run power_LoadTest.1hour Check that there are only 5 tabs in the background window Change-Id: I650f636e23435c4f8e9a26b09a39ef378cd94068 Reviewed-on: https://chromium-review.googlesource.com/309543 Commit-Ready: Derek Basehore <dbasehore@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="2" gerrit_number="309543" owner_email="dbasehore@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/43/309543/1" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="Ided06df7d51cc193228b3e8344c0de14f9bfa035" commit="4905638f3a4c8d9bf2340da6f2d8c89953405056" commit_message="power_LoadTest: fix names of control variants The new different versions of the test all had power_LoadTest.1hour for the name. This corrects the names for those tests. BUG=None TEST=From workstation: test_that --board <any board> <DUT IP address> power_LoadTest.web_1hour Test will fail since ethernet is connected, but check that it finds the test Change-Id: Ided06df7d51cc193228b3e8344c0de14f9bfa035 Reviewed-on: https://chromium-review.googlesource.com/309544 Commit-Ready: Derek Basehore <dbasehore@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="2" gerrit_number="309544" owner_email="dbasehore@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/44/309544/1" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I39f0ec0d943002b77f95b920f204f31ea99f2cbe" commit="43f3f9127bd43ddc9fa5d45df637513b3cbd6021" commit_message="power_LoadTest: add single page test version This measures the power of an individual page for 5 minutes. BUG=None TEST=from workstation to DUT test_that --board <board> <IP> power_LoadTest on DUT cd /usr/local/autotest ./bin/autotest tests/power_LoadTest/control.single_page --args \ "https://news.google.com" Check that the test runs for 5 minutes with the news.google.com webpage Change-Id: I39f0ec0d943002b77f95b920f204f31ea99f2cbe Reviewed-on: https://chromium-review.googlesource.com/309545 Commit-Ready: Derek Basehore <dbasehore@chromium.org> Tested-by: Matt Sheets <msheets@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="2" gerrit_number="309545" owner_email="dbasehore@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/45/309545/3" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I8fae7e8fc9205f4e587917cb0b4b9d763e37830b" commit="c8a8d18f31ce52f4abf52efec4c8e3daa80b5c4e" commit_message="Add brillo_WifiInterfaceTest. This implements the Brillo PTS wifi interface test: * Tests that a given (default: any) wifi interface is connected to a wireless network with given (default: any) SSID. * Tests that a given (default: any active) wifi interface is configured with an IPv4 address. BUG=b:25341629 TEST=brillo_test_launcher.py -t brillo_WifiInterfaceTest ==> PASS TEST=brillo_test_launcher.py -t brillo_WifiInterfaceTest -A wifi_iface=wlan0 ==> PASS TEST=brillo_test_launcher.py -t brillo_WifiInterfaceTest -A wifi_iface=p2p0 ==> FAIL: Interface p2p0 is not connected to any SSID TEST=brillo_test_launcher.py -t brillo_WifiInterfaceTest -A wifi_ssid=FooNetwork ==> FAIL: No interface is connected to SSID FooNetwork TEST=brillo_test_launcher.py -t brillo_WifiInterfaceTest -A wifi_iface=wlan0 -A wifi_ssid=FooNetwork ==> FAIL: Interface wlan0 is not connected to SSID FooNetwork TEST=brillo_test_launcher.py -t brillo_WifiInterfaceTest -A wifi_iface=notthere ==> FAIL: Interface notthere not listed by iw Change-Id: I8fae7e8fc9205f4e587917cb0b4b9d763e37830b Reviewed-on: https://chromium-review.googlesource.com/309686 Commit-Ready: Gilad Arnold <garnold@chromium.org> Tested-by: Gilad Arnold <garnold@chromium.org> Reviewed-by: Gilad Arnold <garnold@chromium.org> " fail_count="1" gerrit_number="309686" owner_email="garnold@chromium.org" pass_count="0" patch_number="9" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/86/309686/9" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ic105411d353cf79c8e70df89ba36eec99ccf4cf9" commit="8900f631d18bb25a6f6eeb295a7ad2842878379d" commit_message="Add brillo_DiskSizeTest. This implements the Brillo PTS minimum disk size test. BUG=b:25341629 TEST=brillo_test_launcher.py -t brillo_DiskSizeTest ==> PASS TEST=brillo_test_launcher.py -t brillo_DiskSizeTest -A path=/firmware ==> FAIL: Size of device /dev/block/mmcblk0p1 (65488) is less than required (65536) TEST=brillo_test_launcher.py -t brillo_DiskSizeTest -A min_size=262144 ==> FAIL: Size of device /dev/block/mmcblk0p27 (124912) is less than required (262144) Change-Id: Ic105411d353cf79c8e70df89ba36eec99ccf4cf9 Reviewed-on: https://chromium-review.googlesource.com/309780 Commit-Ready: Gilad Arnold <garnold@chromium.org> Tested-by: Gilad Arnold <garnold@chromium.org> Reviewed-by: Gilad Arnold <garnold@chromium.org> " fail_count="1" gerrit_number="309780" owner_email="garnold@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/80/309780/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I4c38fc1b273ae20e9e164c5f37e47401edcd7bf6" commit="bd5f806609b9895d74078d0155e9a8e98fa617ff" commit_message="Add brillo_MemorySizeTest. This implements the Brillo PTS minimum memory size test. BUG=b:25341629 TEST=brillo_test_launcher.py -t brillo_MemorySizeTest ==> PASS TEST=brillo_test_launcher.py -t brillo_MemorySizeTest -A min_total=1048576 ==> FAIL: MemTotal (959964 kB) is less than required (1048576 kB) TEST=brillo_test_launcher.py -t brillo_MemorySizeTest -A min_total=880640 -A min_free=879616 ==> FAIL: MemFree (843168 kB) is less than required (879616 kB) TEST=brillo_test_launcher.py -t brillo_MemorySizeTest -A min_free=879616 ==> ERROR: Requiring more free memory (879616) than total memory (32768) Change-Id: I4c38fc1b273ae20e9e164c5f37e47401edcd7bf6 Reviewed-on: https://chromium-review.googlesource.com/309762 Commit-Ready: Gilad Arnold <garnold@chromium.org> Tested-by: Gilad Arnold <garnold@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> " fail_count="1" gerrit_number="309762" owner_email="garnold@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/62/309762/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I661110cc7021f6d17937688787ea4f5f4b82973d" commit="20adb53c55acf8e28b19006ced473ed7cff08807" commit_message="pd: add more power improvements to PD task Added more improvements to power consumption when using CONFIG_USB_PD_LOW_POWER. On the TCPC, when this option is defined, then decrease the PD task wake interval when we are presenting Rd, we don't have a connection, AND we haven't dual-role toggled recently. This shouldn't affect connection time because we will get an interrupt when VBUS is detected. Note: we can't use the low power task wake interval when we are connected because we need to monitor CC line for Rp change and we can't do this when we are presenting Rp because we need to quickly detect loss of Rd. BUG=chrome-os-partner:45010 BRANCH=none TEST=tested on glados. verified we connect to a charger in S0 and S5. and verified that in S5, we spend >99% of our time in deepsleep (as measured by idlestats console command). note, that when testing EC and PD must both define CONFIG_USB_PD_LOW_POWER to get maximum power improvements. Change-Id: I661110cc7021f6d17937688787ea4f5f4b82973d Signed-off-by: Alec Berg <alecaberg@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309310 Reviewed-by: Vincent Palatin <vpalatin@chromium.org> " fail_count="2" gerrit_number="309310" owner_email="alecaberg@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/10/309310/2" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I04441fb8339652cf073689177175a98f28807897" commit="1f3faa5ba80cec2f47287c98f42471a3f5481d5d" commit_message="pd: turn on CONFIG_USB_PD_LOW_POWER by default Define CONFIG_USB_PD_LOW_POWER by default to save power on both TCPM and TCPC side by waking PD task less often when possible. BUG=none BRANCH=none TEST=test on glados and samus. Change-Id: I04441fb8339652cf073689177175a98f28807897 Signed-off-by: Alec Berg <alecaberg@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309311 Reviewed-by: Vincent Palatin <vpalatin@chromium.org> " fail_count="1" gerrit_number="309311" owner_email="alecaberg@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/11/309311/2" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Icd2306d25d5863b0fc3379e46885a227efb23cca" commit="b3bcb4d2105af1cbe03e3c8d737c4b088cfe19b7" commit_message="stm32f0: i2c: Set timing register values by port clock source I2C1 may be clocked by HSI or SCLK. I2C2 is always clocked by PCLK. Therefore, apply different timing register values according to the selected clock source for a port. BUG=chrome-os-partner:46188 BRANCH=None TEST=Manual on glados_pd. Verify slave i2c communication is functional. Change-Id: Icd2306d25d5863b0fc3379e46885a227efb23cca Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309781 Commit-Ready: Shawn N <shawnn@chromium.org> Tested-by: Shawn N <shawnn@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> " fail_count="0" gerrit_number="309781" owner_email="shawnn@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/81/309781/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I4443951ccc9b5199f5fdb06433b3a60a849aed70" commit="3af106fb2a844f4e5bed81192fe0ab34bb20bcc5" commit_message="autotest (wifi): update AP build for stumpy and panther Update the AP image for wifi cells to R47-7424.0.0-b10 BUG=chromium:548356 TEST=updated stumpy with test_that network_WiFi_UpdateRouter pre-cq-configs: mixed-wificell-pre-cq Change-Id: I4443951ccc9b5199f5fdb06433b3a60a849aed70 Reviewed-on: https://chromium-review.googlesource.com/309262 Commit-Ready: Rebecca Silberstein <silberst@chromium.org> Tested-by: Rebecca Silberstein <silberst@chromium.org> Reviewed-by: Tien Chang <tienchang@chromium.org> " fail_count="3" gerrit_number="309262" owner_email="silberst@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/62/309262/2" remote="cros" total_fail_count="3"/><pending_commit branch="master" change_id="I5d331d354fcfdc3c4d44a9b8a4a3ac97bd04981b" commit="47b9605a512348ffb75d78a10bb994e06b3a1a66" commit_message="[Autotest] Add device id to touch_* test gesture filenames. As more and more platforms have touchpads and touchscreens sourced from several companies, identify recorded gesture files with the hardware id of the device in order to differentiate. This change will prevent bugs like the one where the Cypress daisy files failed on Atmel daisy. Renames all device files to have the same format: <platform>_<input type>_<hwid>_<gesture-name> Also make all tests with per-platform gestures use the same common code to find these renamed gesture files. Finally, this change restructures how device infomation is saved by adding a device class with the pertinant information. We now find the hardware and firmware ids (if present) and save them in this new class, along with the previously found node, name, and folder path. Now output firmware and hardware info in all tests for debugging. TEST=ran all affected tests across several devices BUG=chromium:488282 Change-Id: I5d331d354fcfdc3c4d44a9b8a4a3ac97bd04981b Reviewed-on: https://chromium-review.googlesource.com/309360 Commit-Ready: Katherine Threlkeld <kathrelkeld@chromium.org> Tested-by: Katherine Threlkeld <kathrelkeld@chromium.org> Reviewed-by: Mussa Kiroga <mussa@chromium.org> " fail_count="0" gerrit_number="309360" owner_email="kathrelkeld@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/60/309360/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I781f6f8227867ea9c0e265b3064f48602c0f5f07" commit="d277ff920654b5904d2b13b10e838581d9a91cac" commit_message="nuc: Add state machines to handle i2c master stall bus and call i2c_xfer again. Create two state machines SMB_WRITE_SUSPEND and SMB_READ_SUSPEND to handle i2c master stall bus and call i2c_xfer again. Notice we should disable i2c interrupt since cannot read/write SDA reg to clear interrupt pending bit. Modified drivers: 1. i2c.c: Modified to handle calling i2c_xfer twice or more. BUG=chrome-os-partner:34346 TEST=make buildall -j; test nuvoton IC specific drivers BRANCH=none Change-Id: I781f6f8227867ea9c0e265b3064f48602c0f5f07 Signed-off-by: Mulin Chao <mlchao@nuvoton.com> Reviewed-on: https://chromium-review.googlesource.com/309381 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="309381" owner_email="mlchao@nuvoton.com" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/81/309381/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ic09cef117563ee56d59dae1a538ef5512cf75b91" commit="37f6bf18b64fe24f31b54a9e14466c2c343b109e" commit_message="Terra: Add bluetooth device ID BUG=chrome-os-partner:46929 TEST=Verified SDP output for DI contains 00E0:2445:0400 Change-Id: Ic09cef117563ee56d59dae1a538ef5512cf75b91 Reviewed-on: https://chromium-review.googlesource.com/309623 Commit-Ready: Huki Huang <huki.huang@intel.com> Tested-by: Huki Huang <huki.huang@intel.com> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="1" gerrit_number="309623" owner_email="huki.huang@intel.com" pass_count="0" patch_number="1" project="chromiumos/overlays/board-overlays" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/board-overlays" ref="refs/changes/23/309623/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I214388538549661a8e99714df6b5f0101746082f" commit="3e10c9d0128d503e0746b8953b7f72adf3cd5fd1" commit_message="UPSTREAM: phy: core: Fixup return value of phy_exit when !pm_runtime_enabled When phy_pm_runtime_get_sync() returns -ENOTSUPP, phy_exit() also returns -ENOTSUPP if !phy->ops->exit. Fix it. Also move the code to override ret close to the code we got ret. I think it is less error prone this way. BUG=chrome-os-partner:46308 TEST=w/ series both USB ports are happy Change-Id: I214388538549661a8e99714df6b5f0101746082f Signed-off-by: Axel Lin <axel.lin@ingics.com> Acked-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Doug Anderson <dianders@chromium.org> (cherry picked from commit 736b67a32062240592aad49033859f9712dd18ca) Reviewed-on: https://chromium-review.googlesource.com/308543 Commit-Ready: Douglas Anderson <dianders@chromium.org> Tested-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: Andrew Bresticker <abrestic@chromium.org> " fail_count="0" gerrit_number="308543" owner_email="dianders@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/43/308543/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I2d76270c3b94039c98b7510c53bc2d8a35b0b80a" commit="76fbf26d705fa38e7efe55a45429faa7b6e9dbbf" commit_message="Add jetstream_cq hwtest to the commit queue, nonblocking. BUG=chrome-os-partner:45210 TEST=tested in roundabout ways Change-Id: I2d76270c3b94039c98b7510c53bc2d8a35b0b80a Reviewed-on: https://chromium-review.googlesource.com/309577 Commit-Ready: John Carey <ranix@google.com> Tested-by: John Carey <ranix@google.com> Reviewed-by: John Carey <ranix@google.com> Reviewed-by: David James <davidjames@chromium.org> Reviewed-by: Adam Haberlach <ahaberlach@chromium.org> " fail_count="1" gerrit_number="309577" owner_email="ranix@google.com" pass_count="0" patch_number="3" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/77/309577/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I129123997c1f539d9248bd25fdb91120dcf02395" commit="14daab7f6ff0373ba42ef463d3fd2827eb405ef2" commit_message="vboot: fix text heights getting smaller get_text_width calls get_image_size repeatedly for each letter in a text to calculate the total width of the text being printed on screen. Since it reuses the height returned from get_image_size, the height can get smaller and smaller because of integer rounding. This patch fixes the issue by not carrying over the returned height to the next iteration. BUG=chromium:502066 BRANCH=tot TEST=Tested on Glados Change-Id: I129123997c1f539d9248bd25fdb91120dcf02395 Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309771 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="1" gerrit_number="309771" owner_email="dnojiri@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/71/309771/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="If7c756f758dc312d54878374d6b7bb0a2b988260" commit="df8f82f71a55791968f6d0828d98a7532830836a" commit_message="Remove extra space in file path. There is an extra space in the path to a test video. Causing the video to not load. BUG=None. TEST=Test on link. Change-Id: If7c756f758dc312d54878374d6b7bb0a2b988260 Reviewed-on: https://chromium-review.googlesource.com/309905 Commit-Ready: Mussa Kiroga <mussa@chromium.org> Tested-by: Mussa Kiroga <mussa@chromium.org> Reviewed-by: Rohit Makasana <rohitbm@chromium.org> " fail_count="0" gerrit_number="309905" owner_email="mussa@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/05/309905/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I5bccb57ace1511f49522849c5ab8c1a3cf99d54d" commit="7dd040bd721bde74981f711b76578fc03f0d2dd2" commit_message="bypass broken screen after attempting to bypass insert screen This patch integrates broken screen bypass code with insert screen bypass code. It means we first attempt to bypass the insert screen and waits for a ping connection. If the dut is running on old firmware, it should boot and respond to ping. If it doesn't, it implies the dut is running on the new firmware and stuck at the broken screen. Then, we take the broken screen bypass action. This is needed for the boards which have to run on both tot firmware and branched firmware. BUG=chromium:501060,chrome-os-partner:46752 BRANCH=tot TEST=test_that -b veyron_jerry suite:faft_bios Change-Id: I5bccb57ace1511f49522849c5ab8c1a3cf99d54d Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309558 Reviewed-by: Wai-Hong Tam <waihong@chromium.org> " fail_count="2" gerrit_number="309558" owner_email="dnojiri@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/58/309558/1" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="Ic25f580c608f21aab0f006bc304a92ac8c8e23d9" commit="355f51f675dff3c8c86be5a3319a61f54baa2ac4" commit_message="lint: add check for unittest module names Make sure people don't actually try to use foo_unittests.py. BUG=None TEST=tests pass & no new lint errors Change-Id: Ic25f580c608f21aab0f006bc304a92ac8c8e23d9 Reviewed-on: https://chromium-review.googlesource.com/309610 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Don Garrett <dgarrett@chromium.org> " fail_count="2" gerrit_number="309610" owner_email="vapier@chromium.org" pass_count="0" patch_number="1" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/10/309610/1" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="Idb9a3bd8ea091b93d1763703930a4f3200ae8253" commit="57f89b375d994a99e99009fbe35e75e23669cd5d" commit_message="Add terra builder config BUG=chrome-os-partner:46775 TEST=None Change-Id: Idb9a3bd8ea091b93d1763703930a4f3200ae8253 Reviewed-on: https://chromium-review.googlesource.com/308252 Commit-Ready: Bernie Thompson <bhthompson@chromium.org> Tested-by: Bernie Thompson <bhthompson@chromium.org> Reviewed-by: Shawn N <shawnn@chromium.org> " fail_count="0" gerrit_number="308252" owner_email="bhthompson@chromium.org" pass_count="0" patch_number="1" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/52/308252/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iba29d53918245714ffcf6c87f42d1fa98be028b8" commit="5d8fb1600360056bc8d77152e6e385803d8ce273" commit_message="samus: increase POWERBTN task stack size BUG=chromium:547879 BRANCH=samus TEST=make BOARD=samus Change-Id: Iba29d53918245714ffcf6c87f42d1fa98be028b8 Signed-off-by: Alec Berg <alecaberg@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309142 Reviewed-by: Shawn N <shawnn@chromium.org> (cherry picked from commit 12d924b7a05ddcd64a6d845faba5d6dc348c4bbd) Reviewed-on: https://chromium-review.googlesource.com/309553 " fail_count="2" gerrit_number="309553" owner_email="alecaberg@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/53/309553/1" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I812c7573494dfed149d2cc6ffcb184abb78a6f60" commit="fcbcb8d4647dc22330cb5da800f871d36822bd08" commit_message="lib/launch_control: Add library. Move two libraries for working with Launch Control over, so that they can be shared between multiple Site Specific cbuildbot builders. BUG=chromium:547996 TEST=Unitests Change-Id: I812c7573494dfed149d2cc6ffcb184abb78a6f60 Reviewed-on: https://chromium-review.googlesource.com/308754 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> " fail_count="2" gerrit_number="308754" owner_email="dgarrett@chromium.org" pass_count="0" patch_number="3" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/54/308754/3" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-2015.07" change_id="I4d34905c04effd54d0d0edf8809e192283db2ca3" commit="48ebb5fe5402e53adcb025960526ec725be8f908" commit_message="t210: lp0_resume: clear the MC_INTSTATUS if MC_INTMASK was 0 The MC/SMMU should be resumed by the kernel. And the unexpected value in the MC_INTSTATUS should be cleared before that. Or it will cause some noisy MC interrupt once we enable the IRQ in the kernel. BUG=chrome-os-partner:46796 BRANCH=none TEST=LP0 suspend/resume test and the EMEM decode/arbitration errors should not be observed on resume. Change-Id: I4d34905c04effd54d0d0edf8809e192283db2ca3 Signed-off-by: Joseph Lo <josephl@nvidia.com> Reviewed-on: https://chromium-review.googlesource.com/309248 Reviewed-by: Tom Warren <twarren@nvidia.com> Reviewed-by: Andrew Bresticker <abrestic@chromium.org> Commit-Queue: Joseph Lo <yushun.lo@gmail.com> Tested-by: Joseph Lo <yushun.lo@gmail.com> (cherry picked from commit 13cbcaf441bd762af9cf00eff24eb7709db38d95) Signed-off-by: Joseph Lo <josephl@nvidia.com> Reviewed-on: https://chromium-review.googlesource.com/309497 " fail_count="0" gerrit_number="309497" owner_email="josephl@nvidia.com" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/97/309497/1" remote="cros" total_fail_count="0"/><lkgm version="7593.0.0-rc6"/></manifest> |
