From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Keerthy <j-keerthy@ti.com>, David Miller <davem@davemloft.net>
Cc: <linux-omap@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <johan@kernel.org>,
<ivan.khoronzhuk@linaro.org>, <t-kristo@ti.com>, <nsekhar@ti.com>
Subject: Re: [PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe
Date: Fri, 21 Jul 2017 10:55:00 -0500 [thread overview]
Message-ID: <185e1781-d9b5-226d-2dde-26faaec7198d@ti.com> (raw)
In-Reply-To: <ca11fb55-b248-f912-ac63-46ba376e30cf@ti.com>
On 07/20/2017 11:45 PM, Keerthy wrote:
>
>
> 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@ti.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.
>
Thank you Keerthy, I've also simulated and tested it on am335x and dra7
and see networking working and no crashes.
--
regards,
-grygorii
prev parent reply other threads:[~2017-07-21 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 11:29 Keerthy
2017-07-20 16:08 ` Grygorii Strashko
2017-07-20 22:28 ` David Miller
2017-07-20 22:44 ` Grygorii Strashko
2017-07-21 4:45 ` Keerthy
2017-07-21 15:55 ` Grygorii Strashko [this message]
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=185e1781-d9b5-226d-2dde-26faaec7198d@ti.com \
--to=grygorii.strashko@ti.com \
--cc=davem@davemloft.net \
--cc=ivan.khoronzhuk@linaro.org \
--cc=j-keerthy@ti.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=t-kristo@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®