[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <TY3P286MB2611256E28AF951F2B38A5B098A19@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
Date: Fri, 17 Feb 2023 22:14:13 +0800
From: Shengyu Qu <wiagn233@...look.com>
To: Michael Tretter <m.tretter@...gutronix.de>,
devicetree@...r.kernel.org, ezequiel@...guardiasur.com.ar,
frattaroli.nicolas@...il.com, heiko@...ech.de,
jacob-chen@...wrt.com, krzysztof.kozlowski+dt@...aro.org,
krzysztof.kozlowski@...aro.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, linux-rockchip@...ts.infradead.org,
mchehab@...nel.org, robh+dt@...nel.org, kernel@...gutronix.de
Subject: Re: [PATCH RESEND 2/2] arm64: dts: rockchip: Add RGA2 support to
rk356x
Hi Michael,
Seems we could use GFP_DMA32 flag to limit memory required by driver into
upper size range(actually using ZONE_DMA32 configured by device tree). Just
some driver modification needed. Maybe Nicolas could help testing? I would
like to fix this, but I don't have much free time these days.
Best regards,
Shengyu
> Hi,
>
> On Sun, 22 Jan 2023 00:50:37 +0800, Shengyu Qu wrote:
>> Since we have the over-4GB problem now, should we mark this problem as a
>> TODO or something?
> I am not really sure where to put such a TODO to make it visible for people
> that are running into the issue and to make sure that it is removed once it is
> fixed.
>
> Maybe it would be better to add error handling to the rga_buf_map function to
> fail if the address of the buffer that should be mapped has the upper 32 bit
> set and print a warning. Furthermore, the driver would be able to skip the
> buffer and prevent potential memory corruption caused by the erroneous
> mapping.
>
> Unfortunately, I don't have hardware that allows me to test this.
>
> Michael
Download attachment "OpenPGP_0xE3520CC91929C8E7.asc" of type "application/pgp-keys" (6869 bytes)
Download attachment "OpenPGP_signature" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists