public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Marcin Wojtas <mw@semihalf.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Leif Lindholm" <leif.lindholm@linaro.org>,
	"Jan Dąbroś" <jsd@semihalf.com>, "Hua Jing" <jinghua@marvell.com>,
	"Grzegorz Jaszczyk" <jaz@semihalf.com>,
	"David Sniatkiwicz" <davidsn@marvell.com>
Subject: Re: [platforms PATCH 3/4] Marvell/Armada7k8k: Introduce capsule FW update implementation
Date: Fri, 1 Jun 2018 18:08:56 +0200	[thread overview]
Message-ID: <CAKv+Gu_HY0_hrGb3vu083kgoSkg0KVb48R-59eD61grkPxRSVw@mail.gmail.com> (raw)
In-Reply-To: <CAPv3WKeOrhe3B-z4+Uz26xKvU3Zb8bfdBShFT9YvWDAqRYOeJQ@mail.gmail.com>

On 1 June 2018 at 18:02, Marcin Wojtas <mw@semihalf.com> wrote:
> Hi Ard,
>
> 2018-06-01 17:32 GMT+02:00 Ard Biesheuvel <ard.biesheuvel@linaro.org>:
>>  On 1 June 2018 at 16:32, Marcin Wojtas <mw@semihalf.com> wrote:
>>> From: David Sniatkiwicz <davidsn@marvell.com>
>>>
>>> This patch adds necessary code that allows to update
>>> firmware on Armada7k8k platforms, using generic gRT->UpdateCapsule,
>>> i.e.
>>>   * PlatformFlashAccessLib implementation to write data to SPI flash
>>>   * SystemFirmwareDescriptor for FMP protocol
>>>   * SystemFirmwareUpdateConfig to specify binary description
>>>     within SystemFirmwareFile
>>>
>>> Contributed-under: TianoCore Contribution Agreement 1.1
>>> Signed-off-by: David Sniatkiwicz <davidsn@marvell.com>
>>> Signed-off-by: Marcin Wojtas <mw@semihalf.com>
>>
>> Please take the [very recent] changes made in
>> 550de36633fec97d4f7467c02a33b3217f440ae9 into account here.
>> Unfortunately, there is no loop in your code from which you can report
>> progress, but you should at least implement the new entry point.
>>
>
> Actually there is a loop and current % of progress printed when
> updating data in the SPI.
> It is implemented in the SPI flash protocol callback.
>
> https://github.com/tianocore/edk2-platforms/blob/master/Silicon/Marvell/Drivers/Spi/MvSpiFlashDxe/MvSpiFlashDxe.c#L382
>
> What would you recommend me to do in such case?
>

You could find a way to pass the callback argument into your SPI flash
protocol method, perhaps by adding a new member to it?


  reply	other threads:[~2018-06-01 16:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 14:32 [platforms PATCH 0/4] Armada capsule support Marcin Wojtas
2018-06-01 14:32 ` [platforms PATCH 1/4] Marvell/Armada70x0Db: Shift main FV from 0x0 address Marcin Wojtas
2018-06-01 15:26   ` Ard Biesheuvel
2018-06-01 14:32 ` [platforms PATCH 2/4] Marvell/Aramda7k8k: Enable PEI booting stage Marcin Wojtas
2018-06-01 15:30   ` Ard Biesheuvel
2018-06-01 16:43     ` Marcin Wojtas
2018-06-01 16:57       ` Ard Biesheuvel
2018-06-01 17:18         ` Marcin Wojtas
2018-06-01 14:32 ` [platforms PATCH 3/4] Marvell/Armada7k8k: Introduce capsule FW update implementation Marcin Wojtas
2018-06-01 15:32   ` Ard Biesheuvel
2018-06-01 16:02     ` Marcin Wojtas
2018-06-01 16:08       ` Ard Biesheuvel [this message]
2018-06-01 16:20         ` Marcin Wojtas
2018-06-01 14:32 ` [platforms PATCH 4/4] Marvell/Armada7k8k: Wire up capsule support Marcin Wojtas
2018-06-01 15:34 ` [platforms PATCH 0/4] Armada " Ard Biesheuvel

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-list 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=CAKv+Gu_HY0_hrGb3vu083kgoSkg0KVb48R-59eD61grkPxRSVw@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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