| <?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="09edad6e69fb57097299a2d346f916983a8c7ab6" 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="326375b8027a4c874afe9487c0a7912c7260dda5" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="1f9ca48a305f5ae34699629b5345a9bdb9656295" 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="1c924c19d271bb5b17a743e499edd06826cc5222" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="641b1f8ad2bea61409e0f966db404387ce3fe8b9" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="ba4e00f161e55bd7967e154aba7755f96470e935" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/dm-verity" path="src/platform/verity" revision="c4df284b32558f631862f79c75fc03af4f5ca68a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/drm-tests" path="src/platform/drm-tests" revision="987a60f5ae48541c1df1aab8a01560446b712f76" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/ec" path="src/platform/ec" revision="2ea7b194d928950db1aed87097975a8ffb9df2ac" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory" path="src/platform/factory" revision="f14ac0a16e21e17da9067929a6bccdb879036211" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory_installer" path="src/platform/factory_installer" revision="f90b5268a73704d68700a782d170261d546fd85a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/firmware" path="src/platform/firmware" revision="8b14a26ccaaac20c33535a38199273c0acecb33f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/frecon" path="src/platform/frecon" revision="38917fe2b121610c487570bb41f97167a76132ce" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/gestures" path="src/platform/gestures" revision="05325e18158f8519f853e086e92c04504e2b87aa" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/glbench/images" path="src/platform2/glbench/images" revision="5fd5ce655833f65d46b1950bec4eedeb4e96959b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/go-seccomp" path="src/platform/go-seccomp" revision="0280326e5bd212fcfbe3696e113730045debae74" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/google-breakpad" path="src/platform/google-breakpad" revision="cf5b98e801bcf0218dfe19ac722c5fa600814678" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/initramfs" path="src/platform/initramfs" revision="7efff0e164437b46def2b2f556d822827e29a0be" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/inputcontrol" path="src/platform/inputcontrol" revision="ae0b15dc322bab9bf6d7c4fcd5f77d488766a275" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/jabra_vold" path="src/platform/jabra_vold" revision="5ee665e7c68856d3b6ce8bb0f610d43503e603af" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/libevdev" path="src/platform/libevdev" revision="61f882f395b9f39478d7164209e7134cccdcb72b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/memento_softwareupdate" path="src/platform/memento_softwareupdate" revision="0b6e7be80034cbede5e111108c46bb75bb5942dd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/microbenchmark" path="src/platform/microbenchmark" revision="d5ea30febe406c5b486325dfae926564f3a46efd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/minigbm" path="src/platform/minigbm" revision="dc94b474288cec3c8c9ca55e0f0b5ee2d681f2e7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/monitor_reconfig" path="src/platform/monitor_reconfig" revision="c02c806dfe581dcff530f75f7b73847f7c3dc229" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mosys" path="src/platform/mosys" revision="46479afc8eb9d0801e2ee066ec6b1842d8ab8290" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtpd" path="src/platform/mtpd" revision="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="e1517ab9becc2b8525a4352943febc794d107b7f" 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="b491bc8bb1499452536eb140c22f749d1c9f9fc3" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/vpd" path="src/platform/vpd" revision="f07e3dfe1be57bc778d84657bf051ff50443cf56" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/webplot" path="src/platform/webplot" revision="bbd5ea22ef9f8e109e363b26958d9a2fc8921f0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/wireless_automation" path="src/platform/wireless_automation" revision="d7177dbd464f2952e10309bf1eef56bb31a7f8ad" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/workarounds" path="src/platform/workarounds" revision="48a42e96e26edd12bf295ea13b50bcdd40c068e3" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xf86-input-cmt" path="src/platform/xf86-input-cmt" revision="3f2ffc921952e57a4343463b0679d90b80b51fc7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xorg-conf" path="src/platform/xorg-conf" revision="2389885e788815f7d44b6cd3160c4085da7e689e" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform2" path="src/platform2" revision="964d08ddbc222c92f3e9a6602674fa6f5dfbfdfe" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/repohooks" path="src/repohooks" revision="81d07144f3790a66819ecd320101bfdf51dd15f8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/adhd" path="src/third_party/adhd" revision="bc573a33370cf0a323cb7c5dd4fe2956a0141e2f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/android_mtdutils" path="src/third_party/android_mtdutils" revision="9bcfc3ee238f16925e9aaa4573129784ebb397e7" upstream="chromeos"/> |
| <project name="chromiumos/third_party/arm-trusted-firmware" path="src/third_party/arm-trusted-firmware" revision="f57e2db6ef4b86a6af57891a2d7a90266ad6c033" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/atheros" path="src/third_party/atheros" revision="52a5bdaa8930c14ee42518354de3e5ec09911c6b" upstream="refs/heads/master"/> |
| <project groups="buildtools" name="chromiumos/third_party/autotest" path="src/third_party/autotest/files" revision="9c451b48cabb46e26af40bfb7dd689ac719b5f14" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/binutils" path="src/third_party/binutils" revision="ff847b57d425687df548c860b48851f090bd79e2" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bluez" path="src/third_party/bluez" revision="3cc29b0281e14f1bb5b36e9a569c663cc54db970" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bootstub" path="src/third_party/bootstub" revision="5ac54e8d3d305c2c6c7297e8e54d3cf7e4629b29" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/broadcom" path="src/third_party/broadcom" revision="4070e7161f2f1a1a22027a744eb868500688f0b6" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bsdiff" path="src/third_party/bsdiff" revision="8c17bdc0d759c8e6da90c5f72b052ba2605a0a3a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cbootimage" path="src/third_party/cbootimage" revision="b7d5b2d6a6dd05874d86ee900ff441d261f9034c" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/chrontel" path="src/third_party/chrontel" revision="7bcd0328d0eeef6a0539bd0ba80cd9a545e6cf4a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/coreboot" path="src/third_party/coreboot" revision="e7fee2450a7ec96f345047830e2017778b72bdf9" 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="f40dc81315226652baad6bd18d1b515597a95b5a" upstream="refs/heads/chromeos-3.8"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.10" revision="d200a34f72072cd531f08bba1b5d7e32d6b65e7a" upstream="refs/heads/chromeos-3.10"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.14" revision="6f3810a070803092d5e9e9aa5dde90d1a9d9c275" upstream="refs/heads/chromeos-3.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="155881f37f8624bb2d2d6ef42bb849d6943a08db" upstream="refs/heads/chromeos-3.18"/> |
| <project name="chromiumos/third_party/khronos" path="src/third_party/khronos" revision="c4932bd57b6edfc42773b4527180a219b9af9ca4" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libc-bench" path="src/third_party/libc-bench" revision="76793dd4b09191a78a78180012718e72d792717f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libmbim" path="src/third_party/libmbim" revision="c4e2949edeed01ca3b810729a7af0d265c49629b" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libqmi" path="src/third_party/libqmi" revision="a436c551cf226af66cdb3dd74ee3971d0b1dae04" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libresample" path="src/third_party/libresample" revision="cc9f20f439396b7d45e94b8301edd95d33f26a46" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libscrypt" path="src/third_party/libscrypt" revision="b45c53f9418a6eff2c8ed98703a55f96029304b1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libsigrok" path="src/third_party/libsigrok" revision="199fe31115c76231746f5953271795d58679561c" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrok-cli" path="src/third_party/sigrok-cli" revision="c9edfa218e5a5972531b6f4a3ece8d33a44ae1b5" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrokdecode" path="src/third_party/libsigrokdecode" revision="3279c2825684c7009775b731d0a9e37815778282" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libv4lplugins" path="src/third_party/libv4lplugins" revision="07f7a81118f74a8a7bc4ef5b81ee651aa12b8adb" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/linux-firmware" path="src/third_party/linux-firmware" revision="0ece365f95c0b1a81dc9b768504c5994202798c8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ltp" path="src/third_party/ltp" revision="4290bd545748cae9e3abad8113dcf4f6dc82e840" upstream="refs/heads/chromeos-20150119"/> |
| <project name="chromiumos/third_party/marvell" path="src/third_party/marvell" revision="f1684f7174aad3f4249416a3e9049899d05824ba" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/memtest" path="src/third_party/memtest" revision="3d4be6e3bfd819856e38a82e35c206fec4551851" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa" revision="c2a0600d5b0645533ba442b5ab879b23c2564a4d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa-img" revision="129178893b2260df22db96327c5ca9c2ce7db046" upstream="refs/heads/mesa-img"/> |
| <project name="chromiumos/third_party/minifakedns" path="src/third_party/miniFakeDns" revision="6184bea119dea53da539727fe8c2a116f98cef24" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mmc-utils" path="src/third_party/mmc-utils" revision="c2faa3df83d679cb01b553d567b16ecc2299f134" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/modemmanager-next" path="src/third_party/modemmanager-next" revision="52fbe37e5d78011366eec0033d5374a0c8950f0e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/opencryptoki" path="src/third_party/opencryptoki" revision="b67690aeeb4174b2253db18a9c1b19eeb219a4ef" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ply-image" path="src/third_party/ply-image" revision="7d5367e2a8618718e90274ae920bc6f406b59b9e" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/third_party/pyelftools" path="chromite/third_party/pyelftools" revision="19b3e610c86fcadb837d252c794cb5e8008826ae" upstream="refs/heads/master-0.22"/> |
| <project groups="project_sdk" name="chromiumos/third_party/rootdev" path="src/third_party/rootdev" revision="5d7d7ff513315abd103d0c95e92ae646c1a7688c" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/seabios" path="src/third_party/seabios" revision="3004147dd3707e600772ec6c5d37beac7f4b8eb4" upstream="refs/heads/chromeos-2014.11.03"/> |
| <project name="chromiumos/third_party/sysbios" path="src/third_party/sysbios" revision="33e1db34b8162de72a5e9bbbc44e6bce38978396" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegra-power-query" path="src/third_party/tegra-power-query" revision="66f1f0d949f4ca4836c1a65b622629205240e37a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegrastats" path="src/third_party/tegrastats" revision="1be161a89525d840e1f6d1f21b3f45645a7dedb3" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tlsdate" path="src/third_party/tlsdate" revision="ab36a75379f1cfaa7a803cb6f8b33ad31e49fcbf" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm-emulator" path="src/third_party/tpm-emulator" revision="310a21ef24ace14b4d6e8095172445494f54ff25" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm2" path="src/third_party/tpm2" revision="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="Ia74f40a2463df0419e511590e7250932da8d58ce" commit="a491b13006390410d13ac1c670a834a7a0b23ddb" commit_message="UPSTREAM: ath9k: add correct MAC/BB name for ar9561 MAC/BB name is"????" if the MAC/BB is unknown. Signed-off-by: Miaoqing Pan <miaoqing@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 1165dd900cc8de3addbc8bef7e6196b07799d25e) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ia74f40a2463df0419e511590e7250932da8d58ce Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310080 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="310080" 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/80/310080/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ia440a6d4d8643372cbdc63fd334a488baede5d68" commit="18cb706a81ff342a537ad7656bf77b528fc96baa" commit_message="UPSTREAM: ath9k_htc: do ani shortcalibratio if we got -ETIMEDOUT current code will handle -ETIMEDOUT as success which is probalbly wrong. According to this comment I assume it is safe to handle -ETIMEDOUT as false: drivers/net/wireless/ath/ath9k/calib.c 290 /* 291 * We timed out waiting for the noisefloor to load, probably due to an 292 * in-progress rx. Simply return here and allow the load plenty of time 293 * to complete before the next calibration interval. We need to avoid 294 * trying to load -50 (which happens below) while the previous load is 295 * still in progress as this can cause rx deafness. Instead by returning 296 * here, the baseband nf cal will just be capped by our present 297 * noisefloor until the next calibration timer. 298 */ Since no other error wariants are present, this patch is checking only for (ret <= 0). Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 14250640cd52bf12831799c35502184c4ae8963b) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ia440a6d4d8643372cbdc63fd334a488baede5d68 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310081 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="310081" 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/81/310081/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ia7b8367ad6d621af06454acbb3a6f87c862dfcbc" commit="9d2b382d3ec6bd86bd8599a723c3766179709893" commit_message="UPSTREAM mac80211: allow to transmit A-MSDU within A-MPDU Advertise the capability to send A-MSDU within A-MPDU in the AddBA request sent by mac80211. Let the driver know about the peer's capabilities. Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com> (cherry picked from commit d1a72f4d58016abbec2bcfb27d5fdcc07b08fc89) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ia7b8367ad6d621af06454acbb3a6f87c862dfcbc Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310082 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="310082" 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/82/310082/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I06f977cc32bdcfd778b1bc3fe764be1890d3549a" commit="1b59254c16670809f6b7bb32a951f75520fe3a78" commit_message="UPSTREAM: ath10k: enable monitor when OTHER_BSS requested By default, ath10k restricts received frames to those matching BSSID. When other BSS frames are requested (e.g. in mesh mode), add an internal monitor device so those frames are not filtered. Signed-off-by: Bob Copeland <me@bobcopeland.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 0d031c8995bcc065f9c5778069f2131f7d92d4d5) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I06f977cc32bdcfd778b1bc3fe764be1890d3549a Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310083 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="310083" 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/83/310083/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I8b76d21b020a77f7b331459bd600dc61cb9fdbc3" commit="09ccf55bd00fa32acdf908991ad45767f20484ac" commit_message="UPSTREAM: ath10k: check for encryption before adding MIC_LEN In the case of raw mode without nohwcrypt parameter, we should still make sure the frame is protected before adding MIC_LEN to avoid skb_under_panic errors. Signed-off-by: Bob Copeland <me@bobcopeland.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit bc76c28719d4333248a516fd4d469ab741b44b63) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I8b76d21b020a77f7b331459bd600dc61cb9fdbc3 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310084 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="310084" 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/84/310084/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I70df114a630c178288827294afd4f66baff0d315" commit="5d82612b72d62ed67258962ae131045a3a847307" commit_message="UPSTREAM: ath10k: implement mesh support Add support for mesh to ath10k. We simply use an AP virtual interface in the firmware in order to enable beaconing without TSF adoption, and use the raw (802.11) transmit mode. Due to firmware limitations, the firmware must operate in raw (non-native 802.11) mode. As this is configured at firmware init time, a new "rawmode" modparam is added, and mesh interfaces are available only if rawmode=true. The firmware must advertise support for rawmode; tested successfully with firmware 10.2.4.70.6-2. When the module is loaded with (newly implemented) modparam rawmode=1, it will enable operating an open mesh STA via something like the following: ip link set wlan0 down iw dev wlan0 set type mp ip link set wlan0 up iw dev wlan0 set freq 5745 80 5775 iw dev wlan0 mesh join mesh-vht Signed-off-by: Bob Copeland <me@bobcopeland.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit b6c7bafa7d4b1398cce93e4af0a48603919fa933) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I70df114a630c178288827294afd4f66baff0d315 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310085 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="310085" 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/85/310085/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I79c99361ec4781fd86840b4b84d0cc53636edf99" commit="4d16915b5919e0f139c534d1089d739f82cbeed2" commit_message="UPSTREAM: ath10k: move hw_scan worker queuing The remain_on_channel callback needs different timeout. Calling ieee80211_queue_work() with a shorter delay after calling it with a longer delay will not change the timer. This caused the offchannel timeout worker to not trigger in time and caused the device to stay on channel longer then expected. This could cause some problems and was be easily reproduced with `iw offchannel` command. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 634349bae0b2a23f71cabbdb770d35fffc1aad8c) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I79c99361ec4781fd86840b4b84d0cc53636edf99 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310086 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="310086" 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/86/310086/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I06f12212e57fd22bb57183dd5d314106fe417fe9" commit="ff2c2d6169107ca8ed365fac6468a01cfc190caa" commit_message="UPSTREAM: ath10k: split switch_vif_chanctx guts This is necessary to make vdev restarting logic reusable later. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 7be6d1b7625ab20e1dfde07a0c6dc77784efbb48) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I06f12212e57fd22bb57183dd5d314106fe417fe9 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310087 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="310087" 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/87/310087/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I229707a6cfcb434d3b851fba8c49d56a9339aa8c" commit="ad5cc9818439ac91eb36265c58aebb57e8a08532" commit_message="UPSTREAM: ath10k: handle IEEE80211_CHANCTX_CHANGE_WIDTH properly Vdevs associated with a given chanctx should be restarted if the bandwidth changes. Otherwise traffic may cease. This is known to fix STA CSA with bandwidths wider than 20MHz. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 9713e3de801eb9c2dd2221ba8c1dddd5bc7ba360) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I229707a6cfcb434d3b851fba8c49d56a9339aa8c Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310088 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="310088" 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/88/310088/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ib7c5540d9a62f0e4e5248c67907f95d25636f914" commit="1efd6a81d1f85651c5000652e7413e7888c06f78" commit_message="UPSTREAM: ath10k: add ATH10K_FW_FEATURE_RAW_MODE_SUPPORT to ath10k_core_fw_feature_str[] This was missed in the original commit adding the flag and ath10k only printed "bit10": ath10k_pci 0000:02:00.0: qca988x hw2.0 (0x4100016c, 0x043202ff) fw 10.2.4.70.6-2 api 3 htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 features no-p2p,bit10 Also add a build test to avoid this happening again. Fixes: ccec9038c721 ("ath10k: enable raw encap mode and software crypto engine") Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 5af82fa66a7ee8dfc29fadb487a02e2ef14ea965) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ib7c5540d9a62f0e4e5248c67907f95d25636f914 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310089 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="310089" 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/89/310089/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I987a61c24f698eb36567aebf9d7968584dfa9269" commit="7afcfc2ff969e7ac47ab1f850ceff1e1d14981ec" commit_message="UPSTREAM: ath9k_htc: introduce support for different fw versions Current kernel support only one fw name with theoretically only one fw version located in firmware/htc_[9271|7010].fw. Which is ok so far we have only one fw version (1.3). After we realised new fw 1.4, we faced compatibility problem which was decided to solve by firmware name and location: - new firmware is located now in firmware/ath9k_htc/htc_[9271|7010]-1.4.0.fw - old version 1.3 should be on old place, so old kernel have no issues with it. - new kernels including this patch should be able to try different supported (min..max) fw version. - new kernel should be able to support old fw location too. At least for now. At same time this patch will add new module option which should allow user to play with development fw version without replacing stable one. If user will set ath9k_htc use_dev_fw=1 module will try to find firmware/ath9k_htc/htc_[9271|7010]-1.dev.0.fw first and if it fails, use stable version: for example...1.4.0.fw. Signed-off-by: Oleksij Rempel <linux@rempel-privat.de> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit e904cf6fe23022cde4e0ea9d41601411a315a3dc) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I987a61c24f698eb36567aebf9d7968584dfa9269 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310090 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="310090" 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/90/310090/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I23e0ed899b85cc98720e4c3577fe1733e67c8531" commit="155c5355d1c04900bcf3569e477dbd0d2f46cefd" commit_message="UPSTREAM: ath9k: declare required extra tx headroom ath9k inserts padding between the 802.11 header and the data area (to align it). Since it didn't declare this extra required headroom, this led to some nasty issues like randomly dropped packets in some setups. Cc: stable@vger.kernel.org Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 029cd0370241641eb70235d205aa0b90c84dce44) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I23e0ed899b85cc98720e4c3577fe1733e67c8531 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310091 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="310091" 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/91/310091/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Icdbd447741592376174dc901b754d3409c529772" commit="101a1470119c28704de1b510ae278ded62887266" commit_message="UPSTREAM: ath10k: fix DMA related firmware crashes on multiple devices Some platforms really don't like DMA bursts of 256 bytes, and this causes the firmware to crash when sending beacons. Also, changing this based on the firmware version does not seem to make much sense, so use 128 bytes for all versions. Cc: stable@vger.kernel.org Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 76d164f582150fd0259ec0fcbc485470bcd8033e) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Icdbd447741592376174dc901b754d3409c529772 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310092 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="310092" 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/92/310092/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I30ab7ad0f0cb57a4f72a67988a870b703619f758" commit="dce44c9954c08d3f0f1077a214aa0998f10dffaa" commit_message="UPSTREAM: ath: fix incorrect PPB on JAPAN chirp radar The number of pulses per burst on Japan chirp radar is between 1 and 3. The previous value, 20, is representing number of bursts, but since current DFS detector is using pulse detection other than bursts, use the pulse number for correct radar detection. Also using the highest number helps to avoid false detection. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit b0b252278082787eec54098556566d4d68b8126c) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I30ab7ad0f0cb57a4f72a67988a870b703619f758 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310093 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="310093" 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/93/310093/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I459cc80d2a0c3bf18ae058ffbca9be8a28e5f1fc" commit="4dbcf63ccf17baf3586d12a0d6e869b09c0b28d5" commit_message="UPSTREAM: ath: use PRI value given by spec for fixed PRI PRI value is used as divider when DFS detector analyzes candidate radar pulses. If PRI deviation is big from its origin PRI, DFS detector could miss valid radar reports since HW often misses detecting radar pulses and causes long interval value of pulses. For instance from practical results, if runtime PRI is calculated as 1431 for fixed PRI value of 1428 and delta timestamp logs 15719, the modular remainder will be 1409 and the delta between the remainder and runtime PRI is 22 that is bigger than PRI tolerance which is 16. As a result this radar report will be ignored even though it's valid. By using spec defined PRI for fixed PRI, we can correct this error. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 44acedb00b6d4b56ddab04362ccfa133b0d3b013) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I459cc80d2a0c3bf18ae058ffbca9be8a28e5f1fc Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310094 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="310094" 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/94/310094/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ifa65e0509992e0e25baf987627b60e9d4af3842f" commit="11dedc2035043fa22b163f04da299af90cf39e2c" commit_message="UPSTREAM: ath10k: fix ldpc param for fixed rate ldpc is not configured for fixed rates. This blocks auto rate vs fixed rate performance comparison. Since firmware is considering ldpc vdev param for fixed rate selection, it has to be configured to enable ldpc for fixed rates. Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit bd4a41e6dee43b5b00876e37d42abffa298d63fe) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ifa65e0509992e0e25baf987627b60e9d4af3842f Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310095 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="310095" 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/95/310095/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ife8aa4aabf3430b40f89a779d10e276db02e2209" commit="74466f9d8942112a542e3ec6a7a7109a1bbfacb2" commit_message="UPSTREAM: ath10k: fix MSI-X registering for qca99x0 In case of qca99x0 and MSI-X supported/enabled we failed during interrupts registering with message: ath10k_pci 0000:04:00.0: failed to request MSI-X ce irq 50: -22 Issue/fix was reproduced/tested using Dell Latitude E6430 laptop. Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit b8402d827fbb288f4ecee585e151bab5a81b3c58) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ife8aa4aabf3430b40f89a779d10e276db02e2209 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310096 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="310096" 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/96/310096/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ic6616e4c7026aa0f7c92467b86c991251f1bc5ea" commit="fe2944e56f4d10413675571a8a149fc0d1cbf976" commit_message="UPSTREAM: ath9k: enable hw manual peak calibration for QCA9561 This patch fix https://lists.openwrt.org/pipermail/openwrt-devel/ 2015-August/034979.html. As the peak detect calibration is set incorrectly. Signed-off-by: Miaoqing Pan <miaoqing@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 61d36370e24bb5d8f83481aa6f76fc05385c75c9) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ic6616e4c7026aa0f7c92467b86c991251f1bc5ea Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310097 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="310097" 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/97/310097/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ie5394a28504e5c388c55c89424961a376db13d1f" commit="70267c3576b6ef1f2802cc7b0b4062c49a9cdef3" commit_message="UPSTREAM: ath9k: Add support for OCB mode The patch adds support for "outside the context of a BSS"(OCB) mode to ath9k driver and extends debugfs files by OCB ralated information. This patch was tested on AR9380-AL1A cards. Signed-off-by: Jan Kaisrlik <kaisrja1@fel.cvut.cz> Cc: Michal Sojka <sojkam1@fel.cvut.cz> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 862a336c8302695cbac6d8d752ee9a2429487478) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ie5394a28504e5c388c55c89424961a376db13d1f Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310098 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="310098" 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/98/310098/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I4b8a8f921864d6006993a2c16b11f8c55d2b4f60" commit="ee0b477a217cddd3ada475619d808415d6842f7d" commit_message="UPSTREAM: ath10k: fix checkpatch warning about logical continuations checkpatch found: drivers/net/wireless-4.2/ath/ath9k/core.c:490: Logical continuations should be on the previous line Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit be62e92a5b2b5960b494fc81ce27611240016821) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I4b8a8f921864d6006993a2c16b11f8c55d2b4f60 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310099 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="310099" 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/99/310099/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ic57e301beb6a73c0b32a57089ccb5ab0715d95f9" commit="daeac6269e811cfb0370429ee0e1000fc5ef82a7" commit_message="UPSTREAM: ath10k: indentation fixes checkpatch found: drivers/net/wireless/ath/ath10k/core.c:513: Alignment should match open parenthesis drivers/net/wireless/ath/ath10k/core.c:1266: code indent should use tabs where possible drivers/net/wireless/ath/ath10k/core.c:1267: code indent should use tabs where possible drivers/net/wireless/ath/ath10k/core.c:1268: code indent should use tabs where possible drivers/net/wireless/ath/ath10k/core.c:1269: code indent should use tabs where possible drivers/net/wireless/ath/ath10k/mac.c:4659: Alignment should match open parenthesis drivers/net/wireless/ath/ath10k/mac.c:6271: Alignment should match open parenthesis drivers/net/wireless/ath/ath10k/pci.c:2260: Alignment should match open parenthesis drivers/net/wireless/ath/ath10k/wmi.c:3510: Alignment should match open parenthesis Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 617b0f4d4a69962e0e86604f889d6af9e8f4150d) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ic57e301beb6a73c0b32a57089ccb5ab0715d95f9 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310100 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="310100" 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/00/310100/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I6bcbf710ae655277f4625936124d9193bcb1609c" commit="bb5aee8bc1c4c6e60db0a73697ace879888c66f5" commit_message="UPSTREAM: ath10k: brace style fixes drivers/net/wireless-4.2/ath/ath10k/htt_tx.c:457: braces {} are not necessary for single statement blocks drivers/net/wireless-4.2/ath/ath10k/htt_tx.c:545: braces {} are not necessary for single statement blocks drivers/net/wireless-4.2/ath/ath10k/mac.c:200: braces {} are not necessary for single statement blocks Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit b9e284e515af75e72043bb802cfb52cd9bd04450) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I6bcbf710ae655277f4625936124d9193bcb1609c Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310101 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="310101" 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/01/310101/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I9da2dd2ca9245baa490190cfc950507dcd11da61" commit="9d39c9b8811e0bdd55b6edb8f0a8936e184c2181" commit_message="UPSTREAM: ath10k: remove void function return statements drivers/net/wireless-4.2/ath/ath10k/wmi.c:3023: void function return statements are not generally useful Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 92438a2cdb5d152d152ca7c449b033c255b977b4) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I9da2dd2ca9245baa490190cfc950507dcd11da61 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310102 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="310102" 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/02/310102/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ic8d85f474e7679e7561dfa4f8f72cdcdc58692cc" commit="020cb29e999694896ed07d971e18bfca6139bb45" commit_message="UPSTREAM: ath10k: fix whitespace usage checkpatch found: drivers/net/wireless/ath/ath10k/core.c:574: Blank lines aren't necessary before a close brace '}' drivers/net/wireless/ath/ath10k/mac.c:4067: Missing a blank line after declarations drivers/net/wireless/ath/ath10k/mac.c:4083: Missing a blank line after declarations drivers/net/wireless/ath/ath10k/mac.c:4084: spaces required around that '>>=' (ctx:WxV) drivers/net/wireless/ath/ath10k/pci.c:1507: Missing a blank line after declarations Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 9a14969fa1674d2215d6d9f171ed323bd3ebb39d) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ic8d85f474e7679e7561dfa4f8f72cdcdc58692cc Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310103 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="310103" 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/03/310103/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Idf83a274f761d4dbc5cd48f61ed32260d6278d0f" commit="95fa3c64d9c5948ba1732c3f0946b23c3aa86278" commit_message="UPSTREAM: ath10k: split an unnecessary long line from checkpatch: drivers/net/wireless/ath/ath10k/mac.c:1113: line over 90 characters Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 2a995088c5aec38db6ffbac96c404f75c7dd9d2c) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Idf83a274f761d4dbc5cd48f61ed32260d6278d0f Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310104 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="310104" 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/04/310104/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ib61e883c0c54d5061a443525c8e450c93176ef5d" commit="208efb6cb723c86c0b20ffbd2b10046c04fee224" commit_message="UPSTREAM: ath10k: add a_sle32_to_cpu() Copy a_sle32_to_cpu() from ath6kl so that we can easily handle signed __le32 values. This is needed in struct wmi_pdev_tpc_config_event. Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 3b8fc902e33e65dd859c0f974c0097b177eeb695) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ib61e883c0c54d5061a443525c8e450c93176ef5d Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310105 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="310105" 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/05/310105/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I4bc1951175d5005eab3f9df016b458ba73e60348" commit="6b08da4e4b2827d1abca13e48dc5fcbd4e2c0977" commit_message="UPSTREAM: ath10k: implement debugfs interface for Transmit Power Control stats The Transmit Power Control (TPC) dump will show the power control values for each rate which makes it easier to debug calibration problems. Example usage: TPC config for channel 5180 mode 10 CTL = 0x10 Reg. Domain = 58 Antenna Gain = 1 Reg. Max Antenna Gain = 0 Power Limit = 34 Reg. Max Power = 34 Num tx chains = 3 Num supported rates = 155 **********CDD POWER TABLE******* No. Preamble Rate_code tpc_valu1 tpc_value2 tpc_value3 0 CCK 0x40 0 0 0 1 CCk 0x41 0 0 0 [...] 154 HTCUP 0x 0 24 0 0 **********STBC POWER TABLE****** No. Preamble Rate_code tpc_valu1 tpc_value2 tpc_value3 0 CCK 0x40 0 0 0 [...] 154 HTCUP 0x 0 24 24 0 **********TXBF POWER TABLE****** is used to dump the tx power control stats. Signed-off-by: Maharaja Kennadyrajan <c_mkenna@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 295426669cd68efc84657e6ee426499cfb54346e) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I4bc1951175d5005eab3f9df016b458ba73e60348 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310106 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="310106" 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/06/310106/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Id6ffca6ad7694b61fd727311ce6994bb2af0ee0b" commit="415e1e67392a83732f50309bb74b15eaa826c26f" commit_message="UPSTREAM: ath10k: use Rx decap mode configured when driver registered ath10k is using Native WiFi mode as default mode for both of Tx and Rx path, but it could be changed when driver registers with a module parameter for specific purpose such as mesh. The Rx decap mode sent to firmware during WMI initialization should use the same mode that driver configured at its registration stage in case of using raw mode, so that host driver receives MAC frame header containing necessary fields such as QoS and Mesh Control and uses them in right way to make data traffic work. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit bc27e8cddda69daa324318ffe3d2e1badad07775) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Id6ffca6ad7694b61fd727311ce6994bb2af0ee0b Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310107 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="310107" 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/07/310107/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="If1afd65319fa6b2fd39787872eea6c8f15315346" commit="239b31b222fb1b5ced87955b34da50585316bf27" commit_message="UPSTREAM: ath10k: use pre-allocated DMA buffer in Tx ath10k driver is using dma_pool_alloc per packet and dma_pool_free in coresponding at Tx completion. Use of pre-allocated DMA buffer in Tx will improve saving CPU resource by 5% while it consumes about 56KB memory more as trade off. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 683b95e8071603b4e945cb26dcae0308457ec478) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: If1afd65319fa6b2fd39787872eea6c8f15315346 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310108 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="310108" 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/08/310108/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I79808303c0058d82e2ae53c605d4bef3a28f3301" commit="21ef7d5dea3a99017280c702781324b300906f4b" commit_message="UPSTREAM: ath10k: increase pci wakeup timeout to 30 ms It is noticed that pci wakeup time is exceeding current timeout (10ms) randomly which is tested on QCA988x. So, the wake up time is increased to 30 ms and added debug prints to log total timeout. Signed-off-by: Maharaja Kennadyrajan <c_mkenna@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 39b91b8144e028cbe383548f76c1f8cdb7977532) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I79808303c0058d82e2ae53c605d4bef3a28f3301 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310109 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="310109" 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/09/310109/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ib9a2132cc45e227b9803fbb32b4e7a2bfb90d916" commit="da2883e287ca5ea68660d79a4f9094ee1e528468" commit_message="UPSTREAM: ath10k: optimize ce_lock on post rx buffer processing After processing received packets from copy engine, host will allocate new buffer and queue them back to copy engine ring for further packet reception. On post rx processing path, skb allocation and dma mapping are unnecessarily handled within ce_lock. This is affecting peak throughput and also causing more CPU consumption. Optimize this by acquiring ce_lock only when accessing copy engine ring and moving skb allocation out of ce_lock. In AP148 platform with QCA99x0 in conducted environment, UDP uplink peak throughput is improved from ~1320 Mbps to ~1450 Mbps and TCP uplink peak throughput is increased from ~1240 Mbps (70% host CPU load) to ~1300 Mbps (71% CPU load). Similarly ~40Mbps improvement is observed in downlink path. Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit ab4e3db043589204041c00272f751d05b4e52c50) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ib9a2132cc45e227b9803fbb32b4e7a2bfb90d916 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310110 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="310110" 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/10/310110/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ie76af6fbd6fe9e3beb049f119e0d71094a3b7862" commit="3aad7df59132282f847445a8350060fdacb8f1e4" commit_message="UPSTREAM: ath10k: use station's current operating mode from assoc request The current number of spatial streams used by the client is advertised as a separate IE in assoc request. Use this information to set the NSS operating mode. Fixes: 45c9abc059fa ("ath10k: implement more versatile set_bitrate_mask"). Signed-off-by: Vivek Natarajan <nataraja@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 72f8cef5d1155209561b01e092ce1a04ad50c4cb) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ie76af6fbd6fe9e3beb049f119e0d71094a3b7862 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310111 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="310111" 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/11/310111/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ic1808c9f3a9146448460564534087c34b5898899" commit="8a2d6a5f9bd2ae5bfda269f68688c64762de5612" commit_message="UPSTREAM: ath: fix DFS timestamp wraparound reset condition The DFS pattern detector ought to reset the detector lines when a pulse is added with lower time stamp than the previous (which indicates a TSF restart). This did not work so far and is fixed with this patch. The modification does not change detection performance within the driver, since it only ensures early reset (which is later performed by the PRI detectors anyway). It is relevant for synthetic tests and statistical evaluations, where millions of pulse patterns are processed and an early reset helps reducing load. Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 706452b06866f950febb91e582c1d06c03ca85ee) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ic1808c9f3a9146448460564534087c34b5898899 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310112 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="310112" 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/12/310112/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I25ae4d8ee31e501c143d4225f92d0e0f904ec71c" commit="9799e6abd19c71d5a94713a03dd6c9211b405aef" commit_message="UPSTREAM: ath10k: add board 2 API support QCA6174 needs different board files based on board type. To make it easier to distribute multiple board files and automatically choose correct board file create a simple TLV file format following the same principles as with FW IEs. The file is named board-2.bin and contain multiple board files. Each board file then can have multiple names. ath10k searches for file board-N.bin (where N is the interface version number for the board file, just like we for firmware files) in /lib/firmware/*, for example for qca99x0 it will try to find it here: /lib/firmware/ath10k/QCA99X0/hw2.0/board-2.bin If ath10k doesn't find board-2.bin then it will fallback to the old board.bin file. This patch adds a simple name scheme using pci device id which for now will be used by qca6174: bus=%s,vendor=%04x,device=%04x,subsystem-vendor=%04x,subsystem-device=%04x This removes the old method of having subsystem ids in ar->spec_board_id and using that in the board file name. Signed-off-by: Manikanta Pubbisetty <c_mpubbi@qti.qualcomm.com> [kvalo@qca.qualcomm.com: simplified the file format, rewrote commit log, other smaller changes] Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 0a51b343abfe2c0dbcbd9ec3c4b18bb8779fefa8) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I25ae4d8ee31e501c143d4225f92d0e0f904ec71c Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310113 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="310113" 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/13/310113/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I6da62737226c471786d1f0566fe486bc95c6da62" commit="52bb4c13a862cdbd129d6abc47fd73cfa3fb7e70" commit_message="UPSTREAM: ath10k: select board data based on BMI chip id and board id QCA99X0 uses radio specific board names based on chip id and board id combinations. We get these IDs from the target using BMI after otp.bin has been started. This patch reorders the call to the function ath10k_core_fetch_board_file so that we have OTP binary before requesting for boardid-chipid. We get this OTP data after parsing firmware-N.bin. [kvalo@qca.qualcomm.com: try BMI_PARAM_GET_EEPROM_BOARD_ID with all boards and detect if command is not supported] Signed-off-by: Manikanta Pubbisetty <c_mpubbi@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit db0984e51a187f5bbe41231af7e671cc12586346) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I6da62737226c471786d1f0566fe486bc95c6da62 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310114 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="310114" 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/14/310114/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I166f3de8b032471871e66cf7d395d9cda4941175" commit="2c1e3bf9efc3e8a06e46625dcfd55bd08a4d708f" commit_message="UPSTREAM: ath10k: fix cleanup in ath10k_thermal_unregister First remove the 'cooling_device#n' syslink created for ath10k and then unregsiter from the thermal subsystem(cooling) Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 83cfce87d91f06e37bd38f782f0714b406a95873) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: I166f3de8b032471871e66cf7d395d9cda4941175 Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310115 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="310115" 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/15/310115/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ie175a0fda6d1b85ef855b2a88e710715f92b306a" commit="21fafc639cf2a5d41ebb0afbbc2ea0117626c1d8" commit_message="UPSTREAM: ath10k: cleanup ath10k_mac_register() error handling The logic in the error-handling path of ath10k_mac_register() is divergent from the logic in ath10k_mac_unregister(). Update the ath10k_mac_register() error handling logic to align with the ath10k_mac_unregister() logic. Signed-off-by: Jeff Johnson <jjohnson@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 0e339447cf2c8b5c742f9be8e2d73bc27b7ac9c4) (source: https://github.com/kvalo/ath/tree/master) BUG=none TEST=none Change-Id: Ie175a0fda6d1b85ef855b2a88e710715f92b306a Signed-off-by: Ashok Raj Nagarajan <arnagara@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/310116 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="310116" 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/16/310116/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I90885447d5ccca1319db9c7c6efa465b85499d7c" commit="45347a6df28b599b16df96d932e6833f61f7bd3a" commit_message="fastboot: Correct "fastboot boot" behavior 1. Fastboot boot should allow only officially-signed recovery images if device is locked or device is unlocked but fastboot full cap is not set in GBB and VbNvStorage. 2. In case of unlocked device with fastboot full cap set, device should allow any valid boot image (signed or unsigned). 3. Add a cleanup on handoff function to decide if device should return OKAY message back to host. 4. If device is not able to boot the memory image, then device should reboot into fastboot mode to ensure a clean state. BUG=chrome-os-partner:44585 BRANCH=None TEST=Compiles successfully for smaug. Change-Id: I90885447d5ccca1319db9c7c6efa465b85499d7c Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/309830 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> " fail_count="0" gerrit_number="309830" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/30/309830/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I51298b2509181392bb5b35db3e36625fad0e7c4f" commit="164b737f5b13e0e482d179310b5825580aa0af3d" commit_message="spi/flash: Provide API to write protect region. BUG=chrome-os-partner:44433 BRANCH=None TEST=Compiles successfully Change-Id: I51298b2509181392bb5b35db3e36625fad0e7c4f Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/295422 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309831 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Reviewed-by: David Hendricks <dhendrix@chromium.org> " fail_count="0" gerrit_number="309831" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/31/309831/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ib85ba9d75ac02116110f719f6d721da2b4aa3161" commit="a8bf46502cb79af3862c3b08ee304a900c9897c9" commit_message="flash: Add support for read_status ops BUG=chrome-os-partner:44433 BRANCH=None TEST=Compiles successfully Change-Id: Ib85ba9d75ac02116110f719f6d721da2b4aa3161 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/296507 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309832 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Reviewed-by: David Hendricks <dhendrix@chromium.org> " fail_count="0" gerrit_number="309832" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/32/309832/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ia9f5605b19806569d484eabf266e2104ade02ccb" commit="2c6f12040838db06e96255dade37116add41cd05" commit_message="flash: Add is_wp_enabled() function This adds a simple check to see if the SPI flash write-protect bit is set. For now it assumes that the status register protect bit is at position 7 which is true for NOR flash chips we currently use in ChromeOS devices. BUG=chrome-os-partner:44433 BRANCH=firmware-smaug TEST=compiles Signed-off-by: David Hendricks <dhendrix@chromium.org> Change-Id: Ia9f5605b19806569d484eabf266e2104ade02ccb Reviewed-on: https://chromium-review.googlesource.com/297415 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Hung-Te Lin <hungte@chromium.org> Tested-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309833 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309833" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/33/309833/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ie7629a3450398042c9fccbf785d7ae8076083610" commit="50a984762af2e738b41196f71217eaa69c21d6aa" commit_message="flash: Add API for is_wp_enabled BUG=chrome-os-partner:44433 BRANCH=None TEST=Compiles successfully. Verified clear_gbb behavior Change-Id: Ie7629a3450398042c9fccbf785d7ae8076083610 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/298073 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309834 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Reviewed-by: David Hendricks <dhendrix@chromium.org> " fail_count="0" gerrit_number="309834" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/34/309834/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I8410fb86ae14e1d1c88b213c1b2d922449b31b3f" commit="fa33493a53449b0517ddbaafe890263cb224dc7c" commit_message="fastboot: Add OEM-specific command to allow write protect BUG=chrome-os-partner:44433 BRANCH=None TEST=Compiles successfully Change-Id: I8410fb86ae14e1d1c88b213c1b2d922449b31b3f Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/295423 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309835 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309835" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/35/309835/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ia534b5bba26330b25074737d77bed4dae9a64e94" commit="8e267115b4f8883029f5287f78a05bbe3101f76e" commit_message="blockdev: Add erase to block ops BUG=chrome-os-partner:44681 BRANCH=None TEST=Compiles successfully. Change-Id: Ia534b5bba26330b25074737d77bed4dae9a64e94 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/296220 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Hung-Te Lin <hungte@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309836 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> " fail_count="0" gerrit_number="309836" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/36/309836/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I40be53b0e26150a8ed3ce5e5a0f308727c9dde88" commit="e60a9bce1fc898279f0e120312832c90476b5a7e" commit_message="flash: Add block_erase operation to flash BUG=chrome-os-partner:44681 BRANCH=None TEST=Compiles successfully Change-Id: I40be53b0e26150a8ed3ce5e5a0f308727c9dde88 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/296221 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Hung-Te Lin <hungte@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309837 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309837" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/37/309837/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I86e1a5d6a67457f69d910e1fffb083111cb3af92" commit="7a558dde3b07bf935b89429a46227b7c3cac0ae6" commit_message="mmc: Add block erase operation to mmc block ops Reference: https://chromium-review.googlesource.com/#/c/295581/ BUG=chrome-os-partner:44681 BRANCH=None TEST=Compiles successfully and verified blocks read back all 0s after TRIM operation. Change-Id: I86e1a5d6a67457f69d910e1fffb083111cb3af92 Signed-off-by: Grant Grundler <grundler@google.com> Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/296222 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309838 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> " fail_count="0" gerrit_number="309838" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/38/309838/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I533361b6495a5555bbf72fea297894eaa4874ee1" commit="d5c4a1c7d5c57a6476d39a617d20d689063c5695" commit_message="fastboot: Use TRIM erase operation instead of fill_write For erasing a partition: 1. Try using TRIM erase operation first. (This reduces the erase time from 25minutes on 23GiB partition to 15 seconds). 2. If TRIM fails, fallback to fill_write with 0xFF. BUG=chrome-os-partner:44681 BRANCH=None TEST=Compiles successfully and erase operation verified. Change-Id: I533361b6495a5555bbf72fea297894eaa4874ee1 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/296223 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309839 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> " fail_count="0" gerrit_number="309839" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/39/309839/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I42f5feb28d5817b6b1de9017101f696faea7f4fe" commit="8353340cbedc42530f2d3db56e1bcb9acf579d04" commit_message="smaug: Change firmware version reporting for fastboot BUG=None BRANCH=None TEST=Compiles successfully and verified bootloader version with OTA. Change-Id: I42f5feb28d5817b6b1de9017101f696faea7f4fe Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/296124 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309840 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309840" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/40/309840/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I92c9ed0dfc7a7ddf577b6b22a84061b3fcefc067" commit="9a30b04a91859e767ecf46509721b8a05ee8e319" commit_message="fastboot: Erase partitions by default Now, since we have the ability to erase partitions in tens of seconds instead of minutes even for 20GiB+ partitions, force erase partitions by default even in unlocked mode. fastboot oem Setenv force-erase:0 can still be used to skip erasing partitions if fastboot GBB override flag is set. BUG=chrome-os-partner:44681 BRANCH=None TEST=Compiles successfully and erase partition works as expected. Change-Id: I92c9ed0dfc7a7ddf577b6b22a84061b3fcefc067 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/296464 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Hung-Te Lin <hungte@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309841 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> " fail_count="0" gerrit_number="309841" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/41/309841/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I3db9503a763d978efed5663caf2481fa9a959621" commit="2ddfc0cfbc2ff40d584971acbef87ee5b18fdc1e" commit_message="GBB: Clear gbb only if wp is not enabled. BUG=chrome-os-partner:44433 BRANCH=None TEST=Compiles successfully for smaug Change-Id: I3db9503a763d978efed5663caf2481fa9a959621 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/309842 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> " fail_count="0" gerrit_number="309842" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/42/309842/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I237bd02c41fed84154ecb33e06b26e3212af7fe6" commit="75c39811b9346be869e1448107600293c04c6364" commit_message="fastboot: Add getvar for reading GBB flags BUG=None BRANCH=None TEST=Compiles successfully and able to read gbb flags. Change-Id: I237bd02c41fed84154ecb33e06b26e3212af7fe6 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/298075 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309843 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309843" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/43/309843/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iff4d5dc2827f2da01656be3b291a7e7b58e240a5" commit="0305e5e3c6df81ab358174f26b8a2f76f993b5c6" commit_message="device_tree: Add verifiedbootstate parameter to device-tree BUG=None BRANCH=None TEST=Compiles successfully. Verified correct value in normal/dev mode. Change-Id: Iff4d5dc2827f2da01656be3b291a7e7b58e240a5 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/299487 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Rom Lemarchand <romlem@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309844 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309844" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/44/309844/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I063e0ef81d9aa31a3a1236d251389801ee816170" commit="3bc1c88cb256b6992ad621ca0ae726e776353955" commit_message="fastboot: Fix double-free Fix-double free of partition string BUG=None BRANCH=None TEST=Compiles succesfully Change-Id: I063e0ef81d9aa31a3a1236d251389801ee816170 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/299810 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309874 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309874" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/74/309874/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Id189449e1a4da2372a70db4c13836ef27b861029" commit="197e15dffe38aa6c670c5c333aebab0a510aa99d" commit_message="fastboot: Re-factor getvar_all for variables with arguments Instead of repeating the same code or adding multiple-checks for table/parameter name for arguments to variables while formatting input command for getvar all, provide a function that accepts: 1. table - containing different records for each possible variable for an argument 2. record_size: size of record in table 3. name_offset: offset of name string in record 4. count: Total number of records in table Prepare appropriate input commands and return values to host in the form of INFO messages. BUG=None BRANCH=None TEST=Compiles successfully. getvar all returns same values as before. Change-Id: Id189449e1a4da2372a70db4c13836ef27b861029 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/299962 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309875 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309875" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/75/309875/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I10a0579e18efed87550afaa7cb26edb91bb82e9b" commit="3f9d6cfafd9911035cf1606c3be95c041fd22b99" commit_message="fastboot: Add Oem-version to getvar Oem-version can be used to get bootloader version for different copies i.e. RO, RW-A and RW-B. This helps test team to quickly check the versions of different firmware copies on device. BUG=None BRANCH=None TEST=Compiles successfully. Reports correct bootloader version. Change-Id: I10a0579e18efed87550afaa7cb26edb91bb82e9b Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/299963 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309876 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309876" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/76/309876/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ic6017834e57bccb75eb0f9ac24f0d96543f84f18" commit="f7bcfcec720e90f126e04ff483dcc9b11c99c6d4" commit_message="command_line: Provide information required for cmdline subst In case of command line being present in the device-tree, currently, no substitution can be performed since kparams info is not passed into commandline_subst correctly. Store kparams pointer in boot_info structure and use that to prepare commandline_info required for substitution. BUG=None BRANCH=None TEST=Added "kernel_guid=%U" to device-tree and depthcharge fills it appropriately. Change-Id: Ic6017834e57bccb75eb0f9ac24f0d96543f84f18 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/299955 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309877 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309877" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/77/309877/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I78db7cdf20febd508a5e17045996dcf1ac705cff" commit="56693b535ec5d17a837ac3fcdfaf2ae745c83a3d" commit_message="ec: Add support to enable/disable motion sense activity BUG=chrome-os-partner:45710 BRANCH=None TEST=Compiles successfully Change-Id: I78db7cdf20febd508a5e17045996dcf1ac705cff Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/301745 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309878 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309878" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/78/309878/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I86f0338073e309203dcc58591e2e1398955963ac" commit="98775b51f7d87ab4ca306ee92cd8919a21bbd0c9" commit_message="fastboot: Add command to disable double-tap BUG=chrome-os-partner:45710 BRANCH=None TEST=Compiles successfully. Change-Id: I86f0338073e309203dcc58591e2e1398955963ac Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/301746 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309879 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309879" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/79/309879/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ib30414640445a6242e4759182b3467a589fe45b9" commit="de82ee8fff98b5c4ccc6c8b880902a9f83c4c71b" commit_message="fastboot: backend: Check for chunk-size overflow always Irrespective of chunk-type (Write, Fill-write, Dont-care, CRC32) always report back an error if chunk size overflows partition-size for sparse image. BUG=None BRANCH=None TEST=Compiles successfully and reports error for image size exceeding partition size. Change-Id: Ib30414640445a6242e4759182b3467a589fe45b9 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/302196 Trybot-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309950 Commit-Ready: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309950" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/depthcharge" project_url="https://chromium-review.googlesource.com/chromiumos/platform/depthcharge" ref="refs/changes/50/309950/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I0e92ada54157d2fd29cbd06fbe5d06fda65642ea" commit="7fddfe927dc7ab3e1154bb26714307820375c180" commit_message="BACKPORT: drm/i915: implement sync_audio_rate callback HDMI audio may not work at some frequencies with the HW provided N/CTS. This patch sets the proper N value for the given audio sample rate at the impacted frequencies. At other frequencies, it will use the N/CTS value which HW provides. Signed-off-by: Libin Yang <libin.yang@intel.com> Reviewed-by: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Takashi Iwai <tiwai@suse.de> Link: git://anongit.freedesktop.org/drm-intel (cherry picked from commit 4a21ef7d1d2b19fdd986783e9ef53bd15fdc87bf) Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com> Conflicts (backport into pre-hdac/intel_audio context): drivers/gpu/drm/i915/i915_dma.c drivers/gpu/drm/i915/i915_drv.h drivers/gpu/drm/i915/intel_audio.c BUG=chrome-os-partner:38919 TEST=On BDW, with entire patch series applied, verify correct programming of N value for TMDS_296M and TMDS_297M with 4K HDMI test instrument for multiple audio rates. Verify proper audio output on 4K HDMI displays. Change-Id: I0e92ada54157d2fd29cbd06fbe5d06fda65642ea Reviewed-on: https://chromium-review.googlesource.com/305218 Commit-Ready: Ullysses A Eoff <ullysses.a.eoff@intel.com> Tested-by: Nathan D Ciobanu <nathan.d.ciobanu@intel.com> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> Reviewed-by: Clinton A Taylor <clinton.a.taylor@intel.com> " fail_count="0" gerrit_number="305218" owner_email="ullysses.a.eoff@intel.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/18/305218/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Id19ae5006a7ed4d33da7b365ab28148e80ac4243" commit="a6580bfc5c18b0612374213e19d67d11c8b287ef" commit_message="BACKPORT: drm/i915: set proper N/CTS in modeset When modeset occurs and the TMDS frequency is set to some speical values, the N/CTS need to be set manually if audio is playing. Signed-off-by: Libin Yang <libin.yang@intel.com> Reviewed-by: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Takashi Iwai <tiwai@suse.de> Link: git://anongit.freedesktop.org/drm-intel (cherry picked from commit 7e8275c2f2bbb384e18af37066b8b2f32b7d092f) Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com> Conflicts (backport into pre-hdac/intel_audio context): drivers/gpu/drm/i915/intel_audio.c include/drm/i915_component.h BUG=chrome-os-partner:38919 TEST=On BDW, with entire patch series applied, verify correct programming of N value for TMDS_296M and TMDS_297M with 4K HDMI test instrument for multiple audio rates. Verify proper audio output on 4K HDMI displays. Change-Id: Id19ae5006a7ed4d33da7b365ab28148e80ac4243 Reviewed-on: https://chromium-review.googlesource.com/305219 Commit-Ready: Ullysses A Eoff <ullysses.a.eoff@intel.com> Tested-by: Nathan D Ciobanu <nathan.d.ciobanu@intel.com> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> Reviewed-by: Clinton A Taylor <clinton.a.taylor@intel.com> " fail_count="0" gerrit_number="305219" owner_email="ullysses.a.eoff@intel.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/19/305219/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I848a3a1c8c4989b681f964e19d29651d2f0ae328" commit="12ad06544fc6e028adec32fb6898ad4905b70d4c" commit_message="UPSTREAM: drm/edid: Fix up clock for CEA/HDMI modes specified via detailed timings EDID detailed timings have a resolution of 10kHz for the pixel clock, so they can't represent certain CEA/HDMI modes accurately. If we see a mode coming in via detailed timings which otherwise matches one of the CEA/HDMI modes except the clock is just a bit off, let's assume that the intention was for that mode to be one of the CEA/HDMI modes and go ahead and fix up the clock to match the CEA/HDMI spec exactly (well, as close as we can get with the 1 kHz resolution we use). This should help code that's looking for an exact clock match (eg. i915 audio N/CTS setup). Cc: Adam Jackson <ajax@redhat.com> Cc: Clint Taylor <clinton.a.taylor@intel.com> Cc: Libin Yang <libin.yang@intel.com> Signed-off-by: Ville Syrjl <ville.syrjala@linux.intel.com> Reviewed-by: Adam Jackson <ajax@redhat.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: git://anongit.freedesktop.org/drm-intel (cherry picked from commit 7a1994136f3a0f32d0f80dff760d3c4d2ea3591b) Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com> BUG=chrome-os-partner:38919 TEST=On BDW, with entire patch series applied, verify correct programming of N value for TMDS_296M and TMDS_297M with 4K HDMI test instrument for multiple audio rates. Verify proper audio output on 4K HDMI displays. Change-Id: I848a3a1c8c4989b681f964e19d29651d2f0ae328 Reviewed-on: https://chromium-review.googlesource.com/305511 Commit-Ready: Ullysses A Eoff <ullysses.a.eoff@intel.com> Tested-by: Nathan D Ciobanu <nathan.d.ciobanu@intel.com> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> Reviewed-by: Clinton A Taylor <clinton.a.taylor@intel.com> " fail_count="0" gerrit_number="305511" owner_email="ullysses.a.eoff@intel.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/11/305511/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I0a1f326156f4f47496be57c61b82da92bb6c8a5f" commit="a4e6298a268ebc1f471f577d2741ec9d813bf1e9" commit_message="UPSTREAM: drm/edid: Round to closest when computing the CEA/HDMI alternate clock Rounding to the closest kHz seems like the better option that round down or up when computing the alternate clock for CEA/HDMI modes. It'll give us a slightly more accurate clock in some cases. Not sure why I went for the down+up approach originally. Perhaps I was thinking we can go back and forth betwen the two frequencies without introducing errors, but round to closest still maintains that property. Cc: Adam Jackson <ajax@redhat.com> Cc: Clint Taylor <clinton.a.taylor@intel.com> Cc: Libin Yang <libin.yang@intel.com> Signed-off-by: Ville Syrjl <ville.syrjala@linux.intel.com> Reviewed-by: Adam Jackson <ajax@redhat.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: git://anongit.freedesktop.org/drm-intel (cherry picked from commit cc9719eb170c41c2e20090c7681e5f805addf39c) Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com> BUG=chrome-os-partner:38919 TEST=On BDW, with entire patch series applied, verify correct programming of N value for TMDS_296M and TMDS_297M with 4K HDMI test instrument for multiple audio rates. Verify proper audio output on 4K HDMI displays. Change-Id: I0a1f326156f4f47496be57c61b82da92bb6c8a5f Reviewed-on: https://chromium-review.googlesource.com/305512 Commit-Ready: Ullysses A Eoff <ullysses.a.eoff@intel.com> Tested-by: Nathan D Ciobanu <nathan.d.ciobanu@intel.com> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> Reviewed-by: Clinton A Taylor <clinton.a.taylor@intel.com> " fail_count="0" gerrit_number="305512" owner_email="ullysses.a.eoff@intel.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/12/305512/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I4ec11648820b048fad482fd656522ce658b49ea8" commit="3a633fe0b0b2223ed58d41443a597737033c74f7" commit_message="BACKPORT: drm/i915: Use round to closest when computing the CEA 1.001 pixel clocks drm_edid.c now computes the alternate CEA clocks using DIV_ROUND_CLOSEST(), so follow suit in the N/CTS setup to make sure we pick the right setting for the mode. Unfortunately we can't actually use DIV_ROUND_CLOSEST() here due to the ({}) construct used, so just stick in raw numbers instead. Cc: Clint Taylor <clinton.a.taylor@intel.com> Cc: Libin Yang <libin.yang@intel.com> Signed-off-by: Ville Syrjl <ville.syrjala@linux.intel.com> (am from https://patchwork.freedesktop.org/patch/61349/) Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com> Applied to intel_display.c instead, since hdac framework does not exist in this kernel version. BUG=chrome-os-partner:38919 TEST=On BDW, with entire patch series applied, verify correct programming of N value for TMDS_296M and TMDS_297M with 4K HDMI test instrument for multiple audio rates. Verify proper audio output on 4K HDMI displays. Change-Id: I4ec11648820b048fad482fd656522ce658b49ea8 Reviewed-on: https://chromium-review.googlesource.com/305513 Commit-Ready: Ullysses A Eoff <ullysses.a.eoff@intel.com> Tested-by: Nathan D Ciobanu <nathan.d.ciobanu@intel.com> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> Reviewed-by: Clinton A Taylor <clinton.a.taylor@intel.com> " fail_count="0" gerrit_number="305513" owner_email="ullysses.a.eoff@intel.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/13/305513/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I7c0f07a3cc06a6e3a09c00a77a2b6afa27be8e1b" commit="269847355e4a58cb1e0b39b1282e583fc12ae717" commit_message="CHROMIUM: drm/i915: Add i915_sync_audio_rate callback Add i915_sync_audio_rate callback to the current HDA-to-i915 interface in intel_pm. This has the same intentions as upstream from git://anongit.freedesktop.org/drm-intel: commit 5334240c30cb0058fa8c373bf0d653337833230d Author: Libin Yang <libin.yang@intel.com> Date: Wed Sep 2 14:11:38 2015 +0800 drm/i915: Add audio sync_audio_rate callback Add the sync_audio_rate callback. With the callback, audio driver can trigger i915 driver to set the proper N/CTS or N/M based on different sample rates. ...however, the upstream version depends on the hdac framework which does not exist in this kernel version. Hence, the custom solution. BUG=chrome-os-partner:38919 TEST=On BDW, with entire patch series applied, verify correct programming of N value for TMDS_296M and TMDS_297M with 4K HDMI test instrument for multiple audio rates. Verify proper audio output on 4K HDMI displays. Change-Id: I7c0f07a3cc06a6e3a09c00a77a2b6afa27be8e1b Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com> Reviewed-on: https://chromium-review.googlesource.com/305510 Commit-Ready: Ullysses A Eoff <ullysses.a.eoff@intel.com> Tested-by: Nathan D Ciobanu <nathan.d.ciobanu@intel.com> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> " fail_count="0" gerrit_number="305510" owner_email="ullysses.a.eoff@intel.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/10/305510/5" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Iaea641a12eaa41943d12a3270728b8487330201a" commit="13d3640c0bf060765a1d4a7bbd055342eb49a61f" commit_message="CHROMIUM: ALSA: hda - call i915 sync audio rate This has the same intentions as upstream from git://anongit.freedesktop.org/drm-intel: commit ddd621fbba35178643a39559c9688a373285bbc0 Author: Libin Yang <libin.yang@intel.com> Date: Wed Sep 2 14:11:40 2015 +0800 ALSA: hda - display audio call sync_audio_rate callback For display audio, call the sync_audio_rate callback function to do the synchronization between gfx driver and audio driver. ...however, the upstream version depends on the hdac framework which does not exist in this kernel version. Hence, the custom solution. BUG=chrome-os-partner:38919 TEST=On BDW, with entire patch series applied, verify correct programming of N value for TMDS_296M and TMDS_297M with 4K HDMI test instrument for multiple audio rates. Verify proper audio output on 4K HDMI displays. Change-Id: Iaea641a12eaa41943d12a3270728b8487330201a Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com> Reviewed-on: https://chromium-review.googlesource.com/305514 Commit-Ready: Ullysses A Eoff <ullysses.a.eoff@intel.com> Tested-by: Nathan D Ciobanu <nathan.d.ciobanu@intel.com> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> Reviewed-by: Clinton A Taylor <clinton.a.taylor@intel.com> " fail_count="0" gerrit_number="305514" owner_email="ullysses.a.eoff@intel.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/14/305514/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I650f636e23435c4f8e9a26b09a39ef378cd94068" commit="bf64435d9258f07de877cdd5495b00514597dbd4" commit_message="power_LoadTest: Open trap window for auto loaded tabs There's a tab that opens on first login for Chromebooks for free offers. Since every login for power_LoadTest is a first login (since the state is cleared), open a window to catch that tab (and any others) which will be closed by the test later. BUG=None TEST=run power_LoadTest.1hour Check that there are only 5 tabs in the background window Change-Id: I650f636e23435c4f8e9a26b09a39ef378cd94068 Reviewed-on: https://chromium-review.googlesource.com/309543 Commit-Ready: Derek Basehore <dbasehore@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="3" gerrit_number="309543" owner_email="dbasehore@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/43/309543/1" remote="cros" total_fail_count="3"/><pending_commit branch="master" change_id="Ided06df7d51cc193228b3e8344c0de14f9bfa035" commit="4905638f3a4c8d9bf2340da6f2d8c89953405056" commit_message="power_LoadTest: fix names of control variants The new different versions of the test all had power_LoadTest.1hour for the name. This corrects the names for those tests. BUG=None TEST=From workstation: test_that --board <any board> <DUT IP address> power_LoadTest.web_1hour Test will fail since ethernet is connected, but check that it finds the test Change-Id: Ided06df7d51cc193228b3e8344c0de14f9bfa035 Reviewed-on: https://chromium-review.googlesource.com/309544 Commit-Ready: Derek Basehore <dbasehore@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="3" gerrit_number="309544" owner_email="dbasehore@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/44/309544/1" remote="cros" total_fail_count="3"/><pending_commit branch="master" change_id="I39f0ec0d943002b77f95b920f204f31ea99f2cbe" commit="43f3f9127bd43ddc9fa5d45df637513b3cbd6021" commit_message="power_LoadTest: add single page test version This measures the power of an individual page for 5 minutes. BUG=None TEST=from workstation to DUT test_that --board <board> <IP> power_LoadTest on DUT cd /usr/local/autotest ./bin/autotest tests/power_LoadTest/control.single_page --args \ "https://news.google.com" Check that the test runs for 5 minutes with the news.google.com webpage Change-Id: I39f0ec0d943002b77f95b920f204f31ea99f2cbe Reviewed-on: https://chromium-review.googlesource.com/309545 Commit-Ready: Derek Basehore <dbasehore@chromium.org> Tested-by: Matt Sheets <msheets@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="3" gerrit_number="309545" owner_email="dbasehore@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/45/309545/3" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-3.18" change_id="Iafa2c9d98da002ea554d08271146ebec7094d195" commit="abb0a8cec29c28c2dab91136bcb5a87838be27fd" commit_message="FROMLIST: ASoC: rt5677: handle reset_pin logical state correctly According to the datasheet RESET is active low pin, i.e. system goes to reset state when pin is low. Handle logic state correctly - set reset_pin to logical 0 at boot time, and set it to logical 1 when we need to reset the chip. BUG=chrome-os-partner:45497 TEST=check that the chip power usage in reset state is ~0 Change-Id: Iafa2c9d98da002ea554d08271146ebec7094d195 Reviewed-on: https://chromium-review.googlesource.com/309582 Commit-Ready: Anatol Pomazau <anatol@google.com> Tested-by: Anatol Pomazau <anatol@google.com> Reviewed-by: Anatol Pomazau <anatol@google.com> Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="3" gerrit_number="309582" owner_email="anatol@google.com" 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/82/309582/1" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-3.18" change_id="I59b3f1dd0a4b41a97d2287b491c36f2ba1a28a83" commit="5dc11e45c66110355928c723a718cd67333c4271" commit_message="CHROMIUM: Smaug: dts: To put rt5677 into suspend mode use RESET Realtek confirmed that driving POW_LDO2 low causes current leak and recommends keep this pin always HIGH. Instead we are going to put chip into RESET state while in suspend. This reduces power usage to almost zero mW. BUG=chrome-os-partner:45497 TEST=check that the chip power usage in suspend is ~0 Change-Id: I59b3f1dd0a4b41a97d2287b491c36f2ba1a28a83 Reviewed-on: https://chromium-review.googlesource.com/309583 Commit-Ready: Anatol Pomazau <anatol@google.com> Tested-by: Anatol Pomazau <anatol@google.com> Reviewed-by: Anatol Pomazau <anatol@google.com> Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="309583" owner_email="anatol@google.com" 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/83/309583/1" remote="cros" total_fail_count="4"/><pending_commit branch="master" change_id="I046c4f5ebf5a4fed765fa90402704cc5ee61a0a7" commit="0f03be9dab6ebe2f1ad078c7008e18b41dde8a5a" commit_message="quipper: Use test binary from 20151030 BUG=chromium:476570 TEST=unit tests pass CQ-DEPEND=I8ec6d26c15f338d700ad7ed3bccd88a5aea4896c Change-Id: I046c4f5ebf5a4fed765fa90402704cc5ee61a0a7 Signed-off-by: Simon Que <sque@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309989 Reviewed-by: Emma Rapati <rapati@chromium.org> " fail_count="0" gerrit_number="309989" owner_email="sque@chromium.org" pass_count="0" patch_number="1" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/89/309989/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I8ec6d26c15f338d700ad7ed3bccd88a5aea4896c" commit="162fa8d11b74f6a88fe446779b7c8d3731a0ff73" commit_message="quipper: Rename test files to reflect kernel versions BUG=chromium:476570 TEST=unit tests pass CQ-DEPEND=I046c4f5ebf5a4fed765fa90402704cc5ee61a0a7 Change-Id: I8ec6d26c15f338d700ad7ed3bccd88a5aea4896c Signed-off-by: Simon Que <sque@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310051 Reviewed-by: Emma Rapati <rapati@chromium.org> " fail_count="0" gerrit_number="310051" owner_email="sque@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/51/310051/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ia6bb8071fd759545d8cf70d6e73eac494dcddd2f" commit="a72b3f4d72aaffb7eef07c3d5ccd75082db9e28c" commit_message="ACPI / Fan: Use bus id as the name for non PNP0C0B (Fan) devices We have back ported this patch from latest upstream kernel for fan driver. The _ART (Active Cooling Relationship Table), specifies relationship among heat generating sources to a target active cooling device like fan. The _ART table refers to actual bus id name for specifying relationship. Naming "Fan" is not enough as name in the _ART table can change on every platform, to establish relationship for user space thermal controllers. Upstreamed patch: "https://git.kernel.org/cgit/linux/kernel/git/stable/ linux-stable.git/commit/drivers/acpi/fan.c?id=bbb16fef19122ec9f20fb865c45375e12f85d2a1" BRANCH=None BUG=chrome-os-partner:46493 TEST=Built for kunimitsu board. Tested to see that the thermal devices and the participants are enumerated and can be seen in the /sys/bus/platform/devices. Also, checked the FAN type the cooling devices enumerated in the /sys/class/thermal with sysfs interface. Change-Id: Ia6bb8071fd759545d8cf70d6e73eac494dcddd2f Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Shaunak Saha <shaunak.saha@intel.com> Reviewed-on: https://chromium-review.googlesource.com/309581 Commit-Ready: Sumeet R Pawnikar <sumeet.r.pawnikar@intel.com> Tested-by: Sumeet R Pawnikar <sumeet.r.pawnikar@intel.com> Reviewed-by: Brian Bian <brian.bian@intel.com> Reviewed-by: Sumeet R Pawnikar <sumeet.r.pawnikar@intel.com> Reviewed-by: Duncan Laurie <dlaurie@chromium.org> " fail_count="0" gerrit_number="309581" owner_email="shaunak.saha@intel.com" pass_count="0" patch_number="5" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/81/309581/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iaddfbe601c3b50ae5334f24fcad88c5e1df9bc7d" commit="485073f17c3ff4794c6c72aae8efb8bae5e9c9e8" commit_message="FAFT: Modify FWtries test to accomodate Android There is no mechanism in Android to block init from setting fw_tries to 0. Need to modify test to accomodate Android boot behavior. BUG=chromos-partner:46904 BRANCH=None TEST=Ran FWtries on smaug, gnawty, veyron_jerry Change-Id: Iaddfbe601c3b50ae5334f24fcad88c5e1df9bc7d Signed-off-by: Shelley Chen <shchen@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309028 Reviewed-by: danny chan <dchan@chromium.org> Reviewed-by: Furquan Shaikh <furquan@chromium.org> " fail_count="0" gerrit_number="309028" owner_email="shchen@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/28/309028/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I1a54ee90f4daa9f0ef101bfe3160490853f93b3b" commit="bc1c85855b1157c9c10db9e35c822edcf6d2c7cc" commit_message="cros-kernel2: Add Rockchip DP settings As per Heiko's latest tree. BUG=None TEST=DP comes up Change-Id: I1a54ee90f4daa9f0ef101bfe3160490853f93b3b Reviewed-on: https://chromium-review.googlesource.com/310222 Commit-Ready: Douglas Anderson <dianders@chromium.org> Tested-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="0" gerrit_number="310222" owner_email="dianders@chromium.org" pass_count="0" patch_number="1" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/22/310222/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2015.07" change_id="Id681a19d0eedb0e2c29e259c5467bcde577e3460" commit="08e0894e5558b9b9b229f907743cad067096bb31" commit_message="libpayload: usb: xhci: Workaround to get Intel xHCI reset working more reliably Existing Intel xHCI controllers require a delay of 1 mS, after setting the CMD_RESET bit in command register, before accessing any HC registers. This allows the HC to complete the reset operation and be ready for HC register access. Without this delay, the subsequent HC register access, may result in a system hang, very rarely. Verified CherryView / Braswell platforms go through over 1000 warm reboot cycles (which was not possible without this patch), without any xHCI reset hang in depthcharge. BRANCH=None BUG=None TEST=Verified CherryView / Braswell platforms go through over 1000 warm reboot cycles, without any xHCI reset hang in depthcharge. Change-Id: Id681a19d0eedb0e2c29e259c5467bcde577e3460 Signed-off-by: Rajmohan Mani <rajmohan.mani@intel.com> Reviewed-on: https://chromium-review.googlesource.com/310022 Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="0" gerrit_number="310022" owner_email="rajmohan.mani@intel.com" pass_count="0" patch_number="2" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/22/310022/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I32dd118c7c03c5899742cebe437d34b9cef984de" commit="0ec75c9060c9df74a8110bd3d48091d76c5ee884" commit_message="Add support for devserver latestbuild RPC for Android build Add a new request argument os_type to differentiate requests for android builds and ChromeOS builds. The value needs to be set to `android` for any request related to Android build. If the value is not set or has other values, default to ChromeOS builds. BUG=chromium:512668 TEST=run devserver locally, and curl http://localhost:8082/stage?target=shamu-userdebug\&build_id=2040953\&artifacts=test_zip\&branch=git_mnc-release\&os_type=android curl http://localhost:8082/latestbuild?target=shamu-userdebug\&branch=git_mnc-release\&os_type=android Change-Id: I32dd118c7c03c5899742cebe437d34b9cef984de Reviewed-on: https://chromium-review.googlesource.com/308755 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="308755" owner_email="dshi@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/55/308755/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iab5238036cd8329e379d0080e2e5480ef71e9c91" commit="cb53da98cfc19d970a0456cfa5e26a136dcb76cb" commit_message="CRAS: libcras - Add SHM wrappers and Android.mk. BUG=chrome-os-partner:45706 TEST=Test build with tinyalsa. Change-Id: Iab5238036cd8329e379d0080e2e5480ef71e9c91 Reviewed-on: https://chromium-review.googlesource.com/310023 Commit-Ready: Chinyue Chen <chinyue@chromium.org> Tested-by: Chinyue Chen <chinyue@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="0" gerrit_number="310023" owner_email="chinyue@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/adhd" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/adhd" ref="refs/changes/23/310023/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I5c25fd7406e30b96d12bc4bf8210d3c3f4ae79f1" commit="a3eb7f1a4cd93cb632c7dd746156a8086c30e611" commit_message="vboot: Add GBB flag to turn on serial output Currently this does nothing. This will eventually be used to enable serial output. BUG=chromium:210230 BRANCH=none TEST=none Change-Id: I5c25fd7406e30b96d12bc4bf8210d3c3f4ae79f1 Signed-off-by: Mary Ruthven <mruthven@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/309716 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="309716" owner_email="mruthven@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/vboot_reference" project_url="https://chromium-review.googlesource.com/chromiumos/platform/vboot_reference" ref="refs/changes/16/309716/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I9a66949b66e0d6736c007773740b4f7431faa3cc" commit="5728a1804d965c84e653c3f13eec34557c4f5cac" commit_message="stm32: i2c: Use correct timingr values based on clock source Previous change 813e56e10af4 broke this by interchanging the values. BUG=chrome-os-partner:46188 BRANCH=None TEST=`make buildall -j` Change-Id: I9a66949b66e0d6736c007773740b4f7431faa3cc Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310057 Commit-Ready: Shawn N <shawnn@chromium.org> Tested-by: Shawn N <shawnn@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-by: Alec Berg <alecaberg@chromium.org> " fail_count="0" gerrit_number="310057" owner_email="shawnn@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/57/310057/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-2015.07" change_id="If6f8744f020a35a76647366b247723b03c02991a" commit="5057073960fa751e42ba9eb73c9adc6eb7a99afd" commit_message="chell: Fix USB port assignment The PCH pin names in the schematic were incorrectly labeled. BUG=chrome-os-partner:46289 BRANCH=none TEST=build and boot on chell Change-Id: If6f8744f020a35a76647366b247723b03c02991a Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310061 Reviewed-by: Aaron Durbin <adurbin@chromium.org> " fail_count="0" gerrit_number="310061" owner_email="dlaurie@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/61/310061/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I3fbbb4f23c967659c34c4c6cd767b31d0c914c01" commit="b8d48cbbbffda8afe639421ae582e47b60de87ae" commit_message="CHROMIUM: net: wireless: Remove iwl7000 driver from wireless-3.8 All wireless-3.8 users of iwl7000 have moved to using native driver from 3.18 kernel tree. Removing this driver also opens possibility of removing wireless-3.8 subsystem completely. Change-Id: I3fbbb4f23c967659c34c4c6cd767b31d0c914c01 Signed-off-by: Anatol Pomazau <anatol@google.com> Reviewed-on: https://chromium-review.googlesource.com/309551 Reviewed-by: Sameer Nanda <snanda@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> " fail_count="3" gerrit_number="309551" owner_email="anatol@google.com" 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/51/309551/1" remote="cros" total_fail_count="3"/><pending_commit branch="master" change_id="I62c6a3621e2da882a5acd8209c17686152810806" commit="0cbae8de6eba54331641c4615769e683b71c5f61" commit_message="paygen: Generate the payload hash and metadata hash together. Due to recent changes in delta_generator, payload hash and metadata hash are calculated together, calling it twice are just doing repeated work. BUG=None TEST=./paygen_payload_lib_unittest Change-Id: I62c6a3621e2da882a5acd8209c17686152810806 Reviewed-on: https://chromium-review.googlesource.com/310226 Commit-Ready: Sen Jiang <senj@chromium.org> Tested-by: Sen Jiang <senj@chromium.org> Reviewed-by: Matthew Sartori <msartori@chromium.org> Reviewed-by: Alex Deymo <deymo@chromium.org> " fail_count="0" gerrit_number="310226" owner_email="senj@chromium.org" pass_count="0" patch_number="2" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/26/310226/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I2f0970e494ea49611abc315587c7c9aa0bc2d14a" commit="31f2c7006453e212a4d7756f8db05b2a51c26ba9" commit_message="cleanup: Standardize use of CONFIG_I2C and add MASTER/SLAVE CONFIGs Some chips previously defined CONFIG_I2C and others didn't. Standardize the usage by removing CONFIG_I2C from all config_chip files and force it to be defined at the board level. Also, make boards define CONFIG_I2C_MASTER and/or CONFIG_I2C_SLAVE based on the I2C interfaces they will use - this will assist with some later cleanup. BUG=chromium:550206 TEST=`make buildall -j` BRANCH=None Change-Id: I2f0970e494ea49611abc315587c7c9aa0bc2d14a Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310070 Commit-Ready: Shawn N <shawnn@chromium.org> Tested-by: Shawn N <shawnn@chromium.org> Reviewed-by: Alec Berg <alecaberg@chromium.org> " fail_count="0" gerrit_number="310070" owner_email="shawnn@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/70/310070/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ia614bcf5f7aa1e309e6b6d0a32e3cee17c263197" commit="1d03efc95fb3ac7185749e83eeb328f4627547dd" commit_message="Disable security_SandboxStatus temporarily. Until we get a new chrome. I don't want to patch this test any further. BUG=chromium:549472 TEST=disabling this test. Change-Id: Ia614bcf5f7aa1e309e6b6d0a32e3cee17c263197 Reviewed-on: https://chromium-review.googlesource.com/310069 Commit-Ready: Achuith Bhandarkar <achuith@chromium.org> Tested-by: Achuith Bhandarkar <achuith@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> " fail_count="0" gerrit_number="310069" owner_email="achuith@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/69/310069/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iedb389806e2d1f741e498f2854dd9ff83eccf8bb" commit="c246eaa3cb45a976854c3400feac4e21700ea97a" commit_message="cros-board.eclass: add samus-cheets BUG=b:25124604 TEST=build (note: build fails, need to fix elsewhere) Change-Id: Iedb389806e2d1f741e498f2854dd9ff83eccf8bb Reviewed-on: https://chromium-review.googlesource.com/310059 Commit-Ready: Luigi Semenzato <semenzato@chromium.org> Tested-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="0" gerrit_number="310059" owner_email="semenzato@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/59/310059/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ic50311dcabb44939c10492152d96b7833c650ec8" commit="9633f1ed8f047c077e9e3ca0cfd8275d0d56a63c" commit_message="FROMLIST: linux-firmware: New minor DMC release for Skylake - ver1_23 "FROMLIST" + SHA1 below because this is a pull request: Link: http://lists.freedesktop.org/archives/intel-gfx/2015-October/078584.html Version: 1.23 Date : 10/19/2015 Notes: DC 5 and 6 count locations are in the below mentioned offsets - same as ver1.21 DC3_DC5_COUNT 80030 DC5_DC6_COUNT 8002C Following additions from ver1.22 - WA for Palette and DMC RAM corruption issue. Following additions from ver1.21 - PLL lock wait time updated Conflicts: WHENCE (WHENCE is a ToC, so there is a conflict on almost every cherry-pick) Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com> (cherry picked from commit 182a82e604111683e1ab56e588f7a1911e3c9fa3) Signed-off-by: Marc Herbert <marc.herbert@intel.com> BUG=chrome-os-partner:43454,chrome-os-partner:42700 TEST=/lib/firmware/skl_dmc_ver1.bin links to skl_dmc_ver1_23.bin Change-Id: Ic50311dcabb44939c10492152d96b7833c650ec8 Reviewed-on: https://chromium-review.googlesource.com/307904 Commit-Ready: Joe Konno <joe.konno@linux.intel.com> Tested-by: Philip Hanson <philip.hanson@intel.com> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Joe Konno <joe.konno@linux.intel.com> Reviewed-by: James Ausmus <james.ausmus@intel.com> " fail_count="0" gerrit_number="307904" owner_email="marc.herbert@intel.com" pass_count="0" patch_number="1" project="chromiumos/third_party/linux-firmware" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/linux-firmware" ref="refs/changes/04/307904/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I3cb159b685d08d72f7687f0f9206bc207b2eb0f6" commit="92a0cbd0f1541ee4bd4c5cf26318e12e3da07e37" commit_message="Correct frame count conditional. We need to check if the # of golden checkums and the # of test checksums does not differ too much. Add the check in the conditional. BUG=None. TEST=Ran vp8 and mp4 tests on falco. Change-Id: I3cb159b685d08d72f7687f0f9206bc207b2eb0f6 Reviewed-on: https://chromium-review.googlesource.com/310213 Commit-Ready: Mussa Kiroga <mussa@chromium.org> Tested-by: Mussa Kiroga <mussa@chromium.org> Reviewed-by: Mussa Kiroga <mussa@chromium.org> Reviewed-by: Rohit Makasana <rohitbm@chromium.org> " fail_count="0" gerrit_number="310213" owner_email="mussa@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/13/310213/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ibf40a20656c4c99f9625b516cff3e7da9bf2f69d" commit="f3259e8de5432d9d2091860888ef2b5e0ac0d957" commit_message="mec1322: fix gpio_disable_interrupt MEC1322_INT_DISABLE(interrupt enable clear register) is 'Write 1 to Clear' for each bit. To disable interrupt for specific GPIO pin, only specific bit should be written with 1. BUG=NONE BRANCH=NONE TEST=NONE Change-Id: Ibf40a20656c4c99f9625b516cff3e7da9bf2f69d Signed-off-by: Kyoung Kim <kyoung.il.kim@intel.com> Reviewed-on: https://chromium-review.googlesource.com/309979 Commit-Ready: Kyoung Il Kim <kyoung.il.kim@intel.com> Tested-by: Kyoung Il Kim <kyoung.il.kim@intel.com> Reviewed-by: Shawn N <shawnn@chromium.org> " fail_count="0" gerrit_number="309979" owner_email="kyoung.il.kim@intel.com" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/79/309979/2" remote="cros" total_fail_count="0"/><lkgm version="7605.0.0-rc5"/></manifest> |
