From: dinguyen@altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3] ARM: socfpga: dts: Add support for SD/MMC
Date: Tue, 13 Aug 2013 15:17:57 -0500 [thread overview]
Message-ID: <1376425077.3167.6.camel@linux-builds1> (raw)
In-Reply-To: <520A92D2.2090208@wwwdotorg.org>
On Tue, 2013-08-13 at 14:10 -0600, Stephen Warren wrote:
> On 08/13/2013 01:58 PM, Dinh Nguyen wrote:
> > On Tue, 2013-08-13 at 13:52 -0600, Stephen Warren wrote:
> >> On 08/12/2013 09:49 AM, dinguyen at altera.com wrote:
> >>> From: Dinh Nguyen <dinguyen@altera.com>
> >>>
> >>> Add bindings for SD/MMC for SOCFPGA.
> >>> Add "syscon" to the "altr,sys-mgr" binding.
>
> >>> diff --git a/arch/arm/boot/dts/socfpga.dtsi b/arch/arm/boot/dts/socfpga.dtsi
> >>
> >>> sysmgr at ffd08000 {
> >>> - compatible = "altr,sys-mgr";
> >>> + compatible = "altr,sys-mgr", "syscon";
> >>
> >> That seems like an unrelated change?
> >
> > This patch is to enable SD/MMC for SOCFPGA. The "syscon" is needed in
> > dw_mmc-socfpga.c as the clock phases for the SD IP is controlled by
> > registers in "altr,sys-mgr".
>
> But nothing in the dwmmc nodes refers to the syscon node, so how can the
> syscon driver possibly provide services to the MMC driver; the MMC
> driver won't be able to find it. I hope there's no back-door assumption
> that some syscon exists, and that there's only one of them...
In dw_mmc-socfpga.c:
priv->sysreg = syscon_regmap_lookup_by_compatible("altr,sys-mgr");
then, uses regmap_write() to set the correct values from
"altr,dw-mshc-sdr-timing".
This was a suggestion from Arnd. It seems that this part of patch is
causing alot of confusion, I should just split the patches out?
Dinh
>
next prev parent reply other threads:[~2013-08-13 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 15:49 [PATCHv3] ARM: socfpga: dts: Add support for SD/MMC dinguyen at altera.com
2013-08-13 19:52 ` Stephen Warren
2013-08-13 19:58 ` Dinh Nguyen
2013-08-13 20:10 ` Stephen Warren
2013-08-13 20:17 ` Dinh Nguyen [this message]
2013-08-13 20:24 ` Stephen Warren
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=1376425077.3167.6.camel@linux-builds1 \
--to=dinguyen@altera.com \
--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).