From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753987AbbIRNTO (ORCPT ); Fri, 18 Sep 2015 09:19:14 -0400 Received: from mout.kundenserver.de ([212.227.126.131]:55589 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753415AbbIRNTJ (ORCPT ); Fri, 18 Sep 2015 09:19:09 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Maxime Ripard , ulf.hansson@linaro.org, Mike Turquette , Stephen Boyd , linux-kernel@vger.kernel.org, Hans de Goede , linux-sunxi@googlegroups.com, Chen-Yu Tsai , linux-clk@vger.kernel.org Subject: Re: [PATCH 0/5] ARM: sunxi: Introduce CHIP support Date: Fri, 18 Sep 2015 15:18:57 +0200 Message-ID: <13485899.XsimukeSAF@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20150918121905.GO4684@lukather> References: <1442566130-3497-1-git-send-email-maxime.ripard@free-electrons.com> <2353279.QTDzFUHVnF@wuerfel> <20150918121905.GO4684@lukather> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:vTigCndpb+HLQQeIjOG4JBDhTaZRO4cTNhvhYMY1bOdwqtZqLS6 5MlpeN31UlNf1l+IIJRTadvI89GwPin23NK3wC0QXiLQ6Vf7FVBEF+6HTBFQVZO3Ch28VCN ERnQXyWqs9H2YoZ0ki8DF+qtIrxKTjUGMqfkYEzzWn0jXyCMGjYrckoEH8FcnKghEnXRCQ4 LtdnUoCT3atfHYeBEoiJg== X-UI-Out-Filterresults: notjunk:1;V01:K0:hoMUKSniV00=:qa+EYg84R078ZjXfT7A538 fYAh6Mke2FsDS576kWAKEKdsPoS6/G+XZzACyiSYkQI/RLlL5RoF5aCu6z8L+S3EtkQzIH/Ld wnsc4VUAgbh5NWxf+bJUVD/CB5ONNNaI+Xib6MLYBfoNexV+FPZqjtxByZvyvCrXcXIkd+GPC 8XwMXtu8ddSSj3sm0NtB7JLcegSrdbs34MGap8ArGw8sZqyrfU3g1baGjq6QBreaMHMpKGR01 y6OM5z3KBzUX5I4xPXBEOtIECqycGmMWKKfXRMVLKFXJr7kk7PLZfRJaYWqcrE2c+8OHQ0IjY 60VexmFuTzoemP2+J9/7+h+OdfMFGp7Zt5awAGxgz/2kye0DFZAB5gpKd+KCiRaLc3OoKpbfY 9juFRHsWsz+UAH6l/3RyM/3zMjBwu8ogixGZvdYI2ArQun56dtki1S2oANRp+zL/3AxWUUs6c 9+i1tKsbJl2WrVU5BMSANIUWij/qolxUzwEsOM+JJFHmhsgzb9y1FTRT2A9ub4wjix3CKSYhx vZ6jz0Dyjkb4kO82r8GI8zMP79IhKS9w20wM68PPU+07cZRbZjDLoXlp3JJCSgM79ktIl/N3R x8RpOgQOPQMiwnWeqW7Uin5OLZQ0CVl8tq0n9y/djtNPMKeQiyTXmCR0XPzOPVD6AA0x/YqIf 5wgpuwzxgrVSoKs+otNVcTQW4Tasx8nQUhfioX39QpPPg4g4HmuouU0cuv4e7s+J6p83Y4exA 3bb/j07lL2/fmEsK Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > * 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? 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? Arnd