From: Bean Huo <firstname.lastname@example.org>
To: Ulf Hansson <email@example.com>
Cc: firstname.lastname@example.org, Linus Walleij <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>,
"Bean Huo (beanhuo)" <email@example.com>,
"# 4.0+" <firstname.lastname@example.org>
Subject: Re: [PATCH v1 2/2] mmc: cavium: Remove redundant if-statement checkup
Date: Fri, 19 Mar 2021 16:42:37 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On Fri, 2021-03-19 at 15:09 +0100, Ulf Hansson wrote:
> On Fri, 19 Mar 2021 at 13:14, Bean Huo <firstname.lastname@example.org> wrote:
> > From: Bean Huo <email@example.com>
> > Currently, we have two ways to issue multiple-block read/write the
> > command to the eMMC. One is by normal IO request path fs->block-
> > >mmc.
> > Another one is that we can issue multiple-block read/write through
> > MMC ioctl interface. For the first path, mrq->stop, and mrq->stop-
> > >opcode
> > will be initialized in mmc_blk_data_prep(). However, for the second
> > IO
> > path, mrq->stop is not initialized since it is a pre-defined
> > multiple
> > blocks read/write.
> As a matter of fact this way is also supported for the regular block
> I/O path. To make the mmc block driver to use it, mmc host drivers
> need to announce that it's supported by setting MMC_CAP_CMD23.
> It looks like that is what your patch should be targeted towards, can
> you have a look at this instead?
Thanks for your comments. I will look at that as your suggestion.
The patch [1/2] is accepted, so I will just update this patch to
the next version.
> Kind regards
next prev parent reply other threads:[~2021-03-19 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 12:13 [PATCH v1 0/2] wo minor changes for Cavium MMC host driver Bean Huo
2021-03-19 12:13 ` [PATCH v1 1/2] mmc: cavium: Use '"%s...", __func__' to print function name Bean Huo
2021-03-19 14:12 ` Ulf Hansson
2021-03-19 12:13 ` [PATCH v1 2/2] mmc: cavium: Remove redundant if-statement checkup Bean Huo
2021-03-19 14:09 ` Ulf Hansson
2021-03-19 15:42 ` Bean Huo [this message]
2021-04-29 20:30 ` Bean Huo
2021-05-10 14:01 ` Ulf Hansson
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).