From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 0/6] mmc: sdhi: add basic r8a7795 support
Date: Fri, 22 Jan 2016 08:54:08 +0000 [thread overview]
Message-ID: <20160122085408.GA3967@tetsubishi> (raw)
In-Reply-To: <1453220461-2598-1-git-send-email-wsa@the-dreams.de>
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
Hi Dirk,
> 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:
I am not the clock expert, but I try to have a look next week.
> Second, I'm mainly interested in eMMC support for the Salvator-X. Therefore
OK, nice to know. I have eMMC running now, without DMA and HS200, of
course. My patches need some refactoring, though.
> I picked (hopefully) all patches from the Renesas BSP to
> renesas-drivers-2016-01-13-v4.4
Yes, that's where I picked your clock patches from :)
> 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.
I usually don't have high hopes that putting more than a trivial amount
of any BSP code on top of upstream will result in success ;)
My obviuos plan is to work incrementally. First basic support, then DMA,
then UHS-I/HS200. Review, refactor existing patches. Upstream first, etc
pp... You know all this, I guess.
> 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.
I have seen this patch and my gut feeling is that it won't make a
difference? SCLKDIVEN is like CBUSY plus some more cycles AFAIU. But I
am not working on DMA issues now, this has to wait.
Kind regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-22 8:54 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
2016-01-22 8:54 ` Wolfram Sang [this message]
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=20160122085408.GA3967@tetsubishi \
--to=wsa@the-dreams.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.