[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5b6a642d-b9c6-4648-b1ab-1823bbcb7ea2@kernel.org>
Date: Wed, 11 Jun 2025 21:17:53 +0200
From: Sven Peter <sven@...nel.org>
To: Sasha Finkelstein <fnkl.kernel@...il.com>
Cc: asahi@...ts.linux.dev,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Simona Vetter <simona@...ll.ch>, David Airlie <airlied@...il.com>,
Neal Gompa <neal@...pa.dev>, Maxime Ripard <mripard@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Rob Herring <robh@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Alyssa Rosenzweig <alyssa@...enzweig.io>, Janne Grunau <j@...nau.net>,
linux-arm-kernel@...ts.infradead.org, dri-devel@...ts.freedesktop.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: Add Apple SoC GPU
On 11.06.25 21:06, Sasha Finkelstein wrote:
> On Wed, 11 Jun 2025 at 20:44, Sven Peter <sven@...nel.org> wrote:
>>> + - description: Driver-opaque calibration blob
>>> + - description: Calibration blob
>>
>> Like Alyssa mentioned, this description also raises more questions than
>> it answers for me. Do we know what these two blobs contain or why they
>> are two separate blobs?
>
> At some point in the gpu initialization process we give the firmware a bag
> of pointers to various stuff it needs. HwCalA and HwCalB are separate
> pointers, and they use separate gpu allocations. We do not fully know
> what is in there, but we know what some of the fields do and how to
> create the blobs based on data from apple device tree.
I looked at the driver itself and there are two comments related to
these:
HwDataA: This mostly contains power-related configuration.
HwDataB: This mostly contains GPU-related configuration.
Are they still accurate our just outdated leftovers from an early
version? If they're accurate I'd include them in the description here as
well.
Best,
Sven
Powered by blists - more mailing lists