From: dinguyen@opensource.altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: socfpga: Add a 3.3V fixed regulator node
Date: Fri, 17 Oct 2014 14:19:59 -0500 [thread overview]
Message-ID: <54416BDF.6010204@opensource.altera.com> (raw)
In-Reply-To: <CAD=FV=V3Ewv7Ns_JD0+gd4J6p3k-N-rmFjkdYQobMgB8m7z6SA@mail.gmail.com>
On 10/17/2014 11:57 AM, Doug Anderson wrote:
> Dinh,
>
> On Thu, Oct 16, 2014 at 2:03 PM, <dinguyen@opensource.altera.com> wrote:
>> From: Dinh Nguyen <dinguyen@opensource.altera.com>
>>
>> Without the 3.3V regulator node, the SDMMC driver will give these warnings:
>>
>> dw_mmc ff704000.dwmmc0: No vmmc regulator found
>> dw_mmc ff704000.dwmmc0: No vqmmc regulator found
>>
>> This patch adds the regulator node, and points the SD/MMC to the regulator.
>>
[...]
>>
>> - dwmmc0 at ff704000 {
>> + mmc0: dwmmc0 at ff704000 {
>> num-slots = <1>;
>> broken-cd;
>> bus-width = <4>;
>> @@ -41,4 +41,13 @@
>> cpu1-start-addr = <0xffd080c4>;
>> };
>> };
>> +
>> + regulator_3_3v_hps: fixed_3_3v_hps_regulator at 0 {
>
> nit: no @0 since there is no "reg" (register) under this node.
>
> nit: usually people don't like "_" in node names. ...I would probably
> do this but I'm not an expert:
> regulator_3_3v_hps: hps-regulator {
Ok..will fix up.
>
> This regulator also looks pretty bogus to me. Is this really a
> regulator that software has no control over? It means you can't fully
> reset a card but I guess that's OK.
Yes, this is a generic 3.3V regulator that is used for the 3.3V power
rail for the SOC, and any IP the needs 3.3V.
Schematics are here:
http://www.rocketboards.org/pub/Documentation/AlteraSoCDevelopmentBoard/c5_soc_devkit_c.pdf?t=1365712679
http://www.rocketboards.org/pub/Documentation/ArrowSoCKitEvaluationBoard/SoCKit_RevC.pdf
And right, I don't see anyway to be able to reset the card.
>
> I'd also expect this regulator to be defined in the same dts / dtsi
> file that it's used in. Your current patch says "there's a generic
> 3.3V regulator on all boards of the socfpga_arria5 class even if they
> don't use MMC, but the "socfpga_arria5_socdk" uses it for MMC. Is
> that really true?
>
yeah...My original patch had the regulator placed in it's appropriate
dts board file, but I saw that as a bit of duplication. I figured that
most people are just copying Altera's devkit schematic, that if a new
board file shows up that has a different controllable regulator, then
the board file can have the new regulator node. Meanwhile, this patch
saves adding an additional regulator node for the existing board files.
The 3.3V is not just used by MMC, but the for all 3.3V peripherals.
Thanks for feedback.
Dinh
next prev parent reply other threads:[~2014-10-17 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 21:03 [PATCH 0/2] ARM: dts: socfpga: fix booting with SD/MMC dinguyen at opensource.altera.com
2014-10-16 21:03 ` [PATCH 1/2] ARM: dts: socfpga: Fix SD card detect dinguyen at opensource.altera.com
2014-10-16 21:03 ` [PATCH 2/2] ARM: dts: socfpga: Add a 3.3V fixed regulator node dinguyen at opensource.altera.com
2014-10-17 1:43 ` Jaehoon Chung
2014-10-17 13:37 ` Dinh Nguyen
2014-10-17 16:57 ` Doug Anderson
2014-10-17 19:19 ` Dinh Nguyen [this message]
2014-10-17 19:43 ` Doug Anderson
2014-10-17 20:04 ` Dinh Nguyen
2014-10-17 22:36 ` Doug Anderson
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=54416BDF.6010204@opensource.altera.com \
--to=dinguyen@opensource.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).