Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=v3.15.2 2014-02-23T15:40:08+00:00 2014-02-23T15:40:08+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-12-18T08:57:38+00:00 urn:sha1:68eb80e06bfa06035d0304686124974780308fae Rename host->max_discard_to to host->max_busy_timeout, to reflect that it tells the mmc core layer about the maximum supported busy detection timeout by the host. This timeout is at the moment only applicable to erase/trim/discard commands. By the renaming we provide the option of make use of it for other commands that cares about busy detection. In other words, those commands that wants an R1B response, like for example the mmc switch command. Do note that the max_busy_timeout is supposed to be specified only by hosts supporting MMC_CAP_WAIT_WHILE_BUSY. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <chris@printf.net> 2014-02-14T03:58:49+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-12-18T10:59:17+00:00 urn:sha1:7536d3f83aa42ba1a3b1c6b30c2b6d94a820cbb2 There are no reason to why the use of a non-volatile internal eMMC cache should be controlled by a host cap. Instead let's just enable it if the eMMC card supports it. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Acked-by: Seungwon Jeon <tgih.jun@samsung.com> Signed-off-by: Chris Ball <chris@printf.net> 2014-02-14T03:58:41+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-12-16T15:23:22+00:00 urn:sha1:10e5d9652499a8bc0a99ffc2a96a3030fee576cb Earlier we disabled the cache during suspend, which meant a flush was internally at the eMMC performed as well. To simplify code we can make use of the mmc_flush_cache(), during mmc suspend, which makes the mmc_cache_ctrl() redundant so then we can remove it. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Acked-by: Seungwon Jeon <tgih.jun@samsung.com> Signed-off-by: Chris Ball <chris@printf.net> 2014-02-14T03:58:37+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-12-16T13:46:00+00:00 urn:sha1:469a00b017a9b2c630bff962ffd64ba626977830 There are no active users of this host capability. The primary reason for adding this cap was due to a bug in ux500 boot loader code, which is not a relevant issue any more. So, let's remove it. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <chris@printf.net> 2014-02-14T03:58:32+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-12-16T13:43:51+00:00 urn:sha1:325e2f96b926ae852fa2aa5e64d1040ed9518ae1 Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <chris@printf.net> 2014-02-14T03:58:27+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-12-16T13:37:26+00:00 urn:sha1:a2d1086de6cc3ae2378d9db8b92712911c9e5fef There is no need for keeping a host cap for MMC_CAP2_SANITIZE, instead we just make the feature default available. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <chris@printf.net> 2014-02-14T03:58:15+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-10-30T00:00:18+00:00 urn:sha1:2501c9179dff2add6aadd3898cd729e94e777d3a Invoking system suspend or shutdown without using the Kconfig option MMC_UNSAFE_RESUME, did trigger an ungraceful power cut of the card. To improve the situation, change the behavior to always make use of the available bus_ops callbacks that handles system suspend and shutdown properly. By changing the behavior MMC_UNSAFE_RESUME becomes redundant, so lets's remove it. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <chris@printf.net> 2013-10-31T00:28:43+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-10-10T15:22:23+00:00 urn:sha1:4d22378221bd0ed69c2e99408d31c108d72aeb80 In some environments it is to prefer to postpone the resume of the card device until runtime_resume is being carried out, since it will mean a signficant decrease of the total system resume time. The reason of the decreased resume time is simply because of the actual re-initalization of the card, which typically takes hundreds of milliseconds, is performed outside the resume sequence and wont thus affect it. For removable card, the detect work tries to re-detect the card to make sure it is still present, as a part of that sequence the card will also be runtime_resumed and thus also fully resumed. For a non-removable card, typically a mmc blk request will trigger a runtime_resume and thus fully resume the card. This also means the first request will likely suffer from an inital latency since the re-initialization of the card needs to be performed. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <cjb@laptop.org> 2013-10-31T00:28:38+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-09-26T09:01:18+00:00 urn:sha1:3c0d22e8180b98eea412b84aa0f0c42c16159679 The are no more users of the deprecated mmc_suspend|resume_host API, so let's remove it. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <cjb@laptop.org> 2013-10-31T00:26:29+00:00 Ulf Hansson ulf.hansson@linaro.org 2013-09-13T09:31:33+00:00 urn:sha1:6904115095ad60ced638eb1e36e0e4e5e7de00b0 The negotiated ocr mask is directly related to the card. Once a card gets removed, the mask shall be dropped. By moving the cache of the ocr mask from the host struct to the card struct we have accomplished this. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <cjb@laptop.org>