All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <sean.anderson@linux.dev>
To: stable@vger.kernel.org, stable-commits@vger.kernel.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Michal Simek <michal.simek@amd.com>
Subject: Re: Patch "drm: zynqmp_dpsub: Always register bridge" has been added to the 6.9-stable tree
Date: Mon, 3 Jun 2024 11:04:28 -0400	[thread overview]
Message-ID: <12c2adcf-cc18-48a8-8411-0ba9ec3551e0@linux.dev> (raw)
In-Reply-To: <20240603114605.1823279-1-sashal@kernel.org>

Hi Sasha,

Please also pick [1] when it is applied.

--Sean

[1] https://lore.kernel.org/all/974d1b062d7c61ee6db00d16fa7c69aa1218ee02.1716198025.git.christophe.jaillet@wanadoo.fr/

On 6/3/24 07:46, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
> 
>     drm: zynqmp_dpsub: Always register bridge
> 
> to the 6.9-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>      drm-zynqmp_dpsub-always-register-bridge.patch
> and it can be found in the queue-6.9 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
> 
> 
> 
> commit d6817dc61b3b6a1e4f098b25109e7f2ecaaf0ee8
> Author: Sean Anderson <sean.anderson@linux.dev>
> Date:   Fri Mar 8 15:47:41 2024 -0500
> 
>     drm: zynqmp_dpsub: Always register bridge
>     
>     [ Upstream commit be3f3042391d061cfca2bd22630e0d101acea5fc ]
>     
>     We must always register the DRM bridge, since zynqmp_dp_hpd_work_func
>     calls drm_bridge_hpd_notify, which in turn expects hpd_mutex to be
>     initialized. We do this before zynqmp_dpsub_drm_init since that calls
>     drm_bridge_attach. This fixes the following lockdep warning:
>     
>     [   19.217084] ------------[ cut here ]------------
>     [   19.227530] DEBUG_LOCKS_WARN_ON(lock->magic != lock)
>     [   19.227768] WARNING: CPU: 0 PID: 140 at kernel/locking/mutex.c:582 __mutex_lock+0x4bc/0x550
>     [   19.241696] Modules linked in:
>     [   19.244937] CPU: 0 PID: 140 Comm: kworker/0:4 Not tainted 6.6.20+ #96
>     [   19.252046] Hardware name: xlnx,zynqmp (DT)
>     [   19.256421] Workqueue: events zynqmp_dp_hpd_work_func
>     [   19.261795] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
>     [   19.269104] pc : __mutex_lock+0x4bc/0x550
>     [   19.273364] lr : __mutex_lock+0x4bc/0x550
>     [   19.277592] sp : ffffffc085c5bbe0
>     [   19.281066] x29: ffffffc085c5bbe0 x28: 0000000000000000 x27: ffffff88009417f8
>     [   19.288624] x26: ffffff8800941788 x25: ffffff8800020008 x24: ffffffc082aa3000
>     [   19.296227] x23: ffffffc080d90e3c x22: 0000000000000002 x21: 0000000000000000
>     [   19.303744] x20: 0000000000000000 x19: ffffff88002f5210 x18: 0000000000000000
>     [   19.311295] x17: 6c707369642e3030 x16: 3030613464662072 x15: 0720072007200720
>     [   19.318922] x14: 0000000000000000 x13: 284e4f5f4e524157 x12: 0000000000000001
>     [   19.326442] x11: 0001ffc085c5b940 x10: 0001ff88003f388b x9 : 0001ff88003f3888
>     [   19.334003] x8 : 0001ff88003f3888 x7 : 0000000000000000 x6 : 0000000000000000
>     [   19.341537] x5 : 0000000000000000 x4 : 0000000000001668 x3 : 0000000000000000
>     [   19.349054] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff88003f3880
>     [   19.356581] Call trace:
>     [   19.359160]  __mutex_lock+0x4bc/0x550
>     [   19.363032]  mutex_lock_nested+0x24/0x30
>     [   19.367187]  drm_bridge_hpd_notify+0x2c/0x6c
>     [   19.371698]  zynqmp_dp_hpd_work_func+0x44/0x54
>     [   19.376364]  process_one_work+0x3ac/0x988
>     [   19.380660]  worker_thread+0x398/0x694
>     [   19.384736]  kthread+0x1bc/0x1c0
>     [   19.388241]  ret_from_fork+0x10/0x20
>     [   19.392031] irq event stamp: 183
>     [   19.395450] hardirqs last  enabled at (183): [<ffffffc0800b9278>] finish_task_switch.isra.0+0xa8/0x2d4
>     [   19.405140] hardirqs last disabled at (182): [<ffffffc081ad3754>] __schedule+0x714/0xd04
>     [   19.413612] softirqs last  enabled at (114): [<ffffffc080133de8>] srcu_invoke_callbacks+0x158/0x23c
>     [   19.423128] softirqs last disabled at (110): [<ffffffc080133de8>] srcu_invoke_callbacks+0x158/0x23c
>     [   19.432614] ---[ end trace 0000000000000000 ]---
>     
>     Fixes: eb2d64bfcc17 ("drm: xlnx: zynqmp_dpsub: Report HPD through the bridge")
>     Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
>     Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>     Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>     Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>     Link: https://patchwork.freedesktop.org/patch/msgid/20240308204741.3631919-1-sean.anderson@linux.dev
>     (cherry picked from commit 61ba791c4a7a09a370c45b70a81b8c7d4cf6b2ae)
>     Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>     Signed-off-by: Sasha Levin <sashal@kernel.org>
> 
> diff --git a/drivers/gpu/drm/xlnx/zynqmp_dpsub.c b/drivers/gpu/drm/xlnx/zynqmp_dpsub.c
> index 88eb33acd5f0d..face8d6b2a6fb 100644
> --- a/drivers/gpu/drm/xlnx/zynqmp_dpsub.c
> +++ b/drivers/gpu/drm/xlnx/zynqmp_dpsub.c
> @@ -256,12 +256,12 @@ static int zynqmp_dpsub_probe(struct platform_device *pdev)
>  	if (ret)
>  		goto err_dp;
>  
> +	drm_bridge_add(dpsub->bridge);
> +
>  	if (dpsub->dma_enabled) {
>  		ret = zynqmp_dpsub_drm_init(dpsub);
>  		if (ret)
>  			goto err_disp;
> -	} else {
> -		drm_bridge_add(dpsub->bridge);
>  	}
>  
>  	dev_info(&pdev->dev, "ZynqMP DisplayPort Subsystem driver probed");
> @@ -288,9 +288,8 @@ static void zynqmp_dpsub_remove(struct platform_device *pdev)
>  
>  	if (dpsub->drm)
>  		zynqmp_dpsub_drm_cleanup(dpsub);
> -	else
> -		drm_bridge_remove(dpsub->bridge);
>  
> +	drm_bridge_remove(dpsub->bridge);
>  	zynqmp_disp_remove(dpsub);
>  	zynqmp_dp_remove(dpsub);
>  


       reply	other threads:[~2024-06-03 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240603114605.1823279-1-sashal@kernel.org>
2024-06-03 15:04 ` Sean Anderson [this message]
2024-06-12 12:42   ` Patch "drm: zynqmp_dpsub: Always register bridge" has been added to the 6.9-stable tree Greg KH
2024-07-29 19:38     ` 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=12c2adcf-cc18-48a8-8411-0ba9ec3551e0@linux.dev \
    --to=sean.anderson@linux.dev \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=michal.simek@amd.com \
    --cc=mripard@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.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.