From: Greg KH <gregkh@linuxfoundation.org>
To: linux@roeck-us.net, anssi.hannula@bitwise.fi,
briannorris@chromium.org, dianders@chromium.org, heiko@sntech.de,
shawn.lin@rock-chip.com, ulf.hansson@linaro.org
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "mmc: core: Fix access to HS400-ES devices" has been added to the 4.4-stable tree
Date: Mon, 7 Aug 2017 13:58:11 -0700 [thread overview]
Message-ID: <20170807205811.GA23372@kroah.com> (raw)
In-Reply-To: <15021383237673@kroah.com>
On Mon, Aug 07, 2017 at 01:38:43PM -0700, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> mmc: core: Fix access to HS400-ES devices
>
> to the 4.4-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> mmc-core-fix-access-to-hs400-es-devices.patch
> and it can be found in the queue-4.4 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
> >From 773dc118756b1f38766063e90e582016be868f09 Mon Sep 17 00:00:00 2001
> From: Guenter Roeck <linux@roeck-us.net>
> Date: Wed, 1 Mar 2017 14:11:47 -0800
> Subject: mmc: core: Fix access to HS400-ES devices
>
> From: Guenter Roeck <linux@roeck-us.net>
>
> commit 773dc118756b1f38766063e90e582016be868f09 upstream.
>
> HS400-ES devices fail to initialize with the following error messages.
>
> mmc1: power class selection to bus width 8 ddr 0 failed
> mmc1: error -110 whilst initialising MMC card
>
> This was seen on Samsung Chromebook Plus. Code analysis points to
> commit 3d4ef329757c ("mmc: core: fix multi-bit bus width without
> high-speed mode"), which attempts to set the bus width for all but
> HS200 devices unconditionally. However, for HS400-ES, the bus width
> is already selected.
>
> Cc: Anssi Hannula <anssi.hannula@bitwise.fi>
> Cc: Douglas Anderson <dianders@chromium.org>
> Cc: Brian Norris <briannorris@chromium.org>
> Fixes: 3d4ef329757c ("mmc: core: fix multi-bit bus width ...")
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
> Reviewed-by: Shawn Lin <shawn.lin@rock-chip.com>
> Tested-by: Heiko Stuebner <heiko@sntech.de>
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> ---
> drivers/mmc/core/mmc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- a/drivers/mmc/core/mmc.c
> +++ b/drivers/mmc/core/mmc.c
> @@ -1581,7 +1581,7 @@ static int mmc_init_card(struct mmc_host
> err = mmc_select_hs400(card);
> if (err)
> goto free_card;
> - } else {
> + } else if (!mmc_card_hs400es(card)) {
Nope, this breaks the build on 4.4. Anyone want to provide a working
backport?
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-07 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 20:38 Patch "mmc: core: Fix access to HS400-ES devices" has been added to the 4.4-stable tree gregkh
2017-08-07 20:58 ` Greg KH [this message]
2017-08-07 21:11 ` Doug Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170807205811.GA23372@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anssi.hannula@bitwise.fi \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux@roeck-us.net \
--cc=shawn.lin@rock-chip.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.