From: Stephen Warren <swarren@wwwdotorg.org>
To: Dinh Nguyen <dinguyen@altera.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
Seungwon Jeon <tgih.jun@samsung.com>,
Thomas Abraham <thomas.abraham@linaro.org>,
Chris Ball <cjb@laptop.org>,
dinh.linux@gmail.com, Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
devicetree@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: socfpga: dts: Add support for SD/MMC
Date: Fri, 26 Jul 2013 14:02:50 -0600 [thread overview]
Message-ID: <51F2D5EA.7050108@wwwdotorg.org> (raw)
In-Reply-To: <1374867220.20685.44.camel@linux-builds1>
On 07/26/2013 01:33 PM, Dinh Nguyen wrote:
> On Fri, 2013-07-26 at 11:24 -0600, Stephen Warren wrote:
>> On 07/25/2013 04:04 PM, dinguyen@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/Documentation/devicetree/bindings/mmc/socfpga-dw-mshc.txt b/Documentation/devicetree/bindings/mmc/socfpga-dw-mshc.txt
>>> +Example:
>>> +
>>> + The MSHC controller node can be split into two portions, SoC specific and
>>> + board specific portions, as listed below.
>>
>> That doesn't sound like a good idea. There should be one DT node for
>> each logical block. The internal construction of the Linux drivers
>> (presumably you have entirely separate code to handle the two nodes in
>> Linux so far?) should not influence the DT construction at all.
>
> In the end, there is only 1 DT node for each logical block:
Oh right, I see you were intending to show the distinction between the
SoC .dtsi and board .dts file. I hadn't realized that. I don't think
it's common to do that in the examples, so I would recommend just
merging the whole example together myself.
> dwmmc0@ff704000 {
> compatible = "altr,socfpga-dw-mshc";
That should include the baseline synopsis compatible value too.
> reg = <0xff704000 0x00001000>;
> interrupts = <0x00000000 0x0000008b 0x00000004>;
> fifo-depth = <0x00000400>;
> #address-cells = <0x00000001>;
> #size-cells = <0x00000000>;
> clocks = <0x00000016 0x00000017>;
> clock-names = "biu", "ciu";
> num-slots = <0x00000001>;
> supports-highspeed;
> broken-cd;
> altr,dw-mshc-ciu-div = <0x00000003>;
> altr,dw-mshc-sdr-timing = <0x00000000 0x00000003>;
> slot@0 {
> reg = <0x00000000>;
> bus-width = <0x00000004>;
> };
> };
next prev parent reply other threads:[~2013-07-26 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 22:04 [PATCH] ARM: socfpga: dts: Add support for SD/MMC dinguyen
2013-07-26 13:49 ` Pawel Moll
2013-07-26 14:49 ` Dinh Nguyen
2013-07-26 15:00 ` Pawel Moll
2013-07-26 15:27 ` Dinh Nguyen
2013-07-26 17:24 ` Stephen Warren
2013-07-26 19:33 ` Dinh Nguyen
2013-07-26 20:02 ` Stephen Warren [this message]
2013-07-26 20:44 ` Dinh Nguyen
2013-07-26 21:13 ` Stephen Warren
2013-07-26 21:22 ` Dinh Nguyen
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=51F2D5EA.7050108@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=cjb@laptop.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@altera.com \
--cc=dinh.linux@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=tgih.jun@samsung.com \
--cc=thomas.abraham@linaro.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