linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: david.lanzendoerfer@o2s.ch (David Lanzendörfer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: sunxi: Add driver for SD/MMC hosts found on Allwinner sunxi SoCs
Date: Wed, 05 Feb 2014 14:33:56 +0100	[thread overview]
Message-ID: <1929408.6EF83UbB9S@dizzy-6.o2s.ch> (raw)
In-Reply-To: <20131215134415.GE3651@lukather>

Hi
> I'm not that fond of these "default y" patterns. It forces the driver
> down to every user of the multiplatform kernels. I'd suggest removing
> the default and adding the driver to the defconfigs we have.
Ok. Removed it.

> > +static void sunxi_mmc_init_host(struct mmc_host *mmc)
> > +{
> > [...]
> > +	mci_writel(smc_host, REG_FUNS, 0xceaa0000);
> > +	mci_writel(smc_host, REG_DLBA, smc_host->sg_dma);
> I suppose we have no idea what these magics are all about ? :(
That's the parameters I could extract from the Chinese code.
Without proper documentation it will always stay magic what exactly these
values are meaning.

> > +#define mci_readl(host, reg) \
> > +	__raw_readl((host)->reg_base + SDXC_##reg)
> > +#define mci_writel(host, reg, value) \
> > +	__raw_writel((value), (host)->reg_base + SDXC_##reg)
> No barriers ? :(
Fixed that...

cheers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140205/13e73392/attachment-0001.sig>

  parent reply	other threads:[~2014-02-05 13:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14 21:58 [PATCH 0/5] ARM: sunxi: Add driver for SD/MMC hosts found on allwinner sunxi SOCs Hans de Goede
2013-12-14 21:58 ` [PATCH 1/5] ARM: sunxi: Add driver for SD/MMC hosts found on Allwinner sunxi SoCs Hans de Goede
2013-12-15 13:44   ` Maxime Ripard
2013-12-15 14:20     ` Hans de Goede
2013-12-15 16:21       ` Maxime Ripard
2013-12-15 18:41         ` [linux-sunxi] " Hans de Goede
2013-12-15 19:35           ` David Lanzendörfer
2013-12-15 20:18             ` Hans de Goede
2013-12-15 21:19               ` David Lanzendörfer
2013-12-16 12:21                 ` Hans de Goede
2013-12-23 10:36                   ` David Lanzendörfer
2013-12-15 16:33       ` David Lanzendörfer
2013-12-15 22:01     ` [linux-sunxi] " Michal Suchanek
2013-12-16 10:05       ` Maxime Ripard
2013-12-16 11:59         ` Michal Suchanek
2013-12-16 12:49           ` Ian Campbell
2013-12-16 12:53           ` Maxime Ripard
2014-02-05 13:33     ` David Lanzendörfer [this message]
2013-12-17 13:43   ` Mark Brown
2013-12-14 21:58 ` [PATCH 2/5] ARM: dts: sun4i: Add support for mmc Hans de Goede
2013-12-15 13:58   ` Maxime Ripard
2013-12-15 14:31     ` [linux-sunxi] " Hans de Goede
2013-12-15 21:44       ` Henrik Nordström
2013-12-16  9:04       ` David Lanzendörfer
2013-12-16 12:32         ` Hans de Goede
2013-12-16 10:02       ` Maxime Ripard
2013-12-16 12:34         ` Hans de Goede
2013-12-14 21:58 ` [PATCH 3/5] ARM: dts: sun5i: Add new sun5i-a13-olinuxino-micro board Hans de Goede
2013-12-15 14:04   ` Maxime Ripard
2013-12-14 21:58 ` [PATCH 4/5] ARM: dts: sun5i: add mmc support Hans de Goede
2013-12-14 21:58 ` [PATCH 5/5] ARM: dts: sun7i: Add support for mmc Hans de Goede

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=1929408.6EF83UbB9S@dizzy-6.o2s.ch \
    --to=david.lanzendoerfer@o2s.ch \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).