RIOT-OS / RIOT

RIOT - The friendly OS for IoT
https://riot-os.org
GNU Lesser General Public License v2.1
4.95k stars 1.99k forks source link

Support for ST X-NUCLEO IKS01A2 #7282

Closed smlng closed 5 years ago

smlng commented 7 years ago

This issue documents the state of driver support for sensors on the ST X-NUCLEO Shield IKS01A2, plus to coordinate the efforts and synchronize work on distinct drivers. It is a follow up to #6629 and has similar intention as #7152.

Device/Sensor Type Driver state
Humidity and Temperature HTS221 ✅ see #7280
Accelerometer and Gyroscope LSM6DSL ✅ (#6835)
Accelerometer and Magnetometer LSM303AGR ❓ maybe adapt LSM303DLHC
Pressure and Temperature LPS22HB ❓ maybe adapt LPS331AP
miri64 commented 7 years ago

If they are one shield, unifying them under one driver (in addition to the individual device drivers) like we did with the io1_xplained extension board for samr21-xpro might make sense.

smlng commented 7 years ago

mhm, I rather thought about introducing a pseudomodule iks01a2 which has the respective drivers as a dependency.

miri64 commented 7 years ago

Also thinkable. But don't you have to configure the periphs used by the shield somewhere?

smlng commented 7 years ago

could be done with a distinct <DRIVER>_PARAMS_IKS01A2 in drivers/<driver>/include/<driver>_params.h and then using #ifdef MODULE_IKS01A2 I guess? But again: first things first, i.e. getting all drivers ready and afterwards we care about the shield config.

miri64 commented 7 years ago

But again: first things first, i.e. getting all drivers ready and afterwards we care about the shield config.

Yes, just wanted to bring this up.

smlng commented 7 years ago

duly noted, thanks for the pointer to io1_xplained - wasn't aware of that.

aabadie commented 7 years ago

I rather thought about introducing a pseudomodule iks01a2

io1-xplained tries to address something similar for a temperature driver and gpio. I would do the same for iks01a2 and iks01a1

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

smlng commented 5 years ago

closing this, its just a tracking issue.