All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <sean.anderson@linux.dev>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Michal Simek <michal.simek@amd.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 00/13] drm: zynqmp_dp: IRQ cleanups and debugfs support
Date: Tue, 23 Apr 2024 11:39:59 -0400	[thread overview]
Message-ID: <cd183655-e099-4a6d-835d-7555f6f6884d@linux.dev> (raw)
In-Reply-To: <dd82b42b-4987-4bb8-b16e-580fe21009c3@ideasonboard.com>

On 4/23/24 11:30, Tomi Valkeinen wrote:
> On 23/04/2024 17:59, Sean Anderson wrote:
>> On 4/23/24 09:33, Tomi Valkeinen wrote:
>>> Hi Sean,
>>>
>>> On 22/04/2024 21:45, 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.
>>>
>>> What is the base for this series? I'm having trouble applying it.
>>>
>>> I managed to mostly apply it, but I see the board hang when I unload the modules. I didn't debug it as it might as well be caused by my conflict resolution.
>>
>> The base is v6.8-rc1, but it should probably be v6.9. I can rebase and resend.
> 
> Did you have something extra in your branch before the series? I got "error: sha1 information is lacking or useless".

Nope.

--Sean

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Sean Anderson <sean.anderson@linux.dev>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Michal Simek <michal.simek@amd.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 00/13] drm: zynqmp_dp: IRQ cleanups and debugfs support
Date: Tue, 23 Apr 2024 11:39:59 -0400	[thread overview]
Message-ID: <cd183655-e099-4a6d-835d-7555f6f6884d@linux.dev> (raw)
In-Reply-To: <dd82b42b-4987-4bb8-b16e-580fe21009c3@ideasonboard.com>

On 4/23/24 11:30, Tomi Valkeinen wrote:
> On 23/04/2024 17:59, Sean Anderson wrote:
>> On 4/23/24 09:33, Tomi Valkeinen wrote:
>>> Hi Sean,
>>>
>>> On 22/04/2024 21:45, 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.
>>>
>>> What is the base for this series? I'm having trouble applying it.
>>>
>>> I managed to mostly apply it, but I see the board hang when I unload the modules. I didn't debug it as it might as well be caused by my conflict resolution.
>>
>> The base is v6.8-rc1, but it should probably be v6.9. I can rebase and resend.
> 
> Did you have something extra in your branch before the series? I got "error: sha1 information is lacking or useless".

Nope.

--Sean

  reply	other threads:[~2024-04-23 15:40 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 18:45 [PATCH v3 00/13] drm: zynqmp_dp: IRQ cleanups and debugfs support Sean Anderson
2024-04-22 18:45 ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 01/13] drm: xlnx: Store base pointers in zynqmp_disp directly Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-23 12:16   ` Tomi Valkeinen
2024-04-23 12:16     ` Tomi Valkeinen
2024-04-22 18:45 ` [PATCH v3 02/13] drm: xlnx: Fix kerneldoc Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-23 12:17   ` Tomi Valkeinen
2024-04-23 12:17     ` Tomi Valkeinen
2024-04-22 18:45 ` [PATCH v3 03/13] drm: zynqmp_dp: Downgrade log level for aux retries message Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 04/13] drm: zynqmp_dp: Adjust training values per-lane Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 05/13] drm: zynqmp_dp: Rearrange zynqmp_dp for better padding Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 06/13] drm: zynqmp_dp: Don't delay work Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-23 12:18   ` Tomi Valkeinen
2024-04-23 12:18     ` Tomi Valkeinen
2024-04-22 18:45 ` [PATCH v3 07/13] drm: zynqmp_dp: Add locking Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 08/13] drm: zynqmp_dp: Don't retrain the link in our IRQ Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 09/13] drm: zynqmp_dp: Convert to a hard IRQ Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 10/13] drm: zynqmp_dp: Use AUX IRQs instead of polling Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 11/13] drm: zynqmp_dp: Split off several helper functions Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 12/13] drm: zynqmp_dp: Take dp->lock in zynqmp_dp_hpd_work_func Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:45 ` [PATCH v3 13/13] drm: zynqmp_dp: Add debugfs interface for compliance testing Sean Anderson
2024-04-22 18:45   ` Sean Anderson
2024-04-22 18:48 ` [PATCH v3 00/13] drm: zynqmp_dp: IRQ cleanups and debugfs support Sean Anderson
2024-04-22 18:48   ` Sean Anderson
2024-04-23 13:33 ` Tomi Valkeinen
2024-04-23 13:33   ` Tomi Valkeinen
2024-04-23 14:59   ` Sean Anderson
2024-04-23 14:59     ` Sean Anderson
2024-04-23 15:30     ` Tomi Valkeinen
2024-04-23 15:30       ` Tomi Valkeinen
2024-04-23 15:39       ` Sean Anderson [this message]
2024-04-23 15:39         ` Sean Anderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cd183655-e099-4a6d-835d-7555f6f6884d@linux.dev \
    --to=sean.anderson@linux.dev \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=michal.simek@amd.com \
    --cc=mripard@kernel.org \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.