Hi Torsten,

Could you update the calendar? If not already done.

I believe that many will miss out, if the calendar does not reflect the rescheduling of the meeting.

Regards,

  Danny

Are there any plans for Zephyr 2.3 to be BT SIG certified for host, controller, or profile (mesh) subsystems?

Here’s the agenda topics for this week:

* struct device - plans for 2.4:

https://github.com/zephyrproject-rtos/zephyr/issues/22941
https://github.com/zephyrproject-rtos/zephyr/issues/26072
https://github.com/zephyrproject-rtos/zephyr/issues/26073

* Any PR/issues w/dev-review tag

* Any topics anyone else has.

- k

Dear Zephyr developers,
According to the Zephyr Project Roles and Contribution Guidelines
documentation
(https://docs.zephyrproject.org/latest/contribute/project_roles.html#m
erge-criteria), pull requests against the Project’s main branch may be
merged with 2 approvals. Until now, we have been applying this policy
in GitHub, exclusively during Zephyr release stabilization periods
(applying 1-approval policy, otherwise). I would like to notify
everyone that as of now we will permanently enforce the 2-approval
policy.
Consequently, from now on, we will be needing extra assistance in PR
reviews to maintain a high-enough rate of getting PRs approved and
merged to Zephyr master branch.

A big thanks-in-advance to all for your extra efforts in PR reviewing
😊 Best Regards,
Ioannis glaropoulos | R&D
P +47 21 08 88 37 | Oslo, Norway
nordicsemi.com<http://www.nordicsemi.com/> |
devzone.nordicsemi.com<https://devzone.nordicsemi.com/>

[Nordic_logo_signature]<http://www.nordicsemi.com/>

Hi Carles,

thanks, I managed like this:

/ {
aliases {
eeprom_0 = &eeprom0;
};
};

but eeprom_0 is not a valid alias:

dtlib.DTError: /aliases: alias property name 'eeprom_0' should include
only characters from [0-9a-z-]

may I open an issue?

Stefano

Il giorno mar 9 giu 2020 alle ore 10:27 Cufi, Carles
<Carles.Cufi@nordicsemi.no> ha scritto:

For properties there is /delete-property/ to delete one and then be able to override it.
In the case of an alias I am not sure, have you tried to override it directly?

Carles

On 08/06/2020, 19:31, "devel@lists.zephyrproject.org on behalf of Stefano Manni via lists.zephyrproject.org" <devel@lists.zephyrproject.org on behalf of stefano.manni=gmail.com@lists.zephyrproject.org> wrote:

Hi there,

I'm trying to compile test/drivers/eeprom for my board. I see that the
code requires the alias 'eeprom_0' defined, but my board does not have
it natively.

I managed to compile changing in the test app some lines like below:

- eeprom = device_get_binding(DT_LABEL(DT_ALIAS(eeprom_0)));
+ eeprom = device_get_binding(DT_LABEL(DT_NODELABEL(eeprom0)));

where eeprom0 is defined in an overlay for my boards.

But I'd prefer to use the alias and not change the app.
What is the right way to override an alias in an overlay file? Sorry
if my question is already addressed somewhere in documentation.

Another consideration: is 'eeprom_0' a valid name? Alias properties
should include only characters from [0-9a-z-]. May we need to fix it?

Thanks,
Stefano

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On
Behalf Of Carles Cufi via lists.zephyrproject.org
Sent: 09 June 2020 10:35
To: users@lists.zephyrproject.org; devel@lists.zephyrproject.org
Cc: Snekvik, Trond Einar <Trond.Einar.Snekvik@nordicsemi.no>
Subject: [Zephyr-devel] API meeting: agenda

Hi all,

*************************************************
We will be using Teams instead of Zoom:
https://teams.microsoft.com/l/meetup-
join/19%3ameeting_YzYzZTAzNGItOWFiMS00MDBkLTkyYmMtNzljZjkwNDVlMThm%40thr
ead.v2/0?context=%7b%22Tid%22%3a%22686ea1d3-bc2b-4c6f-a92c-
d99c5c301635%22%2c%22Oid%22%3a%2262b63b80-05d3-4465-b5a0-
f04e4e156f10%22%7d
*************************************************

Today's topics:

- PWM: Clarify expected behavior
- PR https://github.com/zephyrproject-rtos/zephyr/pull/25587

- API Change: Call UART_RX_RDY event after rx_disable()
- Issue https://github.com/zephyrproject-rtos/zephyr/issues/25317
- PR https://github.com/zephyrproject-rtos/zephyr/pull/25967

- API Change: Mesh: Add name parameter
- Issue https://github.com/zephyrproject-rtos/zephyr/issues/26037

Additional topics to review and close:

- QSPI flash drivers:
- Should we revisit the common QSPI API?
https://github.com/zephyrproject-rtos/zephyr/pull/20069
- Should it be part of the current SPI API?
https://github.com/zephyrproject-rtos/zephyr/issues/17902
- If not, should we try to unify the common functionality in the
multiple QSPI flash drivers?
- https://github.com/zephyrproject-rtos/zephyr/pull/25806
- https://github.com/zephyrproject-rtos/zephyr/pull/25669

- SPI JEDEC runtime support
- PR https://github.com/zephyrproject-rtos/zephyr/pull/23658

- RTC API follow-up (if the relevant people are present and there is
material for discussion)
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/23526

Pending additional investigation:
- Documenting API behavior in Doxygen:
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/18970
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/21061

Additional items in the "Triage" column in the GitHub project may be
discussed if time permits.
If you want an item included in the meeting, please add it to the GitHub
project.

https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-
Working-Group-Meetings#zephyr-api-discussion
https://github.com/zephyrproject-rtos/zephyr/projects/18
https://docs.google.com/document/d/1lv-
8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles