NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/3282 : libc: Add assert.h to minimal libc - https://gerrit.zephyrproject.org/r/3286 : net: tinydtls: Use assert.h from minimal libc

Hi Baohong, Can you give a little more detail about use-cases? Seems like the information being queried is not unique per-device data but identification values for the HW. In Zephyr pretty much

The device PM states look ok to me. They are architecture independent and the drivers can map them to device specific operations. I think this RFC should be part of other RFCs that define the

That does not explain why 2 functions are better than 1. In the scenario you mention, all that is needed is a way to notify the device of a power state transition.

Hi, There can be a need to provide a generic interface API for getting the SOC ID, version, and other identifying data. These data can be useful for an application to use to generate unique

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 5 [ZEP-512] Add suspend/resume support for some core devices to enable Deep Sleep support in PMA

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/3161 : ext qmsi: Enable linking to qm_init.o - https://gerrit.zephyrproject.org/r/3271 : build: Fix usage of the ISSM toolchain -

Hi Yael, <yael.avramovich(a)intel.com> wrote: Just have a command to select the module you want to operate, e.g. select-module bluetooth, that way one don't have to keep entering the entity name

Hi Ramesh' Please see my comments below. Regards, Hezi

Hi, Please find comments below. Regards, Alex.

That made me think why we originally came up with 2 functions when one was enough. Probably we thought the same way - to keep symmetry. Problem is that we will keep getting more needs and we will

Hi Dimitriy, The get_state is there only for symmetry and good practice. As mentioned below the power manager service will probably not use it as it is not efficient to do get_state to all devices to

Hi Hezi, I think RFC needs to be extended with the description of the idea of controlling power state of each device (if I got you correctly). Without it the need of int (*get_state)(struct device

NEW JIRA items within last 24 hours: 3 [ZEP-546] UART interrupts not triggered on ARC https://jira.zephyrproject.org/browse/ZEP-546 [ZEP-545] Wrong default value of CONFIG_ADC_QMSI_SAMPLE_WIDTH

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/3151 : net: yaip: Set the l2 src/dst addresses in nbuf - https://gerrit.zephyrproject.org/r/3152 : net: yaip: Set the ll src and dst

Hi Ramesh, Please see my comments below/ Thanks for the comments, Hezi

Hi Yael, Clear RFC. I have tiny inputs below As you know the size of fw_commands (which can be declared as const btw) at built time, you will be able to loop directly on that count, thus you

Zephyr Shell Enhancement ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ======== Overview ======== Current shell implementation: * Current Shell implementation is based on UART. It uses one UART for

Hi Alex, Please see my comments below. Thank you for the inputs, Hezi Sent: Tuesday, July 12, 2016 17:31 To: Rahamim, Hezi <hezi.rahamim(a)intel.com>; devel(a)lists.zephyrproject.org Cc: Kidron,

Currently suspend and resume are not actually states but a notification of the state transition. There is a second argument to those functions that specify the current policy for which the