All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Maier <brandon.maier@rockwellcollins.com>
To: u-boot@lists.denx.de
Subject: Fwd: [PATCH] arm64: zynqmp: Support converting pm_cfg_obj.c
Date: Tue, 23 Jun 2020 16:23:40 -0500	[thread overview]
Message-ID: <CA+fik52qTB9RPpOQ9evJ6NQs+xoPzBHtgCBRu36T6fgAQcKkMA@mail.gmail.com> (raw)
In-Reply-To: <CA+fik51z3vVQDs23Yu7i164vzCQfJz_4jOa_k4nsY58edDHYYw@mail.gmail.com>

Forgot to CC
---------- Forwarded message ---------
From: Brandon Maier <brandon.maier@rockwellcollins.com>
Date: Tue, Jun 23, 2020 at 12:16 PM
Subject: Re: [PATCH] arm64: zynqmp: Support converting pm_cfg_obj.c
To: Michal Simek <michal.simek@xilinx.com>


On Tue, Jun 23, 2020 at 11:11 AM Michal Simek <michal.simek@xilinx.com> wrote:
> On 22. 06. 20 22:45, Brandon Maier wrote:
> > Add a config to set the file format, but leave the default as binary
> > type for backwards compatibility.
>
>
> Based on description I can't see the reason for it.
> pmu config object should be aligned with pmu not with u-boot itself.

What I mean is, for example if there is a bug in
zynqmp_pm_cfg_obj_convert then the pm_cfg binary will automatically be
updated the next time U-Boot is built. Compared to if the
pm_cfg_obj.bin is stored separately and has to be independently
updated for a bug. But it's a minor issue and not that important.

>
> Also using this script is just one way how to get pmufw config object.
> I personally don't use it but I can't see any issue to be in u-boot
> project if others want to use it.
>

We've been trying to piece together the scripts to build pmu config
from an HDF using Luca's blog posts and other source code. Out of
curiosity, what are these other methods?

>
> Thanks,
> Michal

      parent reply	other threads:[~2020-06-23 21:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 20:45 [PATCH] arm64: zynqmp: Support converting pm_cfg_obj.c Brandon Maier
2020-06-23 15:17 ` Luca Ceresoli
     [not found]   ` <CA+fik50_-6oRQTY0MdXacg=LHoKtjkBTQ+MYgK4VptDy5Njygg@mail.gmail.com>
2020-06-23 21:22     ` Fwd: " Brandon Maier
2020-06-23 21:23     ` Luca Ceresoli
2020-06-23 21:31       ` Luca Ceresoli
2020-06-23 21:46         ` [External] " Brandon Maier
2020-06-24  6:49           ` Michal Simek
2020-06-23 16:08 ` Michal Simek
     [not found]   ` <CA+fik51z3vVQDs23Yu7i164vzCQfJz_4jOa_k4nsY58edDHYYw@mail.gmail.com>
2020-06-23 21:23     ` Brandon Maier [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=CA+fik52qTB9RPpOQ9evJ6NQs+xoPzBHtgCBRu36T6fgAQcKkMA@mail.gmail.com \
    --to=brandon.maier@rockwellcollins.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.