From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] bootstage: Add a number of new features
Date: Wed, 3 Oct 2012 01:02:41 +0200 [thread overview]
Message-ID: <20121003010241.6905506b@wker> (raw)
In-Reply-To: <1348858600-7095-1-git-send-email-sjg@chromium.org>
Hi Simon,
On Fri, 28 Sep 2012 11:56:34 -0700
Simon Glass <sjg@chromium.org> wrote:
> It is useful to be able to communicate the bootstage information to another
> program, such as the kernel, either by putting it in memory or the device
> tree. This makes the information accessible after boot so that it can easily
> be logged somewhere or perhaps reported back for diagnostics purposes.
> This series includes a few patches to implement this.
>
> Sometimes a peripheral is touched multiple times during boot, or a single
> task is called repeatedly. Examples are reading from a device, which might
> happen in several parts, or setting up an LCD display, which may involve
> multiple steps to comply with backlight power sequences. This series adds a
> new bootstage time accumulation feature to add up all the time spent in a
> particular task.
>
> This series also adds a new command 'bootstage' to provide access to the
> above features.
>
>
> Simon Glass (6):
> bootstage: Export bootstage_add_record() function
> bootstage: Add time accumulation feature
> bootstage: Store boot timings in device tree
> bootstage: Add feature to stash/unstash bootstage info
> bootstage: Add bootstage command
> bootstage: Add new bootstage IDs for board, LCD
>
> README | 25 ++++
> arch/arm/lib/bootm.c | 3 +
> common/Makefile | 1 +
> common/bootstage.c | 306 +++++++++++++++++++++++++++++++++++++++++++++---
> common/cmd_bootstage.c | 116 ++++++++++++++++++
> include/bootstage.h | 85 +++++++++++++
> 6 files changed, 517 insertions(+), 19 deletions(-)
> create mode 100644 common/cmd_bootstage.c
Applied this series to u-boot-staging/agust at denx.de-next, thanks!
I've dropped "BRANCH=snow,link" in commit log of the patches 4 and 5,
hope this is okay?
Thanks,
Anatolij
next prev parent reply other threads:[~2012-10-02 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 18:56 [U-Boot] [PATCH 0/6] bootstage: Add a number of new features Simon Glass
2012-09-28 18:56 ` [U-Boot] [PATCH 1/6] bootstage: Export bootstage_add_record() function Simon Glass
2012-09-28 18:56 ` [U-Boot] [PATCH 2/6] bootstage: Add time accumulation feature Simon Glass
2012-09-28 18:56 ` [U-Boot] [PATCH 3/6] bootstage: Store boot timings in device tree Simon Glass
2012-09-28 18:56 ` [U-Boot] [PATCH 4/6] bootstage: Add feature to stash/unstash bootstage info Simon Glass
2012-09-28 18:56 ` [U-Boot] [PATCH 5/6] bootstage: Add bootstage command Simon Glass
2012-09-28 18:56 ` [U-Boot] [PATCH 6/6] bootstage: Add new bootstage IDs for board, LCD Simon Glass
2012-10-02 23:02 ` Anatolij Gustschin [this message]
2012-10-03 0:07 ` [U-Boot] [PATCH 0/6] bootstage: Add a number of new features Simon Glass
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=20121003010241.6905506b@wker \
--to=agust@denx.de \
--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