On Mon, Nov 21, 2022 at 12:34 PM Ezequiel Garcia <ezequiel@xxxxxxxxxxxxxxxxxxxx> wrote: > > Hi Shengyu, Michael, > > On Mon, Nov 21, 2022 at 2:13 PM Shengyu Qu <wiagn233@xxxxxxxxxxx> wrote: > > > > Hi, > > I remember someone said that rga2 has only 32bit address space but not having a mmu or mmu needs to be configured. Better ask by yourself in pine64 discord since I'm not sure about that. > > > > Shengyu > > > > > > 于 2022年11月22日 GMT+08:00 上午12:41:16, Michael Tretter <m.tretter@xxxxxxxxxxxxxx> 写到: > > >Hi, > > > > > >On Tue, 22 Nov 2022 00:01:28 +0800, Shengyu Qu wrote: > > >> Someone from pine64 discord found that RGA2 doesn't work properly on over > > >> > > >> 4GB memory RK3568 devices. Are you sure current driver works now? > > > > > >I am absolutely sure that the driver works on a 2GB ROCK3A board. > > >Unfortunately, I don't have a device with 4GB or more memory and I cannot test > > >the driver with such a device. > > > > > >As the documentation for the RGA2 is the same in the TRM of the rk3288 and > > >rk3568, I would guess that the driver doesn't work on a rk3288 with more than > > >4GB (if there is such a thing) either and the driver needs to be fixed for > > >both SoCs. > > > > > In any case, if there's some kind of issue it must be in the driver, > and not in the device tree binding (i.e. this patchset). An unfortunate number of Rockchip drivers break on rk356x boards with more than 4GB of ram. I've found requesting memory allocations with the GFP_DMA flag solves the problem, as the kernel only allocates 32bit addresses for DMA on rk356x. This is similar to the bug with the ITS MSI allocations. > > Regards, > Ezequiel > > _______________________________________________ > Linux-rockchip mailing list > Linux-rockchip@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-rockchip
