{"push_id":2337294381,"size":428,"distinct_size":0,"ref":"refs/heads/linux-next/akpm","head":"d866ecab27f6f26a2351d5edceaff123810e62ce","before":"4d5e2d42d01290dcb9f420f614ee906c0bfb87c3","commits":[{"sha":"bff52352e0ccc2481f2b6b0d612ff8ff56c50f3a","author":{"name":"Enric Balletbo i Serra","email":"5389eae92731004100e5e58e118a3072c7860e26@collabora.com"},"message":"usb: dwc3: of-simple: fix oops by unbalanced clk disable call\n\ndwc3_of_simple_dev_pm_ops has never been used since commit a0d8c4cfdf31\n(\"usb: dwc3: of-simple: set dev_pm_ops\"), but this commit has brought\nand oops when unbind the device due this sequence:\n\n  dwc3_of_simple_remove\n   -> clk_disable ...\n      -> pm_runtime_put_sync\n         -> dwc3_of_simple_runtime_suspend\n            -> clk_disable (again)\n\nThis double call to clk_core_disable causes a kernel oops like this:\n\n WARNING: CPU: 1 PID: 4022 at drivers/clk/clk.c:656 clk_core_disable+0x78/0x80\n CPU: 1 PID: 4022 Comm: bash Not tainted 4.15.0-rc4+ #44\n Hardware name: Google Kevin (DT)\n pstate: 80000085 (Nzcv daIf -PAN -UAO)\n pc : clk_core_disable+0x78/0x80\n lr : clk_core_disable_lock+0x20/0x38\n sp : ffff00000bbf3a90\n ...\n Call trace:\n  clk_core_disable+0x78/0x80\n  clk_disable+0x1c/0x30\n  dwc3_of_simple_runtime_suspend+0x30/0x50\n  pm_generic_runtime_suspend+0x28/0x40\n\nThis patch fixes the unbalanced clk disable call by setting the num_clocks\nvariable to zero once the clocks were disabled.\n\nFixes: a0d8c4cfdf31 (\"usb: dwc3: of-simple: set dev_pm_ops\")\nSigned-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/bff52352e0ccc2481f2b6b0d612ff8ff56c50f3a"},{"sha":"e3190868e5f52fb26544f16463593d54ce46ce61","author":{"name":"Yoshihiro Shimoda","email":"806084c42fbad0778b005fdc6faa04d57cfdf777@renesas.com"},"message":"usb: gadget: udc: renesas_usb3: fix oops in renesas_usb3_remove()\n\nThis patch fixes an issue that the renesas_usb3_remove() causes\nNULL pointer dereference because the usb3_to_dev() macro will use\nthe gadget instance and it will be deleted before.\n\nFixes: cf06df3fae28 (\"usb: gadget: udc: renesas_usb3: move pm_runtime_{en,dis}able()\")\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/e3190868e5f52fb26544f16463593d54ce46ce61"},{"sha":"6180026341e852a250e1f97ebdcf71684a3c81b9","author":{"name":"Thinh Nguyen","email":"2826d61ffd89baed1553e5fa7d62c0799c586a70@synopsys.com"},"message":"usb: dwc3: gadget: Set maxpacket size for ep0 IN\n\nThere are 2 control endpoint structures for DWC3. However, the driver\nonly updates the OUT direction control endpoint structure during\nConnectDone event. DWC3 driver needs to update the endpoint max packet\nsize for control IN endpoint as well. If the max packet size is not\nproperly set, then the driver will incorrectly calculate the data\ntransfer size and fail to send ZLP for HS/FS 3-stage control read\ntransfer.\n\nThe fix is simply to update the max packet size for the ep0 IN direction\nduring ConnectDone event.\n\nCc: stable@vger.kernel.org\nFixes: 72246da40f37 (\"usb: Introduce DesignWare USB3 DRD Driver\")\nSigned-off-by: Thinh Nguyen <thinhn@synopsys.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/6180026341e852a250e1f97ebdcf71684a3c81b9"},{"sha":"f035d139ffece7b6a7b8bfb17bd0ba715ee57a04","author":{"name":"Thinh Nguyen","email":"2826d61ffd89baed1553e5fa7d62c0799c586a70@synopsys.com"},"message":"usb: dwc3: ep0: Reset TRB counter for ep0 IN\n\nDWC3 tracks TRB counter for each ep0 direction separately. In control\nread transfer completion handler, the driver needs to reset the TRB\nenqueue counter for ep0 IN direction. Currently the driver only resets\nthe TRB counter for control OUT endpoint. Check for the data direction\nand properly reset the TRB counter from correct control endpoint.\n\nCc: stable@vger.kernel.org\nFixes: c2da2ff00606 (\"usb: dwc3: ep0: don't use ep0in for transfers\")\nSigned-off-by: Thinh Nguyen <thinhn@synopsys.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/f035d139ffece7b6a7b8bfb17bd0ba715ee57a04"},{"sha":"8813a59ed892305b5ac1b5b901740b1ad4b5fefa","author":{"name":"John Keeping","email":"febb44f0a3536761749f6c82b901d79bfa74cce8@metanate.com"},"message":"usb: gadget: f_uac2: fix bFirstInterface in composite gadget\n\nIf there are multiple functions associated with a configuration, then\nthe UAC2 interfaces may not start at zero.  Set the correct first\ninterface number in the association descriptor so that the audio\ninterfaces are enumerated correctly in this case.\n\nReviewed-by: Krzysztof Opasiak <k.opasiak@samsung.com>\nSigned-off-by: John Keeping <john@metanate.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/8813a59ed892305b5ac1b5b901740b1ad4b5fefa"},{"sha":"00b42170c86f90ac9dea83a7dfcd3f0c38098fe2","author":{"name":"Brian Norris","email":"6171de59f5d877bdf30f45ca152231ebf21255a1@chromium.org"},"message":"usb: dwc3: Undo PHY init if soft reset fails\n\nIn this function, we init the USB2 and USB3 PHYs, but if soft reset\ntimes out, we don't unwind this.\n\nNoticed by inspection.\n\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/00b42170c86f90ac9dea83a7dfcd3f0c38098fe2"},{"sha":"c4a5153e87fdf6805f63ff57556260e2554155a5","author":{"name":"Manu Gautam","email":"876e9847b0240db58d29900a57b080fdd1e2cc11@codeaurora.org"},"message":"usb: dwc3: core: Power-off core/PHYs on system_suspend in host mode\n\nCommit 689bf72c6e0d (\"usb: dwc3: Don't reinitialize core during\nhost bus-suspend/resume\") updated suspend/resume routines to not\npower_off and reinit PHYs/core for host mode.\nIt broke platforms that rely on DWC3 core to power_off PHYs to\nenter low power state on system suspend.\n\nPerform dwc3_core_exit/init only during host mode system_suspend/\nresume to addresses power regression from above mentioned patch\nand also allow USB session to stay connected across\nruntime_suspend/resume in host mode. While at it also replace\nexisting checks for HOST only dr_mode with current_dr_role to\nhave similar core driver behavior for both Host-only and DRD+Host\nconfigurations.\n\nFixes: 689bf72c6e0d (\"usb: dwc3: Don't reinitialize core during host bus-suspend/resume\")\nReviewed-by: Roger Quadros <rogerq@ti.com>\nSigned-off-by: Manu Gautam <mgautam@codeaurora.org>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/c4a5153e87fdf6805f63ff57556260e2554155a5"},{"sha":"499350865387f8b8c40a9e9453a9a7eb3cec5dc4","author":{"name":"Fabio Estevam","email":"f37aab7b304f42579817075af31d50648f6a90af@nxp.com"},"message":"usb: phy: mxs: Fix NULL pointer dereference on i.MX23/28\n\nCommit e93650994a95 (\"usb: phy: mxs: add usb charger type detection\")\ncauses the following kernel hang on i.MX28:\n\n[    2.207973] usbcore: registered new interface driver usb-storage\n[    2.235659] Unable to handle kernel NULL pointer dereference at virtual address 00000188\n[    2.244195] pgd = (ptrval)\n[    2.246994] [00000188] *pgd=00000000\n[    2.250676] Internal error: Oops: 5 [#1] ARM\n[    2.254979] Modules linked in:\n[    2.258089] CPU: 0 PID: 1 Comm: swapper Not tainted 4.15.0-rc8-next-20180117-00002-g75d5f21 #7\n[    2.266724] Hardware name: Freescale MXS (Device Tree)\n[    2.271921] PC is at regmap_read+0x0/0x5c\n[    2.275977] LR is at mxs_phy_charger_detect+0x34/0x1dc\n\nmxs_phy_charger_detect() makes accesses to the anatop registers via regmap,\nhowever i.MX23/28 do not have such registers, which causes a NULL pointer\ndereference.\n\nFix the issue by doing a NULL check on the 'regmap' pointer.\n\nFixes: e93650994a95 (\"usb: phy: mxs: add usb charger type detection\")\nCc: <stable@vger.kernel.org> # v4.15\nReviewed-by: Li Jun <jun.li@nxp.com>\nAcked-by: Peter Chen <peter.chen@nxp.com>\nSigned-off-by: Fabio Estevam <fabio.estevam@nxp.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/499350865387f8b8c40a9e9453a9a7eb3cec5dc4"},{"sha":"6cf439e0d37463e42784271179c8a308fd7493c6","author":{"name":"Jack Pham","email":"f646de8ac2008412216aeba4d048e5819cf51aef@codeaurora.org"},"message":"usb: gadget: f_fs: Process all descriptors during bind\n\nDuring _ffs_func_bind(), the received descriptors are evaluated\nto prepare for binding with the gadget in order to allocate\nendpoints and optionally set up OS descriptors. However, the\nhigh- and super-speed descriptors are only parsed based on\nwhether the gadget_is_dualspeed() and gadget_is_superspeed()\ncalls are true, respectively.\n\nThis is a problem in case a userspace program always provides\nall of the {full,high,super,OS} descriptors when configuring a\nfunction. Then, for example if a gadget device is not capable\nof SuperSpeed, the call to ffs_do_descs() for the SS descriptors\nis skipped, resulting in an incorrect offset calculation for\nthe vla_ptr when moving on to the OS descriptors that follow.\nThis causes ffs_do_os_descs() to fail as it is now looking at\nthe SS descriptors' offset within the raw_descs buffer instead.\n\n_ffs_func_bind() should evaluate the descriptors unconditionally,\nso remove the checks for gadget speed.\n\nFixes: f0175ab51993 (\"usb: gadget: f_fs: OS descriptors support\")\nCc: stable@vger.kernel.org\nCo-Developed-by: Mayank Rana <mrana@codeaurora.org>\nSigned-off-by: Mayank Rana <mrana@codeaurora.org>\nSigned-off-by: Jack Pham <jackp@codeaurora.org>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/6cf439e0d37463e42784271179c8a308fd7493c6"},{"sha":"675272d092e4a5570bace92593776f7348daf4c5","author":{"name":"Jack Pham","email":"f646de8ac2008412216aeba4d048e5819cf51aef@codeaurora.org"},"message":"usb: gadget: f_fs: Use config_ep_by_speed()\n\nIn commit 2bfa0719ac2a (\"usb: gadget: function: f_fs: pass\ncompanion descriptor along\") there is a pointer arithmetic\nbug where the comp_desc is obtained as follows:\n\n comp_desc = (struct usb_ss_ep_comp_descriptor *)(ds +\n\t       USB_DT_ENDPOINT_SIZE);\n\nSince ds is a pointer to usb_endpoint_descriptor, adding\n7 to it ends up going out of bounds (7 * sizeof(struct\nusb_endpoint_descriptor), which is actually 7*9 bytes) past\nthe SS descriptor. As a result the maxburst value will be\nread incorrectly, and the UDC driver will also get a garbage\ncomp_desc (assuming it uses it).\n\nSince Felipe wrote, \"Eventually, f_fs.c should be converted\nto use config_ep_by_speed() like all other functions, though\",\nlet's finally do it. This allows the other usb_ep fields to\nbe properly populated, such as maxpacket and mult. It also\neliminates the awkward speed-based descriptor lookup since\nconfig_ep_by_speed() does that already using the ones found\nin struct usb_function.\n\nFixes: 2bfa0719ac2a (\"usb: gadget: function: f_fs: pass companion descriptor along\")\nCc: stable@vger.kernel.org\nSigned-off-by: Jack Pham <jackp@codeaurora.org>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/675272d092e4a5570bace92593776f7348daf4c5"},{"sha":"c49f63055e252810e5d6c83a4943b18db16b3cd8","author":{"name":"Roger Quadros","email":"45431f80c5dfd91b829b7e39671862f046d4356e@ti.com"},"message":"usb: dwc3: omap: don't miss events during suspend/resume\n\nThe USB cable state can change during suspend/resume\nso be sure to check and update the extcon state.\n\nSigned-off-by: Roger Quadros <rogerq@ti.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/c49f63055e252810e5d6c83a4943b18db16b3cd8"},{"sha":"e74bd4d358e5455233f1dcc3975425905b270b91","author":{"name":"Manu Gautam","email":"876e9847b0240db58d29900a57b080fdd1e2cc11@codeaurora.org"},"message":"usb: gadget: core: Fix use-after-free of usb_request\n\nDriver is tracing usb_request after freeing it.\nFix it by changing the order.\n\nSigned-off-by: Manu Gautam <mgautam@codeaurora.org>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/e74bd4d358e5455233f1dcc3975425905b270b91"},{"sha":"b16ea8b9492e99e03b1269fe93ebdbf8e4eabf8a","author":{"name":"Thinh Nguyen","email":"2826d61ffd89baed1553e5fa7d62c0799c586a70@synopsys.com"},"message":"usb: dwc3: Fix GDBGFIFOSPACE_TYPE values\n\nThe FIFO/Queue type values are incorrect. Correct them according to\nDWC_usb3 programming guide section 1.2.27 (or DWC_usb31 section 1.2.25).\n\nAdditionally, this patch includes ProtocolStatusQ and AuxEventQ types.\n\nFixes: cf6d867d3b57 (\"usb: dwc3: core: add fifo space helper\")\nSigned-off-by: Thinh Nguyen <thinhn@synopsys.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/b16ea8b9492e99e03b1269fe93ebdbf8e4eabf8a"},{"sha":"20bf410ecf9e9c045f4b0548d516dd3de8691074","author":{"name":"Ulf Magnusson","email":"264870b8c4e89b6f44c5592420a2bec4c2e7d4e1@gmail.com"},"message":"usb: gadget: udc: Remove USB_GADGET_DUALSPEED select\n\nUSB_GADGET_DUALSPEED was removed by commit 85b8614d7223 (\"usb: gadget:\nget rid of USB_GADGET_{DUAL,SUPER}SPEED\"), but the USB_SNP_UDC_PLAT\nsymbol still selects it.\n\nRemove the USB_GADGET_DUALSPEED select from USB_SNP_UDC_PLAT.\n\nDiscovered with the\nhttps://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py\nscript.\n\nSigned-off-by: Ulf Magnusson <ulfalizer@gmail.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/20bf410ecf9e9c045f4b0548d516dd3de8691074"},{"sha":"17aa31f13cad25daa19d3f923323f552e87bc874","author":{"name":"Yoshihiro Shimoda","email":"806084c42fbad0778b005fdc6faa04d57cfdf777@renesas.com"},"message":"usb: renesas_usbhs: missed the \"running\" flag in usb_dmac with rx path\n\nThis fixes an issue that a gadget driver (usb_f_fs) is possible to\nstop rx transactions after the usb-dmac is used because the following\nfunctions missed to set/check the \"running\" flag.\n - usbhsf_dma_prepare_pop_with_usb_dmac()\n - usbhsf_dma_pop_done_with_usb_dmac()\n\nSo, if next transaction uses pio, the usbhsf_prepare_pop() can not\nstart the transaction because the \"running\" flag is 0.\n\nFixes: 8355b2b3082d (\"usb: renesas_usbhs: fix the behavior of some usbhs_pkt_handle\")\nCc: <stable@vger.kernel.org> # v3.19+\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/17aa31f13cad25daa19d3f923323f552e87bc874"},{"sha":"20c63f4089cceab803438c383631963e34c4d8e5","author":{"name":"Stefan Agner","email":"6fe76ede026e27600863a1ff38da4e776dcaecdf@agner.ch"},"message":"usb: gadget: fsl_udc_core: fix ep valid checks\n\nClang reports the following warning:\n  drivers/usb/gadget/udc/fsl_udc_core.c:1312:10: warning: address of array\n  'ep->name' will always evaluate to 'true' [-Wpointer-bool-conversion]\n        if (ep->name)\n        ~~  ~~~~^~~~\n\nIt seems that the authors intention was to check if the ep has been\nconfigured through struct_ep_setup. Check whether struct usb_ep name\npointer has been set instead.\n\nSigned-off-by: Stefan Agner <stefan@agner.ch>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/20c63f4089cceab803438c383631963e34c4d8e5"},{"sha":"201ec568c57a43dbc73c7ac00e73c3c2d39559fc","author":{"name":"Minas Harutyunyan","email":"61028789fee5c2264f4998ff864864817b9ad55d@synopsys.com"},"message":"usb: dwc2: Add safety check in setting of descriptor chain pointers\n\nIn some cases device sending ZLP IN on non EP0 which\nreassigning EP0 OUT descriptor pointer to that EP.\nDedicated for EP0 OUT descriptor multiple time re-used by\nother EP while that descriptor already in use by EP0 OUT\nfor SETUP transaction. As result when SETUP packet received\nBNA interrupt asserting.\n\nIn dwc2_hsotg_program_zlp() function dwc2_gadget_set_ep0_desc_chain()\nmust be called only for EP0.\n\nAcked-by: John Youn <johnyoun@synopsys.com>\nSigned-off-by: Minas Harutyunyan <hminas@synopsys.com>\nSigned-off-by: Grigor Tovmasyan <tovmasya@synopsys.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/201ec568c57a43dbc73c7ac00e73c3c2d39559fc"},{"sha":"9e95a66cce7250c358d496e1c3b62e29ce79ef40","author":{"name":"Minas Harutyunyan","email":"61028789fee5c2264f4998ff864864817b9ad55d@synopsys.com"},"message":"usb: dwc2: Add safety check for STSPHSERCVD intr\n\nSTSPHSERCVD (status phase received) interrupt should be\nhandled when EP0 is in DWC2_EP0_DATA_OUT state.\n\nSometimes STSPHSERCVD interrupt asserted , when EP0\nis not in DATA_OUT state. Spurios interrupt.\n\nAcked-by: John Youn <johnyoun@synopsys.com>\nSigned-off-by: Minas Harutyunyan <hminas@synopsys.com>\nSigned-off-by: Grigor Tovmasyan <tovmasya@synopsys.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/9e95a66cce7250c358d496e1c3b62e29ce79ef40"},{"sha":"755d739534f998d92e348fba8ffb0478416576e7","author":{"name":"Vardan Mikayelyan","email":"652f65f71531a76937e013094864c653d473eef9@synopsys.com"},"message":"usb: dwc2: Fix dwc2_hsotg_core_init_disconnected()\n\nWe should call dwc2_hsotg_enqueue_setup() after properly\nsetting lx_state. Because it may cause error-out from\ndwc2_hsotg_enqueue_setup() due to wrong value in lx_state.\n\nIssue can be reproduced by loading driver while connected\nA-Connector (start in A-HOST mode) then disconnect A-Connector\nto switch to B-DEVICE.\n\nAcked-by: John Youn <johnyoun@synopsys.com>\nSigned-off-by: Vardan Mikayelyan <mvardan@synopsys.com>\nSigned-off-by: Grigor Tovmasyan <tovmasya@synopsys.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/755d739534f998d92e348fba8ffb0478416576e7"},{"sha":"af6657ca21ee036643f3f39cd96f9f6a5303ea39","author":{"name":"Kishon Vijay Abraham I","email":"669a5051aa3ad2b0bd05b89e440269ea9433179e@ti.com"},"message":"mmc: sdhci-omap: Update 'power_mode' outside sdhci_omap_init_74_clocks\n\nUpdating 'power_mode' in sdhci_omap_init_74_clocks results in\n'power_mode' never updated to MMC_POWER_OFF during card\nremoval. This results in initialization sequence not sent to the\ncard during re-insertion.\nFix it here by adding sdhci_omap_set_power_mode to update power_mode.\nThis function can also be used later to perform operations that\nare specific to a power mode (e.g, disable tuning during power off).\n\nSigned-off-by: Kishon Vijay Abraham I <kishon@ti.com>\nAcked-by: Adrian Hunter <adrian.hunter@intel.com>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm/commits/af6657ca21ee036643f3f39cd96f9f6a5303ea39"}]}
{"actor":{"display_login":"Jackeagle"}}