public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/2] Enable private ATF handoff structure
Date: Fri, 17 Jan 2020 07:38:24 +0100	[thread overview]
Message-ID: <75d8a431-fbc0-e623-1a24-eae71f25c38d@xilinx.com> (raw)
In-Reply-To: <c305da6b-63c5-cd80-4974-b019142f81e6@denx.de>

On 16. 01. 20 11:05, Marek Vasut wrote:
> On 1/16/20 10:42 AM, Michal Simek wrote:
>> On 16. 01. 20 10:10, Marek Vasut wrote:
>>> On 1/16/20 8:25 AM, Michal Simek wrote:
>>>> čt 19. 12. 2019 v 18:32 odesílatel Michal Simek
>>>> <michal.simek@xilinx.com> napsal:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Xilinx ZynqMP platform is using from the beggining specific structure which
>>>>> is passed from FSBL/SPL to ATF.
>>>>> Maybe in future both options can be supported by ATF and we can remove this
>>>>> private structure completely. But as of now bl31_params are completely
>>>>> ignored by ATF by RESET_TO_BL31=1 build flag.
>>>>>
>>>>> Thanks,
>>>>> Michal
>>>>>
>>>>>
>>>>> Michal Simek (2):
>>>>>   spl: atf: Enable option to rewrite bl2_plat_get_bl31_params()
>>>>>   arm: zynqmp: Wire SPL/ATF handoff structure properly
>>>>>
>>>>>  arch/arm/mach-zynqmp/handoff.c                | 17 +++++++++++-----
>>>>>  arch/arm/mach-zynqmp/include/mach/sys_proto.h |  2 --
>>>>>  arch/arm/mach-zynqmp/spl.c                    |  2 --
>>>>>  common/spl/spl_atf.c                          | 15 +-------------
>>>>>  include/spl.h                                 | 20 +++++++++++++++++++
>>>>>  5 files changed, 33 insertions(+), 23 deletions(-)
>>>>>
>>>>> --
>>>>> 2.24.0
>>>>>
>>>>
>>>> Applied.
>>>
>>> Can't you rather pass DT around ?
>>>
>>
>> Unfortunately not. The best will be just update ATF to support standard
>> method how to get information but that means that we break all backward
>> compatibility and nothing will work.
> 
> Isn't that what Xilinx does with their ABI between all BSP versions ?
> The only stable thing is the ABI version, which never changes :-)

This handoff structure is stable from beginning.


>> Xilinx handoff structure is around fro quite a long time and that's
>> something I need to unfortunately live with.
> 
> Maybe you can develop a better method (DT) in parallel and slowly switch
> over then ?

bl2_plat_get_bl31_params() is something what it is used by ATF for a
long time. Not sure if they are moving to DT way how to describe stuff.
But from my point of view having alternatives and a way for conversion
is right way to go.

Thanks,
Michal

      reply	other threads:[~2020-01-17  6:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 17:31 [PATCH 0/2] Enable private ATF handoff structure Michal Simek
2019-12-19 17:31 ` [PATCH 1/2] spl: atf: Enable option to rewrite bl2_plat_get_bl31_params() Michal Simek
2019-12-19 17:32 ` [PATCH 2/2] arm: zynqmp: Wire SPL/ATF handoff structure properly Michal Simek
2020-01-16  7:25 ` [PATCH 0/2] Enable private ATF handoff structure Michal Simek
2020-01-16  9:10   ` Marek Vasut
2020-01-16  9:42     ` Michal Simek
2020-01-16 10:05       ` Marek Vasut
2020-01-17  6:38         ` Michal Simek [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=75d8a431-fbc0-e623-1a24-eae71f25c38d@xilinx.com \
    --to=michal.simek@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox