From: Arnd Bergmann <arnd@arndb.de>
To: Yangbo Lu <yangbo.lu@freescale.com>
Cc: linux-mmc@vger.kernel.org, chris@printf.net, ulf.hansson@linaro.org
Subject: Re: [v3, 2/6] mmc: sdhci-pltfm: support both LE and BE mode for SDHCI platform
Date: Fri, 08 May 2015 09:40:42 +0200 [thread overview]
Message-ID: <2093374.CPZJl41Uyy@wuerfel> (raw)
In-Reply-To: <1431067818-41378-1-git-send-email-yangbo.lu@freescale.com>
On Friday 08 May 2015 14:50:18 Yangbo Lu wrote:
> -static inline u32 sdhci_be32bs_readl(struct sdhci_host *host, int reg)
> +static inline void sdhci_clrsetbits(struct sdhci_host *host, u32 mask,
> + u32 val, int reg)
> {
> - return in_be32(host->ioaddr + reg);
> + void __iomem *base = host->ioaddr + (reg & ~0x3);
> + u32 shift = (reg & 0x3) * 8;
> +
> + if (host->mmc->big_endian_mode)
> + iowrite32be(((ioread32be(base) & ~(mask << shift)) |
> + (val << shift)), base);
> + else
> + iowrite32(((ioread32(base) & ~(mask << shift)) |
> + (val << shift)), base);
> }
>
>
I think it would be better to use function pointers that are assigned at probe
time than run-time checks here.
Have a look at drivers/mmc/host/sdhci-of-hlwd.c:
static const struct sdhci_ops sdhci_hlwd_ops = {
.read_l = sdhci_be32bs_readl,
.read_w = sdhci_be32bs_readw,
.read_b = sdhci_be32bs_readb,
.write_l = sdhci_hlwd_writel,
.write_w = sdhci_hlwd_writew,
.write_b = sdhci_hlwd_writeb,
.set_clock = sdhci_set_clock,
.set_bus_width = sdhci_set_bus_width,
.reset = sdhci_reset,
.set_uhs_signaling = sdhci_set_uhs_signaling,
};
You can copy this method into your own driver.
Arnd
next prev parent reply other threads:[~2015-05-08 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 6:50 [v3, 2/6] mmc: sdhci-pltfm: support both LE and BE mode for SDHCI platform Yangbo Lu
2015-05-08 7:40 ` Arnd Bergmann [this message]
2015-05-11 6:46 ` yangbo.lu
2015-05-11 10:15 ` Ulf Hansson
[not found] ` <BY1PR0301MB1192FEF44307B98995292CCDF2DA0@BY1PR0301MB1192.namprd03.prod.outlook.com>
2015-05-13 11:19 ` 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=2093374.CPZJl41Uyy@wuerfel \
--to=arnd@arndb.de \
--cc=chris@printf.net \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yangbo.lu@freescale.com \
/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