device-tree

UART4 with Pandaboard and Arch Linux

由 孤者浪人 提交于 2019-12-12 03:59:35
问题 I'm trying to use UART4 in my Pandaboard with Arch Linux. I'm using the latest kernel (4.2.0-2-ARCH) so I can't configure MUX in the old way using omap_mux , I have to do it using Device Tree Overlay. This is new to me so it's hard, I've never done this before. I have been reading some post about how to use them in Beaglebone boards in sites like this and this. So I downloaded the OMAP4 Technical Reference Manual (download here). Table 18-504 shows the UART4 control register. Based on that

Getting information from the device tree and requesting irq

由 烈酒焚心 提交于 2019-12-11 19:29:12
问题 Context In the device tree I am using, in one of its node, the filed interrupts is: interrupts = <0x0 0x1d 0x4>; (from a device tree of a Pynq board, equipaged with a ZYnq device with a dual-core ARM A9 ) Now, in the device tree .probe function, I use the Linux kernel API: irq_line = platform_get_irq(pdev, 0); in order to get the irq to use for the function request_irq (described in ldd3 chapter 10). Ones the irq_line = platform_get_irq(pdev, 0); is executed, I get the value 0x2e that DOESN'T

Device Tree for changing UART Mode and enabling GPIOs for iMX6ULL System-on-module

由 廉价感情. 提交于 2019-12-11 12:13:14
问题 I am using iMX6ULL system-on-module on my custom board. I am struggling with UART, GPIOs of my custom board. I have solved the SPI issue on my board but later I got to know about another issue with my board and that's why I thought to ask a new question. I am able to activate desired UART port and SPI port for my board. But I got to know that my peripheral sensors which are soldered on my custom board have TX and RX lines swapped. I was trying to swap tx rx pins of UART5 of the imx6ull soc

DTS File to disable LCD and use it's GPIO in iMX6ULL

由 二次信任 提交于 2019-12-11 08:47:48
问题 I am using the Toradex system-on-module colibri imx6ULL with a custom board. I am trying to disable the LCD and use it's GPIOs for my sensors. I have followed the answer in this link. I got stuck with one of the suggestion in the answer. In addition to assigning these pings to an iomuxc pinctrl group, you'll also need to assign the pinctrl group to an enabled node for them to get initialized. You can create a new node specifically for this purpose if you'd like. What does that line mean? Do I

Cannot configure SPI0 on BeagleBone Green Wireless

由 半腔热情 提交于 2019-12-11 06:27:27
问题 Note: the selected answer is the original one that solved the problem, for more details refer to the additional one below. I'm not able to configure SPI0 on my BeagleBone Green Wireless (BBGW). I'm trying to achieve this without using overlays, only pure DeviceTree. /dev/spidev1.0 and /dev/spidev1.1 are there, but any I/O returns garbage. Oscilloscope connected to SCLK displays mostly noise, here are pictures (each in different time scale). Important parts of my .dts/.dtsi: &am33xx_pinmux {

How to correctly configure interrupt for INT line of Atmel MXT641T touch chip in Android 5 kernel device tree?

由 三世轮回 提交于 2019-12-11 03:50:33
问题 I am having troubles getting a touch screen powered by an Atmel MXT641T on an Android 5 platform to work. The setup I have is as follows: Hardware: Inforce 6309 SBC with Qualcomm Snapdragon 410 msm8916 ARM64 processor. Custom touch screen with Atmel MXT641T controller chip. I2C connection between Atmel and Snapdragon connected to I2C0. Android 5 operating system using Linux kernel 3.10 from git://codeaurora.org/kernel/msm-3.10.git branch Rel_V1.3 (this is part of the BSP that comes with the

device tree overlay phandle

由 醉酒当歌 提交于 2019-12-08 07:12:46
问题 I'm working on a Cyclone V SOC FPGA from Altera with a double Cortex-A9 processor. The embedded system (linux-socfpga 4.16) is created with Buildroot-2018.05. I use a "top" device tree at boot time for processor component and a device-tree overlay to configure the FPGA part of the component and load the associated drivers. The overlay will be attach to the base_fpga_region of the top DT. top device tree /dts-v1/; / { model = "MY_PROJECT"; /* appended from boardinfo */ compatible = "altr

mmap EINVAL error on UIO device

由 江枫思渺然 提交于 2019-12-07 07:15:25
I have trouble mapping physical memory on Xilinx Zynq after attempting to use UIO instead of mapping directly /dev/mem . While the plan is to run the application as a normal user instead of root this is still being run as root . Apparently the first mapping is successful while the rest done to the same file descriptor 12 ( /dev/uio/ps2pl ) fail. While the obvious difference is the offset, it is within the range (see device tree) and it is properly page aligned. This application was working well with /dev/mem . The error observed by running with strace is: open("/dev/uio/ps2pl", O_RDWR|O_SYNC)

i am unable to boot with my latest rpi-3.18.0 kernel and enabling the device tree?

由 和自甴很熟 提交于 2019-12-06 15:26:29
I am working on the latest rpi kernel ie 3.18.0 and by enabling the device tree. I compiled the source code and with that image and modules i am unable to boot. I am getting a blank screen and its not booting. I added the following into the config.txt even though i am unable to boot device_tree=bcm2708-rpi-b.dtb device_tree_address=0x100 kernel_address=0x8000 disable_commandline_tags=2 But with the image and modules that are given in the link https://github.com/raspberrypi/firmware/tree/next , it is booting well with the same config.txt file and i also using the firmware that are from the link

I've added a MAX7320 i2c output chip. How can I get the kernel to load the driver for it?

由 柔情痞子 提交于 2019-12-06 10:13:25
问题 I've added a MAX7320 i2c expander chip to i2c bus 0 on my ARM Linux board. The chip works correctly from userspace with commands such as /usr/sbin/i2cset -y 0 0x5d 0x02 and /usr/sbin/i2cget -y 0 0x5d . There is a drivers/gpio/gpio-max732x.c file in the kernel source, which is compiled into the kernel that I'm running. (I've built it from source.) How do I tell the kernel that it should instantiate the gpio-max732x driver on "i2c bus 0, chip id 0x5d"? Do I need to modify the device tree .dts
订阅 device-tree