All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 1/3] binman: Allow selecting default FIT configuration
Date: Tue, 8 Sep 2020 20:33:00 +0300	[thread overview]
Message-ID: <7a121628-6fbd-0006-73dc-69b3993b6c53@gmail.com> (raw)
In-Reply-To: <20200906103901.v4.1.Ie75709c8b68c270e911bba4dbd521706c966087f@changeid>

On 06/09/2020 19:39, Simon Glass wrote:
> Add a new entry argument to the fit entry which allows selection of the
> default configuration to use. This is the 'default' property in the
> 'configurations' node.
> 
> Update the Makefile to pass in the value of DEVICE_TREE or
> CONFIG_DEFAULT_DEVICE_TREE to provide this information.
> 
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Suggested-by: Michal Simek <michal.simek@xilinx.com>
> ---
> 
> Changes in v4:
> - Add more documentation for DEFAULT-SEQ

I might be too late to say this but the SEQ thing looks ugly to me.
Maybe there could be some generic control-flow-like nodes that could
generate and insert things in their own place. If it makes sense, I'm
imagining something like:

    fit {
        images {
            __for__ {
                for,variable = "name";
                for,in-args = "of-list";

                fdt-#name {
                    description = "fdt-$name.dtb";
                    type = "flat_dt";
                    compression = "none";
                };
            };
        };

        configurations {
            __for__ {
                for,variable = "name"
                for,in-args = "of-list";

                __if__ {
                    if,arg-equals = "default-dt", "$name";
                    default = "config-#name";
                };

                config-#name {
                    description = "conf-$name.dtb";
                    fdt = "fdt-#name";
                };
            };
        };
    };

  reply	other threads:[~2020-09-08 17:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06 16:39 [PATCH v4 0/3] binman: Further updates for FIT support Simon Glass
2020-09-06 16:39 ` [PATCH v4 1/3] binman: Allow selecting default FIT configuration Simon Glass
2020-09-08 17:33   ` Alper Nebi Yasak [this message]
2020-09-08 23:56     ` Simon Glass
2020-09-09 20:27       ` Alper Nebi Yasak
2020-09-27  1:59       ` Simon Glass
2020-09-06 16:39 ` [PATCH v4 2/3] binman: Support help messages for missing blobs Simon Glass
2020-09-08 16:37   ` Alper Nebi Yasak
2020-09-08 23:56     ` Simon Glass
2020-09-09 20:29       ` Alper Nebi Yasak
2020-09-27  1:59       ` Simon Glass
2020-09-06 16:39 ` [PATCH v4 3/3] binman: sunxi: Add help message for missing sunxi ATF BL31 Simon Glass
2020-09-07  8:44 ` [PATCH v4 0/3] binman: Further updates for FIT support Michal Simek
2020-09-07 13:57   ` Simon Glass
2020-09-12 20:43   ` Samuel Holland
2020-09-14  6:48     ` Michal Simek

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=7a121628-6fbd-0006-73dc-69b3993b6c53@gmail.com \
    --to=alpernebiyasak@gmail.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 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.