[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42a9cd04-135b-40e9-ab42-a4a4a4f3ae27@kernel.org>
Date: Tue, 26 Nov 2024 10:32:08 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Parthiban <parthiban@...umiz.com>, Conor Dooley <conor@...nel.org>
Cc: Frank Binns <frank.binns@...tec.com>, Matt Coster
<matt.coster@...tec.com>, David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: gpu: add reset control property
On 26/11/2024 04:46, Parthiban wrote:
> On 11/25/24 11:37 PM, Conor Dooley wrote:
>> On Mon, Nov 25, 2024 at 10:07:03PM +0530, Parthiban Nallathambi wrote:
>>> GE8300 in Allwinner A133 have reset control from the ccu.
>>> Add the resets property as optional one to control it.
>>
>> There's no specific compatible here for an a133, but the binding
>> requires one. Where is your dts patch?
> A133 GPU is still work in progress in both Kernel and Mesa3D. Also power
> domain support needs an additional driver.
>
> But reset control is independent of those changes. Should reset control
> needs to be clubbed GPU dts changes?
How is it independent? Are you adding it for the new platforms? If yes,
then it is part of new platforms. Don't add properties which are not used.
Best regards,
Krzysztof
Powered by blists - more mailing lists