Skip to content

Tag: device-tree

How to include device tree overlay into Raspberry Pi CM4

I would like to include UART3 and UART5 overlay to enable them, using Yocto. They are already delivered with the whole package ( I added to my main image recipe lines: I have also added .bbappend to enable them in /boot/config.txt (file /meta-mylayer/recipes-bsp/bootfiles/rpi-config_%.bbappend): And I receive an error: I suppose that those overlays are not compiled, how can I include

DFU not transferring data in barebox

Am working on a custom board – has no removable storage (sd) and only one UART. I need to transfer files on the the QSPI storage using barebox bootloader. I am trying to use DFU to transfer various files to write to QSPI Device tree has the follow among other things On the board, the OTG mode has been set

Purpose and usage of GPIO-Hog declaration

Questions What is the purpose and use-case of the gpio-hog declaration? Can a ‘hogged’ gpio pin be interfaced with from Userspace? If a ‘hogged’ gpio pin cannot be interfaced with from Userspace, then is there any mechanism to configure GPIO pins in the dts file for Userspace interaction? Background I am trying to configure many (10+) GPIOs to speak with

Example device-tree-aware i2c gpio driver for Linux?

Is there a good example device-tree-aware i2c gpio driver for Linux? I’ve been looking at gpio-pcf857x but it has a header file containing struct pcf857x_platform_data which is used in board files. I am looking for a similar example, but where the i2c id is defined-in/retrieved-from the device tree. Answer Take a look at max732x.c driver (code). As for I2C ID

Linux device tree (AD5628)

I am trying to use AD5628 Digital to analog converter on my raspberry Pi 3 board . I have enabled the driver for that ( in the Yocto kernel . But when i opened the path /sys/bus/iio/devices/ Mentioned in ( i am not getting any device0. I got to know that it is a Device tree issue , So i

Difference between spi_driver.id_table and spi_driver.driver.of_match_table

I’m currently trying to understand how linux drivers work. As far as I know, A driver’s probe/init function is called when the kernel parses the corresponding .compatible string in the device tree. However, in the arizona-spi driver it looks like there are multiple compatible strings referenced in different members: This is an excerpt from here. So what is the difference