linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ARM: sunxi: Introduce CHIP support
Date: Fri, 18 Sep 2015 15:55:38 +0200	[thread overview]
Message-ID: <20150918135538.GS4684@lukather> (raw)
In-Reply-To: <13485899.XsimukeSAF@wuerfel>

On Fri, Sep 18, 2015 at 03:18:57PM +0200, Arnd Bergmann wrote:
> On Friday 18 September 2015 14:19:05 Maxime Ripard wrote:
> > 
> > There's actually two issues that are pretty orthogonal:
> > 
> >   * the fact that the regulator to power the wifi chip needs to be
> >     enabled before it enumerates and the driver is probed. The MMC
> >     pwrseq stuff seems to fix that, even if it doesn't really fit in
> >     the usual DT model.
> 
> Ok. If there is anything missing in the pwrseq implementation or
> binding at the moment, you'll have to work with Ulf to get it to
> drive your hardware then.

Yep.

> >   * The fact that that regulator on this board is actually two
> >     regulators in parallel that needs to be controlled in parallel
> >     too. Here, it will probably require a new regulator driver to
> >     combine two regulators into one.
> 
> I don't yet understand what it means to control them in parallel.
> Do you mean the hardware uses two outputs to support a higher
> current than you could do with one?

Yes.

> How critical is the timing? Would it be enough if the mmc
> code knew how to set more than one regulator and do them
> one at a time?

I don't think it's critical as in both should happen exactly at the
same time (but I've not really tried it either, so I'm not 100% sure).

And I don't think it's something the MMC core should deal with. The
device itself has a single pin to provide its power, it's the board
that is wired that way. The way I was seeing it was more that I needed
to create a regulator driver that would take two inputs, that the mmc
core would use. Last time I discussed it with Mark (Brown), it semes
like he was open to the idea, so I just need to find some time to do
just that.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150918/cf968413/attachment-0001.sig>

  reply	other threads:[~2015-09-18 13:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  8:48 [PATCH 0/5] ARM: sunxi: Introduce CHIP support Maxime Ripard
2015-09-18  8:48 ` [PATCH 1/5] ARM: sunxi: Add R8 support Maxime Ripard
2015-09-18  9:47   ` Chen-Yu Tsai
2015-09-18 12:20     ` Maxime Ripard
2015-09-30 22:38   ` Stephen Boyd
2015-10-01  6:58     ` Maxime Ripard
2015-09-18  8:48 ` [PATCH 2/5] ARM: sun5i: Add R8 DTSI Maxime Ripard
2015-09-18  9:41   ` Chen-Yu Tsai
2015-09-18 12:19     ` Maxime Ripard
2015-09-18  8:48 ` [PATCH 3/5] ARM: sun5i: dt: Move uart3 pinctrl node to common DTSI Maxime Ripard
2015-09-18  8:48 ` [PATCH 4/5] ARM: sun5i: dt: Add UART3 CTS and RTS pins Maxime Ripard
2015-09-18  8:48 ` [PATCH 5/5] ARM: sun5i: Add C.H.I.P DTS Maxime Ripard
2015-09-18 16:41   ` Chen-Yu Tsai
2015-09-22 12:47     ` Maxime Ripard
2015-09-22 12:57       ` [linux-sunxi] " Chen-Yu Tsai
2015-09-22 13:01         ` Hans de Goede
2015-09-22 13:34           ` Hans de Goede
2015-09-22 14:04           ` Maxime Ripard
2015-09-22 14:30             ` Hans de Goede
2015-09-29 19:36               ` Maxime Ripard
2015-09-18  9:02 ` [PATCH 0/5] ARM: sunxi: Introduce CHIP support Arnd Bergmann
2015-09-18 12:19   ` Maxime Ripard
2015-09-18 13:18     ` Arnd Bergmann
2015-09-18 13:55       ` Maxime Ripard [this message]
2015-09-18 13:58         ` Arnd Bergmann
2015-09-18 15:36 ` [linux-sunxi] " Hans de Goede

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=20150918135538.GS4684@lukather \
    --to=maxime.ripard@free-electrons.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).