[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c5247f81-9a5b-49f5-8567-343776030c43@ideasonboard.com>
Date: Sat, 27 Apr 2024 10:45:11 +0300
From: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
To: Sean Anderson <sean.anderson@...ux.dev>
Cc: Daniel Vetter <daniel@...ll.ch>, linux-arm-kernel@...ts.infradead.org,
Michal Simek <michal.simek@....com>, linux-kernel@...r.kernel.org,
David Airlie <airlied@...il.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH v4 00/13] drm: zynqmp_dp: IRQ cleanups and debugfs support
On 25/04/2024 18:17, Sean Anderson wrote:
> On 4/24/24 14:54, Tomi Valkeinen wrote:
>> Hi Sean,
>>
>> On 23/04/2024 20:18, Sean Anderson wrote:
>>> This series cleans up the zyqnmp_dp IRQ and locking situation. Once
>>> that's done, it adds debugfs support. The intent is to enable compliance
>>> testing or to help debug signal-integrity issues.
>>>
>>> Last time I discussed converting the HPD work(s) to a threaded IRQ. I
>>> did not end up doing that for this series since the steps would be
>>>
>>> - Add locking
>>> - Move link retraining to a work function
>>> - Harden the IRQ
>>> - Merge the works into a threaded IRQ (omitted)
>>>
>>> Which with the exception of the final step is the same as leaving those
>>> works as-is. Conversion to a threaded IRQ can be done as a follow-up.
>>
>> If it's ok to you, I'd like to pick the first four patches to drm-misc already.
>
> Fine by me.
I have pushed the first four to drm-misc. I'll try to look at the rest
of the patches next week.
Tomi
Powered by blists - more mailing lists