From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: shmobile: r8a7790 - fix shdi resource sies
Date: Fri, 13 Dec 2013 08:23:21 +0000 [thread overview]
Message-ID: <52AAC3F9.3050909@codethink.co.uk> (raw)
In-Reply-To: <871u1hsd44.wl%kuninori.morimoto.gx@gmail.com>
On 13/12/13 02:37, Kuninori Morimoto wrote:
>
> Hi Ben
>
> Thank you for your patch
>
>> The r8a7790.dtsi file has three sdhi nodes which all have the wrong resource
>> size for their register block. This causes the sh_modbile_sdhi driver to
>> fail to communicate with card at-all.
>>
>> Change each sdhi node size from 0x100 to 0x200 to correct this.
>>
>> Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>> Cc: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
>> Cc: Magnus Damm <magnus.damm@gmail.com>
>> Cc: Simon Horman <horms@verge.net.au>
>> Cc: Linux SH <linux-sh@vger.kernel.org>
>> Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>
>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>> Tested-by: William Towle <william.towle@codethink.co.uk>
>> ---
>
> Unfortunately, sdhi resource size 0x100 is corrent on Renesas SDHI.
> The wrong is SDHI/TMIO driver side, not SoC side.
> Now, I'm working/sending sh_modbile_sdhi driver fixup patches for R-Car H2,
> but it need more time (= there is merge timing issue)
Ok, thanks. We will keep this in our tree until the SDHI driver
is sorted out.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2013-12-13 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 17:24 [PATCH] ARM: shmobile: r8a7790 - fix shdi resource sies Ben Dooks
2013-12-13 2:37 ` Kuninori Morimoto
2013-12-13 8:23 ` Ben Dooks [this message]
2013-12-13 10:56 ` Magnus Damm
2013-12-13 11:04 ` Ben Dooks
2013-12-14 0:27 ` Simon Horman
2013-12-16 4:18 ` Kuninori Morimoto
2013-12-16 10:59 ` 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=52AAC3F9.3050909@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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).