Date   

Dev Review Agenda - Feb 17, 2022

Maureen Helm
 

We haven’t had a dev review meeting in a few weeks due to lack of topics (because everyone’s busy fixing bugs and writing release notes, right?). This week the meeting is back on and will revisit Gerard’s Kconfig extension enhancement. Additional topics can be added to the agenda by adding the dev-review label to a PR or Issue.

 

Tom Burdick will run the meeting, as I’ll be out of the office tomorrow.

 

Dev Review Agenda for Feb 17, 2022:

 

All open PRs/Issues with the dev-review label:

https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aopen+label%3Adev-review+sort%3Aupdated-desc

 

Teams meeting:

https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZmMwZDAwMjQtNDQxOC00ZmI3LWEwNzYtNjc2OWI5ZmE0ZjIw%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d

 

Minutes:

https://docs.google.com/document/d/13YxmRsaZ7u0tarhQ31Ca_MeHcg9M9e_GyHJqSYfnSpQ

 


Event: Zephyr Project: APIs - 02/15/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr Project: APIs

When:
02/15/2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:

Meeting decisions/discussions in their respective PRs, tracked here: https://github.com/zephyrproject-rtos/zephyr/projects/18


________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Re: API meeting: agenda

Carles Cufi
 

Hi all,

Last minute change, the dai driver interface discussion is postponed until next week.

The items for today:

- Modularisation and Restructuring of Documentation
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/33725

- Road to pinctrl: tracking progress
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/39740

Thanks,

Carles

-----Original Message-----
From: Cufi, Carles
Sent: 15 February 2022 12:30
To: devel@...
Subject: API meeting: agenda

Hi all,

Today we'll mainly talk about a new audio DAI driver and the documentation
overhaul.

- [RFC] drivers: add new audio dai driver interface
- PR https://github.com/zephyrproject-rtos/zephyr/pull/42697

- Modularisation and Restructuring of Documentation
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/33725

- Road to pinctrl: tracking progress
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/39740


If you have additional items please let me know.

Teams link: https://teams.microsoft.com/l/meetup-
join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40threa
d.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-
b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-
5e334e88f6d8%22%7d

https://lists.zephyrproject.org/g/devel/calendar
https://github.com/zephyrproject-rtos/zephyr/projects/18

Minutes:
https://docs.google.com/document/d/1lv-
8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles


API meeting: agenda

Carles Cufi
 


Zephyr v3.0.0-rc3 tagged and released

Dan Kalowsky
 

The third and hopefully final release candidate for Zephyr 3.0.0 has been
tagged (v3.0.0-rc3).

The merge window for features and enhancements is now closed for this release,
and it will remain closed until 3.0.0 is released; the stabilization period is
now open. During the stabilization period only bug-fix, documentation, and
stabilization-related patches may be merged to main. Additional features or
enhancements for the 3.0.0 release require approval by the TSC.

The full release log can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/v3.0.0-rc3

Please note we currently have the following bug counts:
  High - 1     (goal 0)
  Medium - 23  (goal < 20)
  Low - 121    (goal < 50)

Any assistance in resolving the low priority bugs is appreciated.  The list can
be found at
https://github.com/zephyrproject-rtos/zephyr/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22priority%3A+low%22+sort%3Aupdated-desc+-milestone%3Av1.14.1+-milestone%3Av1.14.2+-milestone%3Av1.14.3



Re: Changes to Review Process in Github

David Leach
 

Just FYI, for reasons unknown, GitHub is attributing the dismissed approved reviews to my account, dleach02. I am not doing this and I have submitted a bug to the GitHub support to get them to look into this.

 

David Leach

 

From: devel@... <devel@...> On Behalf Of Nashif, Anas via lists.zephyrproject.org
Sent: Friday, February 11, 2022 8:42 AM
To: devel@...
Subject: [Zephyr-devel] Changes to Review Process in Github

 

Hit send too fast… fixed subject.

 

