{"push_id":721780438,"size":10,"distinct_size":10,"ref":"refs/heads/LNX.LA.3.5.2.2.1_rb1","head":"76e6ab6844a429f7518ad2df809aa49a70f63c9d","before":"18cdeb684f0a050dd97bcbf59fdccd3a16371269","commits":[{"sha":"7d5fde11e32aaeee2fa5c4fcfe62883528652d93","author":{"email":"6439d4d9ffdf8e13b6026617ba51aa18f8d15ddd@codeaurora.org","name":"Mahesh A Saptasagar"},"message":"wcnss: add null check in pm_ops unregister\n\nAdd null check for pm_ops in pm_ops unregister to avoid\nnull pointer dereference.\n\nChange-Id: I885618a3244b91ba5eddcadb81ae08e965db63b3\nCRs-Fixed: 690191\nSigned-off-by: Mahesh A Saptasagar <msapta@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/7d5fde11e32aaeee2fa5c4fcfe62883528652d93"},{"sha":"126190dd27b274490983717919ac361383982c51","author":{"email":"879c510d2a39b8f040e184ea2c0202dd3e019172@codeaurora.org","name":"Ashish Jain"},"message":"ASoC: msm: fix bounds checking for ADM get params\n\nUpdate boundary check in ADM_GET_PARAM response,\nthe param_size returned from DSP is in number\nof bytes, update the same in GET_PARAM_CDM_RSP.\n\nChange-Id: Iac0f0c070a021618499bf8545c455885f2346d6a\nSigned-off-by: Ashish Jain <ashishj@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/126190dd27b274490983717919ac361383982c51"},{"sha":"835350fe71adfd97e157acf769725361cc090e24","author":{"email":"d3c7bae90ce2477533ec852edf38b65198016249@localhost","name":"Linux Build Service Account"},"message":"Merge 7d5fde11e32aaeee2fa5c4fcfe62883528652d93 on remote branch\n\nChange-Id: Ia35e56d092c96174033b1b6bc280d4d9b05043f1","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/835350fe71adfd97e157acf769725361cc090e24"},{"sha":"d7e026fc17ca683f380dd6ea53ee3e323761c263","author":{"email":"879c510d2a39b8f040e184ea2c0202dd3e019172@codeaurora.org","name":"Ashish Jain"},"message":"ASoC: msm: fix bounds checking for ADM get params\n\nUpdate boundary check in ADM_GET_PARAM response,\nthe param_size returned from DSP is in number\nof bytes, update the same in GET_PARAM_CDM_RSP.\n\nChange-Id: Iac0f0c070a021618499bf8545c455885f2346d6a\nSigned-off-by: Ashish Jain <ashishj@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/d7e026fc17ca683f380dd6ea53ee3e323761c263"},{"sha":"f20cc13f9df566cdceaabcbda15c5f39df0a6750","author":{"email":"76e30dc6511df6537bc8f74ebde59f1a6034d162@codeaurora.org","name":"Vijayavardhan Vennapusa"},"message":"USB: dwc3: ep0: Use WARN_ON_ONCE to fix message flooding issue\n\nCurrently driver is using WARN_ON to print call stack whenever\nstarting control transfer fails. This could cause issue of\nflooding of messages. Hence fix this by moving to WARN_ON_ONCE.\nAlso add debug events in case of error instead printing error\nmessage.\n\nChange-Id: Ie3b52b046276d82a7055e9b43d081408c7bcff51\nSigned-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/f20cc13f9df566cdceaabcbda15c5f39df0a6750"},{"sha":"baa8dd5e2767021fb055e24a847818ff80b9d91c","author":{"email":"d3c7bae90ce2477533ec852edf38b65198016249@localhost","name":"Linux Build Service Account"},"message":"Merge 126190dd27b274490983717919ac361383982c51 on remote branch\n\nChange-Id: Id1dba835fb853b73d2b2e69fa6d0b804aeb9f824","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/baa8dd5e2767021fb055e24a847818ff80b9d91c"},{"sha":"226131828d34a9b8ca6d711ecce852eb0d144e00","author":{"email":"4ea348ebd818e67772cb0086d44dc1b57ba54129@freescale.com","name":"Timur Tabi"},"message":"dt: introduce for_each_available_child_of_node, of_get_next_available_child\n\nMacro for_each_child_of_node() makes it easy to iterate over all of the\nchildren for a given device tree node, including those nodes that are\nmarked as unavailable (i.e. status = \"disabled\").\n\nIntroduce for_each_available_child_of_node(), which is like\nfor_each_child_of_node(), but it automatically skips unavailable nodes.\nThis also requires the introduction of helper function\nof_get_next_available_child(), which returns the next available child\nnode.\n\nChange-Id: I9ea2f76c0359bf27256d61302db9ab0feec86bc6\nSigned-off-by: Timur Tabi <timur@freescale.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nGit-commit: 3296193d1421c2d6f9e49e181cecfd917f0f5764\n[mgautam@codeaurora.org: resolve trivial merge conflicts]\nSigned-off-by: Manu Gautam <mgautam@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/226131828d34a9b8ca6d711ecce852eb0d144e00"},{"sha":"1aa0b8142e36c17643b164fd53865ecf24c32090","author":{"email":"d3c7bae90ce2477533ec852edf38b65198016249@localhost","name":"Linux Build Service Account"},"message":"Merge \"USB: dwc3: ep0: Use WARN_ON_ONCE to fix message flooding issue\" into LNX.LA.3.5.2.2.1_rb1","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/1aa0b8142e36c17643b164fd53865ecf24c32090"},{"sha":"f480ced8071a00e239bc725508d049476f9aa1c3","author":{"email":"51907cac86db5f2ed57a4ac58c042ecc27c0b352@codeaurora.org","name":"Manu Gautam"},"message":"usb: dwc3: Improve erratic errors events handling\n\nIn rare cases if the controller is unable to communicate with the\nPHY it will trigger an ERRATIC ERROR event, upon which it is\nrecommended that the controller be reset. Currently the reset\nis scheduled to be performed in a workqueue, which relinquishes\nthe dwc3_interrupt handler to continue to process the event buffer.\nMeanwhile if the reset runs concurrently, it would disable the core\nclock resulting in unclocked I/O access if the gadget interrupt handler\ncontinues to run. Fix this by bailing out from ISR and prevent further\ninterrupts from reading DWC3 registers until the reset sequence has\ncompleted.\nAs sometimes after receiving erratic event controller is generating\ninterrupt storm even if driver acknowledges events generated after erratic\nevents. This continues until block reset happens from wq and may result in\nwatchdog bark. To prevent this assert core soft reset and wait until\nerratic event recovery is performed which brings the core out of reset for\nnormal operation.\nThe current handling of erratic errors that occur in peripheral\nmode does so by scheduling a block reset. Since this occurs\nasynchronously, additional changes needed to be made to ensure\nthe device controller would not generate spurious events or\ntry to access any registers while the reset was in progress\nand the clocks were off. Even after that, the controller would\nstill not be functional until a cable reconnect since the block\nreset routine did not do anything to re-establish the peripheral\nsession.\n\nInstead, improve the erratic error handling to simulate a\ncable disconnection-reconnection sequence. The forced disconnect\nshould solve issues related to post-error events as well as\nprevent any function drivers from continuing to issue endpoint\ncommands. This is followed with the controller entering low\npower mode. If the cable is still physically connected, then\ninvoke a reconnection which does the full reset and power-on\ninitialization sequence that is more complete than the current\nblock reset. The USB session would then get re-enumerated\n\nChange-Id: I45ccb30ff12064e5410d45c423a404d97b299022\nSigned-off-by: Jack Pham <jackp@codeaurora.org>\nSigned-off-by: Hemant Kumar <hemantk@codeaurora.org>\nSigned-off-by: Azhar Shaikh<azhars@codeaurora.org>\nSigned-off-by: Manu Gautam <mgautam@codeaurora.org>\nSigned-off-by: Karthik Jadala <karthikjk@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/f480ced8071a00e239bc725508d049476f9aa1c3"},{"sha":"76e6ab6844a429f7518ad2df809aa49a70f63c9d","author":{"email":"76e30dc6511df6537bc8f74ebde59f1a6034d162@codeaurora.org","name":"Vijayavardhan Vennapusa"},"message":"USB: dwc3: msm: Don't disable/enable clocks if in lpm during block reset\n\nWhenever interrupt is triggered for erratic event, USB driver schedules\nwork to do USB block reset as part of recovery. Currently while doing\nblock reset, not checking whether USB is in lpm and going ahead with\ndisabling clocks which messup clock counters. Hence check if USB is in lpm\nand do disabling/enabling clocks only if it is not lpm\n\nChange-Id: Ib28e76f0786184506bec69b7541e56dd7a16ed0f\nSigned-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>\nSigned-off-by: Karthik Jadala <karthikjk@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/76e6ab6844a429f7518ad2df809aa49a70f63c9d"}]}