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: [linux-sunxi] Re: [PATCH 4/5] ARM: dts: sun5i: Add dts file for the Empire Electronix D709 tablet
Date: Mon, 4 Jan 2016 11:11:21 +0100	[thread overview]
Message-ID: <20160104101121.GC11722@lukather> (raw)
In-Reply-To: <CAGb2v67+XpYwUFAVSGEGAfJ0bzubQ87Ebaf5W5Ze619mEE6uUA@mail.gmail.com>

Hi,

On Tue, Dec 22, 2015 at 12:29:24PM +0800, Chen-Yu Tsai wrote:
> >>> So this means enabled the sdio controller (should be safe on all
> >>> boards?)  and enabling 2 regulators to power the wifi-chip. I
> >>> think it will be safe to do this even on boards where those
> >>> regulators are not used, what do you think ?
> >>
> >> Wouldn't that introduce some useless power drain on those boards?
> >
> >
> > If nothing is attached to those regulators (which I expect to be
> > the case when they are not used to power wifi) then I would expect
> > the drain to be minimal, my biggest worry is some board having
> > tied these to ground, but I don't think that is very likely.
> 
> AFAIK the AXP datasheets mention that unused DCDC outputs should be left
> floating. Not sure if this applies to LDO outputs as well. But any used
> outputs would have a bypass capacitor.
> 
> From the board designs I've seen, this seems to be the common case.
> I'm not an electrical engineer, but I think we're covered here.

Ok, I guess we're good then.

Thanks!
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/20160104/222f1583/attachment-0001.sig>

  parent reply	other threads:[~2016-01-04 10:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 11:42 [PATCH 1/5] ARM: dts: sun4i: Add touchscreen node to inet9f-rev03 tablet dts file Hans de Goede
2015-12-20 11:42 ` [PATCH 2/5] ARM: dts: sun4i: Add touchscreen node to chuwi-v7 " Hans de Goede
2015-12-21  5:56   ` Chen-Yu Tsai
2015-12-20 11:43 ` [PATCH 3/5] ARM: dts: sun4i: Add touchscreen node to inet97fv2 " Hans de Goede
2015-12-21  5:58   ` Chen-Yu Tsai
2015-12-20 11:43 ` [PATCH 4/5] ARM: dts: sun5i: Add dts file for the Empire Electronix D709 tablet Hans de Goede
2015-12-21  6:09   ` Chen-Yu Tsai
2015-12-21 10:46     ` [linux-sunxi] " Hans de Goede
2015-12-21 16:11       ` Maxime Ripard
2015-12-21 19:36         ` Hans de Goede
2015-12-22  4:29           ` Chen-Yu Tsai
2015-12-22 10:50             ` Hans de Goede
2016-01-04 10:11             ` Maxime Ripard [this message]
2015-12-21 16:10   ` Maxime Ripard
2015-12-20 11:43 ` [PATCH 5/5] ARM: dts: sun7i: Enable gmac on Wits Pro A20 DKT Hans de Goede
2015-12-21  5:55   ` Chen-Yu Tsai
2015-12-21 16:08     ` Maxime Ripard
2015-12-21  5:57 ` [PATCH 1/5] ARM: dts: sun4i: Add touchscreen node to inet9f-rev03 tablet dts file Chen-Yu Tsai
2015-12-21 10:40   ` [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=20160104101121.GC11722@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).