From: Nashif, Anas <anas.nashif@...>
Date: Friday, February 11, 2022 at 9:40 AM
To: devel@... <devel@...>
Subject: Changes to

Hi,

The TSC has discussed and voted in favor of changing the pull request and review process by enabling options provided by Github.

 

Specifically, we will be enabling an option that will cause new reviewable commits pushed to a pull-request branch to dismiss existing pull request review approvals and asking reviewers to revisit and re-review the new changes since they last reviewed the PR.

 

For reference, here is the settings screen with the option enabled:

 

Graphical user interface, text, application, email

Description automatically generated

 

This means that you will be asked to re-review changes when new content is being added to a pull-request. Please continue to provide reviews and keep watching for changes and enhancements added to pull-requests as they evolve.

 

This change will go into effect immediately.

 

Regards,

Anas


Re: Changes to Review Process in Github

Gydesen, Emil
 

Hi Anas,

A question on the feature:

If I rebase a PR without changing the content, does it trigger request for new reviews?

Also a clarification:
The text says "New reviewable commits pushed" - Does that also trigger if you amend an existing commit and push that, or is it only if you add new commits?

Best regards,
Emil Gydesen
Software Developer, Nordic Semiconductor | +4528265669 | emil.gydesen@...

From: devel@... <devel@...> on behalf of Nashif, Anas via lists.zephyrproject.org <anas.nashif=intel.com@...>
Sent: Friday, February 11, 2022 15:41
To: devel@... <devel@...>
Subject: [Zephyr-devel] Changes to Review Process in Github
 

Hit send too fast… fixed subject.

 

From: Nashif, Anas <anas.nashif@...>
Date: Friday, February 11, 2022 at 9:40 AM
To: devel@... <devel@...>
Subject: Changes to

Hi,

The TSC has discussed and voted in favor of changing the pull request and review process by enabling options provided by Github.

 

Specifically, we will be enabling an option that will cause new reviewable commits pushed to a pull-request branch to dismiss existing pull request review approvals and asking reviewers to revisit and re-review the new changes since they last reviewed the PR.

 

For reference, here is the settings screen with the option enabled:

 

Graphical user interface, text, application, email

Description automatically generated

 

This means that you will be asked to re-review changes when new content is being added to a pull-request. Please continue to provide reviews and keep watching for changes and enhancements added to pull-requests as they evolve.

 

This change will go into effect immediately.

 

Regards,

Anas


Changes to Review Process in Github

Nashif, Anas
 

Hit send too fast… fixed subject.

 

From: Nashif, Anas <anas.nashif@...>
Date: Friday, February 11, 2022 at 9:40 AM
To: devel@... <devel@...>
Subject: Changes to

Hi,

The TSC has discussed and voted in favor of changing the pull request and review process by enabling options provided by Github.

 

Specifically, we will be enabling an option that will cause new reviewable commits pushed to a pull-request branch to dismiss existing pull request review approvals and asking reviewers to revisit and re-review the new changes since they last reviewed the PR.

 

For reference, here is the settings screen with the option enabled:

 

Graphical user interface, text, application, email

Description automatically generated

 

This means that you will be asked to re-review changes when new content is being added to a pull-request. Please continue to provide reviews and keep watching for changes and enhancements added to pull-requests as they evolve.

 

This change will go into effect immediately.

 

Regards,

Anas


Changes to

Nashif, Anas
 

Hi,

The TSC has discussed and voted in favor of changing the pull request and review process by enabling options provided by Github.

 

Specifically, we will be enabling an option that will cause new reviewable commits pushed to a pull-request branch to dismiss existing pull request review approvals and asking reviewers to revisit and re-review the new changes since they last reviewed the PR.

 

For reference, here is the settings screen with the option enabled:

 

Graphical user interface, text, application, email

Description automatically generated

 

This means that you will be asked to re-review changes when new content is being added to a pull-request. Please continue to provide reviews and keep watching for changes and enhancements added to pull-requests as they evolve.

 

This change will go into effect immediately.

 

Regards,

