{"push_id":2472285928,"size":81,"distinct_size":81,"ref":"refs/heads/mko-mr1","head":"220b886297b924921cd29670008c9c881da10550","before":"652bc87d9b989288a53c5156b1bb1611c7a91b84","commits":[{"sha":"9408ce8fa553d14e696d1d203e8b9304c5561652","author":{"name":"Isaac Chen","email":"e56bd0201a3803255e0f12a98bc980b9d88a5730@isaacchen.cn"},"message":"fs: pstore: Import Xiaomi change\n\nSigned-off-by: Isaac Chen <isaacchen@isaacchen.cn>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/9408ce8fa553d14e696d1d203e8b9304c5561652"},{"sha":"6008ce05b8b08ca52a4c246cd1b4f85997fb423a","author":{"name":"Ethan Chen","email":"bc6501c174fe21162c67cfc51ecb38b9a4d035f0@gmail.com"},"message":"power: reset: Allow device to preserve memory on restart\n\n* Always perform a soft reset as this preserves memory contents,\n  including pstore and other persistent memory.\n\nChange-Id: Ideca44c9f38d2ebcd437ff289f8e036922eafcd2","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/6008ce05b8b08ca52a4c246cd1b4f85997fb423a"},{"sha":"2a117b3bb30852224135398480bbfcc4f561c59f","author":{"name":"Ricardo Cerqueira","email":"d4e7430f1534a12df46cedd1ac369935436dbb94@cyngn.com"},"message":"power: qpnp-smbcharger: Initialize the type as USB instead of Unknown\n\nThe type of the supply _is_ USB. And userspace looks at it at boot to\nmap out existing supplies\n\nChange-Id: I9e42186ce9f87ab9d4f3afb84c8e6776b08ea88b\n\nConflicts:\n\tdrivers/power/qpnp-smbcharger.c","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/2a117b3bb30852224135398480bbfcc4f561c59f"},{"sha":"3d82bb8fbd56f89f0d2d75c45c81e17e136cad9c","author":{"name":"Ricardo Cerqueira","email":"d4e7430f1534a12df46cedd1ac369935436dbb94@bsp.ninja"},"message":"power: qpnp-smbcharger: Pass voltage limits from charger to USB supply\n\nCurrent userspace uses microvoltage data to calculate charge\nrates instead of assuming 5V.\n\nRef ANDROID7QC-376","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/3d82bb8fbd56f89f0d2d75c45c81e17e136cad9c"},{"sha":"e966aac94a2d7f16b561b74907538a61d35ce370","author":{"name":"dukwung.kim","email":"56268e1de7b87e51c6cd54e9e8cb1cc8fd0f563f@lge.com"},"message":"power: qpnp-smbcharger: init power supply type as USB\n\nIf power supply type is POWER_SUPPLY_TYPE_UNKNOWN at\nbootup, some userspace apps, such as heathd, fail to\nparse power supply properties. So, set power supply type\nto USB when the charger is not plugged during bootup.\n\nChange-Id: Iad3881b0fadb36ace6e5f2de6eaeac11f33a532c\nSigned-off-by: dukwung.kim <dukwung.kim@lge.com>\nSigned-off-by: choongryeol.lee <choongryeol.lee@lge.com>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/e966aac94a2d7f16b561b74907538a61d35ce370"},{"sha":"e2be074eea287112fe40c1dd50b3959ebde66f52","author":{"name":"Animesh Kishore","email":"de971e14a6a45e6396c1cac59fc62fa715d1041e@codeaurora.org"},"message":"msm: mdss: Add multi-rectangle validation support\n\nRectangle number is being passed to kernel from\nuserspace. Added required validation checks.\n\nCRs-Fixed: 2000464\n\nChange-Id: I179caa1a86beb9a8f5f3f9b9ef489bf1fd12c73e\nSigned-off-by: Animesh Kishore <animeshk@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/e2be074eea287112fe40c1dd50b3959ebde66f52"},{"sha":"2d3c52549b597e1e2c6e05f09f866abd21c1c825","author":{"name":"Benjamin Chan","email":"9d02e91494759a45db8e9239adcc094cc8cc249d@codeaurora.org"},"message":"msm: mdss: Retrict use of DMA Multi-Rect for FB pan_display\n\nFor non-atomic display commit that use pan_display, it is not possible\nto use multi-rect feature from the DMA pipe. This fix is to reject any\nmulti-rect DMA pipe being used in the commit when all the non\nmulti-rect DMA pipes are not available.\n\nCRs-Fixed: 2036486\nChange-Id: I16722d62650807b5f46ca2bb544653f43a01edf1\nSigned-off-by: Benjamin Chan <bkchan@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/2d3c52549b597e1e2c6e05f09f866abd21c1c825"},{"sha":"7f061c492896393dc87f58410c0ad4bce124fe81","author":{"name":"Willi Ye","email":"961d3a915928af0641640efab152d3d1523ccd87@gmail.com"},"message":"qpnp-haptic: Add sysfs interface to control intensity\n\nChange-Id: Ib8ad562c5e847a8511bf1e2dbda7c0f863ea25dd","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/7f061c492896393dc87f58410c0ad4bce124fe81"},{"sha":"dedee4713cef15e4a4c4893eeeb71a2bb62f8683","author":{"name":"dianlujitao","email":"426a063be0e36cd758b6e57f81d0d38f9087ed32@gmail.com"},"message":"msm: qpnp-haptic: set up sysfs interface for common cmhw implementation\n\n * Rename vmax_mv to vtg_level\n * Add min/max/default voltage sysfs entries\n\nChange-Id: Iefa3accdb75fcef9bcb2d4c730ca0a72763994f3","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/dedee4713cef15e4a4c4893eeeb71a2bb62f8683"},{"sha":"45b4bbefd1f750864d943350a22592a263e0c246","author":{"name":"Steve Kondik","email":"9ce5770b3bb4b2a1d59be2d97e34379cd192299f@cyngn.com"},"message":"qpnp-haptic: Dejank the haptics\n\n * Add mutexes and call hap_set without the workqueue for direct mode\n\nChange-Id: I98f5b8ddea572def2706ad2cfa18f9dd460757ed","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/45b4bbefd1f750864d943350a22592a263e0c246"},{"sha":"0cd6454e540aa0c412f575561dc45af4905f450c","author":{"name":"Sultanxda","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"msm: qpnp-haptic: Process haptics asynchronously\n\nBlocking the timed_output sysfs node due to mutex contention causes severe\ndevice wake-up latency, as a process crucial to system resume writes to the\ntimed_output vibrator node every time the device is resumed via the\nfingerprint reader (fingerprint reader triggers a haptic response on\nsuccess).\n\nBy processing haptics asynchronously via a worker, the timed_output sysfs\nwon't get stalled for long periods of time (>30ms), and thus the device\nwill consistently wake from sleep faster.\n\nSigned-off-by: Sultanxda <sultanxda@gmail.com>\n\nmsm: qpnp-haptic: Prevent redundant calls to disable vibrator\n\nA redundant call to disable the vibrator right before something wants to\nenable it results in lack of vibration.\n\nAvoid re-disabling haptics to fix this.\n\nSigned-off-by: Sultanxda <sultanxda@gmail.com>\n\nmsm: qpnp-haptic: Start shutoff timer after haptics actually start\n\nqpnp_hap_set() sometimes lags when enabling haptics, causing the shutoff\ntimer to kill the haptics prematurely.\n\nStart the shutoff timer after haptics are enabled so that the requested\nduration is actually carried out.\n\nChange-Id: I91bad94d18415476b5b05c1e1a4a60ae180947df\nSigned-off-by: Sultanxda <sultanxda@gmail.com>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/0cd6454e540aa0c412f575561dc45af4905f450c"},{"sha":"568f723a2175e9b3265ab4e5fa53b8b3010928e5","author":{"name":"André Rivotti Casimiro","email":"bc9800b9d52a24cce72a73dd528afed53f10e5fc@convergent-evolution.com"},"message":"ASoC: wcd-mbhc: correct lineout detection\n\nChange-Id: I9b352b69872e9fb185404457f349c6abef923a4f","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/568f723a2175e9b3265ab4e5fa53b8b3010928e5"},{"sha":"d580cdd389ffd4128d0e968b50164d6111f90178","author":{"name":"Paolo Valente","email":"77843028b8f8419c9977951e271784ccf7804be9@unimore.it"},"message":"block: cgroups, kconfig, build bits for BFQ-v7r8-3.18.0\n\nUpdate Kconfig.iosched and do the related Makefile changes to include\nkernel configuration options for BFQ. Also add the bfqio controller\nto the cgroups subsystem.\n\nChange-Id: I9a935f01f91d9abdc6813a65fc6bd5cd86fbfc74\nSigned-off-by: Paolo Valente <paolo.valente@unimore.it>\nSigned-off-by: Arianna Avanzini <avanzini.arianna@gmail.com>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/d580cdd389ffd4128d0e968b50164d6111f90178"},{"sha":"9ced5f76dba2f6212d2c4abb0fd0946049f7bbcf","author":{"name":"Paolo Valente","email":"77843028b8f8419c9977951e271784ccf7804be9@unimore.it"},"message":"block: introduce the BFQ-v7r8 I/O sched for 3.18.0\n\nAdd the BFQ-v7r8 I/O scheduler to 3.18.0.\nThe general structure is borrowed from CFQ, as much of the code for\nhandling I/O contexts. Over time, several useful features have been\nported from CFQ as well (details in the changelog in README.BFQ). A\n(bfq_)queue is associated to each task doing I/O on a device, and each\ntime a scheduling decision has to be made a queue is selected and served\nuntil it expires.\n\n    - Slices are given in the service domain: tasks are assigned\n      budgets, measured in number of sectors. Once got the disk, a task\n      must however consume its assigned budget within a configurable\n      maximum time (by default, the maximum possible value of the\n      budgets is automatically computed to comply with this timeout).\n      This allows the desired latency vs \"throughput boosting\" tradeoff\n      to be set.\n\n    - Budgets are scheduled according to a variant of WF2Q+, implemented\n      using an augmented rb-tree to take eligibility into account while\n      preserving an O(log N) overall complexity.\n\n    - A low-latency tunable is provided; if enabled, both interactive\n      and soft real-time applications are guaranteed a very low latency.\n\n    - Latency guarantees are preserved also in the presence of NCQ.\n\n    - Also with flash-based devices, a high throughput is achieved\n      while still preserving latency guarantees.\n\n    - BFQ features Early Queue Merge (EQM), a sort of fusion of the\n      cooperating-queue-merging and the preemption mechanisms present\n      in CFQ. EQM is in fact a unified mechanism that tries to get a\n      sequential read pattern, and hence a high throughput, with any\n      set of processes performing interleaved I/O over a contiguous\n      sequence of sectors.\n\n    - BFQ supports full hierarchical scheduling, exporting a cgroups\n      interface.  Since each node has a full scheduler, each group can\n      be assigned its own weight.\n\n    - If the cgroups interface is not used, only I/O priorities can be\n      assigned to processes, with ioprio values mapped to weights\n      with the relation weight = IOPRIO_BE_NR - ioprio.\n\n    - ioprio classes are served in strict priority order, i.e., lower\n      priority queues are not served as long as there are higher\n      priority queues.  Among queues in the same class the bandwidth is\n      distributed in proportion to the weight of each queue. A very\n      thin extra bandwidth is however guaranteed to the Idle class, to\n      prevent it from starving.\n\nChange-Id: I8da08487ff332f178a121c3d906f972f37a71da9\nSigned-off-by: Paolo Valente <paolo.valente@unimore.it>\nSigned-off-by: Arianna Avanzini <avanzini.arianna@gmail.com>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/9ced5f76dba2f6212d2c4abb0fd0946049f7bbcf"},{"sha":"058643ffc8a63373e00faa2d08bce17a673b8476","author":{"name":"Mauro Andreolini","email":"ddd3503978591997e768ebc37fca6c687c31d545@unimore.it"},"message":"block, bfq: add Early Queue Merge (EQM) to BFQ-v7r8 for 3.18.0\n\nA set of processes may happen  to  perform interleaved reads, i.e.,requests\nwhose union would give rise to a  sequential read  pattern.  There are two\ntypical  cases: in the first  case,   processes  read  fixed-size chunks of\ndata at a fixed distance from each other, while in the second case processes\nmay read variable-size chunks at  variable distances. The latter case occurs\nfor  example with  QEMU, which  splits the  I/O generated  by the  guest into\nmultiple chunks,  and lets these chunks  be served by a  pool of cooperating\nprocesses,  iteratively  assigning  the  next  chunk of  I/O  to  the first\navailable  process. CFQ  uses actual  queue merging  for the  first type of\nrocesses, whereas it  uses preemption to get a sequential  read pattern out\nof the read requests  performed by the second type of  processes. In the end\nit uses  two different  mechanisms to  achieve the  same goal: boosting the\nthroughput with interleaved I/O.\n\nThis patch introduces  Early Queue Merge (EQM), a unified mechanism to get a\nsequential  read pattern  with both  types of  processes. The  main idea is\nchecking newly arrived requests against the next request of the active queue\nboth in case of actual request insert and in case of request merge. By doing\nso, both the types of processes can be handled by just merging their queues.\nEQM is  then simpler and  more compact than the  pair of mechanisms used in\nCFQ.\n\nFinally, EQM  also preserves the  typical low-latency properties of BFQ, by\nproperly restoring the weight-raising state of a queue when it gets back to\na non-merged state.\n\nChange-Id: Ie7e0818fe5a7cb58ba84c1605ec6f4cc0414dafd\nSigned-off-by: Mauro Andreolini <mauro.andreolini@unimore.it>\nSigned-off-by: Arianna Avanzini <avanzini.arianna@gmail.com>\nSigned-off-by: Paolo Valente <paolo.valente@unimore.it>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/058643ffc8a63373e00faa2d08bce17a673b8476"},{"sha":"49975bd473d92554e187d59f39b06fe9050a2973","author":{"name":"Yazen Ghannam","email":"90fbc5f72d145c37c06c9ccf437a088384a94d6d@linaro.org"},"message":"crypto: crc32 - Add ARM64 CRC32 hw accelerated module\n\nThis module registers a crc32 algorithm and a crc32c algorithm\nthat use the optional CRC32 and CRC32C instructions in ARMv8.\n\nTested on AMD Seattle.\n\nImprovement compared to crc32c-generic algorithm:\nTCRYPT CRC32C speed test shows ~450% speedup.\nSimple dd write tests to btrfs filesystem show ~30% speedup.\n\nChange-Id: I733dfcfc4a17493fd5d9e63cd30ec394f4ab1f9d\nSigned-off-by: Yazen Ghannam <yazen.ghannam@linaro.org>\nAcked-by: Steve Capper <steve.capper@linaro.org>\nAcked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/49975bd473d92554e187d59f39b06fe9050a2973"},{"sha":"54c10a8dee4f6510edb52693f1970f2ca8e24df4","author":{"name":"Ard Biesheuvel","email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org"},"message":"crypto: arm64/crc32 - bring in line with generic CRC32\n\nThe arm64 CRC32 (not CRC32c) implementation was not quite doing\nthe same thing as the generic one. Fix that.\n\nChange-Id: Ia994facbe7ca05ab852919731eb4c5fb62810919\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nAcked-by: Steve Capper <steve.capper@linaro.org>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/54c10a8dee4f6510edb52693f1970f2ca8e24df4"},{"sha":"3cfc4ae5e3191f424f4d033746ed6648bd3550d6","author":{"name":"Riley Andrews","email":"11e4191b1ae5cae13d3da02c22f40620ad984fdf@google.com"},"message":"arm64: crypto: Change priority of arm64 aes cipher.\n\nChange-Id: I0c614e0eca71b65945ff8bd17c65b03a02918b18\nSigned-off-by: Riley Andrews <riandrews@google.com>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/3cfc4ae5e3191f424f4d033746ed6648bd3550d6"},{"sha":"83139461e12ef8728360e781edd2e71c957dd088","author":{"name":"Ard Biesheuvel","email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org"},"message":"arm64/crypto: issue aese/aesmc instructions in pairs\n\nThis changes the AES core transform implementations to issue aese/aesmc\n(and aesd/aesimc) in pairs. This enables a micro-architectural optimization\nin recent Cortex-A5x cores that improves performance by 50-90%.\n\nMeasured performance in cycles per byte (Cortex-A57):\n\n                CBC enc         CBC dec         CTR\n  before        3.64            1.34            1.32\n  after         1.95            0.85            0.93\n\nNote that this results in a ~5% performance decrease for older cores.\n\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\n(cherry picked from commit 4a97abd44329bf7b9c57f020224da5f823c9c9ea)\nChange-Id: I9d6b28b9bd9263bb273607590704111529323ca9","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/83139461e12ef8728360e781edd2e71c957dd088"},{"sha":"47c7ef7beb778e6b6473ceae4ee561f644d6deb9","author":{"name":"Ard Biesheuvel","email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org"},"message":"arm64: crypto: increase AES interleave to 4x\n\nThis patch increases the interleave factor for parallel AES modes\nto 4x. This improves performance on Cortex-A57 by ~35%. This is\ndue to the 3-cycle latency of AES instructions on the A57's\nrelatively deep pipeline (compared to Cortex-A53 where the AES\ninstruction latency is only 2 cycles).\n\nAt the same time, disable inline expansion of the core AES functions,\nas the performance benefit of this feature is negligible.\n\n  Measured on AMD Seattle (using tcrypt.ko mode=500 sec=1):\n\n  Baseline (2x interleave, inline expansion)\n  ------------------------------------------\n  testing speed of async cbc(aes) (cbc-aes-ce) decryption\n  test 4 (128 bit key, 8192 byte blocks): 95545 operations in 1 seconds\n  test 14 (256 bit key, 8192 byte blocks): 68496 operations in 1 seconds\n\n  This patch (4x interleave, no inline expansion)\n  -----------------------------------------------\n  testing speed of async cbc(aes) (cbc-aes-ce) decryption\n  test 4 (128 bit key, 8192 byte blocks): 124735 operations in 1 seconds\n  test 14 (256 bit key, 8192 byte blocks): 92328 operations in 1 seconds\n\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nSigned-off-by: Catalin Marinas <catalin.marinas@arm.com>\n(cherry picked from commit 0eee0fbd41c7b57d01136df2519c92ec1506e333)\nChange-Id: I0fb82b0cc7f685a13c3d15c919be435917e17429","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_xiaomi_msm8937/commits/47c7ef7beb778e6b6473ceae4ee561f644d6deb9"}]}
{"actor":{"display_login":"mokeeopensource"}}