From: Nishanth Menon <nm@ti.com>
To: Afzal Mohammed <afzal.mohd.ma@gmail.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>,
Tony Lindgren <tony@atomide.com>,
lkml <linux-kernel@vger.kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
ARM Linux <arm@kernel.org>, Olof Johansson <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 1/3] ARM: multi_v7_defconfig: Enable beaglebone PMIC TPS65217
Date: Wed, 16 Dec 2015 08:04:24 -0600 [thread overview]
Message-ID: <56716F68.6090701@ti.com> (raw)
In-Reply-To: <20151216134541.GA5574@afzalpc>
On 12/16/2015 07:45 AM, Afzal Mohammed wrote:
[...]
> Changelog refers to old beagle bone's, does new ones have a different
> PMIC ?, i only have white bones ;)
Blacks seem to boot (see cover-letter) - could be because of default
configuration of tps65217. From my test log:
11: beaglebone-black: BOOT: PASS: err=4 warn=13:
http://pastebin.ubuntu.com/14008272/
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-12-16 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 18:42 [PATCH V2 0/3] ARM: multi_v7_defconfig: Enable more OMAP family platforms Nishanth Menon
2015-12-14 18:42 ` [PATCH V2 1/3] ARM: multi_v7_defconfig: Enable beaglebone PMIC TPS65217 Nishanth Menon
2015-12-15 13:51 ` Afzal Mohammed
2015-12-15 14:49 ` Nishanth Menon
2015-12-16 13:45 ` Afzal Mohammed
2015-12-16 14:04 ` Nishanth Menon [this message]
2015-12-16 14:15 ` Afzal Mohammed
2015-12-22 19:31 ` Olof Johansson
2015-12-26 13:33 ` Afzal Mohammed
2015-12-14 18:42 ` [PATCH V2 2/3] ARM: multi_v7_defconfig: Enable AM437x PMIC TPS65218 Nishanth Menon
2015-12-22 19:32 ` Olof Johansson
2015-12-14 18:43 ` [PATCH V2 3/3] ARM: multi_v7_defconfig: Enable generic SoC internal OMAP regulators Nishanth Menon
2015-12-22 19:32 ` Olof Johansson
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=56716F68.6090701@ti.com \
--to=nm@ti.com \
--cc=afzal.mohd.ma@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=tony@atomide.com \
/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).