From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: EMMA/EMEV2 SDHCI driver
Date: Tue, 16 Jul 2013 16:09:11 +0000 [thread overview]
Message-ID: <51E57027.9030502@codethink.co.uk> (raw)
In-Reply-To: <51E5616A.70106@codethink.co.uk>
On 16/07/13 16:06, Ben Dooks wrote:
> I am currently trying to get a driver going for the SDIO0/1/2 blocks
> in the EMEV2 device. Using the SDHCI platform driver I've added a
> sub-driver to get the bus and sclks and then instantiate the sdhci
> core.
>
> I have checked that the device is out of reset, and that all clocks
> in to the block are enabled. I have a quick verification that all
> SDHCI writes are making it to the registers.
>
> Has anyone tried this with any success? Is there something I have
> missed doing this?
I'm pretty sure we are somehow losing the interrupt from the SDIO0
block to the gic, but can't see how as the interrupt seems to be
appropriately unmasked.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2013-07-16 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 15:06 EMMA/EMEV2 SDHCI driver Ben Dooks
2013-07-16 16:09 ` Ben Dooks [this message]
2013-07-16 16:33 ` Ben Dooks
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=51E57027.9030502@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).