'label' is marked as deprecated in 'properties:' nordic,nrf-saadc.yaml

[nRF5xFanboy]

Hi Nordic,

I upgrade from ncs v2.1.2 to v2.2.0 and the following warnings appears:

-- Found devicetree overlay: c:/cm/projects/zorba/library_sdk/boards/nrf52840_orbitz.overlay
'label' is marked as deprecated in 'properties:' in C:/cm/ncs/v2.2.0/zephyr/dts/bindings\adc\nordic,nrf-saadc.yaml for node /soc/adc@40007000.
node '/soc/i2c@40003000/mp2723@4B' compatible 'mp,mp2723' has unknown vendor prefix 'mp'
-- Generated zephyr.dts: C:/cm/projects/zorba/application/build_betronic/zephyr/zephyr.dts

I am hoping these deprecated warnings will soon be resolved in next nCS upgrade.

best regards,
   nRF5xFanBoy

[dejans]

Hi,

The note in important properties specifies that using label property is discouraged and that label property should not be used for new bindings or device implementations. Documentation also specifies that it is deprecated for nordic, nrf-saadc.

Best regards,
Dejan

[nRF5xFanboy]

Hello dejans,

Thanks for the not-helping reply.
Of course I do know what deprecated means.

Is there some form of migration guide available for migrate ncs v2.1.x to v2.2.x regarding the new deprecated components?

remark: It was not dangerous in v2.1.x  because it was not marked 'deprecated' at that time.

I strongly advise to present a planning of (new) deprecated modules in future nCS upgrades
so developers can plan & act upon it (on time) and not be surprised by them.
Please do improve on this.

Question is more what is the proper alternative way of using the saADC.

regards,
   nRF5xFanBoy   

[dejans]

Hi,

I am not aware of the existence of such a migration guide. However, it is possible for you to find information that you need in the documentation. For example, compare basic properties of nrf-saadc and important properties in NCS v2.2.0 vs nrf-saadc basic properties and important properties in NCS v2.1.0.  

nRF5xFanboy said:

I strongly advise to present a planning of (new) deprecated modules in future nCS upgrades
so developers can plan & act upon it (on time) and not be surprised by them.
Please do improve on this.

Thank you for your suggestion. We will have this in mind and try to improve going forward by making our customers aware of the maintenance period for device driver APIs.

Best regards,
Dejan