Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add support for the following devices and sensors that have kernel support #364

Open
Jibun-no-Kage opened this issue Aug 27, 2024 · 5 comments

Comments

@Jibun-no-Kage
Copy link

Please add support for the following devices and sensors that have kernel support:

AHTx0
BH1750
BME280, BME680, BMP280, BMP380, HDC100X,
JC42 complaint sensors, for example MCP980x, MPU6050, MPU9250
LM75
TMP102
DHT11/DHT21/DHT22
htu2x i.e. htu21
sht3x i.e. sht31
sht4x i.e. sht41
si7020

enc28j60
pcf8574,pcf8575

Reference... See i2c-sensor.dtbo content...
https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README

@RadxaYuntian
Copy link
Member

enc28j60 is already supported. For others PRs are welcome.

@Jibun-no-Kage
Copy link
Author

Jibun-no-Kage commented Aug 28, 2024

Cool. I should looked at the existing support! For RTCs, I know at least one is noted in the documentation. https://wiki.radxa.com/Zero/dev/RTC_module_ds3231. I need to check and see which ones I have. I believe I have DS3121s, and also DS1307. Does anything need to be changed/added to support DS1307?

@Jibun-no-Kage
Copy link
Author

Jibun-no-Kage commented Aug 28, 2024

Are you planning to create a master 'dtbo' file for sensors, similar to the Pi device implementation? Or individual dtbo files for each sensor? I find the i2c-sensor implementation easy to use, since you just pass in the i2c bus, sensor identifier, and i2c address to the dtbo. But if you choose to establish separate dtbo files, that works too. You will always need to allow for the bus, and i2c address even if separate files.

@RadxaYuntian
Copy link
Member

Raspberry Pi's overlay parameters is exclusive to themselves. Normal U-Boot does not support this, so everything has to be its own overlay. We do split overlays into reusable modules if possible, but that's at source level: https://github.com/radxa-pkg/radxa-overlays/blob/main/arch/arm64/boot/dts/rockchip/overlays/rk3399-spi1-waveshare35.dts#L1-L2

@Jibun-no-Kage
Copy link
Author

Ah... OK, was just an idea, that seemed reasonable to suggest. It is what it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants