RE: [RESEND v2 3/5] PCI: imx6: Fix the regulator dump when link never came up

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com>
Sent: Saturday, October 16, 2021 2:35 AM
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: Lucas Stach <l.stach@pengutronix.de>; Bjorn Helgaas
[off-list ref]; Lorenzo Pieralisi [off-list ref];
linux-pci@vger.kernel.org; dl-linux-imx [off-list ref]; moderated
list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE
[off-list ref]; linux-kernel
[off-list ref]; Sascha Hauer [off-list ref]
Subject: Re: [RESEND v2 3/5] PCI: imx6: Fix the regulator dump when link
never came up

Hi Richard,

On Fri, Oct 15, 2021 at 3:32 AM Richard Zhu [off-list ref] wrote:

quoted

When PCIe PHY link never came up and vpcie regulator is present, there
would be following dump when try to put the regulator.
Disable this regulator to fix this dump when link never came up.

  imx6q-pcie 33800000.pcie: Phy link never came up
  imx6q-pcie: probe of 33800000.pcie failed with error -110
  ------------[ cut here ]------------
  WARNING: CPU: 3 PID: 119 at drivers/regulator/core.c:2256

_regulator_put.part.0+0x14c/0x158

quoted

  Modules linked in:
  CPU: 3 PID: 119 Comm: kworker/u8:2 Not tainted

5.13.0-rc7-next-20210625-94710-ge4e92b2588a3 #10

quoted

  Hardware name: FSL i.MX8MM EVK board (DT)
  Workqueue: events_unbound async_run_entry_fn
  pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)
  pc : _regulator_put.part.0+0x14c/0x158
  lr : regulator_put+0x34/0x48
  sp : ffff8000122ebb30
  x29: ffff8000122ebb30 x28: ffff800011be7000 x27: 0000000000000000
  x26: 0000000000000000 x25: 0000000000000000 x24: ffff00000025f2bc
  x23: ffff00000025f2c0 x22: ffff00000025f010 x21: ffff8000122ebc18
  x20: ffff800011e3fa60 x19: ffff00000375fd80 x18: 0000000000000010
  x17: 000000040044ffff x16: 00400032b5503510 x15:

0000000000000108

quoted

  x14: ffff0000003cc938 x13: 00000000ffffffea x12: 0000000000000000
  x11: 0000000000000000 x10: ffff80001076ba88 x9 : ffff80001076a540
  x8 : ffff00000025f2c0 x7 : ffff0000001f4450 x6 : ffff000000176cd8
  x5 : ffff000003857880 x4 : 0000000000000000 x3 : ffff800011e3fe30
  x2 : ffff0000003cc4c0 x1 : 0000000000000000 x0 : 0000000000000001
  Call trace:
   _regulator_put.part.0+0x14c/0x158
   regulator_put+0x34/0x48
   devm_regulator_release+0x10/0x18
   release_nodes+0x38/0x60
   devres_release_all+0x88/0xd0
   really_probe+0xd0/0x2e8
   __driver_probe_device+0x74/0xd8
   driver_probe_device+0x7c/0x108
   __device_attach_driver+0x8c/0xd0
   bus_for_each_drv+0x74/0xc0
   __device_attach_async_helper+0xb4/0xd8
   async_run_entry_fn+0x30/0x100
   process_one_work+0x19c/0x320
   worker_thread+0x48/0x418
   kthread+0x14c/0x158
   ret_from_fork+0x10/0x18
  ---[ end trace 3664ca4a50ce849b ]---

Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>

I am seeing this on imx6 too. When you send a v2, after addressing Lucas'
comments, please add a Fixes tag/

[Richard Zhu] Okay, no problem. Thanks.
BR
Richard