• State Verified Answer
  • Replies 7 replies
  • Subscribers 70 subscribers
  • Views 1288 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 296076
Options

NCS-2.1.0 - CONFIG_ADP536X_BUS_NAME not longer valid?

Achim Kraus

Updating to NCS 2.1.0 the CONFIG_ADP536X_BUS_NAME is still defined but seems to be not longer valid.

The "adp536x.h" is now in the includes. Is there a supported way to use it?

In the boards definition for the Thingy:91 DEVICE_DT_GET(DT_NODELABEL(i2c2)) is used.

Is that the preferred way to address the  adp536x?

Parents
  • 0

    Hi, 

    Updating to NCS 2.1.0 the CONFIG_ADP536X_BUS_NAME is still defined but seems to be not longer valid.

    Please kindly elaborate more detail about "but seems to be not longer valid.". What is the log you get?

    Also, check the adp536x/Configuration. 

    Regards,
    Amanda

  • 0 in reply to Amanda Hsieh

    It's possible to compile

    i2c_dev = device_get_binding(CONFIG_ADP536X_BUS_NAME);

    but with NCS-2.1.0 i2c_dev is always NULL on a Thingy:91.

    Before I used it with NCS-2.0.1, and there the device pointer was returned.

    Anyway, you may just find out, if CONFIG_ADP536X_BUS_NAME is considered to be supported, but may be currently failing, maybe even only on my side, or if it's considered to be replaced by something else.

    > Also, check the adp536x/Configuration. 

    Of course! It's still in Kconfig there. Therefore it compiles.

    Did you check the current implementation? Could you point me to the source, where this actually used? Because my finding analyzing the code was, that this Kconfig CONFIG_ADP536X_BUS_NAME is not longer used and replaced by DEVICE_DT_GET(DT_NODELABEL(i2c2)).

    I wonder, if someone at nordic is aware and take care of such changes. It makes it very hard to update.

Reply
  • 0 in reply to Amanda Hsieh

    It's possible to compile

    i2c_dev = device_get_binding(CONFIG_ADP536X_BUS_NAME);

    but with NCS-2.1.0 i2c_dev is always NULL on a Thingy:91.

    Before I used it with NCS-2.0.1, and there the device pointer was returned.

    Anyway, you may just find out, if CONFIG_ADP536X_BUS_NAME is considered to be supported, but may be currently failing, maybe even only on my side, or if it's considered to be replaced by something else.

    > Also, check the adp536x/Configuration. 

    Of course! It's still in Kconfig there. Therefore it compiles.

    Did you check the current implementation? Could you point me to the source, where this actually used? Because my finding analyzing the code was, that this Kconfig CONFIG_ADP536X_BUS_NAME is not longer used and replaced by DEVICE_DT_GET(DT_NODELABEL(i2c2)).

    I wonder, if someone at nordic is aware and take care of such changes. It makes it very hard to update.

Children
Related