[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ca11fb55-b248-f912-ac63-46ba376e30cf@ti.com>
Date: Fri, 21 Jul 2017 10:15:55 +0530
From: Keerthy <j-keerthy@...com>
To: Grygorii Strashko <grygorii.strashko@...com>,
David Miller <davem@...emloft.net>
CC: <linux-omap@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <johan@...nel.org>,
<ivan.khoronzhuk@...aro.org>, <t-kristo@...com>, <nsekhar@...com>
Subject: Re: [PATCH] net: ethernet: ti: cpsw: Push the request_irq function to
the end of probe
On Friday 21 July 2017 04:14 AM, Grygorii Strashko wrote:
>
>
> On 07/20/2017 05:28 PM, David Miller wrote:
>> From: Grygorii Strashko <grygorii.strashko@...com>
>> Date: Thu, 20 Jul 2017 11:08:09 -0500
>>
>>> In general patch looks good to me, but it's really unexpected to
>>> receive IRQs while CPSW is probing ;(
>>
>> This is a poor expectation.
>>
>> Boot loaders and other entities can leave the device in any state
>> whatsoever.
>>
>> Furthermore, enabling an IRQ whose handler cannot properly execute
>> without crashing is wrong fundamentally. All data structures and
>> state must be set up properly before the IRQ is requested.
>>
>> Therefore this patch is correct and I will apply it.
>>
>
> Thanks. Agree (it just has never triggered before, so I meant - unexpected
> from current driver code point of view ;().
> And I'm just worry that it might not be enough :(, especially for am335x.
I tried nfs boot on am335x-evm with this patch and it boots fine for me.
>
Powered by blists - more mailing lists