From: Varun Wadekar <vwadekar@nvidia.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Alexander Graf <agraf@suse.de>,
Jonathan Hunter <jonathanh@nvidia.com>,
U-Boot <u-boot@lists.denx.de>, Tom Warren <TWarren@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Mian Yousaf Kaukab <yousaf.kaukab@suse.com>
Subject: Re: How to test new bootloaders on Jetson TX1? - ATF
Date: Sat, 17 Feb 2018 07:04:35 +0000 [thread overview]
Message-ID: <e7aae43b-b1c8-4c87-8dcb-a29f1d9a6232@nvidia.com> (raw)
In-Reply-To: <5b1b68d4-e2c2-80e6-8a42-594053d1860c@suse.de>
Sounds good. I reviewed the ATF change upstream. Looks good.
________________________________
From: Andreas Färber <afaerber@suse.de>
Sent: Friday, February 16, 2018 7:34 PM
To: Varun Wadekar
Cc: Tom Warren; Jonathan Hunter; linux-tegra@vger.kernel.org; U-Boot; Alexander Graf; Mian Yousaf Kaukab
Subject: Re: How to test new bootloaders on Jetson TX1? - ATF
Am 16.02.2018 um 07:18 schrieb Varun Wadekar:
> Yes. That's a custom SMC we have for some non-L4T uses. It has not been
> upstreamed yet.
>
> You can add dummy handling in tegra_sip_calls.c to move forward.
Thanks, on my 1.4 based branch I succeeded to boot into Nvidia U-Boot
with the following change:
--- a/plat/nvidia/tegra/common/tegra_sip_calls.c
+++ b/plat/nvidia/tegra/common/tegra_sip_calls.c
@@ -162,6 +162,11 @@ uint64_t tegra_sip_handler(uint32_t smc_fid,
*/
break;
+ case 0x82000015:
+ INFO("%s: SMC 0x%x\n", __func__, smc_fid);
+ SMC_RET1(handle, 0);
+ break;
+
default:
ERROR("%s: unhandled SMC (0x%x)\n", __func__, smc_fid);
break;
The INFO output shows up exactly once.
On master branch I've further needed to fix a regression:
https://github.com/ARM-software/arm-trusted-firmware/pull/1271
Regards,
Andreas
>
> ------------------------------------------------------------------------
> *From:* Andreas Färber <afaerber@suse.de>
> *Sent:* Thursday, February 15, 2018 7:04 PM
> *To:* Varun Wadekar
> *Cc:* Tom Warren; Jonathan Hunter; linux-tegra@vger.kernel.org; U-Boot;
> Alexander Graf; Mian Yousaf Kaukab
> *Subject:* Re: How to test new bootloaders on Jetson TX1? - ATF
>
> Hi Varun,
>
> Am 15.02.2018 um 17:57 schrieb Varun Wadekar:
>> Andreas, can you try the TOS packaging script available in our public repo?
>>
>> http://nv-tegra.nvidia.com/gitweb/?p=3rdparty/ote_partner/tlk.git;a=blob;f=tools/gen_tos_part_img.py;h=47828f7028e56a6cffb9b773502b13dc431a015e;hb=HEAD
>
> Great, that script does work. It is lacking usage output, but looking at
> the code, its arguments were self-documenting.
>
>> Please let me know if this does not work for you.
>>
>> For the upstream ATF code, our downstream has not caught up with upstream yet, so I am not sure if upstream would directly work for TX1. But its definitely worth a try.
>
> I tried R28.1 flash.sh -k TOS with my ATF v1.4 with Spectre backports,
> without SPD. BL31 appears to initialize okay, but later something runs
> into an unhandled SMC 0x82000015 - things then go south and it doesn't
> reach the Nvidia U-Boot. Serial log attached.
>
> According to
> https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/arm-sip-service.rst
> that SMC function ID falls into the SiP range, so indeed something
> Nvidia-specific missing in v1.4?
>
> Regards,
> Andreas
>
> https://build.opensuse.org/package/show/hardware:boot/arm-trusted-firmware-tegra210
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
next prev parent reply other threads:[~2018-02-17 7:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 1:51 How to test new bootloaders on Jetson TX1? Andreas Färber
[not found] ` <5ff3ffde-653c-ea50-490c-efcc6dccecc2-l3A5Bk7waGM@public.gmane.org>
2018-02-15 7:56 ` Mikko Perttunen
[not found] ` <2089c895-7992-9741-a471-fae5b410d4b7-/1wQRMveznE@public.gmane.org>
2018-02-15 13:25 ` Andreas Färber
[not found] ` <8320e1df-774c-65c1-28ae-96e1b90ad178-l3A5Bk7waGM@public.gmane.org>
2018-02-15 14:22 ` Mikko Perttunen
2018-02-15 9:22 ` Jon Hunter
[not found] ` <0247bb39-1f53-5c45-4d37-247813b53b96-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-15 12:32 ` Andreas Färber
[not found] ` <8d80b0d3-eaed-b1ab-02c9-86f81ac4b7fa-l3A5Bk7waGM@public.gmane.org>
2018-02-15 14:01 ` Jon Hunter
[not found] ` <33de1065-1372-282c-9646-30a63729e08e-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-15 15:12 ` Andreas Färber
2018-02-15 15:38 ` Jon Hunter
2018-02-15 15:44 ` Tom Warren
[not found] ` <d6a44448867a47028685fb0af0005d59-wO81nVYWzR7wKU+G0hyRhFaTQe2KTcn/@public.gmane.org>
2018-02-15 16:57 ` Varun Wadekar
2018-02-16 3:04 ` How to test new bootloaders on Jetson TX1? - ATF Andreas Färber
2018-02-16 6:18 ` Varun Wadekar
[not found] ` <e9728e54-8c58-4586-8863-0f26eb156deb-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-17 5:34 ` Andreas Färber
2018-02-17 7:04 ` Varun Wadekar [this message]
2018-02-15 23:38 ` How to test new bootloaders on Jetson TX1? Stephen Warren
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=e7aae43b-b1c8-4c87-8dcb-a29f1d9a6232@nvidia.com \
--to=vwadekar@nvidia.com \
--cc=TWarren@nvidia.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=u-boot@lists.denx.de \
--cc=yousaf.kaukab@suse.com \
/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