Skip to content

Conversation

@avisconti
Copy link
Contributor

update to the new GPIO API

The LIS3MDL sensor is quite old and the driver requires to be restructured. This commit is only addressing the new GPIO API in order to compile properly.

Copy link
Member

@MaureenHelm MaureenHelm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to add gpio flags to the the board and shield dts files that instantiate this sensor.

@avisconti avisconti force-pushed the lis3mdl-new-gpio-api branch from e1b474b to da1068f Compare January 16, 2020 13:50
@avisconti avisconti requested a review from erwango as a code owner January 16, 2020 13:50
@avisconti
Copy link
Contributor Author

Need to add gpio flags to the the board and shield dts files that instantiate this sensor.

ok, done!
There is actually only one place declaring the interrupt as well; x_nucleo_iks01a1 shield

@carlescufi carlescufi changed the title driver/sensor: lis3mdl: update to use new GPIO API [topic-gpio] driver/sensor: lis3mdl: update to use new GPIO API Jan 16, 2020
Get rid of all the deprecated functions and definitions
replacing them with the new ones.

Signed-off-by: Armando Visconti <[email protected]>
@avisconti avisconti force-pushed the lis3mdl-new-gpio-api branch from da1068f to 0b0074f Compare January 17, 2020 10:17
@avisconti avisconti requested a review from nashif as a code owner January 17, 2020 10:17
@zephyrbot zephyrbot added the area: Tests Issues related to a particular existing or missing test label Jan 17, 2020
@galak galak merged commit cc4d171 into zephyrproject-rtos:topic-gpio Jan 17, 2020
@avisconti avisconti deleted the lis3mdl-new-gpio-api branch January 17, 2020 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Boards area: Devicetree area: GPIO area: Sensors Sensors area: Tests Issues related to a particular existing or missing test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants