{"push_id":1303628476,"size":79,"distinct_size":1,"ref":"refs/heads/master","head":"cf60901e26c2b33a2375250470b8e5090c323613","before":"efc56aa7593372abb4b0206fcdc3954132c0ef6e","commits":[{"sha":"b83e867026caedd6d67fccfbe6e9a621edd79b21","author":{"name":"Grant Grundler","email":"7fbd66175251e06d12da27fc2a22a8b88f819c00@chromium.org"},"message":"mmc: core: remove dead function mmc_try_claim_host\n\ncscope says there are no callers for mmc_try_claim_host in the kernel.\nNo reason to keep it.\n\nSigned-off-by: Grant Grundler <grundler@chromium.org>\nAcked-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/b83e867026caedd6d67fccfbe6e9a621edd79b21"},{"sha":"357002b9c09e5332c9fcd4fa3d3c0fa00ca6ae4f","author":{"name":"Kuninori Morimoto","email":"c9d45deca9657f8e968f060b64a4b787b35486ff@renesas.com"},"message":"sh: ecovec: fixup compile error on sdhi\n\nafa2c9407f8908 (\"sh: ecovec24: Use MMC/SDHI CD and RO GPIO\") added\n.tmio_flags = TMIO_MMC_USE_GPIO_CD on sh_mobile_sdhi_info, but it needs\n<linux/mfd/tmio.h> header.  This patch adds it.\n\nSigned-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>\nReviewed-by: Yusuke Goda <yusuke.goda.sx@renesas.com>\nAcked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/357002b9c09e5332c9fcd4fa3d3c0fa00ca6ae4f"},{"sha":"369ac8614fcef040f96f6548acb43dcefebd21b9","author":{"name":"Doug Anderson","email":"654d5d600e907ff4a0e75ec2e21c072be3e1556d@chromium.org"},"message":"mmc: dw_mmc: don't queue up a card detect at slot startup\n\nThe MMC subsystem handles looking for a card at probe time. Queuing up our\nown can race with the rest of the MMC subsystem and cause problems if we\nget unlucky with timing. Just remove driver own detection triggering.  While\nprogressing the request from 'mmc_rescan', if 'dw_mci_work_routine_card'\nroutine is activated, it will cancel the current request. The problem case\nis that 'mmc_rescan' is prior to 'dw_mci_work_routine_card' from host own.\nSpecifically, the following message shows the detection problem in driver's\nprobing. It would get an err -123 (-ENOMEDIUM) during probe.\n\n[    4.216595] dwmmc_exynos 12210000.dwmmc1: Using internal DMA controller.\n[    4.395935] dwmmc_exynos 12210000.dwmmc1: Version ID is 250a\n[    4.401948] dwmmc_exynos 12210000.dwmmc1: DW MMC controller at irq 108, 64 bit host data width, 64 deep fifo\n[    4.424430] dwmmc_exynos 12210000.dwmmc1: sdr0 mode (irq=108, width=0)\n[    4.453975] dwmmc_exynos 12210000.dwmmc1: sdr0 mode (irq=108, width=0)\n[    4.459592] mmc_host mmc1: Bus speed (slot 0) = 100000000Hz (slot req 400000Hz, actual 400000HZ div = 125)\n[    4.484258] dwmmc_exynos 12210000.dwmmc1: 1 slots initialized\n[    4.485406] dwmmc_exynos 12210000.dwmmc1: sdr0 mode (irq=108, width=0)\n[    4.487606] dwmmc_exynos 12210000.dwmmc1: sdr0 mode (irq=108, width=0)\n[    4.489794] dwmmc_exynos 12210000.dwmmc1: sdr0 mode (irq=108, width=0)\n[    4.509757] mmc1: error -123 whilst initialising SDIO card\n\nSigned-off-by: Doug Anderson <dianders@chromium.org>\nAcked-by: Seungwon Jeon <tgih.jun@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/369ac8614fcef040f96f6548acb43dcefebd21b9"},{"sha":"e2c635999f44324d0c9db3330debd807be809507","author":{"name":"Doug Anderson","email":"654d5d600e907ff4a0e75ec2e21c072be3e1556d@chromium.org"},"message":"mmc: dw_mmc: Add exynos resume_noirq callback to clear WAKEUP_INT\n\nIf the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up\nlooping around forever.  This has been seen to happen on exynos5420\nsilicon despite the fact that we haven't enabled any wakeup events due\nto a silicon errata.  It is safe to do on all exynos variants.\n\nSigned-off-by: Doug Anderson <dianders@chromium.org>\nAcked-by: Seungwon Jeon <tgih.jun@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/e2c635999f44324d0c9db3330debd807be809507"},{"sha":"fdf492a1cc6db8c13f650948f43855a077600895","author":{"name":"Doug Anderson","email":"654d5d600e907ff4a0e75ec2e21c072be3e1556d@chromium.org"},"message":"mmc: dw_mmc: Honor requests to set the clock to 0\n\nPreviously the dw_mmc driver would ignore any requests to disable the\ncard's clock.  This doesn't seem like a good thing in general, but had\none extra bad side effect in the following situation:\n* mmc core would set clk to 400kHz at boot time while scanning\n* mmc core would set clk to 0 since no card, but it would be ignored.\n* suspend to ram and resume; clocks in the dw_mmc IP block are now 0\n  but dw_mmc thinks that they're 400kHz (it ignored the set to 0).\n* insert card\n* mmc core would set clk to 400kHz which would be considered a no-op.\n\nNote that if there is no card in the slot and we do a suspend/resume\ncycle, we _do_ still end up with differences in a dw_mmc register\ndump, but the differences are clock related and we've got the clock\ndisabled both before and after, so this should be OK.\n\nSigned-off-by: Doug Anderson <dianders@chromium.org>\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/fdf492a1cc6db8c13f650948f43855a077600895"},{"sha":"2eb2944fa7d14703898063eaee34d41524fb46ad","author":{"name":"Doug Anderson","email":"654d5d600e907ff4a0e75ec2e21c072be3e1556d@chromium.org"},"message":"mmc: dw_mmc: Set timeout to max upon resume\n\nThe TMOUT register is set to 0xffffffff at probe time but isn't\nset after suspend/resume.  Add an init of this value.\n\nNo problems were observed without this (it will also be set in\n__dw_mci_start_request if there is data to send), but it makes the\nregister dump before and after suspend cleaner.\n\nSigned-off-by: Doug Anderson <dianders@chromium.org>\nAcked-by: Seungwon Jeon <tgih.jun@samsung.com>\nReviewed-by: Tomasz Figa <t.figa@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/2eb2944fa7d14703898063eaee34d41524fb46ad"},{"sha":"e6c784eded7b39caeaf2e9206336fa1daeccfd09","author":{"name":"Yuvaraj Kumar C D","email":"575c9eb6d334b08a4adc258040710e4ac9ebd53c@gmail.com"},"message":"mmc: dw_mmc: exynos: move the exynos private init\n\nCurrently platform specific private data initialization is done by\ndw_mci_exynos_priv_init and dw_mci_exynos_parse_dt. As we already have\nseparate platform specific device tree parser dw_mci_exynos_parse_dt,\nmove the dw_mci_exynos_priv_init code to dw_mci_exynos_parse_dt.\nWe can use the dw_mci_exynos_priv_init to do some actual platform\nspecific initialization of SMU and etc.\n\nSigned-off-by: Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nTested-by: Jaehoon Chung <jh80.chung@samsung.com>\nAcked-by: Seungwon Jeon <tgih.jun@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/e6c784eded7b39caeaf2e9206336fa1daeccfd09"},{"sha":"3aa741f39587d03f38b1c8883d3cf06d242abf16","author":{"name":"Yuvaraj Kumar C D","email":"575c9eb6d334b08a4adc258040710e4ac9ebd53c@gmail.com"},"message":"mmc: dw_mmc: socfpga: move socfpga private init\n\nCurrently platform specific private data initialization is done by\ndw_mci_socfpga_priv_init and dw_mci_socfpga_parse_dt. As we already have\nseparate platform specific device tree parser dw_mci_socfpga_parse_dt,\nmove the dw_mci_socfpga_priv_init code to dw_mci_socfpga_parse_dt.\nWe can use the dw_mci_socfpga_priv_init to do some actual platform\nspecific initialization.\n\nSigned-off-by: Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nTested-by: Jaehoon Chung <jh80.chung@samsung.com>\nAcked-by: Seungwon Jeon <tgih.jun@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/3aa741f39587d03f38b1c8883d3cf06d242abf16"},{"sha":"002f0d5c63e9f37347864c1c9f5656c3cfdb6947","author":{"name":"Yuvaraj Kumar C D","email":"575c9eb6d334b08a4adc258040710e4ac9ebd53c@gmail.com"},"message":"mmc: dw_mmc: move the platform specific init call\n\nCurrent platform specific private data initialization call\ndw_mci_exynos_priv_init() can be used to do platform specific\ninitialization of SMU and others in future. So the drv_data->init\ncall has moved to dw_mci_probe().\n\nSigned-off-by: Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nTested-by: Jaehoon Chung <jh80.chung@samsung.com>\nAcked-by: Seungwon Jeon <tgih.jun@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/002f0d5c63e9f37347864c1c9f5656c3cfdb6947"},{"sha":"6bce431ca13bb72261adbd20b7bc58c447ef2ce3","author":{"name":"Yuvaraj Kumar C D","email":"575c9eb6d334b08a4adc258040710e4ac9ebd53c@gmail.com"},"message":"mmc: dw_mmc: exynos: configure SMU in exynos5420\n\nExynos5420 Mobile Storage Host controller has Security Management\nUnit (SMU) for channel 0 and channel 1 (mainly for eMMC).\nThis time, SMU configuration is set for non-encryption mode.\n\nSigned-off-by: Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>\nSigned-off-by: Alim Akhtar <alim.akhtar@samsung.com>\nTested-by: Jaehoon Chung <jh80.chung@samsung.com>\nAcked-by: Seungwon Jeon <tgih.jun@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/6bce431ca13bb72261adbd20b7bc58c447ef2ce3"},{"sha":"0976f16d2d7fdd3d33738c1f64b83cde6f783db3","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: add support tuning scheme\n\nFor the speed modes HS200 and SDR104, tuning is needed to determine the\ncorrect sampling point. Actual tuning procedure is provided by specific\nhost controller driver.  This patch defines the tuning command and\ntuning data.  Additionally, 'struct dw_mci_slot' is moved to header\nfile to consider the extensive usages in driver.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/0976f16d2d7fdd3d33738c1f64b83cde6f783db3"},{"sha":"c537a1c5ff63d3553617a9ff80ef5ed1493028e2","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: exynos: add variable delay tuning sequence\n\nImplements variable delay tuning. In this change, exynos host can\ndetermine the correct sampling point for the HS200 and SDR104 speed mode.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/c537a1c5ff63d3553617a9ff80ef5ed1493028e2"},{"sha":"c6d9deda64d426a25aafeb179962c9cf3c834e2f","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: exynos: adjust the clock rate with speed mode\n\nExynos's host has divider logic before 'cclk_in' to controller core.\nIt means that actual clock rate of ciu clock comes from this divider\nvalue. So, source clock should be adjusted along with 'ciu_div' which\nindicates the host's divider ratio. Setting clock rate basically fits\nthe required speed. Specially, 'cclk_in' should have double rate of\ntarget speed in case of DDR 8-bit mode.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/c6d9deda64d426a25aafeb179962c9cf3c834e2f"},{"sha":"5dd63f524666d0b1d1b07da7cc993bc8fcd141a9","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: add the capability to support hs200 mode\n\nAs host controller can support eMMC's HS200 mode at 1.8V or 1.2V,\nthese capability will be added.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/5dd63f524666d0b1d1b07da7cc993bc8fcd141a9"},{"sha":"10b498419f41ffaca7510286c0db8ea34300576d","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: move supports-highspeed of quirks to caps\n\n'supports-highspeed' is not one of the quirks but is a capability.\nSo, it's removed from quirks.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/10b498419f41ffaca7510286c0db8ea34300576d"},{"sha":"1f44a2a55787faa08a50266fa5dc99f0dcd36b7c","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: set the supported max/min frequency\n\nBoth f_max and f_min will be informed for core layer to request\nvalid clock rate. But current setting from 'host->bus_hz' may\nnot represent the max/min frequency properly. Even if host can\nactually support high speed than bus_hz, core layer will not\nrequest clock rate over bus_hz. Basically, f_max/f_min can be set\nwith the values according to spec. And then host will make its best\neffort to meet the rate.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/1f44a2a55787faa08a50266fa5dc99f0dcd36b7c"},{"sha":"524268990e54dab9bd71a984b70c13ce0eb1c525","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: adjust the fifoth with block size\n\nThis change helps to choose msize, rx_watermark and tx_watermark\ndepending on block size for IDMAC mode.  For SDIO block size can be\nvariable, so if these values are set incorrectly, card clock may stop.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/524268990e54dab9bd71a984b70c13ce0eb1c525"},{"sha":"f1d2736c815629f3b43d8eebf73a81b581438e65","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: control card read threshold\n\nCard Read Threshold should be ensured that the card clock does not stop\nin the middle of a block of data being transferred from the card to the\nHost. Specially, clock stop is allowed in fast transfer such as HS200\nor SDR104 mode. And so, it should be enabled.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/f1d2736c815629f3b43d8eebf73a81b581438e65"},{"sha":"71abb1339436160b6ab0ae2f816a4046c7328f28","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: fix error handling on response error\n\nEven if response error is detected in case data command, data transfer\nis continued. It means that data can live in FIFO. Current handling\njust breaks out the request when seeing the command error. This causes\nkernel panic in dw_mci_read_data_pio() [host->data = NULL]. And also,\nFIFO should be guaranteed to be empty.\n\nUnable to handle kernel NULL pointer dereference at virtual address 00000018\n<...>\n[<c02af814>] (dw_mci_read_data_pio+0x68/0x198) from [<c02b04b4>] (dw_mci_interrupt+0x374/0x3a0)\n[<c02b04b4>] (dw_mci_interrupt+0x374/0x3a0) from [<c006b094>] (handle_irq_event_percpu+0x50/0x194)\n[<c006b094>] (handle_irq_event_percpu+0x50/0x194) from [<c006b214>] (handle_irq_event+0x3c/0x5c)\n[<c006b214>] (handle_irq_event+0x3c/0x5c) from [<c006de1c>] (handle_fasteoi_irq+0xa4/0x148)\n[<c006de1c>] (handle_fasteoi_irq+0xa4/0x148) from [<c006aa88>] (generic_handle_irq+0x20/0x30)\n[<c006aa88>] (generic_handle_irq+0x20/0x30) from [<c000f154>] (handle_IRQ+0x38/0x90)\n[<c000f154>] (handle_IRQ+0x38/0x90) from [<c00085bc>] (gic_handle_irq+0x34/0x68)\n[<c00085bc>] (gic_handle_irq+0x34/0x68) from [<c0011f40>] (__irq_svc+0x40/0x70)\nException stack(0xef0b1c00 to 0xef0b1c48)\n1c00: 000eb0cf ffffffff 00001300 c01a7738 ef295e10 0000000a c04df298 ef0b1dc0\n1c20: ef295ec0 00000000 00000000 00000006 00000000 ef0b1c48 c02b1274 c01a7764\n1c40: 20000113 ffffffff\n[<c0011f40>] (__irq_svc+0x40/0x70) from \t[<c01a7764>] (__loop_delay+0x0/0xc)\nCode: e1a00005 e0891006 e0662004 e12fff33 (e59a3018)\n---[ end trace a7043b9ba9aed1db ]---\nKernel panic - not syncing: Fatal exception in interrupt\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/71abb1339436160b6ab0ae2f816a4046c7328f28"},{"sha":"90c2143a8f6d0cd1dbae1ea32fcd1befb81e4b0d","author":{"name":"Seungwon Jeon","email":"5fcbac928323f8e6f6abe17dd36cd52c7b824ea3@samsung.com"},"message":"mmc: dw_mmc: guarantee stop-abort cmd in data errors\n\nIn error cases, DTO interrupt may or may not be generated depending\non remained data. Stop/Abort command ensures DTO generation for that\nsituation. Currently if 'stop' field of data is empty, there is no\nstop/abort command. So, it could hang waiting DTO. This change\nreinforces these cases.\n\nSigned-off-by: Seungwon Jeon <tgih.jun@samsung.com>\nTested-by: Alim Akhtar <alim.akhtar@samsung.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":false,"url":"https://api.github.com/repos/free-z4u/android_kernel_htc_msm7x30/commits/90c2143a8f6d0cd1dbae1ea32fcd1befb81e4b0d"}]}
{"actor":{"display_login":"0lvin"}}