From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 2/2] OMAP3: igep00x0: add boot status GPIO LED
Date: Thu, 10 Jan 2013 14:40:22 -0500 [thread overview]
Message-ID: <50EF1926.5020700@ti.com> (raw)
In-Reply-To: <CABxcv=n5DRy87Y9VyDi=BVPYXX6Fras+OTJxAP6CcvOT2d5p=g@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/10/2013 02:26 PM, Javier Martinez Canillas wrote:
> On Thu, Jan 10, 2013 at 6:26 PM, Tom Rini <trini@ti.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> On 01/10/2013 11:16 AM, Javier Martinez Canillas wrote:
>>> On Thu, Jan 10, 2013 at 4:35 PM, Tom Rini <trini@ti.com>
>>> wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>
>>>> On 01/10/2013 04:43 AM, Javier Martinez Canillas wrote:
>>>>> On Thu, Dec 27, 2012 at 3:25 PM, Igor Grinberg
>>>>> <grinberg@compulab.co.il> wrote:
>>>>>> On 12/27/12 15:36, Javier Martinez Canillas wrote:
>>>>>>> This patch adds an GPIO LED boot status for IGEP
>>>>>>> boards.
>>>>>>>
>>>>>>> The GPIO LED used is the red LED0 while the Linux
>>>>>>> kernel uses the green LED0 as the boot status.
>>>>>>>
>>>>>>> By using different GPIO LEDs, the user can know in
>>>>>>> which step of the boot process the board currently is.
>>>>>>>
>>>>>>> Signed-off-by: Javier Martinez Canillas
>>>>>>> <javier.martinez@collabora.co.uk>
>>>>>>
>>>>>> Acked-by: Igor Grinberg <grinberg@compulab.co.il>
>>>>>>
>>>>>
>>>>> Hello Tom,
>>>>>
>>>>> Any news of merging this patch?
>>>>
>>>> Things look good, sorry. I'm going to try and get to
>>>> starting a next branch but I might not get a chance before
>>>> the next release.
>>>>
>>>> - -- Tom
>>>
>>> Great, waiting for the next release is not an issue.
>>>
>>> There are also two more patches for IGEP boards that were acked
>>> but not picked for this release:
>>>
>>> [U-Boot,v2,1/2] OMAP3: use a single board file for IGEP devices
>>> [1] [U-Boot,1/1] OMAP3: igep00x0: add CONFIG_SPL_BOARD_INIT for
>>> CONFIG_SPL_NAND_SUPPORT [2]
>>
>> For the second path, did SPL+NAND for the IGEP devices get added
>> already?
>>
>> - -- Tom
>
> Yes, it was added on mainline commit d271a6114 "OMAP3: igep00x0:
> add SPL support for IGEP-based boards"
>
> Before posting that patch I only tested SPL booting from the
> uSD/MMC and later when trying SPL boot from NAND I realized that
> CONFIG_SPL_BOARD_INIT was missing to initialize the GPMC.
>
> Sorry, my bad. I should have tested both MMC and NAND booting
> before posting the SPL support patch.
OK, that makes it a bugfix. Albert, OK if I pull a bugfix patch
(adding a #define to a config) for a TI platform into master or do you
want it to go via u-boot-ti -> u-boot-arm ? Thanks!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBAgAGBQJQ7xklAAoJENk4IS6UOR1WxckQAKzSJF9cmf5uH2dTAWZ++r7f
Y5CS/Ro5E72OWgpjZCNwWts6Rr1uiP8hU15rOSq3a3An1tWPZuP6+xb4YTb2cvpb
X8EgeFQs9R++hJssCLn9lOYCmNdfF73siXJGSunVNUjxWlZePAHIUhLHeXFlYH8C
qAJ4chtD08fWJ5I/XWW5QdX8zAeF9M41U3jwYg1baeg0wiVWX7loV5s3AO76Wogp
qa6OLGXdvWzpV6+1A+vgRzjI9r0GA/rhpCD4vuoComenP6sBJezAK0Mn7s2slqmo
tXLMfi0G1FD7NF37wm3VYXLB8FlPJQfxfxbAk5oreIzl/BYieiGT27NiNrv1mzmm
5e/m1D7e7LJpJSeEJsRcwVrV1P9usEH1n1TVhMhlGOD3Z/XMC2sFX5GOPG4sMgkq
FxmXSM7mTrbYi/kvB16QWV5gn8r9e6Pl1a570+RJcwVKHMgWomvhWV5ihHb3UFww
VH3DBF1Xp3BuYrSmUgWelHCHI5QiZrLnwJoMDxj9jSRumQ0vAgjPPtbzZrNW43Xb
9URHP2oDyO7VEZnqZDMacEhIUHuZ96ENk7nEUWtpTqasCRdWHVTkM4HV5AHYiUxn
UwlcuVL6+4TWHgA1cfCyIcfGHh0zPzjgsDAO49GXGDzYPAEo/Wl3KDggiNZIFzwL
PcNb54gxJj+XEEi2bmRH
=oJ0U
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-01-10 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 13:36 [U-Boot] [PATCH v5 2/2] OMAP3: igep00x0: add boot status GPIO LED Javier Martinez Canillas
2012-12-27 14:25 ` Igor Grinberg
2013-01-10 9:43 ` Javier Martinez Canillas
2013-01-10 15:35 ` Tom Rini
2013-01-10 16:16 ` Javier Martinez Canillas
2013-01-10 17:26 ` Tom Rini
2013-01-10 19:26 ` Javier Martinez Canillas
2013-01-10 19:40 ` Tom Rini [this message]
2013-01-25 22:13 ` [U-Boot] [U-Boot, v5, " Tom Rini
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=50EF1926.5020700@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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