From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>, kishon@ti.com
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v2] phy: meson-g12a-usb3-pcie: disable locking for cr_regmap
Date: Fri, 07 Jun 2019 15:57:11 -0700 [thread overview]
Message-ID: <7hh891atrs.fsf@baylibre.com> (raw)
In-Reply-To: <20190605090215.29905-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Locking is not needed for the phy_g12a_usb3_pcie_cr_bus_read/write() and
> currently it causes the following BUG because of the usage of the
> regmap_read_poll_timeout() running in spinlock_irq, configured by regmap fast_io.
>
> Simply disable locking in the cr_regmap config since it's only used from the
> PHY init callback function.
>
> BUG: sleeping function called from invalid context at drivers/phy/amlogic/phy-meson-g12a-usb3-pcie.c:85
> in_atomic(): 1, irqs_disabled(): 128, pid: 60, name: kworker/3:1
> [snip]
> Workqueue: events deferred_probe_work_func
> Call trace:
> dump_backtrace+0x0/0x190
> show_stack+0x14/0x20
> dump_stack+0x90/0xb4
> ___might_sleep+0xec/0x110
> __might_sleep+0x50/0x88
> phy_g12a_usb3_pcie_cr_bus_addr.isra.0+0x80/0x1a8
> phy_g12a_usb3_pcie_cr_bus_read+0x34/0x1d8
> _regmap_read+0x60/0xe0
> _regmap_update_bits+0xc4/0x110
> regmap_update_bits_base+0x60/0x90
> phy_g12a_usb3_pcie_init+0xdc/0x210
> phy_init+0x74/0xd0
> dwc3_meson_g12a_probe+0x2cc/0x4d0
> platform_drv_probe+0x50/0xa0
> really_probe+0x20c/0x3b8
> driver_probe_device+0x68/0x150
> __device_attach_driver+0xa8/0x170
> bus_for_each_drv+0x64/0xc8
> __device_attach+0xd8/0x158
> device_initial_probe+0x10/0x18
> bus_probe_device+0x90/0x98
> deferred_probe_work_func+0x94/0xe8
> process_one_work+0x1e0/0x338
> worker_thread+0x230/0x458
> kthread+0x134/0x138
> ret_from_fork+0x10/0x1c
>
> Fixes: 36077e16c050 ("phy: amlogic: Add Amlogic G12A USB3 + PCIE Combo PHY Driver")
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Tested-by: Kevin Hilman <khilman@baylibre.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>, kishon@ti.com
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v2] phy: meson-g12a-usb3-pcie: disable locking for cr_regmap
Date: Fri, 07 Jun 2019 15:57:11 -0700 [thread overview]
Message-ID: <7hh891atrs.fsf@baylibre.com> (raw)
In-Reply-To: <20190605090215.29905-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Locking is not needed for the phy_g12a_usb3_pcie_cr_bus_read/write() and
> currently it causes the following BUG because of the usage of the
> regmap_read_poll_timeout() running in spinlock_irq, configured by regmap fast_io.
>
> Simply disable locking in the cr_regmap config since it's only used from the
> PHY init callback function.
>
> BUG: sleeping function called from invalid context at drivers/phy/amlogic/phy-meson-g12a-usb3-pcie.c:85
> in_atomic(): 1, irqs_disabled(): 128, pid: 60, name: kworker/3:1
> [snip]
> Workqueue: events deferred_probe_work_func
> Call trace:
> dump_backtrace+0x0/0x190
> show_stack+0x14/0x20
> dump_stack+0x90/0xb4
> ___might_sleep+0xec/0x110
> __might_sleep+0x50/0x88
> phy_g12a_usb3_pcie_cr_bus_addr.isra.0+0x80/0x1a8
> phy_g12a_usb3_pcie_cr_bus_read+0x34/0x1d8
> _regmap_read+0x60/0xe0
> _regmap_update_bits+0xc4/0x110
> regmap_update_bits_base+0x60/0x90
> phy_g12a_usb3_pcie_init+0xdc/0x210
> phy_init+0x74/0xd0
> dwc3_meson_g12a_probe+0x2cc/0x4d0
> platform_drv_probe+0x50/0xa0
> really_probe+0x20c/0x3b8
> driver_probe_device+0x68/0x150
> __device_attach_driver+0xa8/0x170
> bus_for_each_drv+0x64/0xc8
> __device_attach+0xd8/0x158
> device_initial_probe+0x10/0x18
> bus_probe_device+0x90/0x98
> deferred_probe_work_func+0x94/0xe8
> process_one_work+0x1e0/0x338
> worker_thread+0x230/0x458
> kthread+0x134/0x138
> ret_from_fork+0x10/0x1c
>
> Fixes: 36077e16c050 ("phy: amlogic: Add Amlogic G12A USB3 + PCIE Combo PHY Driver")
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Tested-by: Kevin Hilman <khilman@baylibre.com>
_______________________________________________
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: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>, kishon@ti.com
Cc: Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2] phy: meson-g12a-usb3-pcie: disable locking for cr_regmap
Date: Fri, 07 Jun 2019 15:57:11 -0700 [thread overview]
Message-ID: <7hh891atrs.fsf@baylibre.com> (raw)
In-Reply-To: <20190605090215.29905-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Locking is not needed for the phy_g12a_usb3_pcie_cr_bus_read/write() and
> currently it causes the following BUG because of the usage of the
> regmap_read_poll_timeout() running in spinlock_irq, configured by regmap fast_io.
>
> Simply disable locking in the cr_regmap config since it's only used from the
> PHY init callback function.
>
> BUG: sleeping function called from invalid context at drivers/phy/amlogic/phy-meson-g12a-usb3-pcie.c:85
> in_atomic(): 1, irqs_disabled(): 128, pid: 60, name: kworker/3:1
> [snip]
> Workqueue: events deferred_probe_work_func
> Call trace:
> dump_backtrace+0x0/0x190
> show_stack+0x14/0x20
> dump_stack+0x90/0xb4
> ___might_sleep+0xec/0x110
> __might_sleep+0x50/0x88
> phy_g12a_usb3_pcie_cr_bus_addr.isra.0+0x80/0x1a8
> phy_g12a_usb3_pcie_cr_bus_read+0x34/0x1d8
> _regmap_read+0x60/0xe0
> _regmap_update_bits+0xc4/0x110
> regmap_update_bits_base+0x60/0x90
> phy_g12a_usb3_pcie_init+0xdc/0x210
> phy_init+0x74/0xd0
> dwc3_meson_g12a_probe+0x2cc/0x4d0
> platform_drv_probe+0x50/0xa0
> really_probe+0x20c/0x3b8
> driver_probe_device+0x68/0x150
> __device_attach_driver+0xa8/0x170
> bus_for_each_drv+0x64/0xc8
> __device_attach+0xd8/0x158
> device_initial_probe+0x10/0x18
> bus_probe_device+0x90/0x98
> deferred_probe_work_func+0x94/0xe8
> process_one_work+0x1e0/0x338
> worker_thread+0x230/0x458
> kthread+0x134/0x138
> ret_from_fork+0x10/0x1c
>
> Fixes: 36077e16c050 ("phy: amlogic: Add Amlogic G12A USB3 + PCIE Combo PHY Driver")
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Tested-by: Kevin Hilman <khilman@baylibre.com>
next prev parent reply other threads:[~2019-06-07 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 9:02 [PATCH v2] phy: meson-g12a-usb3-pcie: disable locking for cr_regmap Neil Armstrong
2019-06-05 9:02 ` Neil Armstrong
2019-06-05 9:02 ` Neil Armstrong
2019-06-07 22:57 ` Kevin Hilman [this message]
2019-06-07 22:57 ` Kevin Hilman
2019-06-07 22:57 ` Kevin Hilman
2019-06-24 13:00 ` Neil Armstrong
2019-06-24 13:00 ` Neil Armstrong
2019-06-24 13:00 ` Neil Armstrong
2019-06-25 5:20 ` Kishon Vijay Abraham I
2019-06-25 5:20 ` Kishon Vijay Abraham I
2019-06-25 5:20 ` Kishon Vijay Abraham I
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=7hh891atrs.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=kishon@ti.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/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.