Issue with device driver initialization and a question on devicetree reg property syntax.
Hi,
I'm having a weird problem running Linux (Kernel 4.19) on a Rockchip RK3566 based Pine64 boards (Soquartz and Quartz64-A - both). I partially wrote the device tree file myself , other parts were lifted from similar devices so I expect some errors to be present. Specifically I'm getting an error like this during ISP (a camera image processing chip) driver initialization: Code:
[ 0.905435] iommu: Adding device fdff0000.rkisp to group 7 Code:
rkisp: rkisp@fdff0000 { However, the same "trick" doesn't work for rkisp. First, it is a very complex component and it actually uses registers that go up to 0x5700. So I tried to change the line to give it 0x6000 range, but this didn't help. Additionally I would like to ask, why is it that we have 4 numbers on the reg property line? If this line specifies an address and a region length, why are there 4 numbers? Like this: Code:
reg = <0x0 0xfdff0000 0x0 0xFFFF>; If someone has some ideas or can shed some light on the above, that would be great. |
Quote:
What you posted still has the status as disabled, meaning the device driver will not be initialized! Quote:
The number of <u32> cells for the address in the reg property is specified by the #address-cells property in the parent node (or the default value is 2). The number of <u32> cells for the length in the reg property is specified by the #size-cells property in the parent node (or the default value is 1). Regards |
Quote:
Thank you for the reply. Yes, you're right this is set to disabled. In the file that includes this one it simply has one line enabling the device (status="okay"). So I thought it was the only relevant part. The parent node has only one property: compatible="rockchip, rk3568" And both address-cells and size-cells are commented out. Quote:
However both address-size and size-cells are commented out. So if indeed the defaults are: Code:
address-cells=2 So this answers well my <reg> format question, but it still leaves the reason for the error message as an unknown. |
All times are GMT -5. The time now is 06:30 PM. |