Anas


Cancelled Event: Zephyr Memory Footprint - biweekly discussion - Monday, February 14, 2022 #cal-cancelled

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Cancelled: Zephyr Memory Footprint - biweekly discussion

This event has been cancelled.

When:
Monday, February 14, 2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: devel@...

Description:
Working doc: https://docs.google.com/document/d/1bnQLJKVhgI3zkk3MsSXun8onEsA8z1Rf5ohdbCHASmU/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,546018126# United States, Orlando
Phone Conference ID: 546 018 126#
 
 
________________________________________________________________________________


Event: Zephyr: Power Management Sync - 02/10/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr: Power Management Sync

When:
02/10/2022
9:00am to 10:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:


________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,677440320# United States, Orlando
Phone Conference ID: 677 440 320#
 
________________________________________________________________________________


Updated Event: Zephyr: Power Management Sync #cal-invite

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Zephyr: Power Management Sync

When:
Thursday, February 10, 2022
9:00am to 10:00am
(UTC-08:00) America/Los Angeles
Repeats: Weekly on Thursday

Where:
Microsoft Teams

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:


________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,677440320# United States, Orlando
Phone Conference ID: 677 440 320#
 
________________________________________________________________________________


Cancelled Event: Zephyr Project: Dev Meeting - Thursday, February 10, 2022 #cal-cancelled

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, February 10, 2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: devel@...

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Certifications and Software changes

FIXED-TERM Chintoju Manikanth (SX/EHT3) <fixed-term.Manikanth.Chintoju@...>
 

Hi,

   I have few questions:

1) How Zephyr stack got certified?

2) If I want to TI CC26x2R1 chip and use zephyr stack instead of TI BLE stack what are certifications to be done, Do I have to recertify the whole thing?

3) If I’m done with step 2 what are all the export control restrictions I have to face?

4) To remove the TI BLE stack and add Zephyr stack to my project the do I have to reconstruct all the heap manager? Or what are all the software changes do I have to include?

 

Mit freundlichen Grüßen / Best regards

Manikanth Chintoju


