[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176365870435.207696.4457416829154592287.b4-ty@kernel.org>
Date: Thu, 20 Nov 2025 22:41:44 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Frank.li@....com, kishon@...nel.org, shawnguo@...nel.org,
s.hauer@...gutronix.de, kernel@...gutronix.de, festevam@...il.com,
Xiaolei Wang <xiaolei.wang@...driver.com>
Cc: linux-phy@...ts.infradead.org, imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] phy: freescale: Initialize priv->lock
On Thu, 25 Sep 2025 09:38:06 +0800, Xiaolei Wang wrote:
> Initialize priv->lock to fix the following warning.
>
> WARNING: CPU: 0 PID: 12 at kernel/locking/mutex.c:577 __mutex_lock+0x70c/0x8b8
> Modules linked in:
> Hardware name: Freescale i.MX8QM MEK (DT)
> Call trace:
> __mutex_lock+0x70c/0x8b8 (P)
> mutex_lock_nested+0x24/0x30
> imx_hsio_power_on+0x4c/0x764
> phy_power_on+0x7c/0x12c
> imx_pcie_host_init+0x1d0/0x4d4
> dw_pcie_host_init+0x188/0x4b0
> imx_pcie_probe+0x324/0x6f4
> platform_probe+0x5c/0x98
> really_probe+0xbc/0x29c
> __driver_probe_device+0x78/0x12c
> driver_probe_device+0xd8/0x160
> __device_attach_driver+0xb8/0x138
> bus_for_each_drv+0x84/0xe4
> __device_attach_async_helper+0xb8/0xdc
> async_run_entry_fn+0x34/0xe0
> process_one_work+0x220/0x694
> worker_thread+0x1c0/0x36c
> kthread+0x14c/0x224
>
> [...]
Applied, thanks!
[1/1] phy: freescale: Initialize priv->lock
commit: 95e5905698983df94069e185f9eb3c67c7cf75d5
Best regards,
--
~Vinod
Powered by blists - more mailing lists