All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v3 3/3] tools: Add a tool to get an overview of the usage of CONFIG options
Date: Sat, 3 Nov 2018 00:08:24 -0600	[thread overview]
Message-ID: <CAPnjgZ3GbZ6y6y4VRrJKZhZvnNcq6wUiApK6=ecV_7+t9zNBDg@mail.gmail.com> (raw)
In-Reply-To: <1540552457-27467-4-git-send-email-jjhiblot@ti.com>

On 26 October 2018 at 05:14, Jean-Jacques Hiblot <jjhiblot@ti.com> wrote:
> configs2csv.py is tool that allow to check how some options are used for a
> particular subset of platforms.
> The purpose is to identify the targets that are actually using one or more
> options of interest.
> For example, it can tell what targets are still using CONFIG_DM_I2_COMPAT.
> It relies on the config database produced by tools/moveconfig.py.
> If the database doesn't exist, it will build it for the restricted set of
> the selected platforms. Once the database is built, it is much faster than
> greping the configs directory and more accurate as it relies on the
> information found in u-boot.cfg instead of defconfigs.
> It possible to look for options in the u-boot, the SPL or the TPL
> configurations. It can also perform diffs between those configurations.
>
> usage: configs2csv.py [-h] [-X] [--u-boot] [--spl] [--tpl] [--diff]
>                       [--rebuild-db] [-j JOBS] [-o OUTPUT] [--no-header]
>                       [--discard-empty] [-i] [--soc SOC] [--vendor VENDOR]
>                       [--arch ARCH] [--cpu CPU] [--board BOARD]
>                       [--target TARGET]
>                       OPTION [OPTION ...]
>
> all filtering parameters (OPTION, vendor, arch, ...) accept regexp.
> ex: configs2csv.py .*DM_I2C.* --soc 'omap[2345]|k3' will match
> CONFIG_DM_I2C and CONFIG_DM_I2C_COMPAT and look for it only for targets
> using the omap2, omap3, omap4, omap5 or k3 SOCs.
>
> Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
>
> ---
>
> Changes in v3:
> - stylistics changes
> - Add more comments to describe classes and functions
>
> Changes in v2:
> - basically rewrote the whole thing
> - use tools/moveconfig.py to generate the database of configs
> - use tools/find_defconfigs.py to get the list of defconfigs off interest
> - removed diff with .config. tools/moveconfig.py does a better job
>
>  tools/configs2csv.py | 427 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 427 insertions(+)
>  create mode 100755 tools/configs2csv.py

Reviewed-by: Simon Glass <sjg@chromium.org>

      reply	other threads:[~2018-11-03  6:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 11:14 [U-Boot] [RFC PATCH v3 0/3] python tools to inspect configs Jean-Jacques Hiblot
2018-10-26 11:14 ` [U-Boot] [RFC PATCH v3 1/3] tools: moveconfig: Add an option to build a fuller database of options Jean-Jacques Hiblot
2018-11-03  6:08   ` Simon Glass
2018-10-26 11:14 ` [U-Boot] [RFC PATCH v3 2/3] tools: Add a tool to get a list of defconfigs based on filters Jean-Jacques Hiblot
2018-11-03  6:08   ` Simon Glass
2018-10-26 11:14 ` [U-Boot] [RFC PATCH v3 3/3] tools: Add a tool to get an overview of the usage of CONFIG options Jean-Jacques Hiblot
2018-11-03  6:08   ` Simon Glass [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='CAPnjgZ3GbZ6y6y4VRrJKZhZvnNcq6wUiApK6=ecV_7+t9zNBDg@mail.gmail.com' \
    --to=sjg@chromium.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.