Responsible for PT and BEBS projects (SX/EHT3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
fixed-term.Manikanth.Chintoju@...


Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Prof. Dr. Stefan Asenkerschbaumer; Managing Directors: Dr. Stefan Hartung,
Dr. Christian Fischer, Filiz Albrecht, Dr. Markus Forschner, Dr. Markus Heyn, Rolf Najork


Zephyr v3.0.0-rc2 tagged

Dan Kalowsky
 

The second release candidate for Zephyr 3.0.0 has been tagged (v3.0.0-rc2).

The merge window for features and enhancements is now closed for this release,
and it will remain closed until 3.0.0 is released; the stabilization period is
now open. During the stabilization period only bug-fix, documentation, and
stabilization-related patches may be merged to main. Additional features or
enhancements for the 3.0.0 release require approval by the TSC.

The full release log can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/v3.0.0-rc2

Please note we currently have the following bug counts:
  High - 1     (goal 0)
  Medium - 23  (goal < 20)
  Low - 121    (goal < 50)

Any assistance in resolving the low priority bugs is appreciated.  The list can
be found at
https://github.com/zephyrproject-rtos/zephyr/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22priority%3A+low%22+sort%3Aupdated-desc+-milestone%3Av1.14.1+-milestone%3Av1.14.2+-milestone%3Av1.14.3


Event: Zephyr Project: APIs - 02/08/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr Project: APIs

When:
02/08/2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:

Meeting decisions/discussions in their respective PRs, tracked here: https://github.com/zephyrproject-rtos/zephyr/projects/18


________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


RFC: Replace TinyCBOR with ZCBOR within Zephyr

Ermel, Dominik
 

Hello,

 

I have logged proposal (https://github.com/zephyrproject-rtos/zephyr/issues/40591) for replacement of TinyCBOR in Zephyr source tree with zcbor.

Currently there is only one in-tree user of the TinyCBOR: mcumgr for the SMP implementation.

The mcuboot and tfm are already using zcbor for the SMP (tfm also uses QSBOR for some other things).

The TinyCBOR we have is not actually the Intel TinyCBOR implementation, but variant extracted from the internal code of Mynewt
(https://github.com/apache/mynewt-core/tree/master/encoding/tinycbor), which itself Is older Intel TinyCBOR that has been imported

into the core of Mynewt and become internal code.
Because mcumgr SMP has been written to relay on this significantly modified TinyCBOR implementation we could not directly move

to using Intel TinyCBOR; additionally TinyCBOR itself is quite flash heavy and zcbor is better in this matter.
zcbor has some API compatibility with TinyCBOR and transition should not be that painful: such transition has already been done in mcuboot as proof of concept.

zcbor also allows to describe CBOR data in CDDL language and generate CBOR stream parsing code automatically, to some extent.

Because zcbor is already used in mcuboot’s SMP implementation, and mcuboot is Zephyr application, this means that we are actually using two implementations

of CBOR library in Zephyr (three if we count QCBOR in tfm).

 

My proposal is to replace TinyCBOR within mcumgr SMP implementation with zcbor and remove TinyCBOR from modules – this move would

reduce number of CBOR implementations we use for SMP to one.

 

Best regards,

Dominik Ermel

Dominik ERMEL | Senior Software Engineer
Kraków, Poland
nordicsemi.com | devzone.nordicsemi.com

Nordic_logo_signature

 


Re: API meeting: agenda

Carles Cufi
 

Last minute addition:

- RFC: Replace TinyCBOR with zcbor within Zephyr
- https://github.com/zephyrproject-rtos/zephyr/issues/40591

-----Original Message-----
From: Cufi, Carles
Sent: 08 February 2022 12:44
To: devel@...
Cc: peress@...; piotr.mienkowski@...
Subject: RE: API meeting: agenda

- drivers: gpio: allow specifying GPIO drive strength flags in dts
- https://github.com/zephyrproject-rtos/zephyr/pull/39767

- Sensor API proposal
- https://docs.google.com/document/d/1UsElJJHRudeWXb-
tYwXA6qt9gF6PH8wwS7PjhqO1MLI/edit


-----Original Message-----
From: Cufi, Carles
Sent: 08 February 2022 12:34
To: devel@...
Subject: API meeting: agenda

Hi all,

Agenda for today:

- Road to pinctrl: tracking progress
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/39740

- SPI API: tracking progress
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/39992

- Go over items to follow-up on

If you have additional items please let me know.

Teams link: https://teams.microsoft.com/l/meetup-
join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40threa
d.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-
b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-
5e334e88f6d8%22%7d

https://lists.zephyrproject.org/g/devel/calendar
https://github.com/zephyrproject-rtos/zephyr/projects/18

Minutes:
https://docs.google.com/document/d/1lv-
8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles


Re: API meeting: agenda

Carles Cufi
 

- drivers: gpio: allow specifying GPIO drive strength flags in dts
- https://github.com/zephyrproject-rtos/zephyr/pull/39767

- Sensor API proposal
- https://docs.google.com/document/d/1UsElJJHRudeWXb-tYwXA6qt9gF6PH8wwS7PjhqO1MLI/edit

-----Original Message-----
From: Cufi, Carles
Sent: 08 February 2022 12:34
To: devel@...
Subject: API meeting: agenda

Hi all,

Agenda for today:

- Road to pinctrl: tracking progress
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/39740

- SPI API: tracking progress
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/39992

- Go over items to follow-up on

If you have additional items please let me know.

Teams link: https://teams.microsoft.com/l/meetup-
join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40threa
d.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-
b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-
5e334e88f6d8%22%7d

https://lists.zephyrproject.org/g/devel/calendar
https://github.com/zephyrproject-rtos/zephyr/projects/18

Minutes:
https://docs.google.com/document/d/1lv-
8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles


API meeting: agenda

Carles Cufi
 

421 - 440 of 8790