[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <66a6c513-7277-255d-dd56-eed1d6a8efe8@gmx.net>
Date: Wed, 13 Sep 2023 13:31:15 +0200
From: Stefan Wahren <wahrenst@....net>
To: Umang Jain <umang.jain@...asonboard.com>,
Robin Murphy <robin.murphy@....com>
Cc: gregkh@...uxfoundation.org, f.fainelli@...il.com,
athierry@...hat.com, error27@...il.com,
kieran.bingham@...asonboard.com, laurent.pinchart@...asonboard.com,
dave.stevenson@...pberrypi.com, linux-kernel@...r.kernel.org,
linux-rpi-kernel@...ts.infradead.org,
linux-staging@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org
Subject: Re: [PATCH v10 1/5] staging: vc04_services: vchiq_arm: Add new bus
type and device type
Hi Umang,
Am 12.09.23 um 09:23 schrieb Stefan Wahren:
> Hi Umang,
>
> Am 12.09.23 um 07:50 schrieb Umang Jain:
>> Hi Stephan
>>
>> On 9/12/23 1:52 AM, Stefan Wahren wrote:
>>> Hi Umang,
>>>
>>> Am 11.09.23 um 16:07 schrieb Umang Jain:
>>>> ...
>>>
>>> Unfortunately the call of of_dma_configure() generates warnings likes
>>> this (Raspberry Pi 3A+ with multi_v7_defconfig + VCHIQ):
>>>
>>> [ 9.206802] vchiq-bus bcm2835-audio: DMA mask not set
>>> [ 9.206892] vchiq-bus bcm2835-camera: DMA mask not set
>>
>> huh, really weird, as on my RPi-3-b I get these set correctly and I
>> don't any such warning.
> This warning comes from this line [1]. Did you test with the mainline
> devicetree from [2] which must be specified in the config.txt? Be
> aware the arm dts files has moved into a sub directory just like
> arm64. I don't use U-Boot, just the vendor bootloader from Raspberry
> Pi OS. Please look at [3] for the details.
please look at [4], which is possible a solution. AFAIK the dwc2 also
had the same problem.
[4] -
https://elixir.bootlin.com/linux/latest/source/drivers/usb/dwc2/platform.c#L448
Powered by blists - more mailing lists