From: Lars Doelle <lars.doelle-RMqqONVpFt+ELgA04lAiVw@public.gmane.org>
To: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: Re: Including empty regulator nodes in axp209.dtsi is a BAD idea
Date: Fri, 16 Jan 2015 00:41:56 +0100 [thread overview]
Message-ID: <2741297.nF4Wtine9N@x64.localnet> (raw)
In-Reply-To: <CAGb2v66Go1z-V8spwHvLHQC1R=vgDsk1nQ6iZWTsy+OMF1kK0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
> It is entirely possible to make a board without using the PMIC, as Olimex
> has demonstrated. sun7i-a20 only describes the common SoC bits.
I'm sorry, I wrongly thought that axp209 is on the SoC.
Lars
prev parent reply other threads:[~2015-01-15 23:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 9:39 Including empty regulator nodes in axp209.dtsi is a BAD idea Hans de Goede
[not found] ` <54B4E7B5.6060304-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-01-13 16:46 ` Maxime Ripard
2015-01-14 7:42 ` Hans de Goede
[not found] ` <54B61DD3.6010105-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-01-14 8:11 ` Michal Suchanek
2015-01-15 16:54 ` Chen-Yu Tsai
[not found] ` <CAGb2v67uGV2HBKciRVGhf-vb7K=whruiaUvv8L7Lqz=8=kBnQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-15 22:04 ` Maxime Ripard
2015-01-16 0:58 ` Chen-Yu Tsai
2015-01-16 7:42 ` Hans de Goede
2015-01-15 21:57 ` Maxime Ripard
2015-01-14 10:18 ` Lars Doelle
[not found] ` <5312007.HNApKlEIe7-01DtBWzyqXQXpj0+iOhflA@public.gmane.org>
2015-01-15 16:48 ` Chen-Yu Tsai
[not found] ` <CAGb2v66Go1z-V8spwHvLHQC1R=vgDsk1nQ6iZWTsy+OMF1kK0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-15 21:51 ` Maxime Ripard
2015-01-15 23:41 ` Lars Doelle [this message]
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=2741297.nF4Wtine9N@x64.localnet \
--to=lars.doelle-rmqqonvpft+elga04laivw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=wens-jdAy2FN1RRM@public.gmane.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