linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jbe@pengutronix.de (Jürgen Borleis)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 4/6] DT: add binding for mxs on-chip regulators
Date: Mon, 4 May 2015 15:51:26 +0200	[thread overview]
Message-ID: <201505041551.26355.jbe@pengutronix.de> (raw)
In-Reply-To: <1430346747-28728-5-git-send-email-stefan.wahren@i2se.com>

Hi Stefan,

for the i.MX23 the regulator daisy chain looks a little bit different:

+------------+ ? ? VDD5V ?+---------+ ?VDDIO
| DC-DC ? ? ?| ? +--------> LINREG ?+--------->+
| ? ? ? ? ? ?| ? ? ? ? ? ?| VDDIO ? | ? ? ? ? ?|
| ? ? ? ? ? ?| ? ? ? ? ? ?+---------+ ? ? ? ? ?|
| DCDC_VDDIO +->-+-----------------------------+
| ? ? ? ? ? ?| ? |
|            |   | VDDIO  +---------+  VDDMEM
|            |   +--------> LINREG  +--------->
|            |   |        | VDDMEM  |
|            |   |        +---------+
| ? ? ? ? ? ?| ? | VDDIO ?+---------+ ?VDDA
| ? ? ? ? ? ?| ? +--------> LINREG ?+--------->+
| ? ? ? ? ? ?| ?   ? ? ? ?| VDDA ? ?| ? ? ? ? ?|
| ? ? ? ? ? ?| ?   ? ? ? ?+---------+ ? ? ? ? ?|
| DCDC_VDDA  +->-+-----------------------------+
| ? ? ? ? ? ?| ? | VDDA ? +---------+ ?VDDD
| ? ? ? ? ? ?| ? +--------> LINREG ?+--------->+
| ? ? ? ? ? ?| ? ? ? ? ? ?| VDDD ? ?| ? ? ? ? ?|
| ? ? ? ? ? ?| ? ? ? ? ? ?+---------+ ? ? ? ? ?|
| DCDC_VDDD ?+->-------------------------------+
+------------+ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? |
 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? v

Regards,
Juergen

  reply	other threads:[~2015-05-04 13:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 22:32 [PATCH V2 0/6] regulator: enable regulator support for i.MX23/i.MX28 Stefan Wahren
2015-04-29 22:32 ` [PATCH V2 1/6] DT: add binding for mxs power subsystem Stefan Wahren
2015-04-29 22:32 ` [PATCH V2 2/6] ARM: mxs: select syscon for platform Stefan Wahren
2015-04-29 22:32 ` [PATCH V2 3/6] power: mxs_power: add driver for mxs power subsystem Stefan Wahren
2015-05-23 17:41   ` Sebastian Reichel
2015-05-27  7:12     ` Stefan Wahren
2015-05-27 13:51       ` Sebastian Reichel
2015-05-27 16:34         ` Stefan Wahren
2015-05-28 17:38           ` Sebastian Reichel
2015-04-29 22:32 ` [PATCH V2 4/6] DT: add binding for mxs on-chip regulators Stefan Wahren
2015-05-04 13:51   ` Jürgen Borleis [this message]
2015-05-04 20:20     ` Stefan Wahren
2015-05-05  8:21       ` Jürgen Borleis
2015-05-05 17:12         ` Stefan Wahren
2015-04-29 22:32 ` [PATCH V2 5/6] regulator: add mxs on-chip regulator driver Stefan Wahren
2015-05-04 12:36   ` Mark Brown
2015-05-04 20:34     ` Stefan Wahren
2015-05-07 18:37       ` Stefan Wahren
2015-05-07 18:52         ` Mark Brown
2015-05-07 19:25           ` Stefan Wahren
2015-05-07 19:32             ` Mark Brown
2015-05-26 12:16               ` Stefan Wahren
2015-05-27 17:33                 ` Mark Brown
2015-05-27 20:58                   ` Stefan Wahren
2015-05-28 14:26                     ` Mark Brown
2015-04-29 22:32 ` [PATCH V2 6/6] ARM: dts: enable regulator support for i.MX23/i.MX28 Stefan Wahren

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=201505041551.26355.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --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).