From: Kevin Hilman <khilman@baylibre.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Carlo Caione <carlo@caione.org>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 2/9] mmc: meson-gx: minor improvements in meson_mmc_set_ios
Date: Fri, 03 Feb 2017 07:52:49 -0600 [thread overview]
Message-ID: <m2k297l6tq.fsf@baylibre.com> (raw)
In-Reply-To: <939d5c2d-e518-9388-0800-1be1948f8c65@gmail.com> (Heiner Kallweit's message of "Wed, 1 Feb 2017 21:16:53 +0100")
Heiner Kallweit <hkallweit1@gmail.com> writes:
> Am 01.02.2017 um 12:55 schrieb Jaehoon Chung:
>> On 02/01/2017 05:57 AM, Heiner Kallweit wrote:
>>> val isn't used in the switch clause and afterwards there's an
>>> identical statement. So remove it.
>>>
>>> In case of an unexpected bus width the error message indicates
>>> the intention to set the bus width to 4 and to go on.
>>> So remove the return statement. This return statement also
>>> conflicts with "setting to 4" because nothing would be set
>>> actually before returning.
>>>
>>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>>> ---
>>> drivers/mmc/host/meson-gx-mmc.c | 2 --
>>> 1 file changed, 2 deletions(-)
>>>
>>> diff --git a/drivers/mmc/host/meson-gx-mmc.c b/drivers/mmc/host/meson-gx-mmc.c
>>> index da3cce31..38edc60d 100644
>>> --- a/drivers/mmc/host/meson-gx-mmc.c
>>> +++ b/drivers/mmc/host/meson-gx-mmc.c
>>> @@ -379,7 +379,6 @@ static void meson_mmc_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
>>> meson_mmc_clk_set(host, ios->clock);
>>>
>>> /* Bus width */
>>> - val = readl(host->regs + SD_EMMC_CFG);
>>> switch (ios->bus_width) {
>>> case MMC_BUS_WIDTH_1:
>>> bus_width = CFG_BUS_WIDTH_1;
>>> @@ -394,7 +393,6 @@ static void meson_mmc_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
>>> dev_err(host->dev, "Invalid ios->bus_width: %u. Setting to 4.\n",
>>> ios->bus_width);
>>> bus_width = CFG_BUS_WIDTH_4;
>>> - return;
>>
>> It's a different question..why does meson-gx-mmc use 4bit buswidth for invalid bus-with? not using 1bit-buswidth?
>>
> I think this question is best addressed to Kevin as original author.
>
Because that was the fall-back in the vendor driver that this was based
on.
I'm not really an MMC expert, so I don't know if that's the right thing
to do.
Kevin
next prev parent reply other threads:[~2017-02-03 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <24e8bf35-50ce-270d-c0aa-12bb90d2e3d8@gmail.com>
2017-01-31 20:57 ` [PATCH 2/9] mmc: meson-gx: minor improvements in meson_mmc_set_ios Heiner Kallweit
2017-02-01 11:55 ` Jaehoon Chung
2017-02-01 20:16 ` Heiner Kallweit
2017-02-03 13:52 ` Kevin Hilman [this message]
2017-01-31 20:58 ` [PATCH 3/9] mmc: meson-gx: improve meson_mmc_clk_set Heiner Kallweit
2017-02-01 12:24 ` Jaehoon Chung
2017-02-01 20:29 ` Heiner Kallweit
2017-02-02 9:09 ` Ulf Hansson
2017-01-31 20:58 ` [PATCH 4/9] mmc: meson-gx: improve meson_mmc_irq_thread Heiner Kallweit
2017-01-31 20:58 ` [PATCH 5/9] mmc: meson-gx: improve interrupt handling Heiner Kallweit
2017-01-31 20:58 ` [PATCH 6/9] mmc: meson-gx: set max block count and request size Heiner Kallweit
2017-01-31 20:58 ` [PATCH 7/9] mmc: meson-gx: reduce bounce buffer size Heiner Kallweit
2017-01-31 20:58 ` [PATCH 8/9] mmc: meson-gx: remove unneeded checks in remove Heiner Kallweit
2017-01-31 20:59 ` [PATCH 9/9] mmc: meson-gx: add support for HS400 mode Heiner Kallweit
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=m2k297l6tq.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=carlo@caione.org \
--cc=hkallweit1@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=linux-mmc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox