From: Jan Glauber <jglauber@cavium.com>
To: linux-mmc@vger.kernel.org
Subject: mmc_card_blockaddr() now private
Date: Mon, 30 Jan 2017 14:52:19 +0100 [thread overview]
Message-ID: <20170130135219.GA10099@wintermute> (raw)
Hi,
preparing mmc patches against linux-next I noticed that
mmc_card_blockaddr is now private to the mmc core.
We've been using that in the (not yet upstream) Cavium mmc driver like this:
static void prepare_ext_dma(struct mmc_host *mmc, ...
...
emm_dma->s.sector = mmc_card_blockaddr(mmc->card) ? 1 : 0;
So the hardware controller needs to know if we use 512 byte blocks
or not which seems to be dependent on the medium size.
Any ideas on how I can implement this without mmc_card_blockaddr() ?
thanks,
Jan
next reply other threads:[~2017-01-30 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 13:52 Jan Glauber [this message]
2017-02-02 13:12 ` mmc_card_blockaddr() now private Ulf Hansson
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=20170130135219.GA10099@wintermute \
--to=jglauber@cavium.com \
--cc=linux-mmc@vger.kernel.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