All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	linux-arm-kernel@lists.infradead.org,
	Michal Simek <michal.simek@amd.com>,
	linux-kernel@vger.kernel.org, David Airlie <airlied@gmail.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 v4 00/13] drm: zynqmp_dp: IRQ cleanups and debugfs support
Date: Sat, 27 Apr 2024 10:45:11 +0300	[thread overview]
Message-ID: <c5247f81-9a5b-49f5-8567-343776030c43@ideasonboard.com> (raw)
In-Reply-To: <f418cf10-ad19-4483-96a3-46b5d0630160@linux.dev>

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


WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	linux-arm-kernel@lists.infradead.org,
	Michal Simek <michal.simek@amd.com>,
	linux-kernel@vger.kernel.org, David Airlie <airlied@gmail.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 v4 00/13] drm: zynqmp_dp: IRQ cleanups and debugfs support
Date: Sat, 27 Apr 2024 10:45:11 +0300	[thread overview]
Message-ID: <c5247f81-9a5b-49f5-8567-343776030c43@ideasonboard.com> (raw)
In-Reply-To: <f418cf10-ad19-4483-96a3-46b5d0630160@linux.dev>

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


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

  reply	other threads:[~2024-04-27  7:45 UTC|newest]

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

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=c5247f81-9a5b-49f5-8567-343776030c43@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.com \
    --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=sean.anderson@linux.dev \
    --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.