| <?xml version="1.0" encoding="utf-8"?><manifest revision="72836b292c84559e40b736edaa4e8ecf2512cfcd"> |
| <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="d599c6602bd3cc4c4bf2e3fb7aebb214ee8ea775" upstream="refs/heads/master"> |
| <copyfile dest="AUTHORS" src="AUTHORS"/> |
| <copyfile dest="LICENSE" src="LICENSE"/> |
| </project> |
| <project name="chromiumos/manifest" path="manifest" revision="db2769a8dc6fee7ae83ba4f0c9660c68b1b3d2cc" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/board-overlays" path="src/overlays" revision="adcf3f612456294d81cf67df2eba9c62797d76a3" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="45e1ab8ad44275279eb680cb3fb93fcbcfe82f64" 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="abeb062a0a2a53d5a953c09f181583767ce10c76" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="9b9f20f7e7e6ba7c01cc1facfc8baaa747a2cdbd" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="b5df134d6ad3739a7de3af6081048b9ec707d5c4" 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="7e31d2650b2c5c56303dd086e53d35cd9b594a1c" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory" path="src/platform/factory" revision="1e1dbef30db4c912b28e39b7aca16028116c9497" 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="d8d12dfd3c95e2376d3f6028532969cf8bd69d61" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtpd" path="src/platform/mtpd" revision="d7e73ba3170e8a0c1f0deecad6735034def58ee5" 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="ecbd58958f83b7b32068f328ddd605ba732c7052" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_firmware_test" path="src/platform/touch_firmware_test" revision="9ce13ccbf099a9c5c3c7d54f2f8e445bb711c114" 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="350e5718a449371f2e442771b7f5ed8629a5bf43" 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="e85f6948f0ae8a147ec4d51421ca1bc63f557261" 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="3efaf3da96e671ce6c95be001108b532acb483e1" 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="bcda440d67bace74b8aefa10e414ba7197f7dcbe" 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="8d24ae8edd92c1214f4506a3b4715abf3e02dc6e" 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="4c1485b4b211eab48baf22a449673fcc5928fe17" 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="37a829f88ade57b1d1ad56c9b26b4ca8d86621da" 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="85f61c5f6240d236fc2d5853b2396b54eedfea18" 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="08ff37fc957445dd31646d0dbead4edc0253306f" 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="ce3ec9a734a54ae2b3805c4590c485e3a50c55ba" 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="e1cc77edc5e2d762c7374656636da98a19838b98" upstream="refs/heads/chromeos-3.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="8512717d5c33918c132b56b44ed296ba4e2f38f7" 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="90be3d6efdbaba0941f99a8ed7b04249bbd2699a" 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="5a945def25005e9d88290adb2ab0e3cc340e1c34" 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="Ie47bf5cd64f314a9bcaa1373a92b94ae0ce17115" commit="21b2c9fdb2a812b09e206a4da98ec216b1f9d6ce" commit_message="UPSTREAM: ath10k: configure copy engine 5 for HTT messages Currently target to host (T2H) HTT messages are received at copy engine 1. These messages are processed by HTC layer in both host and target. To avoid HTC level processing overhead in both host and target, the unused copy engine 5 is being used for receiving HTT T2H messages. This will speedup the receive data processing as well as htt tx completion. Hence host and target copy engine configuration tables are updated to enable CE5 pipe. The in-direction HTT mapping is now pointing to CE5 for all HTT T2H. Moreover HTT send completion messages are polled from HTC handler as CE 4 is not interrupt-driven. For faster tx completion, CE4 polling needs to be done whenever CE pipe which transports HTT Rx (target->host) is processed. This avoids overhead of polling HTT messages from HTC layer. Servicing CE 4 faster is helping to solve "failed to transmit packet, dropping: -105". Reviewed-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit a70587b3389ae4a97f2b51153cc86b4c1769dcf5) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ie47bf5cd64f314a9bcaa1373a92b94ae0ce17115 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310121 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310121" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/21/310121/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I4a97852a915b6fe2864b42a578087a017fec655c" commit="eb80a66356f51f955736e3120ab0cec6f351f9ae" commit_message="UPSTREAM: ath10k: remove unused dl_is_polled Since polling for received messages not supported, remove unused dl_is_polled. Reviewed-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 0da64f19f01a6dabc4a55c1ee9cef430fcb47f4a) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I4a97852a915b6fe2864b42a578087a017fec655c Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310122 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="310122" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/22/310122/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I4f4cafa79c62742fdd66202fa2ce8a7abce571ba" commit="f16699613f8246bfff1fc71970b1c3474beead06" commit_message="UPSTREAM: ath10k: remove htc polling for tx completion Since polling for tx completion is handled whenever target to host messages are received, removing the unnecessary polling mechanism for send completion at HTC level. Reviewed-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 400143e45d39fcedb5106c3aa212746a80a61f7c) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I4f4cafa79c62742fdd66202fa2ce8a7abce571ba Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310123 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="310123" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/23/310123/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I50ff82fbd425f06485e8394af4a721ca0a66dc14" commit="8d3190db5020e01358e01ac49b3bebe3df7452f1" commit_message="UPSTREAM: ath10k: disable PCI PS for QCA988X and QCA99X0 This patch disables PCI PS for QCA988X and QCA99X0, Since PCI PS is validated for QCA6174, let it be enabled only for QCA6174. It would be better to execute PCI PS related functions only for the supported devices. PCI time out issue is observed with QCA99X0 on x86 platform, We will disable PCI PS for QCA988X and QCA99X0 until PCI PS is properly implemented. Taking and releasing ps_lock is causing higher CPU consumption. Michal Kazior suggested ps_lock overhead to be reworked so that ath10k_pci_wake/sleep functions are called less often, i.e. move the powersave logic up (only during irq handling, tx path, submitting fw commands) but that's a bigger change and can be implemented later. Signed-off-by: Anilkumar Kolli <akolli@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 1aaf8efba0aeb25eb5858b19472badaa54a41a38) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I50ff82fbd425f06485e8394af4a721ca0a66dc14 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310124 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="310124" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/24/310124/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I6c34ebd44587f859f743f2ea29f6236299b2dda1" commit="a57b3867cce9c2cd0b7ba7e7d42521548f7cb757" commit_message="UPSTREAM: ath10k: make fw stats prints specific to firmware version The patch makes debug stats prints fw specific by adding a new member in wmi_ops. That way it's easier to add fw_stats support to 10.4 firmware. Signed-off-by: Manikanta Pubbisetty <c_mpubbi@qti.qualcomm.com> Signed-off-by: Tamizh Chelvam <c_traja@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit bc6f9ae6043a219b5afadf0391ce77db401a966f) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I6c34ebd44587f859f743f2ea29f6236299b2dda1 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310125 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="310125" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/25/310125/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="Iae5437df2f5d89226f2acefc59d23cc9263e2e95" commit="4e524546de8411ad967cbcea9ed5b9ebeeffc57e" commit_message="HACK: ath10k mgmt frame tx debug now enabled by ATH10K_DBG_MGMT BUG=chrome-os-partner:32568 TEST=built storm image and checked /var/log/messages When JETSTREAM_DEBUG=1, the driver uses ATH10K_DBG_MGMT bit to enable debug messages showing mgmt frame TX instead of ATH10K_DBG_WMI. This allows the use of ATH10K_DBG_WMI without seeing all the beacon debug messages. If the beacon messages are needed, use ATH10K_DBG_MGMT. This change has no effect unless ATH10K_DBG_MGMT or ATH10K_DBG_WMI are enabled for debugging. Signed-off-by: Bill Hegardt <bhegardt@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/250660 Reviewed-by: Toshi Kikuchi <toshik@chromium.org> Commit-Queue: Bill Hegardt <bhegardt@google.com> Tested-by: Bill Hegardt <bhegardt@google.com> Reviewed-by: Bill Hegardt <bhegardt@google.com> (cherry-picked from commit 8e98f9b852508190c18b19ea9b6231dc212d10b2) source: wireless-3.18) Change-Id: Iae5437df2f5d89226f2acefc59d23cc9263e2e95 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310126 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="310126" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/26/310126/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I97e1ea2d4a1a92d57a455f98d569cbc3c58dd8da" commit="ff2be8fbaf49bd9feb160c358817e196f2a180c9" commit_message="FROMLIST: ath10k: Bypass PLL setting on target init for QCA9888 Some of of qca988x solutions are having global reset issue during target initialization. Bypassing PLL setting before downloading firmware and letting the SoC run on REF_CLK is fixing the problem. Corresponding firmware change is also needed to set the clock source once the target is initialized. Since 10.2.4 firmware is having this ROM patch, applying skip_clock_init only for 10.2.4 firmware versions. Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com> BUG=None TEST=build/boot on storm suceeded. Setup Storm board as AP using hostapd and connected to the board using another device. Device was able to connect to the internet and load multiple websites. Reviewed-on: https://chromium-review.googlesource.com/253494 Reviewed-by: Toshi Kikuchi <toshik@chromium.org> Commit-Queue: Toshi Kikuchi <toshik@chromium.org> Tested-by: Toshi Kikuchi <toshik@chromium.org> (cherry-picked from commit 07276332c720c2e372d6840c217dea42bb1be2b3) source: wireless-3.18) Change-Id: I97e1ea2d4a1a92d57a455f98d569cbc3c58dd8da Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310127 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310127" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/27/310127/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I2182e6d5f1243960561fba9567f0a1e6ebd2d7ca" commit="257873fdf65d347a29bc8939d1e9874c8fc0203a" commit_message="FROMLIST: ath10k: Make HTT fill size configurable The HTT RX ring is replenished with a maximum of 16 buffers, but this might be insufficient when RX traffic is high. Not having enough RX buffers throttles the FW, resulting in low throughput. This patch adds a module parameter to adjust the fill size based on the platform/usage. Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com> BUG=None TEST=build/boot on storm suceeded. Setup Storm board as AP using hostapd and connected to the board using another device. Device was able to connect to the internet and load multiple websites. Reviewed-on: https://chromium-review.googlesource.com/253504 Reviewed-by: Toshi Kikuchi <toshik@chromium.org> Tested-by: Toshi Kikuchi <toshik@chromium.org> Commit-Queue: Toshi Kikuchi <toshik@chromium.org> (cherry picked from commit aca77a1dde0d90bd202d0b7e007ccc126799685a) (source: wireless-3.18) Change-Id: I2182e6d5f1243960561fba9567f0a1e6ebd2d7ca Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310128 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310128" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/28/310128/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I38e3d58d98ebe32389e7a1959a64179f30712387" commit="515e843a046ff0a2c26a183f9b3a7bbeb981901a" commit_message="CHROMIUM: ath10k: add support for configuring GPIO via WMI This patch add support to configure GPIO pins through wmi functions. Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@codeaurora.org> Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> BUG=None TEST=build/boot. Load ath10k_core with modparam set enable_smart_antenna=1, bring up AP mode using hostapd and connect a station to this AP. Device was able to connect to the internet and load multiple websites. This testing is done on AP148. Reviewed-on: https://chromium-review.googlesource.com/257430 Reviewed-by: Toshi Kikuchi <toshik@chromium.org> Commit-Queue: Yixiang Li <yixiang@google.com> Tested-by: Yixiang Li <yixiang@google.com> (cherry picked from commit 8160cb1a46f2750f33247c7ddc1e645e2613d54e) source: wireless-3.18) Change-Id: I38e3d58d98ebe32389e7a1959a64179f30712387 Reviewed-on: https://chromium-review.googlesource.com/310129 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310129" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/29/310129/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I5005895cbcf76f3d4389723b0af7b9159f1137cf" commit="0f2c8a323631055dfd5b19547cb581b40b2f7d41" commit_message="CHROMIUM: Read gpio configuration for smart antenna from DT Read gpio pins and gpio functions used for smart antenna from DT. DT definition for ath10k gpio configuration will look like the following and can be added to corresponding pci devices. pci { pcie@0 { ... ... ath10k@0,0 { ... qcom,ath10k-sa-gpio = <1 2 3 4>; qcom,ath10k-sa-gpio-func = <1 2 3 4>; }; }; }; Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@codeaurora.org> BUG=chrome-os-partner:36603 TEST=build/boot. Load ath10k_core with modparam set enable_smart_antenna=1, bring up AP mode using hostapd and connect a station to this AP. Device was able to connect to the internet and load multiple websites. This testing is done on AP148. (cherry picked from commit 968c8deb726fdcd3b5c8038186400ff143c845d3) (source: wireless-3.18) Change-Id: I5005895cbcf76f3d4389723b0af7b9159f1137cf Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310130 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310130" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/30/310130/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I4fefdde10c8e431767d2f17f09bad07e5f1383cc" commit="eba49ca750f588e9aeb02778bfe967e6d2cab86c" commit_message="CHROMIUM: Add smart antenna APIs This patch defines APIs used for smart antenna algorithm. Has a full implementation os wmi ops used for smart antenna configuration. There is a new module param which is used to enable smart antenna logic on host and firmware. Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@codeaurora.org> BUG=chrome-os-partner:37796 TEST=build/boot. Load ath10k_core with modparam set enable_smart_antenna=1, bring up AP mode using hostapd and connect a station to this AP. Device was able to connect to the internet and load multiple websites. This testing is done on AP148. (cherry picked from commit 9a81c88af18aeb7c732184408e569275273d14df) (source: wireless-3.18) Change-Id: I4fefdde10c8e431767d2f17f09bad07e5f1383cc Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310131 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310131" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/31/310131/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ic47af77277a3f358343e57e93b7bc84ee3585fab" commit="d4d2c97b9c94936c6a6d841377b7824fc19c392d" commit_message="CHROMIUM: Add debugfs interface to test some of smart antenna APIs smart_ant_enable : To enable/disable smart antenna support. This configuration should be the first one as soon as wifi interface is up and running. echo 0|1 > /sys/kernel/debug/ieee80211/phyX/ath10k/smart_ant_enable smart_ant_tx_ant: To slect a tx antenna combination for smart antenna for a particular peer. echo <peer_mac_separated by colon (:)> <antenna_combination> > /sys/kernel/debug/ieee80211/phyX/ath10k/smart_ant_tx_ant smart_ant_rx_ant: To select an antenna combination for Rx. echo <antenna_combination> > /sys/kernel/debug/ieee80211/phyX/ath10k/smart_ant_rx_ant smart_ant_train_info: To trigger training on data packets. echo <peer_mac> <ratecode> <antenna_combination> <num_pkts> > /sys/kernel/debug/ieee80211/phyX/ath10k/smart_ant_train_info Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@codeaurora.org> BUG=chrome-os-partner:37796 TEST=build/boot. Load ath10k_core with modparam set enable_smart_antenna=1, bring up AP mode using hostapd. Enable smart antenna from debugs as mentioned in the commit log and connect a station to this AP. Try configuring other smart antenna debugfs interfaces and check the kernel log (debug_mask=0x4000) for API effect. Device was able to connect to the internet and load multiple websites. This testing is done on AP148. (cherry picked from commit 48cc51589388eb2bc871e2e29a2608f31a6d1a53) (source: wireless-3.18) Change-Id: Ic47af77277a3f358343e57e93b7bc84ee3585fab Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310132 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310132" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/32/310132/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Iad568e8c83696af16a9a5b086b5ff4f1b2d2940a" commit="f5a935842d118f7a7d2d7b55c4dbe7ebf3ef0ba6" commit_message="Revert "HACK: ath10k mgmt frame tx debug now enabled by ATH10K_DBG_MGMT" BUG=chrome-os-partner:32568 TEST=built whirlwind image and checked /var/log/messages This reverts commit 8e98f9b852508190c18b19ea9b6231dc212d10b2. It is obsolete due to changes in the 10.2.4.48-2 radio firmware Signed-off-by: Bill Hegardt <bhegardt@chromium.org> (cherry picked from commit f69d10c06da8726b748d19d657231339c43bf850) (source: wireless-3.18) Change-Id: Iad568e8c83696af16a9a5b086b5ff4f1b2d2940a Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310133 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310133" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/33/310133/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I67922cf220f938609912c9d5f406ad260e7f09ce" commit="a722f66b9ccd57dd9fa8aa1891f28529ee747dee" commit_message="FROMLIST:ath10k: Debugfs entry to enable/disable BTC feature As some radio have no connection with BT modules, enable the BTC feature will has some side effect if the radio's GPIO connect with any other HW modules. Add the control switcher "btc_feature" at debugfs and set the feature as disable by default to avoid such case. BUG=chrome-os-partner:40009 TEST=build/boot on storm succeeded, to enable this feature, execute: echo 1 > /sys/kernel/debug/ieee80211/phyX/ath10k/btc_feature To disable: echo 0 > /sys/kernel/debug/ieee80211/phyX/ath10k/btc_feature Signed-off-by: Yanbo Li <yanbol@qca.qualcomm.com> (cherry picked from commit 874494ea87129f09d84ad484bd85b5c8e3396194) (source: wireless-3.18) Change-Id: I67922cf220f938609912c9d5f406ad260e7f09ce Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310134 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310134" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/34/310134/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I508fbc9a1833b1e62262972cd90cdc4541cc5e24" commit="d09e4332da68689a23ade20105358ed205ad8b4f" commit_message="Enable smart antenna API by default. BUG=chrome-os-partner:39674 TEST=Run WiFi performance test and also checked smart antenna config. (cherry picked from commit a58c49235c804593a8f326adbbb20b890a3e4037) (source: wireless-3.18) Change-Id: I508fbc9a1833b1e62262972cd90cdc4541cc5e24 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310135 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Yixiang Li <yixiang@google.com> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Yixiang Li <yixiang@google.com> " fail_count="1" gerrit_number="310135" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/35/310135/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I6f78f302b1f9ad7bd90d9b35d43789ae32e688ec" commit="3b6bef3d753f25e3d83251c1369b8b60b8386507" commit_message="CHROMIUM: PRIVATE: ath10k: Set default antenna when loading driver Currently, ath10k doesn't set default antenna when smart antenna is disabled. Set default antenna during driver load. We do this by adding a new supported value "WMI_SMART_ANT_DISABLED_ANT_SEL" to the existing smart antenna wmi command that allows the FW to set the default antenna irrespective of the availability of Smart Antenna. Default antenna is set to 2. Also use 2 different default values between 2G and 5G radios. Also Becaon transmission should take the default antenna. So change this to default antenna as well. BUG=chrome-os-partner:39682 TEST=build/boot on storm. After the DUT is up, probe the gpio pins corresponding to antenna. Value should be 010 (cherry picked from commit b84f7193617171ef6fb809a00dd267edd28bce67) (source: wireless-3.18) Change-Id: I6f78f302b1f9ad7bd90d9b35d43789ae32e688ec Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310136 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310136" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/36/310136/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Iadb92412e564c36ba25bce761385f50897721c74" commit="a6f2e2f574e60de48259e78193e01dc792709c16" commit_message="CHROMIUM:PRIVATE:ath10k Fix IOT issue for 256-QAM mode in 2G band BUG=chrome-os-partner:41316 TEST=256 QAM in 2G band is working with Asus PCIE AC68 client and Samsung S4 client with vendor_vht enabled in hostapd. Signed-off-by: Yixiang Li <yixiang@chromium.org> (cherry picked from commit 088c949614b38feaefe80ad8e7231015069f6cf7) (source: wireless-3.18) Change-Id: Iadb92412e564c36ba25bce761385f50897721c74 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310137 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Yixiang Li <yixiang@google.com> " fail_count="0" gerrit_number="310137" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/37/310137/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Iceb85368e5889d700a50588ade00fd36e66ff13d" commit="30c867f7f008fc622fceb9eb898f53351e952a7d" commit_message="CHROMIUM:PRIVATE:ath10k: Force driver initialization immediately after probe Workaround for firmware download failure on startup. Cherry-picked from factory-whirlwind-6812.41.B-chromeos-3.14 Branch, originally suggested for BUG=chrome-os-partner:38594. TEST=Using test/reboot script, continuously reboot 4 units for 2 day/nights. BUG=chrome-os-partner:41925 Signed-off-by: Yuji Sasaki <sasaki@chromium.org> (cherry picked from commit af32a8554c37f3af283b6347b3ab88c51f386dc9) (source: wireless-3.18) Change-Id: Iceb85368e5889d700a50588ade00fd36e66ff13d Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310138 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="310138" owner_email="arnagara@codeaurora.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/38/310138/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I3679f247a66184e3a290ded9ca10cd514fcd2979" commit="66a82e75f63bfc2807555ec1e1c790867d6391d6" commit_message="UPSTREAM: mm, compaction: pass classzone_idx and alloc_flags to watermark checking Compaction relies on zone watermark checks for decisions such as if it's worth to start compacting in compaction_suitable() or whether compaction should stop in compact_finished(). The watermark checks take classzone_idx and alloc_flags parameters, which are related to the memory allocation request. But from the context of compaction they are currently passed as 0, including the direct compaction which is invoked to satisfy the allocation request, and could therefore know the proper values. The lack of proper values can lead to mismatch between decisions taken during compaction and decisions related to the allocation request. Lack of proper classzone_idx value means that lowmem_reserve is not taken into account. This has manifested (during recent changes to deferred compaction) when DMA zone was used as fallback for preferred Normal zone. compaction_suitable() without proper classzone_idx would think that the watermarks are already satisfied, but watermark check in get_page_from_freelist() would fail. Because of this problem, deferring compaction has extra complexity that can be removed in the following patch. The issue (not confirmed in practice) with missing alloc_flags is opposite in nature. For allocations that include ALLOC_HIGH, ALLOC_HIGHER or ALLOC_CMA in alloc_flags (the last includes all MOVABLE allocations on CMA-enabled systems) the watermark checking in compaction with 0 passed will be stricter than in get_page_from_freelist(). In these cases compaction might be running for a longer time than is really needed. Another issue compaction_suitable() is that the check for "does the zone need compaction at all?" comes only after the check "does the zone have enough free free pages to succeed compaction". The latter considers extra pages for migration and can therefore in some situations fail and return COMPACT_SKIPPED, although the high-order allocation would succeed and we should return COMPACT_PARTIAL. This patch fixes these problems by adding alloc_flags and classzone_idx to struct compact_control and related functions involved in direct compaction and watermark checking. Where possible, all other callers of compaction_suitable() pass proper values where those are known. This is currently limited to classzone_idx, which is sometimes known in kswapd context. However, the direct reclaim callers should_continue_reclaim() and compaction_ready() do not currently know the proper values, so the coordination between reclaim and compaction may still not be as accurate as it could. This can be fixed later, if it's shown to be an issue. Additionaly the checks in compact_suitable() are reordered to address the second issue described above. The effect of this patch should be slightly better high-order allocation success rates and/or less compaction overhead, depending on the type of allocations and presence of CMA. It allows simplifying deferred compaction code in a followup patch. When testing with stress-highalloc, there was some slight improvement (which might be just due to variance) in success rates of non-THP-like allocations. Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Cc: Minchan Kim <minchan@kernel.org> Cc: Mel Gorman <mgorman@suse.de> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com> Cc: Michal Nazarewicz <mina86@mina86.com> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> Cc: Christoph Lameter <cl@linux.com> Acked-by: Rik van Riel <riel@redhat.com> Cc: David Rientjes <rientjes@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> (cherry picked from commit ebff398017c69a3810bcbc5200ba224d5ccaa207) BUG=chrome-os-partner:47247 TEST=run Epic Citadel, Fruit Ninja, multi-tab chrome browsing and observe for allocation failures in dmesg Change-Id: I3679f247a66184e3a290ded9ca10cd514fcd2979 Signed-off-by: Maneet Singh <mmaneetsingh@nvidia.com> Reviewed-on: https://chromium-review.googlesource.com/310530 Reviewed-by: Andrew Bresticker <abrestic@chromium.org> " fail_count="0" gerrit_number="310530" owner_email="mmaneetsingh@nvidia.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/310530/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I7ed63c3e4578ce639f36b4faa03817835dd5bb91" commit="b5382a8f38824ee610fde9a2fe56a90d01e3391c" commit_message="UPSTREAM: mm: when stealing freepages, also take pages created by splitting buddy page When studying page stealing, I noticed some weird looking decisions in try_to_steal_freepages(). The first I assume is a bug (Patch 1), the following two patches were driven by evaluation. Testing was done with stress-highalloc of mmtests, using the mm_page_alloc_extfrag tracepoint and postprocessing to get counts of how often page stealing occurs for individual migratetypes, and what migratetypes are used for fallbacks. Arguably, the worst case of page stealing is when UNMOVABLE allocation steals from MOVABLE pageblock. RECLAIMABLE allocation stealing from MOVABLE allocation is also not ideal, so the goal is to minimize these two cases. The evaluation of v2 wasn't always clear win and Joonsoo questioned the results. Here I used different baseline which includes RFC compaction improvements from [1]. I found that the compaction improvements reduce variability of stress-highalloc, so there's less noise in the data. First, let's look at stress-highalloc configured to do sync compaction, and how these patches reduce page stealing events during the test. First column is after fresh reboot, other two are reiterations of test without reboot. That was all accumulater over 5 re-iterations (so the benchmark was run 5x3 times with 5 fresh restarts). Baseline: 3.19-rc4 3.19-rc4 3.19-rc4 5-nothp-1 5-nothp-2 5-nothp-3 Page alloc extfrag event 10264225 8702233 10244125 Extfrag fragmenting 10263271 8701552 10243473 Extfrag fragmenting for unmovable 13595 17616 15960 Extfrag fragmenting unmovable placed with movable 7989 12193 8447 Extfrag fragmenting for reclaimable 658 1840 1817 Extfrag fragmenting reclaimable placed with movable 558 1677 1679 Extfrag fragmenting for movable 10249018 8682096 10225696 With Patch 1: 3.19-rc4 3.19-rc4 3.19-rc4 6-nothp-1 6-nothp-2 6-nothp-3 Page alloc extfrag event 11834954 9877523 9774860 Extfrag fragmenting 11833993 9876880 9774245 Extfrag fragmenting for unmovable 7342 16129 11712 Extfrag fragmenting unmovable placed with movable 4191 10547 6270 Extfrag fragmenting for reclaimable 373 1130 923 Extfrag fragmenting reclaimable placed with movable 302 906 738 Extfrag fragmenting for movable 11826278 9859621 9761610 With Patch 2: 3.19-rc4 3.19-rc4 3.19-rc4 7-nothp-1 7-nothp-2 7-nothp-3 Page alloc extfrag event 4725990 3668793 3807436 Extfrag fragmenting 4725104 3668252 3806898 Extfrag fragmenting for unmovable 6678 7974 7281 Extfrag fragmenting unmovable placed with movable 2051 3829 4017 Extfrag fragmenting for reclaimable 429 1208 1278 Extfrag fragmenting reclaimable placed with movable 369 976 1034 Extfrag fragmenting for movable 4717997 3659070 3798339 With Patch 3: 3.19-rc4 3.19-rc4 3.19-rc4 8-nothp-1 8-nothp-2 8-nothp-3 Page alloc extfrag event 5016183 4700142 3850633 Extfrag fragmenting 5015325 4699613 3850072 Extfrag fragmenting for unmovable 1312 3154 3088 Extfrag fragmenting unmovable placed with movable 1115 2777 2714 Extfrag fragmenting for reclaimable 437 1193 1097 Extfrag fragmenting reclaimable placed with movable 330 969 879 Extfrag fragmenting for movable 5013576 4695266 3845887 In v2 we've seen apparent regression with Patch 1 for unmovable events, this is now gone, suggesting it was indeed noise. Here, each patch improves the situation for unmovable events. Reclaimable is improved by patch 1 and then either the same modulo noise, or perhaps sligtly worse - a small price for unmovable improvements, IMHO. The number of movable allocations falling back to other migratetypes is most noisy, but it's reduced to half at Patch 2 nevertheless. These are least critical as compaction can move them around. If we look at success rates, the patches don't affect them, that didn't change. Baseline: 3.19-rc4 3.19-rc4 3.19-rc4 5-nothp-1 5-nothp-2 5-nothp-3 Success 1 Min 49.00 ( 0.00%) 42.00 ( 14.29%) 41.00 ( 16.33%) Success 1 Mean 51.00 ( 0.00%) 45.00 ( 11.76%) 42.60 ( 16.47%) Success 1 Max 55.00 ( 0.00%) 51.00 ( 7.27%) 46.00 ( 16.36%) Success 2 Min 53.00 ( 0.00%) 47.00 ( 11.32%) 44.00 ( 16.98%) Success 2 Mean 59.60 ( 0.00%) 50.80 ( 14.77%) 48.20 ( 19.13%) Success 2 Max 64.00 ( 0.00%) 56.00 ( 12.50%) 52.00 ( 18.75%) Success 3 Min 84.00 ( 0.00%) 82.00 ( 2.38%) 78.00 ( 7.14%) Success 3 Mean 85.60 ( 0.00%) 82.80 ( 3.27%) 79.40 ( 7.24%) Success 3 Max 86.00 ( 0.00%) 83.00 ( 3.49%) 80.00 ( 6.98%) Patch 1: 3.19-rc4 3.19-rc4 3.19-rc4 6-nothp-1 6-nothp-2 6-nothp-3 Success 1 Min 49.00 ( 0.00%) 44.00 ( 10.20%) 44.00 ( 10.20%) Success 1 Mean 51.80 ( 0.00%) 46.00 ( 11.20%) 45.80 ( 11.58%) Success 1 Max 54.00 ( 0.00%) 49.00 ( 9.26%) 49.00 ( 9.26%) Success 2 Min 58.00 ( 0.00%) 49.00 ( 15.52%) 48.00 ( 17.24%) Success 2 Mean 60.40 ( 0.00%) 51.80 ( 14.24%) 50.80 ( 15.89%) Success 2 Max 63.00 ( 0.00%) 54.00 ( 14.29%) 55.00 ( 12.70%) Success 3 Min 84.00 ( 0.00%) 81.00 ( 3.57%) 79.00 ( 5.95%) Success 3 Mean 85.00 ( 0.00%) 81.60 ( 4.00%) 79.80 ( 6.12%) Success 3 Max 86.00 ( 0.00%) 82.00 ( 4.65%) 82.00 ( 4.65%) Patch 2: 3.19-rc4 3.19-rc4 3.19-rc4 7-nothp-1 7-nothp-2 7-nothp-3 Success 1 Min 50.00 ( 0.00%) 44.00 ( 12.00%) 39.00 ( 22.00%) Success 1 Mean 52.80 ( 0.00%) 45.60 ( 13.64%) 42.40 ( 19.70%) Success 1 Max 55.00 ( 0.00%) 46.00 ( 16.36%) 47.00 ( 14.55%) Success 2 Min 52.00 ( 0.00%) 48.00 ( 7.69%) 45.00 ( 13.46%) Success 2 Mean 53.40 ( 0.00%) 49.80 ( 6.74%) 48.80 ( 8.61%) Success 2 Max 57.00 ( 0.00%) 52.00 ( 8.77%) 52.00 ( 8.77%) Success 3 Min 84.00 ( 0.00%) 81.00 ( 3.57%) 79.00 ( 5.95%) Success 3 Mean 85.00 ( 0.00%) 82.40 ( 3.06%) 79.60 ( 6.35%) Success 3 Max 86.00 ( 0.00%) 83.00 ( 3.49%) 80.00 ( 6.98%) Patch 3: 3.19-rc4 3.19-rc4 3.19-rc4 8-nothp-1 8-nothp-2 8-nothp-3 Success 1 Min 46.00 ( 0.00%) 44.00 ( 4.35%) 42.00 ( 8.70%) Success 1 Mean 50.20 ( 0.00%) 45.60 ( 9.16%) 44.00 ( 12.35%) Success 1 Max 52.00 ( 0.00%) 47.00 ( 9.62%) 47.00 ( 9.62%) Success 2 Min 53.00 ( 0.00%) 49.00 ( 7.55%) 48.00 ( 9.43%) Success 2 Mean 55.80 ( 0.00%) 50.60 ( 9.32%) 49.00 ( 12.19%) Success 2 Max 59.00 ( 0.00%) 52.00 ( 11.86%) 51.00 ( 13.56%) Success 3 Min 84.00 ( 0.00%) 80.00 ( 4.76%) 79.00 ( 5.95%) Success 3 Mean 85.40 ( 0.00%) 81.60 ( 4.45%) 80.40 ( 5.85%) Success 3 Max 87.00 ( 0.00%) 83.00 ( 4.60%) 82.00 ( 5.75%) While there's no improvement here, I consider reduced fragmentation events to be worth on its own. Patch 2 also seems to reduce scanning for free pages, and migrations in compaction, suggesting it has somewhat less work to do: Patch 1: Compaction stalls 4153 3959 3978 Compaction success 1523 1441 1446 Compaction failures 2630 2517 2531 Page migrate success 4600827 4943120 5104348 Page migrate failure 19763 16656 17806 Compaction pages isolated 9597640 10305617 10653541 Compaction migrate scanned 77828948 86533283 87137064 Compaction free scanned 517758295 521312840 521462251 Compaction cost 5503 5932 6110 Patch 2: Compaction stalls 3800 3450 3518 Compaction success 1421 1316 1317 Compaction failures 2379 2134 2201 Page migrate success 4160421 4502708 4752148 Page migrate failure 19705 14340 14911 Compaction pages isolated 8731983 9382374 9910043 Compaction migrate scanned 98362797 96349194 98609686 Compaction free scanned 496512560 469502017 480442545 Compaction cost 5173 5526 5811 As with v2, /proc/pagetypeinfo appears unaffected with respect to numbers of unmovable and reclaimable pageblocks. Configuring the benchmark to allocate like THP page fault (i.e. no sync compaction) gives much noisier results for iterations 2 and 3 after reboot. This is not so surprising given how [1] offers lower improvements in this scenario due to less restarts after deferred compaction which would change compaction pivot. Baseline: 3.19-rc4 3.19-rc4 3.19-rc4 5-thp-1 5-thp-2 5-thp-3 Page alloc extfrag event 8148965 6227815 6646741 Extfrag fragmenting 8147872 6227130 6646117 Extfrag fragmenting for unmovable 10324 12942 15975 Extfrag fragmenting unmovable placed with movable 5972 8495 10907 Extfrag fragmenting for reclaimable 601 1707 2210 Extfrag fragmenting reclaimable placed with movable 520 1570 2000 Extfrag fragmenting for movable 8136947 6212481 6627932 Patch 1: 3.19-rc4 3.19-rc4 3.19-rc4 6-thp-1 6-thp-2 6-thp-3 Page alloc extfrag event 8345457 7574471 7020419 Extfrag fragmenting 8343546 7573777 7019718 Extfrag fragmenting for unmovable 10256 18535 30716 Extfrag fragmenting unmovable placed with movable 6893 11726 22181 Extfrag fragmenting for reclaimable 465 1208 1023 Extfrag fragmenting reclaimable placed with movable 353 996 843 Extfrag fragmenting for movable 8332825 7554034 6987979 Patch 2: 3.19-rc4 3.19-rc4 3.19-rc4 7-thp-1 7-thp-2 7-thp-3 Page alloc extfrag event 3512847 3020756 2891625 Extfrag fragmenting 3511940 3020185 2891059 Extfrag fragmenting for unmovable 9017 6892 6191 Extfrag fragmenting unmovable placed with movable 1524 3053 2435 Extfrag fragmenting for reclaimable 445 1081 1160 Extfrag fragmenting reclaimable placed with movable 375 918 986 Extfrag fragmenting for movable 3502478 3012212 2883708 Patch 3: 3.19-rc4 3.19-rc4 3.19-rc4 8-thp-1 8-thp-2 8-thp-3 Page alloc extfrag event 3181699 3082881 2674164 Extfrag fragmenting 3180812 3082303 2673611 Extfrag fragmenting for unmovable 1201 4031 4040 Extfrag fragmenting unmovable placed with movable 974 3611 3645 Extfrag fragmenting for reclaimable 478 1165 1294 Extfrag fragmenting reclaimable placed with movable 387 985 1030 Extfrag fragmenting for movable 3179133 3077107 2668277 The improvements for first iteration are clear, the rest is much noisier and can appear like regression for Patch 1. Anyway, patch 2 rectifies it. Allocation success rates are again unaffected so there's no point in making this e-mail any longer. [1] http://marc.info/?l=linux-mm&m=142166196321125&w=2 This patch (of 3): When __rmqueue_fallback() is called to allocate a page of order X, it will find a page of order Y >= X of a fallback migratetype, which is different from the desired migratetype. With the help of try_to_steal_freepages(), it may change the migratetype (to the desired one) also of: 1) all currently free pages in the pageblock containing the fallback page 2) the fallback pageblock itself 3) buddy pages created by splitting the fallback page (when Y > X) These decisions take the order Y into account, as well as the desired migratetype, with the goal of preventing multiple fallback allocations that could e.g. distribute UNMOVABLE allocations among multiple pageblocks. Originally, decision for 1) has implied the decision for 3). Commit 47118af076f6 ("mm: mmzone: MIGRATE_CMA migration type added") changed that (probably unintentionally) so that the buddy pages in case 3) are always changed to the desired migratetype, except for CMA pageblocks. Commit fef903efcf0c ("mm/page_allo.c: restructure free-page stealing code and fix a bug") did some refactoring and added a comment that the case of 3) is intended. Commit 0cbef29a7821 ("mm: __rmqueue_fallback() should respect pageblock type") removed the comment and tried to restore the original behavior where 1) implies 3), but due to the previous refactoring, the result is instead that only 2) implies 3) - and the conditions for 2) are less frequently met than conditions for 1). This may increase fragmentation in situations where the code decides to steal all free pages from the pageblock (case 1)), but then gives back the buddy pages produced by splitting. This patch restores the original intended logic where 1) implies 3). During testing with stress-highalloc from mmtests, this has shown to decrease the number of events where UNMOVABLE and RECLAIMABLE allocations steal from MOVABLE pageblocks, which can lead to permanent fragmentation. In some cases it has increased the number of events when MOVABLE allocations steal from UNMOVABLE or RECLAIMABLE pageblocks, but these are fixable by sync compaction and thus less harmful. Note that evaluation has shown that the behavior introduced by 47118af076f6 for buddy pages in case 3) is actually even better than the original logic, so the following patch will introduce it properly once again. For stable backports of this patch it makes thus sense to only fix versions containing 0cbef29a7821. [iamjoonsoo.kim@lge.com: tracepoint fix] Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Acked-by: Mel Gorman <mgorman@suse.de> Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com> Acked-by: Minchan Kim <minchan@kernel.org> Cc: David Rientjes <rientjes@google.com> Cc: Rik van Riel <riel@redhat.com> Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com> Cc: Michal Hocko <mhocko@suse.cz> Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Cc: <stable@vger.kernel.org> [3.13+ containing 0cbef29a7821] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> (cherry picked from commit 99592d598eca62bdbbf62b59941c189176dfc614) BUG=chrome-os-partner:47247 TEST=run Epic Citadel, Fruit Ninja, multi-tab chrome browsing and observe for allocation failures in dmesg Change-Id: I7ed63c3e4578ce639f36b4faa03817835dd5bb91 Signed-off-by: Maneet Singh <mmaneetsingh@nvidia.com> Reviewed-on: https://chromium-review.googlesource.com/310531 Reviewed-by: Andrew Bresticker <abrestic@chromium.org> " fail_count="0" gerrit_number="310531" owner_email="mmaneetsingh@nvidia.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/310531/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I96f7bec62f76923e6c0f5c1686fcc81685235b1b" commit="957e655acaa72c3cc288ad3cec00d9f0b40846e6" commit_message="UPSTREAM: mm: always steal split buddies in fallback allocations When allocation falls back to another migratetype, it will steal a page with highest available order, and (depending on this order and desired migratetype), it might also steal the rest of free pages from the same pageblock. Given the preference of highest available order, it is likely that it will be higher than the desired order, and result in the stolen buddy page being split. The remaining pages after split are currently stolen only when the rest of the free pages are stolen. This can however lead to situations where for MOVABLE allocations we split e.g. order-4 fallback UNMOVABLE page, but steal only order-0 page. Then on the next MOVABLE allocation (which may be batched to fill the pcplists) we split another order-3 or higher page, etc. By stealing all pages that we have split, we can avoid further stealing. This patch therefore adjusts the page stealing so that buddy pages created by split are always stolen. This has effect only on MOVABLE allocations, as RECLAIMABLE and UNMOVABLE allocations already always do that in addition to stealing the rest of free pages from the pageblock. The change also allows to simplify try_to_steal_freepages() and factor out CMA handling. According to Mel, it has been intended since the beginning that buddy pages after split would be stolen always, but it doesn't seem like it was ever the case until commit 47118af076f6 ("mm: mmzone: MIGRATE_CMA migration type added"). The commit has unintentionally introduced this behavior, but was reverted by commit 0cbef29a7821 ("mm: __rmqueue_fallback() should respect pageblock type"). Neither included evaluation. My evaluation with stress-highalloc from mmtests shows about 2.5x reduction of page stealing events for MOVABLE allocations, without affecting the page stealing events for other allocation migratetypes. Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Acked-by: Mel Gorman <mgorman@suse.de> Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com> Acked-by: Minchan Kim <minchan@kernel.org> Cc: David Rientjes <rientjes@google.com> Cc: Rik van Riel <riel@redhat.com> Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com> Cc: Michal Hocko <mhocko@suse.cz> Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> (cherry picked from commit 3a1086fba92b6e2311b6a342f68bc380beb240fe) BUG=chrome-os-partner:47247 TEST=run Epic Citadel, Fruit Ninja, multi-tab chrome browsing and observe for allocation failures in dmesg Change-Id: I96f7bec62f76923e6c0f5c1686fcc81685235b1b Signed-off-by: Maneet Singh <mmaneetsingh@nvidia.com> Reviewed-on: https://chromium-review.googlesource.com/310532 Reviewed-by: Andrew Bresticker <abrestic@chromium.org> " fail_count="0" gerrit_number="310532" owner_email="mmaneetsingh@nvidia.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/310532/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I221600d7eeb5942365beb0229d4cf4ddb2e78e52" commit="5fcbc1043481896088c35c016f6320fff55de3a4" commit_message="UPSTREAM: mm: more aggressive page stealing for UNMOVABLE allocations When allocation falls back to stealing free pages of another migratetype, it can decide to steal extra pages, or even the whole pageblock in order to reduce fragmentation, which could happen if further allocation fallbacks pick a different pageblock. In try_to_steal_freepages(), one of the situations where extra pages are stolen happens when we are trying to allocate a MIGRATE_RECLAIMABLE page. However, MIGRATE_UNMOVABLE allocations are not treated the same way, although spreading such allocation over multiple fallback pageblocks is arguably even worse than it is for RECLAIMABLE allocations. To minimize fragmentation, we should minimize the number of such fallbacks, and thus steal as much as is possible from each fallback pageblock. Note that in theory this might put more pressure on movable pageblocks and cause movable allocations to steal back from unmovable pageblocks. However, movable allocations are not as aggressive with stealing, and do not cause permanent fragmentation, so the tradeoff is reasonable, and evaluation seems to support the change. This patch thus adds a check for MIGRATE_UNMOVABLE to the decision to steal extra free pages. When evaluating with stress-highalloc from mmtests, this has reduced the number of MIGRATE_UNMOVABLE fallbacks to roughly 1/6. The number of these fallbacks stealing from MIGRATE_MOVABLE block is reduced to 1/3. There was no observation of growing number of unmovable pageblocks over time, and also not of increased movable allocation fallbacks. Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Acked-by: Mel Gorman <mgorman@suse.de> Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com> Cc: Minchan Kim <minchan@kernel.org> Cc: David Rientjes <rientjes@google.com> Cc: Rik van Riel <riel@redhat.com> Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com> Cc: Michal Hocko <mhocko@suse.cz> Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> (cherry picked from commit 9c0415eb8cbf0c8fd043b6c0f0354308ab099df5) BUG=chrome-os-partner:47247 TEST=run Epic Citadel, Fruit Ninja, multi-tab chrome browsing and observe for allocation failures in dmesg Change-Id: I221600d7eeb5942365beb0229d4cf4ddb2e78e52 Signed-off-by: Maneet Singh <mmaneetsingh@nvidia.com> Reviewed-on: https://chromium-review.googlesource.com/310533 Reviewed-by: Andrew Bresticker <abrestic@chromium.org> " fail_count="0" gerrit_number="310533" owner_email="mmaneetsingh@nvidia.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/310533/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I4629d7d1e60da41bfebe9747e0a7c17cb0ab1f85" commit="58ed884d790b4afcca946c3e05fcdb80997b42e6" commit_message="UPSTREAM: mm/compaction: fix wrong order check in compact_finished() What we want to check here is whether there is highorder freepage in buddy list of other migratetype in order to steal it without fragmentation. But, current code just checks cc->order which means allocation request order. So, this is wrong. Without this fix, non-movable synchronous compaction below pageblock order would not stopped until compaction is complete, because migratetype of most pageblocks are movable and high order freepage made by compaction is usually on movable type buddy list. There is some report related to this bug. See below link. http://www.spinics.net/lists/linux-mm/msg81666.html Although the issued system still has load spike comes from compaction, this makes that system completely stable and responsive according to his report. stress-highalloc test in mmtests with non movable order 7 allocation doesn't show any notable difference in allocation success rate, but, it shows more compaction success rate. Compaction success rate (Compaction success * 100 / Compaction stalls, %) 18.47 : 28.94 Fixes: 1fb3f8ca0e92 ("mm: compaction: capture a suitable high-order page immediately when it is made available") Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com> Acked-by: Vlastimil Babka <vbabka@suse.cz> Reviewed-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com> Cc: Mel Gorman <mgorman@suse.de> Cc: David Rientjes <rientjes@google.com> Cc: Rik van Riel <riel@redhat.com> Cc: <stable@vger.kernel.org> [3.7+] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> (cherry picked from commit 372549c2a3778fd3df445819811c944ad54609ca) BUG=chrome-os-partner:47247 TEST=run Epic Citadel, Fruit Ninja, multi-tab chrome browsing and observe for allocation failures in dmesg Change-Id: I4629d7d1e60da41bfebe9747e0a7c17cb0ab1f85 Signed-off-by: Maneet Singh <mmaneetsingh@nvidia.com> Reviewed-on: https://chromium-review.googlesource.com/310534 Reviewed-by: Andrew Bresticker <abrestic@chromium.org> " fail_count="0" gerrit_number="310534" owner_email="mmaneetsingh@nvidia.com" pass_count="0" patch_number="3" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/34/310534/3" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie3821299424fb0a3e2ef593430d2bbc8baef3b4a" commit="fc974b41d233163e67c1d4f0a4d9336eb34db74a" commit_message="CHROMIUM: zram: lz4: fallback to vmalloc allocation zram lz4 compression algorithm requests order-3 page allocations. When system memory is fragmented, some of the order-3 allocations start failing, therefore fallback to vmalloc which will usually result in a couple of order-0 allocations and hence will work even if memory is fragmented. lz4 compression algorithm is using this allocated buffer as a hashtable and so should not fail even if underlying buffer is allocated from vmalloc instead of kmalloc. BUG=chrome-os-partner:47247 TEST=run Epic Citadel, Fruit Ninja, multi-tab chrome browsing and observe for allocation failures in dmesg Change-Id: Ie3821299424fb0a3e2ef593430d2bbc8baef3b4a Signed-off-by: Maneet Singh <mmaneetsingh@nvidia.com> Reviewed-on: https://chromium-review.googlesource.com/310535 Reviewed-by: Andrew Bresticker <abrestic@chromium.org> " fail_count="0" gerrit_number="310535" owner_email="mmaneetsingh@nvidia.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/310535/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I5c80e1dad3eda035e2610e24e7b227b5e5b3dd5a" commit="3a51d5907dfd70b764974b0d84c7a6b3a09645b5" commit_message="Buddy: Set capture volume to 30dB Volume of the mics was pretty low and the AGC can't completely compensate for it. The capture volume is changed from 0dB + 12.75dB = 12.75dB to 24dB + 6dB = 30dB. This change affect the 4 internal DMICs and the external analog headset mic. BUG=chrome-os-partner:47139 TEST=4ch recording on Buddy and listen to each channel CQ-DEPEND=CL:310593 Change-Id: I5c80e1dad3eda035e2610e24e7b227b5e5b3dd5a Signed-off-by: Ben Zhang <benzh@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310632 Reviewed-by: Alejandro Luebs <aluebs@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="0" gerrit_number="310632" owner_email="benzh@chromium.org" pass_count="0" patch_number="2" project="chromiumos/overlays/board-overlays" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/board-overlays" ref="refs/changes/32/310632/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I2f4ccc312017b2bee2bc7e21553e0de4ec54b669" commit="c2c4056489699544cff499a3e188a75e80e511b8" commit_message="Oak: Rename rt5650 ADC boost volume control The control name is changed from "STO1 ADC Boost Gain" to "ADC Boost Capture Volume" in the upstream. This should be a no-op. This kernel change is cherry-picked to chromeos-3.14 for Buddy. It's cherry-picked to chromeos-3.18 to make the control naming consistent. BUG=chrome-os-partner:40164 TEST=Adjust the updated controls with amixer and see volume change on Buddy CQ-DEPEND=CL:310585 Change-Id: I2f4ccc312017b2bee2bc7e21553e0de4ec54b669 Signed-off-by: Ben Zhang <benzh@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310633 Reviewed-by: Nicolas Boichat <drinkcat@chromium.org> " fail_count="0" gerrit_number="310633" owner_email="benzh@chromium.org" pass_count="0" patch_number="2" project="chromiumos/overlays/board-overlays" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/board-overlays" ref="refs/changes/33/310633/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I93b60aadf152dcb45cc0efdbd9f5414d84840a69" commit="8f4d0e83f1a2bfae985747a6e89573632abf431e" commit_message="UPSTREAM: ASoC: rt5645: Correct the naming and setting of ADC Boost Volume Control Signed-off-by: Oder Chiou <oder_chiou@realtek.com> Signed-off-by: Mark Brown <broonie@kernel.org> (cherry picked from commit 8c1a9d6323abf0fb1e5dad96cf3f1c783505ea5a) Signed-off-by: Ben Zhang <benzh@chromium.org> BUG=chrome-os-partner:47139 TEST=Adjust the updated controls with amixer and see volume change on Buddy CQ-DEPEND=CL:310632 Change-Id: I93b60aadf152dcb45cc0efdbd9f5414d84840a69 Reviewed-on: https://chromium-review.googlesource.com/310593 Commit-Ready: Ben Zhang <benzh@chromium.org> Tested-by: Ben Zhang <benzh@chromium.org> Reviewed-by: Alejandro Luebs <aluebs@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="0" gerrit_number="310593" owner_email="benzh@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/93/310593/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6dcd9deec2ba9c37e145fcf888a94cc978cd5311" commit="e4a8a8152acb39d7c242d16ad4b737e616dcea1d" commit_message="UPSTREAM: ASoC: rt5645: Correct the naming and setting of ADC Boost Volume Control Signed-off-by: Oder Chiou <oder_chiou@realtek.com> Signed-off-by: Mark Brown <broonie@kernel.org> (cherry picked from commit 8c1a9d6323abf0fb1e5dad96cf3f1c783505ea5a) Signed-off-by: Ben Zhang <benzh@chromium.org> BUG=chrome-os-partner:40164 TEST=Adjust the updated controls with amixer and see volume change on Buddy CQ-DEPEND=CL:310633 This patch is cherry-picked to chromeos-3.14 for Buddy. It's cherry-picked to chromeos-3.18 to make the control naming consistent. Change-Id: I6dcd9deec2ba9c37e145fcf888a94cc978cd5311 Reviewed-on: https://chromium-review.googlesource.com/310585 Commit-Ready: Ben Zhang <benzh@chromium.org> Tested-by: Ben Zhang <benzh@chromium.org> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org> " fail_count="0" gerrit_number="310585" owner_email="benzh@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/85/310585/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iad23c105ac57050ffb966d758fbc3f02feab8181" commit="a0c9296ed8420832eb3dd727080249cdc558af02" commit_message="Buddy: Use the right side DMIC pair for 2ch capture Connect DMIC2 to stereo1 and DMIC1 to mono, so that "DMIC Pair2" (on the right side of the camera) is used when doing only 2ch capture. The codec IF1 ADC1/2 Swap Mux are changed so that left/right channel are ordered correctly. The recorded file is verifed with Audacity. Broadwell TDM seems to swap left and right channel in each DMIC pair. MicPositions of "DMIC Pair2" is added. BUG=chrome-os-partner:46725 TEST=2ch and 4ch recording on Buddy, see DMIC Pair2 is in slot0/1 and DMIC Pair1 is in slot2/3. Headset mic continues to work. Change-Id: Iad23c105ac57050ffb966d758fbc3f02feab8181 Signed-off-by: Ben Zhang <benzh@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310555 Reviewed-by: Alejandro Luebs <aluebs@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="0" gerrit_number="310555" owner_email="benzh@chromium.org" 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/55/310555/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I316c744cd98976f98a2e901feeaa4dbc9427b85c" commit="efab0229289afb00443c3e939cbcc63626d2e26b" commit_message="CHROMIUM: drivers: nss-qdisc: Add nss-qdisc module This modules enables nss-qdisc offloading to NSS Firmware BUG=chrome-os-partner:42290 CQ-DEPEND=CL:304357 TEST=build/boot on WW. Verified with all nss-qdisc testplan Change-Id: I316c744cd98976f98a2e901feeaa4dbc9427b85c Signed-off-by: Stephen Wang <wstephen@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/304482 Commit-Ready: Kishan Kunduru <kkunduru@chromium.org> Tested-by: Kishan Kunduru <kkunduru@chromium.org> Reviewed-by: Kishan Kunduru <kkunduru@chromium.org> " fail_count="0" gerrit_number="304482" owner_email="wstephen@codeaurora.org" pass_count="0" patch_number="6" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/82/304482/6" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ifb7232ab9401049a0fc388a91242ec10fd072e72" commit="9ac90aee5424b298ebf1679c24620c28f64f6bdd" commit_message="CHROMIUM: include: Add structures and defines needed to support NSS qdiscs The following patch adds the required data structures and defines for for configuring NSS qdiscs. BUG=chrome-os-partner:42290 TEST=build/boot on WW. Verified that nss qdisc structure can be found when compiling NSS qdisc modulew Change-Id: Ifb7232ab9401049a0fc388a91242ec10fd072e72 Signed-off-by: Stephen Wang <wstephen@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/304386 Commit-Ready: Kishan Kunduru <kkunduru@chromium.org> Tested-by: Kishan Kunduru <kkunduru@chromium.org> Reviewed-by: Kevin Hayes <kevinhayes@google.com> " fail_count="0" gerrit_number="304386" owner_email="wstephen@codeaurora.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/86/304386/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I614ee26c182d8dcdb78de3e62d4ca91a25765b30" commit="84fd54eda889c9c8ad598e2e8e5310a48951f60a" commit_message="CHROMIUM: ipq806x: config: Select nss-qdisc module This enables qca-nss-qdisc module in the ipq806x config BUG=chrome-os-partner:42290 TEST=build/boot on WW. Verified qca-nss-qdisc module are built Change-Id: I614ee26c182d8dcdb78de3e62d4ca91a25765b30 Signed-off-by: Stephen Wang <wstephen@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/306651 Commit-Ready: Kishan Kunduru <kkunduru@chromium.org> Tested-by: Kishan Kunduru <kkunduru@chromium.org> Reviewed-by: Kevin Hayes <kevinhayes@google.com> " fail_count="0" gerrit_number="306651" owner_email="wstephen@codeaurora.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/51/306651/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I71d815b6a9f8c63bb7a85725bc8a724e96334aae" commit="fd29cc895efe32dbe08fa8061c49b83bbf78297e" commit_message="CHROMIUM: alt-syscall: Always define sys_call_ptr_t Unconditionally define sys_call_ptr_t so that ALT_SYSCALL builds for all architectures. Currently only x86 defines a sys_call_ptr_t type. BUG=b:25408860 TEST=Build and boot on Smaug; syscalls still work with ALT_SYSCALL on. Change-Id: I71d815b6a9f8c63bb7a85725bc8a724e96334aae Signed-off-by: Andrew Bresticker <abrestic@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310600 Reviewed-by: Kees Cook <keescook@chromium.org> " fail_count="0" gerrit_number="310600" owner_email="abrestic@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/00/310600/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I90a6c648fa8b66131b0a077dc05ae8d91843902c" commit="fb6ec1c4d97f8d0ae9719275102f52a1cc1a883f" commit_message="CHROMIUM: ARM64: Add alt-syscall support Add ARM64 support for changing a thread's syscall table at runtime using the alt-syscall infrastructure. BUG=b:25408860 TEST=Build and boot on Smaug; syscalls still work with ALT_SYSCALL on. Change-Id: I90a6c648fa8b66131b0a077dc05ae8d91843902c Signed-off-by: Andrew Bresticker <abrestic@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310601 Reviewed-by: Kees Cook <keescook@chromium.org> " fail_count="0" gerrit_number="310601" owner_email="abrestic@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/01/310601/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I5cfa82dfdb72bf50b104183859fd8d067ce7da89" commit="5b95a03d548c34eef73e49f5ca6f782ec8d534c9" commit_message="Add brillo_StorageWriteSpeedTest. This implements the Brillo PTS storage write speed test. BUG=b:25468342 TEST=brillo_test_launcher.py -t brillo_StorageWriteSpeedTest ==> PASS TEST=brillo_test_launcher.py -t brillo_StorageWriteSpeedTest -A min_speed=$((256*1024*1024)) ==> FAIL: Storage write speed is lower than required Change-Id: I5cfa82dfdb72bf50b104183859fd8d067ce7da89 Reviewed-on: https://chromium-review.googlesource.com/310843 Commit-Ready: Gilad Arnold <garnold@chromium.org> Tested-by: Gilad Arnold <garnold@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> " fail_count="0" gerrit_number="310843" owner_email="garnold@chromium.org" pass_count="0" patch_number="4" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/43/310843/4" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Id109f27a7387e75a5f5beacc90aade4331066f62" commit="f007787feb9e7b02757a031213bd4f0f2da1271e" commit_message="Fix import and docstring on all Brillo tests. BUG=None TEST=None Change-Id: Id109f27a7387e75a5f5beacc90aade4331066f62 Reviewed-on: https://chromium-review.googlesource.com/310962 Commit-Ready: Gilad Arnold <garnold@chromium.org> Tested-by: Gilad Arnold <garnold@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> " fail_count="0" gerrit_number="310962" owner_email="garnold@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/62/310962/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I4ce9267c8962cdd4ad606d42dbaad09d8fe3d949" commit="3116e34beb9e15c985d02a8f3a02f42406de5da7" commit_message="CHROMIUM: linux-firmware: Add brcmfmac4371-pcie This firmware allows us to build images that support brcm4371 wifi. Received from leizh@broadcom.com. BUG=None TEST=build, boot, make sure wifi works on glados Change-Id: I4ce9267c8962cdd4ad606d42dbaad09d8fe3d949 Reviewed-on: https://chromium-review.googlesource.com/310850 Commit-Ready: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Anatol Pomazau <anatol@google.com> " fail_count="0" gerrit_number="310850" owner_email="ejcaruso@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/linux-firmware" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/linux-firmware" ref="refs/changes/50/310850/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="If037800b0e440909c62c94f8e957052f5976435a" commit="da126d56d8df5d772ec0e0b4d9576605017537c7" commit_message="Add brcmfmac4371-pcie to linux-firmware This firmware allows us to build images that support brcm4371 wifi. CQ-DEPEND=CL:310850 BUG=None TEST=build, boot, make sure wifi works on glados Change-Id: If037800b0e440909c62c94f8e957052f5976435a Reviewed-on: https://chromium-review.googlesource.com/310861 Commit-Ready: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="0" gerrit_number="310861" owner_email="ejcaruso@chromium.org" pass_count="0" patch_number="2" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/61/310861/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2015.07" change_id="Ife770898b0f2b4f58b8259711101a0cab4a5e4ac" commit="44a7dbaa98e7b8fd85216959d697c99346a99281" commit_message="edid: add hdmi_monitor_detected in data struct edid HDMI driver need to know whether the monitor is DVI or HDMI interface, so this commit just introduce a new number 'hdmi_monitor_detected' to struct edid. There were four bits to indicate the monitor interfaces, it's better to take use of that. But those bits only existed in EDID 1.4 version, but didn't persented in the previous EDID version, so I decided to detect the hdmi cea block. BRANCH=none BUG=chrome-os-partner:43789 TEST=When mickey connect with HDMI monitor, see 'hdmi_monitor_detected' is 'true'. When mickey connect with DVI monitor, see 'hdmi_monitor_detected' is 'false'. Change-Id: Ife770898b0f2b4f58b8259711101a0cab4a5e4ac Signed-off-by: Yakir Yang <ykk@rock-chips.com> Reviewed-on: https://chromium-review.googlesource.com/309055 Tested-by: David Hendricks <dhendrix@chromium.org> Reviewed-by: David Hendricks <dhendrix@chromium.org> " fail_count="2" gerrit_number="309055" owner_email="ykk@rock-chips.com" pass_count="0" patch_number="4" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/55/309055/4" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-2015.07" change_id="I157861d327926b834e1e8606b0b676f413491c70" commit="4ebab544485bc1802d902da714318b6d77d7fc79" commit_message="RK3288: hdmi: configure display output mode with EDID information 'edid->hdmi_monitor_detected' would indicate whether the monitor interface is HDMI or DVI. BRANCH=none BUG=chrome-os-partner:43789 TEST=Previously, my LG monitor couldn't show dev screen. But now I can see dev screen have been posted normally. Change-Id: I157861d327926b834e1e8606b0b676f413491c70 Signed-off-by: Yakir Yang <ykk@rock-chips.com> Reviewed-on: https://chromium-review.googlesource.com/309056 Tested-by: David Hendricks <dhendrix@chromium.org> Reviewed-by: David Hendricks <dhendrix@chromium.org> " fail_count="2" gerrit_number="309056" owner_email="ykk@rock-chips.com" pass_count="0" patch_number="4" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/56/309056/4" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I8339c1512b9e02f1a69d73dc5cbcda42da68e4ac" commit="bcb8bdcc5a7e78cc802ade1a769f7017c370deed" commit_message="power_state: Clear ec_uart_regexp before send a command The ec_uart_regexp is to match the response of an EC command. For sending a command without regarding response, should clear the value of ec_uart_regexp. BUG=chromium:534882 TEST=Ran 'dut-control power_state:off' on servo with dirty ec_uart_regexp. Change-Id: I8339c1512b9e02f1a69d73dc5cbcda42da68e4ac Reviewed-on: https://chromium-review.googlesource.com/310883 Commit-Ready: Wai-Hong Tam <waihong@chromium.org> Tested-by: Wai-Hong Tam <waihong@chromium.org> Reviewed-by: danny chan <dchan@chromium.org> " fail_count="0" gerrit_number="310883" owner_email="waihong@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/hdctools" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/hdctools" ref="refs/changes/83/310883/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Id69dceed3b48c85855dca4074d132495e8c7f1c7" commit="b96db852e9aacecee8d8630f29e8a53ccfbb766d" commit_message="CHROMIUM: Cyclone: The necessary changes for dts in order to make emmc work on cyclone board: - Update dtsi for a38x family regarding sdhci interface - Update dts for cyclone to enable sdhci interface for the emmc device; BUG=chrome-os-partner:43600 TEST=Tested on Cube Proto2 hw Change-Id: Id69dceed3b48c85855dca4074d132495e8c7f1c7 Signed-off-by: kfyao <kfyao@marvell.com> Reviewed-on: https://chromium-review.googlesource.com/305267 Commit-Ready: Kan Yan <kyan@google.com> Tested-by: Kan Yan <kyan@chromium.org> Reviewed-by: Kan Yan <kyan@google.com> " fail_count="0" gerrit_number="305267" owner_email="kfyao@marvell.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/67/305267/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I85edee5cef2093fefecfd5e9db89848d16fc839e" commit="afd9c3ce62bdf185f75857a293fdacf160da0ab7" commit_message="[autotest] Add firmware repair to CrOSHost repair logic. This is to help to revoery duts failed in FAFT. DUT to be repaired by firmware_repair will need to be in pool:faft-test. The board will also need to have an entry in stable_version table, e.g. daisy_spring/firmware: daisy_spring-firmware/R41-6588.127.0 BUG=chromium:279410,chromium:535456 TEST=unititest, local run Change-Id: I85edee5cef2093fefecfd5e9db89848d16fc839e Reviewed-on: https://chromium-review.googlesource.com/305290 Commit-Ready: Dan Shi <dshi@chromium.org> Tested-by: Dan Shi <dshi@chromium.org> Reviewed-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Wai-Hong Tam <waihong@chromium.org> " fail_count="0" gerrit_number="305290" owner_email="dshi@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/90/305290/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ief2f781f669ad201fb293e2f776c040e6c878240" commit="6bb6180afc8b1298c8357038e974c536580242a4" commit_message="Chell/Lars: Enable PD SW sync through GBB flags Refer to the CL https://chromium-review.googlesource.com/#/c/310197/ BRANCH=None BUG=None TEST=None Change-Id: Ief2f781f669ad201fb293e2f776c040e6c878240 Signed-off-by: David Wu <David_Wu@quantatw.com> Reviewed-on: https://chromium-review.googlesource.com/310710 Commit-Ready: David Wu <david_wu@quantatw.com> Tested-by: David Wu <david_wu@quantatw.com> Reviewed-by: Alec Berg <alecaberg@chromium.org> Reviewed-by: Duncan Laurie <dlaurie@chromium.org> " fail_count="0" gerrit_number="310710" owner_email="david_wu@quantatw.com" pass_count="0" patch_number="2" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/10/310710/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I278bbb21edb0f871dcea5be242f04a931a47076a" commit="33d31cc3aa3ded0eac8f1844944d9da17e59e3fe" commit_message="shill: Add 802.1x Key Management property This is useful when specifying 802.1x WEP (Enterprise WEP). BUG=chromium:551085 TEST=Build shill Change-Id: I278bbb21edb0f871dcea5be242f04a931a47076a Reviewed-on: https://chromium-review.googlesource.com/310644 Commit-Ready: Paul Stewart <pstew@chromium.org> Tested-by: Paul Stewart <pstew@chromium.org> Reviewed-by: Steven Bennetts <stevenjb@chromium.org> " fail_count="0" gerrit_number="310644" owner_email="pstew@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/system_api" project_url="https://chromium-review.googlesource.com/chromiumos/platform/system_api" ref="refs/changes/44/310644/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ie67ff28bec3a9788898e99483eedb0ef77de38cd" commit="7aa96b0e73b2e0fe2017b9b17d12477bf5859da5" commit_message="cr50: introduce RO image skeleton The CR50 board will have to have a very different RO image, let's make it possible to override the default list of objects compiled by the top level makefile with a board/chip specific list compiled in the appropriate build.mk file. The CR50 RO will never run on its own for long time, it will always load an RW and go straight to it, so there is no need in running under the OS control, using sophisticated console channel controls, etc. The gist of the functionality is verifying the RW image to run and setting up the hardware to allow the picked image to execute, it will be added in the following patches. This change just provides the plumbing and shows the 'hello world' implementation for the customized RO image. A better solution could be the ability to create distinct sets of make variables for RO and RW, a tracker item was created to look into this. BRANCH=None BUG=chrome-os-partner:43025, chromium:551151 TEST=built and started ec.RO.hex on cr50, observed the 'hello world' message on the console. Change-Id: Ie67ff28bec3a9788898e99483eedb0ef77de38cd Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310410 Reviewed-by: Randall Spangler <rspangler@chromium.org> Reviewed-by: Bill Richardson <wfrichar@chromium.org> " fail_count="0" gerrit_number="310410" owner_email="vbendeb@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/10/310410/4" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I5e914fad5cef5982657c25c82f7bcc1d94a57fe5" commit="a27ae6f5e8dc8dbb74ae3f1352af20b695d47a49" commit_message="Wizpig: add Bluetooth ID DeviceID = bluetooth:00E0:2447:0400 BUG=chrome-os-partner:47032 TEST=run `emerge-wizpig chromeos-bsp-wizpig`, then check the existence of "/build/wizpig/etc/bluetooth/main.conf" and see if DeviceID is 2447. Change-Id: I5e914fad5cef5982657c25c82f7bcc1d94a57fe5 Signed-off-by: Kaiyen Chang <kaiyen.chang@intel.com> Reviewed-on: https://chromium-review.googlesource.com/310636 Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="0" gerrit_number="310636" owner_email="kaiyen.chang@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/36/310636/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I0b930ad02719ec6f431f7db724979c4264a51b34" commit="f30c0738f63cdb3ea5d49aa7a61a7807c83d8f9e" commit_message="modemmanger-next: backport a upstream patch. This backports the upstream commit 4e00558fcbdcfc9232f1007e718b9e2afae6520a to fix the error. BUG=chromium:548901 TEST=the error is gone. Change-Id: I0b930ad02719ec6f431f7db724979c4264a51b34 Reviewed-on: https://chromium-review.googlesource.com/310656 Commit-Ready: Yunlian Jiang <yunlian@chromium.org> Tested-by: Yunlian Jiang <yunlian@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> " fail_count="0" gerrit_number="310656" owner_email="yunlian@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/modemmanager-next" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/modemmanager-next" ref="refs/changes/56/310656/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I39b4cfbd8135c99a6046975f8564522720300dd3" commit="354f63282d72bbb90daa70fb52706f09bc82edac" commit_message="[autotest] Delay getting useflags only when needed. It takes over 30s to get useflags. This adds unnecessary overhead for CLs that do not have changes in control files. This change delays getting useflags. BUG=None TEST=repo upload this CL takes less than 10s. manually pass some control file for the script to check, make sure useflags still works. Change-Id: I39b4cfbd8135c99a6046975f8564522720300dd3 Reviewed-on: https://chromium-review.googlesource.com/310546 Commit-Ready: Dan Shi <dshi@chromium.org> Tested-by: Dan Shi <dshi@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org> " fail_count="0" gerrit_number="310546" owner_email="dshi@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/46/310546/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ib4915f712f9d14caf7418ef4b03aa41e8764fd36" commit="3a773506244a0221287c686d47c8dc2d7651f09b" commit_message="cleanup: ignore compiled executable in extra/ This just adds a .gitignore entry so that git doesn't complain about the executable you may have built in the extra/usb_console/ directory. BUG=none BRANCH=none TEST=make buildall This has no effect on the EC code at all. The things in the extra/ directory are optional and unsupported. Change-Id: Ib4915f712f9d14caf7418ef4b03aa41e8764fd36 Signed-off-by: Bill Richardson <wfrichar@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310840 Reviewed-by: Vadim Bendebury <vbendeb@chromium.org> " fail_count="0" gerrit_number="310840" owner_email="wfrichar@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/40/310840/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ic2d5f4565c96b10bdcdef03141b366bc1519de32" commit="97fb0353b637ef130b2f1419d88726fd6419a570" commit_message="cros-board: Add kblrvp board name Add the kblrvp board name, an internal Intel dev board. BUG=None TEST=kblrvp available in the board name list Change-Id: Ic2d5f4565c96b10bdcdef03141b366bc1519de32 Reviewed-on: https://chromium-review.googlesource.com/310640 Commit-Ready: Kevin Strasser <kevin.strasser@intel.com> Tested-by: Joe Konno <joe.konno@linux.intel.com> Reviewed-by: Marc Herbert <marc.herbert@intel.com> Reviewed-by: James Ausmus <james.ausmus@intel.com> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="0" gerrit_number="310640" owner_email="kevin.strasser@intel.com" pass_count="0" patch_number="1" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/40/310640/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I8149558c83f5a2d5bcd736b4f81cb2ce6871793f" commit="29ba3f83825ef6ba824130779ccea7634b3edec8" commit_message="power_ProbeDriver: fix the ac_paths check for USB Type-C chargers With the USB Type-C added up under the power_supply_path, the check for ac_paths also has to be updated appropriately. Without this patch the test fails with error: "Not exactly one AC found: 3". BUG=chrome-os-partner:47169 TEST=for kunimitsu executed the below command: TEST=test_that -b kunimitsu <IP> power_ProbeDriver.probe_ac ==> PASS Change-Id: I8149558c83f5a2d5bcd736b4f81cb2ce6871793f Signed-off-by: Shirish S <shirish.s@intel.com> Reviewed-on: https://chromium-review.googlesource.com/309978 Reviewed-by: Dan Erat <derat@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="0" gerrit_number="309978" owner_email="shirish.s@intel.com" 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/78/309978/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I3782e936d141f7b7d1d541f50759a7fad81dbdbc" commit="a0fbcf8dff9fc3b624258f1e95c805e37adb6c57" commit_message="edgar: add to Strago based mainboard list for mosys Add edgar mainboard to Strago board list for mosys. BUG=chrome-os-partner:47244 BRANCH=none TEST=emerge-edgar mosys Change-Id: I3782e936d141f7b7d1d541f50759a7fad81dbdbc Reviewed-on: https://chromium-review.googlesource.com/310672 Commit-Ready: Kevin Cheng <kevin.cheng@intel.com> Tested-by: Kevin Cheng <kevin.cheng@intel.com> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="0" gerrit_number="310672" owner_email="kevin.cheng@intel.com" pass_count="0" patch_number="2" project="chromiumos/platform/mosys" project_url="https://chromium-review.googlesource.com/chromiumos/platform/mosys" ref="refs/changes/72/310672/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I4812b056b911a336f9cf821e7b88a9a3d50e71ec" commit="b65f298db6a953e166ee2ee51e454cdbf92b4d67" commit_message="overlord: replace forceUpdate by setState According to React's document, "this.state" object should be treated as an immuable object. So the previous implementation that change some part of this.state and then "this.forceUpdate()" would be error-prone. For example: removeAllClients: function () { this.setState({clients: []}); }, addClient: function (client) { this.state.clients.push(client); this.forceUpdate(); } There might be a case that right after "removeAllClients" is called, "addClient" is also called. But since setState is an asynchronous function, this.state.client might not be an empty array, might still in previous state, and cause wrong behavior. The correct way: this.state.value = new_value; // new_value doesn't depend on current value => this.setState({value: new_value}); this.state.value += 1; // new value depends on current value => this.setState(function (state, props) { // state and props are the current this.state and this.props // right before this anonymous function is called repectively. return {value: state.value + 1}; }); this.state.clients.push(new_client); this.forceUpdate(); => this.setState(function (state, props) { state.clients.push(new_client); // no return value since we are not assigning new values to // any attribute. }); BUG=chromium:551264 TEST=Manual test Change-Id: I4812b056b911a336f9cf821e7b88a9a3d50e71ec Reviewed-on: https://chromium-review.googlesource.com/310690 Commit-Ready: Wei-Han Chen <stimim@chromium.org> Tested-by: Wei-Han Chen <stimim@chromium.org> Reviewed-by: Wei-Ning Huang <wnhuang@chromium.org> " fail_count="0" gerrit_number="310690" owner_email="stimim@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/factory" project_url="https://chromium-review.googlesource.com/chromiumos/platform/factory" ref="refs/changes/90/310690/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I66e0625de02cda3b2f32eea545de641315762cfd" commit="ec733d17170dbb1121427e03d58481115904c071" commit_message="Get peripherals tests run on same test suite. BUG=None TEST=None Change-Id: I66e0625de02cda3b2f32eea545de641315762cfd Reviewed-on: https://chromium-review.googlesource.com/310862 Commit-Ready: Kalin Stoyanov <kalin@chromium.org> Tested-by: Kalin Stoyanov <kalin@chromium.org> Reviewed-by: Kalin Stoyanov <kalin@chromium.org> " fail_count="0" gerrit_number="310862" owner_email="kalin@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/310862/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I74996f8ffca702542e685fce38ef12d50352e5c7" commit="2d5247adaff4b5cb9146380aec7a22f5a573e595" commit_message="CHROMIUM: net: wireless: bcmdhd: no retry on header receive errors Do not attempt retry on rx header failure to avoid out of sync between host and dongle. BUG=chrome-os-partner:45478 Change-Id: I74996f8ffca702542e685fce38ef12d50352e5c7 Signed-off-by: Franky Lin <frankyl@broadcom.com> Reviewed-on: https://chromium-review.googlesource.com/310982 Commit-Ready: Kevin Cernekee <cernekee@chromium.org> Tested-by: Kevin Cernekee <cernekee@chromium.org> Reviewed-by: Andrew Bresticker <abrestic@chromium.org> " fail_count="0" gerrit_number="310982" owner_email="frankyl@broadcom.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/82/310982/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I284606aa91a76262644cfce60913a91ccc36ae60" commit="24853ee2f7ebf9508744ddd317d9b0869c327da6" commit_message="Cr50: Fix bug in print_later, add overflow detection Oops. I was losing one of the args when the USB debugging output was enabled. And with a lot of messages I was also losing some of the output. BUG=chrome-os-partner:34893 BRANCH=none TEST=make buildall, manual test of Cr50 USB: 1. Plug into a USB jack on a Linux host. 2. In src/platform/ec/extra/usb_console, run make ./usb_console -p 5014 -e 1 3. Type something, hit return 4. See whatever you typed come back with swapped case 5. ^D to quit Change-Id: I284606aa91a76262644cfce60913a91ccc36ae60 Signed-off-by: Bill Richardson <wfrichar@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310846 Reviewed-by: Vadim Bendebury <vbendeb@chromium.org> " fail_count="0" gerrit_number="310846" owner_email="wfrichar@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/46/310846/3" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Iea72e5870b3ec2c2d31188cc405f3e02f27c759d" commit="ea570dcb616f6b7aa13d1e849a1454077554ca8b" commit_message="FROMLIST: usb: dwc2: rockchip: Make the max_transfer_size automatic Previously we needed to set the max_transfer_size to explicitly be 65535 because the old driver would detect that our hardware could support much bigger transfers and then would try to do them. This wouldn't work since the DMA alignment code couldn't support it. Later in commit e8f8c14d9da7 ("usb: dwc2: clip max_transfer_size to 65535") upstream added support for clipping this automatically. Since that commit it has been OK to just use "-1" (default), but nobody bothered to change it. Let's change it to default now for two reasons: - It's nice to use autodetected params. - If we can remove the 65535 limit, we can transfer more! BUG=chrome-os-partner:46623 TEST=Audio is better; other stuff still works Change-Id: Iea72e5870b3ec2c2d31188cc405f3e02f27c759d Signed-off-by: Douglas Anderson <dianders@chromium.org> (am from https://patchwork.kernel.org/patch/7555741/) Reviewed-on: https://chromium-review.googlesource.com/310634 " fail_count="0" gerrit_number="310634" 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/34/310634/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ib01484d1c7727b2a89904ac3ffe4a229c4a2cb61" commit="b6292900c953e179787932d1b2fb75b79f1df7ae" commit_message="Celes : Disable zero finger click and decrease palm pressure. We want to disable "Zero Finger Click" on Celes. We want to decrease palm pressure value. With lower palm pressure value, palm detection performance is better. Fix stack version to 2. BUG=chrome-os-partner:43541 TEST=manual, emerge-celes chromeos-base/gestures-conf check cmt conf in build image. check Zero Finger Click on Celes. check palm detection on Celes. Change-Id: Ib01484d1c7727b2a89904ac3ffe4a229c4a2cb61 Signed-off-by: jongpil19.jung <jongpil19.jung@samsung.com> Reviewed-on: https://chromium-review.googlesource.com/310258 Commit-Ready: Jongpil Jung <jongpil19.jung@samsung.com> Tested-by: Jongpil Jung <jongpil19.jung@samsung.com> Reviewed-by: Charlie Mooney <charliemooney@chromium.org> " fail_count="0" gerrit_number="310258" owner_email="jongpil19.jung@samsung.com" pass_count="0" patch_number="2" project="chromiumos/platform/xorg-conf" project_url="https://chromium-review.googlesource.com/chromiumos/platform/xorg-conf" ref="refs/changes/58/310258/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I6c9955054efd3df4a72a0b1d33f2da9b59771f02" commit="02a2c244d17e0e585e2c76c2e1294031c10a927d" commit_message="brillo_payload_generator: Pass the list of partitions to the generator. The list of A/B partitions is specified in ab_partitions.txt in the .zip file. This patch parses and passes that list to the delta_generator. BUG=b:24387863 TEST=brillo_payload_generator logs out passing the new flags. Change-Id: I6c9955054efd3df4a72a0b1d33f2da9b59771f02 Reviewed-on: https://chromium-review.googlesource.com/310921 Commit-Ready: Alex Deymo <deymo@chromium.org> Tested-by: Alex Deymo <deymo@chromium.org> Reviewed-by: Jason Kusuma <jkusuma@chromium.org> " fail_count="0" gerrit_number="310921" owner_email="deymo@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/21/310921/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iab32c04e5354be3085c3fffc3ed61fb312ac85fa" commit="57113389d80ad16de108564e2fd5ed68b9095346" commit_message="media-libs/waffle: add a cast to appease compiler The earlier change to use EGL_DEFAULT_DISPLAY removed a necessary cast. This change puts it back. BUG=chromium:551644 TEST=emerge-link waffle Change-Id: Iab32c04e5354be3085c3fffc3ed61fb312ac85fa Reviewed-on: https://chromium-review.googlesource.com/310572 Commit-Ready: Frank Henigman <fjhenigman@chromium.org> Tested-by: Frank Henigman <fjhenigman@chromium.org> Reviewed-by: Luis Lozano <llozano@chromium.org> " fail_count="0" gerrit_number="310572" owner_email="fjhenigman@chromium.org" pass_count="0" patch_number="4" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/72/310572/4" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I93690f65850b95842cead7ed79ca8218da70502a" commit="b84e9f3729f2ed733f0abbfad0bec421b4114e65" commit_message="autotest(wifi): Filter out unwanted beacons in pcap network_WiFi_ChannelScanDwellTime expects all the beacons captured during the test to be from the AP's configured with a specific prefix during the test. This results in test failures if there are some background AP's interfering. So, filter out the result before analyzing. While there: Add a check to ensure that we have some valid beacons in our capture before procedding to analyze the captures. BUG=b:25345601 TEST=`test_that --board=$board $host network_WiFi_ChannelScanDwellTime` on Dragonboard. Change-Id: I93690f65850b95842cead7ed79ca8218da70502a Reviewed-on: https://chromium-review.googlesource.com/309620 Commit-Ready: Roshan Pius <rpius@chromium.org> Tested-by: Roshan Pius <rpius@chromium.org> Reviewed-by: mukesh agrawal <quiche@chromium.org> " fail_count="0" gerrit_number="309620" owner_email="rpius@chromium.org" pass_count="0" patch_number="6" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/20/309620/6" remote="cros" total_fail_count="0"/><lkgm version="7611.0.0-rc4"/></manifest> |
