From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 3/3] ARM: shmobile: streamline mackerel SD and MMC devices
Date: Wed, 13 Feb 2013 11:15:05 +0000 [thread overview]
Message-ID: <20130213111505.GF22623@verge.net.au> (raw)
In-Reply-To: <1360689333-13525-4-git-send-email-g.liakhovetski@gmx.de>
On Wed, Feb 13, 2013 at 04:56:44PM +0900, Simon Horman wrote:
> On Tue, Feb 12, 2013 at 06:15:33PM +0100, Guennadi Liakhovetski wrote:
> > This patch fixes the following issues with SD and MMC interfaces on mackerel:
> > 1. replace custom card-detection functions with standard GPIO CD API
> > 2. resources don't have to be numbered
> > 3. add SDHI interrupt names
> > 4. remove OCR masks, where regulators are used
> > 5. only specify SDHI CD interrupts on interfaces where a CD pin is present -
> > SDHI0
> > 6. don't instantiate an MMCIF device and initialise MMCIF pins if SDHI1 is
> > selected
>
> With this patch applied on top of next I see the following:
>
> mmc2: host doesn't support card's voltages
> mmc2: error -22 whilst initialising MMC card
> mmc2: host doesn't support card's voltages
> mmc2: error -22 whilst initialising MMC card
> mmc2: host doesn't support card's voltages
> mmc2: error -22 whilst initialising MMC card
> mmc2: host doesn't support card's voltages
> mmc2: error -22 whilst initialising MMC card
> mmc2: host doesn't support card's voltages
> mmc2: error -22 whilst initialising MMC card
> mmc2: host doesn't support card's voltages
>
> Am I missing some dependencies?
>
> (I know you send me a bunch of patches off-list,
> but I'd appreciate not having to hunt through them individually
> to answer this question)
Please ignore that, I think I have things working now.
next prev parent reply other threads:[~2013-02-13 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 17:15 [PATCH 3/3] ARM: shmobile: streamline mackerel SD and MMC devices Guennadi Liakhovetski
2013-02-13 7:56 ` Simon Horman
2013-02-13 11:15 ` Simon Horman [this message]
2013-02-13 11:34 ` Simon Horman
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=20130213111505.GF22623@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@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