All,
We will have the Devicetree call today.
As normal it is at 15 UTC / 10 AM US Eastern.
(One hour from when I send this.)
Today we have several topics:
* a specific reserved memory use for OP-TEE
* a general discussion of memory and the spec.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Hi all,
I’m cancelling this weeks EBBR biweekly as I wasn’t able to send out a reminder and agenda last week. Next meeting is 14th March 2022.
As always, email me if you have a topic for the agenda.
g.
—-
Grant Likely
Senior Technical Director, Arm
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Oliver,
On 2/22/22 7:36 AM, Olivier Masse wrote:
> Hi All,
>
> Could we postpone to the next call ?
>
Yes we can discuss on March 7.
However I think you need to define what you want to discuss.
First of, there is nothing in your suggested DTS that tells Linux (or
other OS) that it should not map the memory area. It looks to me as
you should include the "no-map" property in your node.
How will the Linux video/graphics drivers refer to this node? I presume
by phandle, right?
Are you setting any suggested naming convention for the node name (after
you fix the node name to include @address)?
You are defining a compatible string in the node. The current
suggestion is not in the spec. It could be "optee,sdp" if you get optee
stakeholders to agree. What should be the definition of "optee,sdp".
I presume it means secure data path but that could mean a ton of things.
Will sdp always mean DRM protected media playback or could it include more?
Thanks,
Bill
> BR / Olivier
>
> On mar., 2022-02-15 at 13:46 -0600, Rob Herring wrote:
>> Caution: EXT Email
>>
>> On Fri, Feb 11, 2022 at 8:21 AM Bill Mills <bill.mills(a)linaro.org>
>> wrote:
>>>
>>> Rob,
>>>
>>> Can you confirm for the DT call on Feb 21?
>>
>> I'm on holiday on the 21st.
>>
>>>
>>> Oliver,
>>>
>>> On 2/11/22 4:54 AM, Olivier Masse wrote:
>>>> Hi Bill,
>>>>
>>>> NXP had a discussion with Linaro about this optee os issue:
>>>>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
>>>>
>>>> Which is implemented by this first draft here:
>>>>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
>>>>
>>>> Could we be part of the next Device Tree call to discuss about
>>>> adding
>>>> a reserved memory in optee os embedded DT ?
>>>>
>>>
>>> Thanks for bringing it up.
>>> I have skimmed the PR threads and the discussion seems to be:
>>> 1) OP-TEE internal issues
>>> 2) DT standards questions and issues
>>>
>>> For the DT call we need to focus on #2 above.
>>> We will definitely need Rob for this discussion so we need to do it
>>> when
>>> he can join. (If we don't resolve the question in this email
>>> thread
>>> before then.)
>>>
>>> Context for all:
>>>
>>> SDP here is related to DRM protected playback of media streams.
>>>
>>> Jens comment in PR:
>>> > So far we have managed to avoid defining our own bindings in OP-
>>> TEE,
>>> > instead we've been able to reuse already established bindings.
>>> With
>>> > this you're proposing something new. I'm not sure of the best
>>> way of
>>> > doing such a thing. Are we sure there is nothing to reuse?
>>> > If not: How should it be reviewed? Who should review it?
>>>
>>> DTS in PR:
>>> /*
>>> * Copyright (c) 2021, NXP. All rights reserved.
>>> *
>>> * SPDX-License-Identifier: BSD-3-Clause
>>> */
>>>
>>> /dts-v1/;
>>>
>>> / {
>>> #address-cells = <1>;
>>> #size-cells = <0>;
>>>
>>> reserved-memory {
>>> #address-cells = <1>;
>>> #size-cells = <1>;
>>>
>>> sdp_mem {
>>> compatible = "optee-sdp";
>>> reg = <0x3E800000 0x00400000>;
>>> };
>>> };
>>> };
>>>
>>> However it was modified after that.
>>>
>>> Oliver: please reply to this thread (on list please) with the final
>>> DTS
>>> you are proposing. fix DT conventions and what are you doing with
>>> the
>>> no-map property if anything.
>>>
>>> Is the memory above meant to be visible to NS world AND S
>>> world? Or is
>>> just for secure world.
>>>
>>> Thanks,
>>> Bill
>>>
>>>> Best regards,
>>>> Olivier Masse
>>>
>>> --
>>> Bill Mills
>>> Principal Technical Consultant, Linaro
>>> +1-240-643-0836
>>> TZ: US Eastern
>>> Work Schedule: Tues/Wed/Thur
>>> _______________________________________________
>>> boot-architecture mailing list --
>>> boot-architecture(a)lists.linaro.org
>>> To unsubscribe send an email to
>>> boot-architecture-leave(a)lists.linaro.org
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
All,
There will be no DT meeting tomorrow Monday Feb 21.
It is a holiday in the US and others have declined as well.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Rob,
Can you confirm for the DT call on Feb 21?
Oliver,
On 2/11/22 4:54 AM, Olivier Masse wrote:
> Hi Bill,
>
> NXP had a discussion with Linaro about this optee os issue:
> https://github.com/OP-TEE/optee_os/issues/5133
>
> Which is implemented by this first draft here:
> https://github.com/OP-TEE/optee_os/pull/5149
>
> Could we be part of the next Device Tree call to discuss about adding
> a reserved memory in optee os embedded DT ?
>
Thanks for bringing it up.
I have skimmed the PR threads and the discussion seems to be:
1) OP-TEE internal issues
2) DT standards questions and issues
For the DT call we need to focus on #2 above.
We will definitely need Rob for this discussion so we need to do it when
he can join. (If we don't resolve the question in this email thread
before then.)
Context for all:
SDP here is related to DRM protected playback of media streams.
Jens comment in PR:
> So far we have managed to avoid defining our own bindings in OP-TEE,
> instead we've been able to reuse already established bindings. With
> this you're proposing something new. I'm not sure of the best way of
> doing such a thing. Are we sure there is nothing to reuse?
> If not: How should it be reviewed? Who should review it?
DTS in PR:
/*
* Copyright (c) 2021, NXP. All rights reserved.
*
* SPDX-License-Identifier: BSD-3-Clause
*/
/dts-v1/;
/ {
#address-cells = <1>;
#size-cells = <0>;
reserved-memory {
#address-cells = <1>;
#size-cells = <1>;
sdp_mem {
compatible = "optee-sdp";
reg = <0x3E800000 0x00400000>;
};
};
};
However it was modified after that.
Oliver: please reply to this thread (on list please) with the final DTS
you are proposing. fix DT conventions and what are you doing with the
no-map property if anything.
Is the memory above meant to be visible to NS world AND S world? Or is
just for secure world.
Thanks,
Bill
> Best regards,
> Olivier Masse
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
All,
I have no agenda for tomorrow's DT call. Does anyone want to bring up
something?
If I have not heard anything by noon UTC tomorrow (3 hours before the
meeting) I will cancel the call.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Hi everyone,
Just a reminder that the EBBR biweekly is on today at 15:00 GMT. I've
got the following agenda items:
- Disable U-Boot console for secure boot (Ilias)
- SystemReady IR 2.0 draft requirements
- Any other business
Here are the conference details:
Join Zoom Meeting
https://armltd.zoom.us/j/92081365511?pwd=SFZpRitXUEp3Zy9GM0h3UUZ1b1pnUT09
Meeting ID: 920 8136 5511 Password: 490324
One tap mobile +14086380968,,92081365511#,,#,490324# US (San Jose)
+16465189805,,92081365511#,,#,490324# US (New York)
Dial by your location
+1 408 638 0968 US (San Jose) +1 646 518 9805 US (New York) +1 346
248 7799 US (Houston)
Hi all,
Just a quick note that the EBBR meeting scheduled for today is indeed
on. Ilias and Jose will be presenting the work done on A/B updates which
should be interesting to the EBBR audience.
Here's the agenda and dial in details:
Agenda:
- A/B Update Presentation (Ilias & Jose)
- Requirement to disable or remove command line when secure (Ilias)
Zoom details:
17th Jan 2022, 15:00 GMT
Join Zoom Meeting
https://armltd.zoom.us/j/92081365511?pwd=SFZpRitXUEp3Zy9GM0h3UUZ1b1pnUT09
Meeting ID: 920 8136 5511 Password: 490324
One tap mobile +14086380968,,92081365511#,,#,490324# US (San Jose)
+16465189805,,92081365511#,,#,490324# US (New York)
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Just a reminder, the EBBR biweekly is on today (about 15 minutes from
now). I try to send these reminders out the week before, but it fell off
my radar last week. Here is what I have on the agenda for today:
Agenda
* Requirements on A/B update (Ilias)
* Can the OS be responsible for firmware update? (Ilias) - e.g., via
fwupd or similar to stage UpdateCapsule()
* Requirement to disable or remove command line when secure (Ilias)
---
Join Zoom Meeting
https://armltd.zoom.us/j/92081365511?pwd=SFZpRitXUEp3Zy9GM0h3UUZ1b1pnUT09
Meeting ID: 920 8136 5511
Password: 490324
One tap mobile
+14086380968,,92081365511#,,#,490324# US (San Jose)
+16465189805,,92081365511#,,#,490324# US (New York)
Dial by your location
+1 408 638 0968 US (San Jose)
+1 646 518 9805 US (New York)
+1 346 248 7799 US (Houston)
Meeting ID: 920 8136 5511
Password: 490324
Find your local number: https://armltd.zoom.us/u/adYiWaDyys
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
