From: Arnd Bergmann <arnd@arndb.de>
To: Michal Kadlic <michal.kadlic@spinet.sk>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: moxart-mmc: Fix APP_CMD flag set on non-application commands
Date: Tue, 07 Jun 2016 10:59:01 +0200 [thread overview]
Message-ID: <3845045.bnmKhmzSey@wuerfel> (raw)
In-Reply-To: <734d328a-56ec-34bb-30ab-0a502041af2d@spinet.sk>
On Tuesday, June 7, 2016 10:53:01 AM CEST Michal Kadlic wrote:
> Moxart MMC host controller has an APP_CMD flag, that's set when sending
> an ACMD. This was set by checking command opcode instead of CMD55->ACMDx
> sequence, which could lead to regular commands like CMD6,CMD13,CMD23 and
> CMD42 flagged as application commands.
>
> Patch is against kernel version 4.6
>
> Signed-off-by: Michal Kadlic <michal.kadlic@spinet.sk>
Is this needed for backports to stable kernels as well?
> static inline void moxart_init_sg(struct moxart_host *host,
> @@ -211,10 +213,11 @@ static void moxart_send_command(struct m
> writel(cmd->arg, host->base + REG_ARGUMENT);
>
> cmdctrl = cmd->opcode & CMD_IDX_MASK;
> - if (cmdctrl == SD_APP_SET_BUS_WIDTH || cmdctrl ==
> SD_APP_OP_COND ||
> - cmdctrl == SD_APP_SEND_SCR || cmdctrl ==
> SD_APP_SD_STATUS ||
> - cmdctrl == SD_APP_SEND_NUM_WR_BLKS)
> +
You seem to have an incorrect word wrapping setting in your email
client, so the patch won't apply. I'd recommend using 'git send-email',
which tends to be easier than figuring out the right settings for your
mailer.
> + // If previous command was CMD55 set APP_CMD flag, except for
> CMD0(Reset)
Please use /* ... */ comments.
Arnd
prev parent reply other threads:[~2016-06-07 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 8:53 [PATCH] mmc: moxart-mmc: Fix APP_CMD flag set on non-application commands Michal Kadlic
2016-06-07 8:59 ` Arnd Bergmann [this message]
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=3845045.bnmKhmzSey@wuerfel \
--to=arnd@arndb.de \
--cc=linux-mmc@vger.kernel.org \
--cc=michal.kadlic@spinet.sk \
/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