From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
lkml <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/3] mmc: fix mmc mode selection for HS-DDR and higher
Date: Wed, 1 Jun 2016 11:58:34 -0700 [thread overview]
Message-ID: <CAOCOHw7aHvSUUoxkrDkGwNrTGNbZm-3RSuhJF3CCvRUiK5tDgg@mail.gmail.com> (raw)
In-Reply-To: <1464505484-3661-2-git-send-email-wens@csie.org>
On Sun, May 29, 2016 at 12:04 AM, Chen-Yu Tsai <wens@csie.org> wrote:
> When IS_ERR_VALUE was removed from the mmc core code, it was replaced
> with a simple not-zero check. This does not work, as the value checked
> is the return value for mmc_select_bus_width, which returns the set
> bit width on success. This made eMMC modes higher than HS-DDR unusable.
>
> Fix this by checking for a positive return value instead.
mmc_select_bus_width() can return 0 on "success" as well and the
previous check was !IS_ERR_VALUE(err), which coverts that. So I
believe these checks should be for err >= 0 rather than just > 0.
Either way this fixes the boot failures seen on my Qualcomm based
boards with v4.7-rc1.
Regards,
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] mmc: fix mmc mode selection for HS-DDR and higher
Date: Wed, 1 Jun 2016 11:58:34 -0700 [thread overview]
Message-ID: <CAOCOHw7aHvSUUoxkrDkGwNrTGNbZm-3RSuhJF3CCvRUiK5tDgg@mail.gmail.com> (raw)
In-Reply-To: <1464505484-3661-2-git-send-email-wens@csie.org>
On Sun, May 29, 2016 at 12:04 AM, Chen-Yu Tsai <wens@csie.org> wrote:
> When IS_ERR_VALUE was removed from the mmc core code, it was replaced
> with a simple not-zero check. This does not work, as the value checked
> is the return value for mmc_select_bus_width, which returns the set
> bit width on success. This made eMMC modes higher than HS-DDR unusable.
>
> Fix this by checking for a positive return value instead.
mmc_select_bus_width() can return 0 on "success" as well and the
previous check was !IS_ERR_VALUE(err), which coverts that. So I
believe these checks should be for err >= 0 rather than just > 0.
Either way this fixes the boot failures seen on my Qualcomm based
boards with v4.7-rc1.
Regards,
Bjorn
next prev parent reply other threads:[~2016-06-01 19:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 7:04 [PATCH 0/3] mmc: sunxi: Fix MMC DDR modes for Allwinner A80 Chen-Yu Tsai
2016-05-29 7:04 ` Chen-Yu Tsai
2016-05-29 7:04 ` [PATCH 1/3] mmc: fix mmc mode selection for HS-DDR and higher Chen-Yu Tsai
2016-05-29 7:04 ` Chen-Yu Tsai
2016-05-31 9:30 ` Krzysztof Kozlowski
2016-05-31 9:30 ` Krzysztof Kozlowski
2016-06-01 1:25 ` Jaehoon Chung
2016-06-01 1:25 ` Jaehoon Chung
2016-06-01 2:36 ` Shawn Lin
2016-06-01 2:36 ` Shawn Lin
2016-06-01 9:19 ` Marcel Ziswiler
2016-06-01 9:19 ` Marcel Ziswiler
2016-06-01 18:58 ` Bjorn Andersson [this message]
2016-06-01 18:58 ` Bjorn Andersson
2016-06-02 8:08 ` Chen-Yu Tsai
2016-06-02 8:08 ` Chen-Yu Tsai
2016-06-02 8:31 ` Ulf Hansson
2016-06-02 8:31 ` Ulf Hansson
2016-06-02 8:31 ` Ulf Hansson
2016-06-02 9:35 ` Krzysztof Kozlowski
2016-06-02 9:35 ` Krzysztof Kozlowski
2016-06-02 9:35 ` Krzysztof Kozlowski
2016-06-02 15:01 ` Ulf Hansson
2016-06-02 15:01 ` Ulf Hansson
2016-06-02 15:01 ` Ulf Hansson
2016-05-29 7:04 ` [PATCH 2/3] mmc: sunxi: Fix DDR MMC timings for A80 Chen-Yu Tsai
2016-05-29 7:04 ` Chen-Yu Tsai
2016-05-30 11:34 ` Hans de Goede
2016-05-30 11:34 ` Hans de Goede
2016-05-30 12:59 ` Chen-Yu Tsai
2016-05-30 12:59 ` Chen-Yu Tsai
2016-05-30 15:38 ` Chen-Yu Tsai
2016-05-30 15:38 ` Chen-Yu Tsai
2016-05-30 18:05 ` Hans de Goede
2016-05-30 18:05 ` Hans de Goede
2016-05-29 7:04 ` [PATCH 3/3] mmc: sunxi: Re-enable eMMC HS-DDR modes on Allwinner A80 Chen-Yu Tsai
2016-05-29 7:04 ` Chen-Yu Tsai
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=CAOCOHw7aHvSUUoxkrDkGwNrTGNbZm-3RSuhJF3CCvRUiK5tDgg@mail.gmail.com \
--to=bjorn.andersson@linaro.org \
--cc=arnd@arndb.de \
--cc=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=ulf.hansson@linaro.org \
--cc=wens@csie.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.