Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1708379

Re: [RFC PATCH] PCI: rockchip: fix system hang up if activate CONFIG_DEBUG_SHIRQ

From jeffy <jeffy.chen@rock-chips.com>
Newsgroups linux.kernel
Subject Re: [RFC PATCH] PCI: rockchip: fix system hang up if activate CONFIG_DEBUG_SHIRQ
Date 2017-08-10 11:50 +0200
Message-ID <ucSgh-3P5-1@gated-at.bofh.it> (permalink)
References <ucR0S-2S8-21@gated-at.bofh.it> <ucRWW-3Ia-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Heiko,

On 08/10/2017 05:27 PM, Heiko Stuebner wrote:
> Hi Shawn,
>
> Am Donnerstag, 10. August 2017, 16:21:13 CEST schrieb Shawn Lin:
>> >With CONFIG_DEBUG_SHIRQ enabled, the irq tear down routine
>> >would still access the irq handler registed as a shard irq.
>> >Per the comment within the function of __free_irq, it says
>> >"It's a shared IRQ -- the driver ought to be prepared for
>> >an IRQ event to happen even now it's being freed". However
>> >when failing to probe the driver, it may disable the clock
>> >for accessing the register and the following check for shared
>> >irq state would call the irq handler which accesses the register
>> >w/o the clk enabled. That will hang the system forever.
> The key point would be to fix the ordering. So you could also just use
> devm_add_action to move the clock-disabling into a callback that
> gets run at the appropriate time, as devm does the shutdown in the
> exact opposite order this should fix your problem.
>
> So until all clocks could be enabled, you would disable them manually
> and after that rely on the devm_action to fire at the appropriate time.
>
> ret = clk_prepare_enable(clk1);
> if (ret < 0 )
> 	return ret;
>
> ret = clk_prepare_enable(clk2);
> if (ret < 0) {
> 	clk_disable_unprepare(clk1);
> 	return ret;
> }
>
> devm_add_action_or_reset(dev, rk_pcie_disable_clocks);

right, and we should also move request irq after this, so the devres 
core can release them in reverse.

and we should double check would those clks be the only thing that irq 
handler required...
>
> The rockchip crypto driver [0] shows how this could be done.
>
>
> Heiko
>
> [0]http://elixir.free-electrons.com/linux/latest/source/drivers/crypto/rockchip/rk3288_crypto.c#L307
>

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[RFC PATCH] PCI: rockchip: fix system hang up if activate CONFIG_DEBUG_SHIRQ Shawn Lin <shawn.lin@rock-chips.com> - 2017-08-10 10:30 +0200
  Re: [RFC PATCH] PCI: rockchip: fix system hang up if activate CONFIG_DEBUG_SHIRQ jeffy <jeffy.chen@rock-chips.com> - 2017-08-10 10:50 +0200
    Re: [RFC PATCH] PCI: rockchip: fix system hang up if activate  CONFIG_DEBUG_SHIRQ Shawn Lin <shawn.lin@rock-chips.com> - 2017-08-10 11:20 +0200
      Re: [RFC PATCH] PCI: rockchip: fix system hang up if activate CONFIG_DEBUG_SHIRQ jeffy <jeffy.chen@rock-chips.com> - 2017-08-10 11:30 +0200
  Re: [RFC PATCH] PCI: rockchip: fix system hang up if activate CONFIG_DEBUG_SHIRQ Heiko Stuebner <heiko@sntech.de> - 2017-08-10 11:30 +0200
    Re: [RFC PATCH] PCI: rockchip: fix system hang up if activate CONFIG_DEBUG_SHIRQ jeffy <jeffy.chen@rock-chips.com> - 2017-08-10 11:50 +0200
    Re: [RFC PATCH] PCI: rockchip: fix system hang up if activate  CONFIG_DEBUG_SHIRQ Shawn Lin <shawn.lin@rock-chips.com> - 2017-08-10 13:10 +0200

csiph-web