Re: [U-Boot] [PATCH] net: eth-uclass: call stop only for active devices

2019-03-29 Thread Keerthy
On 27/02/19 11:17 AM, Keerthy wrote: On 22/02/19 12:08 AM, Joe Hershberger wrote: On Wed, Feb 20, 2019 at 6:33 AM Keerthy wrote: Currently stop is being called unconditionally without even checking if start is called. In case of multiple instances eth being present many devices might just

Re: [U-Boot] [PATCH] net: eth-uclass: call stop only for active devices

2019-02-26 Thread Bin Meng
On Wed, Feb 27, 2019 at 1:47 PM Keerthy wrote: > > > > On 22/02/19 12:08 AM, Joe Hershberger wrote: > > On Wed, Feb 20, 2019 at 6:33 AM Keerthy wrote: > >> > >> Currently stop is being called unconditionally without even > >> checking if start is called. In case of multiple instances eth > >> bei

Re: [U-Boot] [PATCH] net: eth-uclass: call stop only for active devices

2019-02-26 Thread Keerthy
On 22/02/19 12:08 AM, Joe Hershberger wrote: On Wed, Feb 20, 2019 at 6:33 AM Keerthy wrote: Currently stop is being called unconditionally without even checking if start is called. In case of multiple instances eth being present many devices might just be initialized without a start call in

Re: [U-Boot] [PATCH] net: eth-uclass: call stop only for active devices

2019-02-21 Thread Joe Hershberger
On Wed, Feb 20, 2019 at 9:01 PM Bin Meng wrote: > > On Wed, Feb 20, 2019 at 8:33 PM Keerthy wrote: > > > > Currently stop is being called unconditionally without even > > checking if start is called. In case of multiple instances eth > > being present many devices might just be initialized withou

Re: [U-Boot] [PATCH] net: eth-uclass: call stop only for active devices

2019-02-21 Thread Joe Hershberger
On Wed, Feb 20, 2019 at 6:33 AM Keerthy wrote: > > Currently stop is being called unconditionally without even > checking if start is called. In case of multiple instances eth > being present many devices might just be initialized without > a start call in such cases stop might lead unpredictable

Re: [U-Boot] [PATCH] net: eth-uclass: call stop only for active devices

2019-02-20 Thread Bin Meng
On Wed, Feb 20, 2019 at 8:33 PM Keerthy wrote: > > Currently stop is being called unconditionally without even > checking if start is called. In case of multiple instances eth > being present many devices might just be initialized without > a start call in such cases stop might lead unpredictable

Re: [U-Boot] [PATCH] net: eth-uclass: call stop only for active devices

2019-02-20 Thread Simon Glass
On Wed, 20 Feb 2019 at 05:32, Keerthy wrote: > > Currently stop is being called unconditionally without even > checking if start is called. In case of multiple instances eth > being present many devices might just be initialized without > a start call in such cases stop might lead unpredictable be

[U-Boot] [PATCH] net: eth-uclass: call stop only for active devices

2019-02-20 Thread Keerthy
Currently stop is being called unconditionally without even checking if start is called. In case of multiple instances eth being present many devices might just be initialized without a start call in such cases stop might lead unpredictable behaviors including aborts and crashes. Hence add a check