From: addy ke <addy.ke@rock-chips.com>
To: dianders@chromium.org
Cc: heiko@sntech.de, sonnyrao@chromium.org, stefan@agner.ch,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: Add mmc0 and mmc1 aliases for rk3288
Date: Thu, 14 Aug 2014 11:57:02 +0800 [thread overview]
Message-ID: <53EC338E.9060409@rock-chips.com> (raw)
In-Reply-To: <CAD=FV=XNJ9RRnOaJ5e-D60S5vjZu6UbphdWqqfRq_YfZaXoq+A@mail.gmail.com>
> Addy,
>
> On Wed, Aug 13, 2014 at 6:57 PM, Addy <addy.ke@rock-chips.com> wrote:
>
>> I think maybe it is suitable as follows:
>> mmc0 = &sdmmc
>> mmc1 = &sdio0
>> mmc2 = &sdio1
>> mmc3 = &emmc
>
> Right, except the only ones that have landed in Heiko's tree are sdmmc
> and emmc, so we can't do sdio0 and sdio1 yet. You could post support
> for sdio0 and adio1?
yes, I will post it today.
>
> Also: it's really handy if emmc is 0. See below: I don't think it's
> great to use the ID to find the sysconfig registers.
>
>
>> So we can get ctrl_id:
>> ctrl_id = of_alias_get_id(host->dev->of_node, "mshc");
>
> Somehow I hadn't realized that was there. I guess we could use that
> too. I'd vote to remove that and use the standard "mmc" numbering
> (and get some momentum to land those patches). If you want I'll
> repost using the mshc stuff, though.
>
>
>> and can get offset of registers:
>> offset = 0x200 + ctrl_id * 8 + 4 * drive_or_sample
>
> I thought the plan was to actually implement the phase stuff as a clock driver.
>
> ...even if we didn't, I'd rather not rely on ID like this to find the
> right address. It's really non-obvious.
>
>
>
prev parent reply other threads:[~2014-08-14 3:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 0:08 [PATCH] ARM: dts: Add mmc0 and mmc1 aliases for rk3288 Doug Anderson
2014-08-14 1:57 ` Addy
2014-08-14 3:40 ` Doug Anderson
2014-08-14 3:57 ` addy ke [this message]
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=53EC338E.9060409@rock-chips.com \
--to=addy.ke@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sonnyrao@chromium.org \
--cc=stefan@agner.ch \
/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