From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-170.mta1.migadu.com (out-170.mta1.migadu.com [95.215.58.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5BE0215AAB1 for ; Mon, 17 Jun 2024 14:49:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.170 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718635752; cv=none; b=Uf1mUZwWQ8wsHh94dkuekCy2jzu8ph6PG5MU2WrZFjW8KcxVK9r802sbgdOIDiQTmCFW/ZbrFV2w836H5oXxux0FzRzJ9iNcXDYDHj/ROeHb77RDzhK/IldxgaQW1UJeKg8tfvazRk5PSMS9WZCBV3E4kwbGfHk1oyYVSg/7ppc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718635752; c=relaxed/simple; bh=JUmKkvfHePYF/cQp25JXVt1Bm3H77iKcoRDz89BCSD8=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=EAgcnEOs/4kH0DgKfICgTYFy8WX/pxxIQzX0DoQ2wD6EU/FdXm+OUOhTcOhFcMmPL0ezfBLBpH2UjkXkFtVoeSlHJoCe36/uLNh8fLLpmQkIv7JBwXwlSnDc3JYY3L1kBi1GjDWm179KAMWdVXvcPZrat7TvPl8V0AHf+hKJMUE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=rRjgk1x0; arc=none smtp.client-ip=95.215.58.170 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="rRjgk1x0" X-Envelope-To: tomi.valkeinen@ideasonboard.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1718635743; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ch7cah993AkVkg+y3U7rb0K5ixT//mKQZ75RYDYWvBI=; b=rRjgk1x0taQwUoPz9ZFDrKfLRRi/dGvlDhP/onKrUm9rDL68yaXQCbwFuRRpE6BpgutiFX YzsKgAPvEarBcalpQ9NMNuEQzn+0p42I0g8FBDZqzDdWu+mC7QD977AODqf6ngZWDIjO7G w/+ZO0s0Wxv4i+HLQBPsW3h0qgsays8= X-Envelope-To: laurent.pinchart@ideasonboard.com X-Envelope-To: maarten.lankhorst@linux.intel.com X-Envelope-To: mripard@kernel.org X-Envelope-To: tzimmermann@suse.de X-Envelope-To: dri-devel@lists.freedesktop.org X-Envelope-To: linux-arm-kernel@lists.infradead.org X-Envelope-To: airlied@gmail.com X-Envelope-To: linux-kernel@vger.kernel.org X-Envelope-To: daniel@ffwll.ch X-Envelope-To: michal.simek@amd.com Message-ID: <5c5aa8ae-75c4-4f0f-ad19-50ad57c61216@linux.dev> Date: Mon, 17 Jun 2024 10:48:58 -0400 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v5 00/10] drm: zynqmp_dp: IRQ cleanups and debugfs support To: Tomi Valkeinen , Laurent Pinchart , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , dri-devel@lists.freedesktop.org Cc: linux-arm-kernel@lists.infradead.org, David Airlie , linux-kernel@vger.kernel.org, Daniel Vetter , Michal Simek References: <20240503192922.2172314-1-sean.anderson@linux.dev> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Sean Anderson In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 6/17/24 03:47, Tomi Valkeinen wrote: > Hi Sean, > > On 03/05/2024 22:29, 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. > > I tested this, and the "drm: zynqmp_dp: Convert to a hard IRQ" causes a hang for me when unloading the drivers. Unfortunately I'm not in the condition to debug it at the moment. > > I have picked the first three patches into drm-misc-next, though, to decrease the number of patches in the series a bit. They looked independent and safe enough to apply. Are you running into [1]? --Sean [1] https://lore.kernel.org/dri-devel/4d8f4c9b-2efb-4774-9a37-2f257f79b2c9@linux.dev/