{"push_id":674038845,"size":268,"distinct_size":268,"ref":"refs/heads/cm-12.1+","head":"74a1d44871d9e584ae101eec9d1418f257b76f5e","before":"12f55308f1b525e0ae78515b1ad5ac9fe2a73ccc","commits":[{"sha":"5bff9ee1ca0b9f24ae7a1d5e8c3476f7d8e9bad1","author":{"email":"87bc22e1ffe89e26fa2661ba9c7fe7c19f55bf7b@gmail.com","name":"Angelo G. Del Regno -- EternityProject Team Manager"},"message":"arm: Seagull: Use Honami-like panel detection\n\nChange-Id: I57b6b9091b9d17343a03afce3f9302e4056c8201","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/5bff9ee1ca0b9f24ae7a1d5e8c3476f7d8e9bad1"},{"sha":"223ea467dee03f329283f5af2ad513c9a377fe25","author":{"email":"eee1008aa969daf35bfa2c19f1f537b2a04bc90b@cyanogenmod.org","name":"Giulio Cervera"},"message":"driver: sony: fix ifdef\n\nChange-Id: I802855ed4864242bb2d27888149aea48fa804c19","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/223ea467dee03f329283f5af2ad513c9a377fe25"},{"sha":"0391fecdd7dff4a25a862229db05f926edb562ba","author":{"email":"7eedd376b992113fc356f96ef94a5d5b793bb724@gmail.com","name":"angelsl"},"message":"clearpad: Don't break when wakeup_gesture toggled during sleep\n\nLet the wakeup_gesture attribute affect the next suspend of the\ntouchscreen, so that if wakeup_gesture is toggled while the touchscreen\nis suspended, the driver/touchscreen doesn't get confused (because the\ndriver wakes it up assuming it is in normal suspend, but the touchscreen\nis in tap-to-wake mode -- or vice versa).\n\nThis fixes the problem where phone calls cannot be answered with\ntap-to-wake on.\n\nChange-Id: I7fa5a826e84bd4a4b6cd25b8c249d2e83c628d3f\nSigned-off-by: angelsl <hidingfromhidden@gmail.com>\n(cherry picked from commit 6dc479f14b11af754f1b16c4ad7e223dd883eb1f)","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/0391fecdd7dff4a25a862229db05f926edb562ba"},{"sha":"5559e9c91a9e97beebdf95ce9b04ca805587e2f6","author":{"email":"eee1008aa969daf35bfa2c19f1f537b2a04bc90b@cyanogenmod.org","name":"Giulio Cervera"},"message":"rhine: update panel dt\n\nChange-Id: Iee0803da97525f385e1e041e847065958f3f9b7a","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/5559e9c91a9e97beebdf95ce9b04ca805587e2f6"},{"sha":"67cd519e04b476cce4e5ed4faa1aa87be703da17","author":{"email":"e642b69ed2fc111e09ffdc37feb733a52253340d@oracle.com","name":"Sasha Levin"},"message":"net: llc: use correct size for sysctl timeout entries\n\nThe timeout entries are sizeof(int) rather than sizeof(long), which\nmeans that when they were getting read we'd also leak kernel memory\nto userspace along with the timeout values.\n\nChange-Id: I328d1186720a6f70f555eeeb62c83ee69814868d\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/67cd519e04b476cce4e5ed4faa1aa87be703da17"},{"sha":"14fe9338fc21863974ebd0fa33927bc810d6e0de","author":{"email":"5a44e6ed17c4e196d25b9ca3d47678de1c8a63ce@codeaurora.org","name":"Biswajit Paul"},"message":"kernel: Restrict permissions of /proc/iomem.\n\nThe permissions of /proc/iomem currently are -r--r--r--. Everyone can\nsee its content. As iomem contains information about the physical memory\ncontent of the device, restrict the information only to root.\n\nChange-Id: If0be35c3fac5274151bea87b738a48e6ec0ae891\nCRs-Fixed: 786116\nSigned-off-by: Biswajit Paul <biswajitpaul@codeaurora.org>\nSigned-off-by: Avijit Kanti Das <avijitnsec@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/14fe9338fc21863974ebd0fa33927bc810d6e0de"},{"sha":"ad9a5a1c32c59dc0b9d5a8ee088fdb1d6d03c34f","author":{"email":"785dce9813c74aa517a07b7a1160c1a9cdebd7be@codeaurora.org","name":"Swetha Chikkaboraiah"},"message":"cpufreq: cpu-boost: Resolve deadlock when waking up sync thread\n\nWaking up sync thread recursively for same CPU causes deadlock.\nFix this by avoiding recursive wakeup call to same thread.\n\nCRs-Fixed: 814956\nChange-Id: Iaa789bc8a441e56524e0851274765a07937d83fb\nSigned-off-by: Swetha Chikkaboraiah <schikk@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/ad9a5a1c32c59dc0b9d5a8ee088fdb1d6d03c34f"},{"sha":"49e313d98124b93a43718061f09644d29dada171","author":{"email":"d742c8926136147b41811902e91ce4bd1f5cc0f6@codeaurora.org","name":"Mahesh Sivasubramanian"},"message":"tick-broadcast: stubs when CLOCKEVENTS_BROADCAST is not defined\n\nDefine defaults stubs for broadcast APIs when the\nCONFIG_GENERIC_CLOCKEVENTS_BROADCASE isn't defined. This allows the\ndrivers to use them without having to conditionally invoke them.\n\nChange-Id: Ie20c6b5edc771f511ea46ab208e2da4e8dc0e80e\nSigned-off-by: Mahesh Sivasubramanian <msivasub@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/49e313d98124b93a43718061f09644d29dada171"},{"sha":"c12f0ae3eaa87f326299e295e6b7f14045700254","author":{"email":"3728a64ea6ee72edfea11b998ffb0ad08804c46e@codeaurora.org","name":"Niranjana Vishwanathapura"},"message":"crypto: msm: enable rfc4309(ccm(aes)) algorithm\n\nThis patch enables rfc4309(ccm(aes)) algorithm. Further more, it fixes\nan issues with ccm.  According to RFC3610, associate\ndata is optional. The assocaite data length can be 0 as shown in\ntestmgr ccm rfc4309 test vectors. The driver did not take this zero\nlength of  associate data situation into account. And the corresponding\ntest vectors in testmgr may fail.\n\nChange-Id: I2f269a54ad269a8ba72c0e570a7859da223e2d9b\nAcked-by: Chemin Hsieh <cheminh@qti.qualcomm.com>\nSigned-off-by: Niranjana Vishwanathapura <nvishwan@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/c12f0ae3eaa87f326299e295e6b7f14045700254"},{"sha":"5e97726ca37934b01e66c73fb5c0cd69156c2252","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"crypto: msm: Add support for multiple qcrypto devices\n\nExpose APIs to enable qcrypto client to select any specific qcrypto\ninstance.\n\nChange-Id: Ia96f7fa0f15216c0656aa6dc495db350b3c574a8\nSigned-off-by: Mona Hossain <mhossain@codeaurora.org>\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/5e97726ca37934b01e66c73fb5c0cd69156c2252"},{"sha":"67fecd00e9935e4b7e280346d35f96a755886fe8","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"crypto: msm: fix memory leak during algorithm registration\n\nDuring driver algorithm registration, if there are errors, the\ndynamically allocated memory needs to be free on the error return.\nOtherwise, there will be memory leak. This patch fixes memory leak\naccordingly.\n\nChange-Id: Ic3c65ebd3d6c7b0e88815e6750ec14990e375587\nAcked-by: Chemin Hsieh <cheminh@qti.qualcomm.com>\nSigned-off-by: Niranjana Vishwanathapura <nvishwan@codeaurora.org>\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/67fecd00e9935e4b7e280346d35f96a755886fe8"},{"sha":"6480c076c835d25478100178d3dd15655e1de872","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"crypto: msm: add dynamic engine assignment support\n\nThis patch provides dynamic engine assignment for better performances.\n\nA platform may configure to support multiple crypto engines.\nCrypto engine assignment to a tranformer(tfm) can be dynamic. Engine\nassignment is deferred until a request of a tfm is served. In contrary,\nfor static assignment, a crypto engine is statically assigned to a\ntransformer.\n\nThis patch supports both schemes.  A transformer can issue multiple\nasynchronous requests in parallel. In case of static assignment, requests\nof the same tfm are served in sequence by the same engine. In case of\ndynamic assignment, requests can be issued in parallel to different\nhardware engines.\n\nThere is a requirement as such, \"for any tfm, ablkcipher, aead, or ahash,\nthey must return results in the order they were given.\"\nIn case of dynamic assignment, the order of completion from different\nhardware engines may not be in the same order as requests issued.\nDriver needs to re-sequence the order of response for a tfm to meet\nthe requirement.\n\nChange-Id: I26495c1df0e44a5276989c33a19fddb5b107cb13\nAcked-by: Chemin Hsieh <cheminh@qti.qualcomm.com>\nSigned-off-by: Rohit Vaswani <rvaswani@codeaurora.org>\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/6480c076c835d25478100178d3dd15655e1de872"},{"sha":"c5df3a81f49dfdbc20e402f1eca6aadf9c6cb275","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"crypto: msm: re-work qcrypto driver clk and bus management\n\nThis patch re-works bus scaling and clk management to respond to\nthe actual crypto engine usage. The driver suspend/resume are\nintegrated with overall driver clk and bus management.\n\nFurthermore, two functions are added to the low level crypto driver. Low\nlevel crypto driver is informed to save and restored hardware context if\nnecessary across PM suspend/resume.\n\nChange-Id: Ic906e0c7e96dee847253d6ef57341d1a38e294cf\nAcked-by: Chemin Hsieh <cheminh@qti.qualcomm.com>\nSigned-off-by: Rohit Vaswani <rvaswani@codeaurora.org>\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/c5df3a81f49dfdbc20e402f1eca6aadf9c6cb275"},{"sha":"a29a5d91a2b0fb1bf2c5c54dfd8d0b066dd436dc","author":{"email":"39a327f78a3cad909353cd37dc34e1a0b046c78b@codeaurora.org","name":"AnilKumar Chimata"},"message":"crypto: msm: Fix SHA-1/256 zero length input data issue\n\nCrypto module generating wrong hash value for zero length input data\nusing SHA1 and SHA256 functions. This patch fixes the issue to generate\nproper hash value.\n\nChange-Id: I795969cf2d3e3887064d56e35cbb488937051ac8\nSigned-off-by: AnilKumar Chimata <anilc@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/a29a5d91a2b0fb1bf2c5c54dfd8d0b066dd436dc"},{"sha":"ed79033f7ff198b3fc8ec17876b8f7d51058a879","author":{"email":"c2628bef6ffa0036fb3a0b3cff089a3ba875af2e@codeaurora.org","name":"Dinesh K Garg"},"message":"crypto: msm: Add support for FIPS complience\n\nFIPS140-2 certification asks to do a Power on Known Answer tests on each\nalgorithm which is getting certified. This patch implements the self tests\nand hardcoded test vectors.  Also, we need to verify the integrity of\nkernel as soon as it boots up. This patch also adds an ioctl for\nintegrity test along with ioctl to query FIPS status (pass / fail) from\nuser land.\nalso, The piece of code is added for FIPS compliance DRBG under\ndrivers/char/hw_random\nThis change is already merged to KK mainline.\n\nChange-Id: I7f3355602d5c2dfaefce0c0e4f9225fde0c5f485\nSigned-off-by: Dinesh K Garg <dineshg@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/ed79033f7ff198b3fc8ec17876b8f7d51058a879"},{"sha":"cd49fc33b51c95601e374969ef936eb48a795377","author":{"email":"41c88242557e7288c285ee699a693678d02cf422@codeaurora.org","name":"William Clark"},"message":"crypto: msm: Remove bw_reaper_timer while in suspend mode\n\nRemove bw_reaper_timer timer while in suspend mode. Otherwise, it\nmay cause power regression than normal.\n\nChange-Id: I5cab2b75baf96e08c7f7a179fdd15509bd919a69\nAcked-by: Chemin Hsieh <cheminh@qti.qualcomm.com>\nSigned-off-by: William Clark <wclark@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/cd49fc33b51c95601e374969ef936eb48a795377"},{"sha":"b1f6484de6948ea60c0d6445cbc922f0600eff86","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"crypto: msm: change timer operation to fix timer list corruption\n\nremove the dulplicate init_timer operation in _qcrypto_resume and\nreplace add_timer with mod_timer to resolve timer list corruption.\n\nChange-Id: I206016686be568ce2eefc41ea74d34639a8b04e5\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/b1f6484de6948ea60c0d6445cbc922f0600eff86"},{"sha":"ad6bb3646d635256c09c92538b1837d0764cf507","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"crypto: msm: Don't enable crypto clock in PM resume\n\nIf a PM suspend happens right after resume, crypto driver returns\n-EBUSY, since reaper worker thread has not kicked in. The suspend\ncan only succeed after timer kicks in to disable crypto clock and\nfree bus.\nThe solution is as the following. Don't enable crypto\nclock and allocate bus bandwidth when entering resume if\nthere is no outstanding crypto requests. The next crypto\noperation will enable crypto clock then. Further more, this patch\nshortens the reaper timer from 1 second to 200 ms.\n\nChange-Id: I116cf1454b020ee2886c8bf6696b6411a5df83b6\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/ad6bb3646d635256c09c92538b1837d0764cf507"},{"sha":"b3e063fd893d8e239e3e94fca5e8b6508e5a527d","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"crypto: msm: Make changes to the reaper timer\n\nChange the periodical reaper timer to on-demand basis. The reaper timer\nis only set to disable clock after the clock is enabled, and it is\nremoved when there is no crypto operations. So that we can prevent the\ntimers from unnecessarily waking up the CPU from power collapse. The\ntimer interval is changed to 1 second.\n\nCRs-Fixed: 719848\nChange-Id: I88901653b779315de558a33ec6d92979c0176e28\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/b3e063fd893d8e239e3e94fca5e8b6508e5a527d"},{"sha":"e75bd6241fc1634b5450db9e352c182be2b0c359","author":{"email":"41c88242557e7288c285ee699a693678d02cf422@codeaurora.org","name":"William Clark"},"message":"crypto: msm: check potential integer overflow\n\nAccording to the specification of AEAD, AEAD request crypt length is\nnot a fixed maximum and associated length is also same. This could\nlead to potential integer overflow, thus allocating less memory. So\nwe need to check potential integer overflow on AEAD request length.\n\nCRs-Fixed: 726872\nChange-Id: Ie7708000bfd8c57e2fba8e02230a7ce9cdc9634c\nSigned-off-by: William Clark <wclark@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/BobZmotion/android_kernel_sony_msm8974/commits/e75bd6241fc1634b5450db9e352c182be2b0c359"}]}