From: Dirk Behme <dirk.behme@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 0/6] mmc: sdhi: add basic r8a7795 support
Date: Tue, 19 Jan 2016 16:56:45 +0000 [thread overview]
Message-ID: <569E6ACD.2060303@gmail.com> (raw)
In-Reply-To: <1453220461-2598-1-git-send-email-wsa@the-dreams.de>
Hi Wolfgang,
On 19.01.2016 17:20, Wolfram Sang wrote:
> So, I started working on the SDHI part. Since Dirk seems to be working on the
> clocks already (thanks!), I evaluated the patches for the mmc-subsystem and
> refactored the subset which gets the basic functionality run. A few cleanups
> were applied, too. The patches are RFC because I want to check one more issue
> (restore clock settings after software reset) and also I need to do Gen2
> regression testing. However, release early, I wanted to show you what I am
> hacking on here. A branch for testing (with Dirk's clock patches and DTS
> additions can be found here):
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/v8-sdhi-nodma
>
> Further testing much appreciated. It works fine on my Salvator using SD cards
> on both, SDHI0 and SDHI3. Simple testing, though, no stress testing yet.
Many thanks for working on this! I'll have a look to it, maybe next week.
Just fyi, some general remarks, what's my recent status:
First, regarding the clocks, if anybody from the experts could advise
me how we'd like to interface dynamic clocks to the existing Gen3
clock code, that would be really welcome:
http://marc.info/?l=linux-sh&m\x145302405811953
Second, I'm mainly interested in eMMC support for the Salvator-X.
Therefore I picked (hopefully) all patches from the Renesas BSP to
renesas-drivers-2016-01-13-v4.4
https://github.com/dirkbehme/linux-renesas-rcar-gen3/commits/dirk/gen3-latest-update
I compared the Renesas BSP code in drivers/mmc with that version, it's
the same. However, this branch crashes more or less immediately after
successfully detecting the eMMC in various core kernel parts. This
happens as soon as I enable the eMMC in the device tree. It looks to
me like a DMA issue, because I'd think the errors are in core kernel
code which is fine, so I'd suspect some memory overwriting. But what
confuses me is that the same code works fine on the the 4.2 based
Renesas BSP. I have no idea regarding this, yet.
And third, from reading the r8a7795 manual I think the manual talks about
https://github.com/dirkbehme/linux-renesas-rcar-gen3/commit/f2a727c859916d59dca85dbb72c1b61da3fd6da0
But testing this it doesn't work. So either the manual is wrong, or I
missed anything else.
Best regards
Dirk
next prev parent reply other threads:[~2016-01-19 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 16:20 [RFC 0/6] mmc: sdhi: add basic r8a7795 support Wolfram Sang
2016-01-19 16:56 ` Dirk Behme [this message]
2016-01-22 8:54 ` Wolfram Sang
2016-01-22 10:32 ` Yoshihiro Shimoda
2016-01-22 11:26 ` Dirk Behme
2016-01-22 11:30 ` Dirk Behme
2016-01-22 11:36 ` Dirk Behme
2016-01-22 21:30 ` Wolfram Sang
2016-01-25 8:51 ` Yoshihiro Shimoda
2016-01-25 9:08 ` Dirk Behme
2016-01-25 16:25 ` Dirk Behme
2016-01-25 19:24 ` Wolfram Sang
2016-01-25 20:47 ` Geert Uytterhoeven
2016-01-26 6:12 ` Dirk Behme
2016-01-26 8:34 ` Wolfram Sang
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=569E6ACD.2060303@gmail.com \
--to=dirk.behme@gmail.com \
--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).