[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20181109.164751.191496935220130040.davem@davemloft.net>
Date: Fri, 09 Nov 2018 16:47:51 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: tanhuazhong@...wei.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
salil.mehta@...wei.com, yisen.zhuang@...wei.com,
linuxarm@...wei.com
Subject: Re: [Patch net-next 00/11] add code optimization for VF reset and
some new reset feature
From: Huazhong Tan <tanhuazhong@...wei.com>
Date: Fri, 9 Nov 2018 22:07:45 +0800
> Currently hardware supports below reset:
> 1. VF reset: triggered by sending cmd to IMP(Integrated Management
> Processor). Only reset specific VF function and do not affect
> other PF or VF.
> 2. PF reset: triggered by sending cmd to IMP. Only reset specific PF
> and it's VF.
> 3. PF FLR: triggered by PCIe subsystem. Only reset specific PF and
> it's VF.
> 4. VF FLR: triggered by PCIe subsystem. Only reset specific VF function
> and do not affect other PF or VF.
> 5. Core reset: triggered by writing to register. Reset most hardware
> unit, such as SSU, which affects all the PF and VF.
> 6. Global reset: triggered by writing to register. Reset all hardware
> unit, which affects all the PF and VF.
> 7. IMP reset: triggered by IMU(Intelligent Management Unit) when
> IMP is not longer feeding IMU's watchdog. IMU will reload the IMP
> firmware and IMP will perform global reset after firmware reloading,
> which affects all the PF and VF.
>
> Current driver only support PF/VF reset, incomplete core and global
> reset(lacking the vf reset handling). So this patchset adds complete
> reset support in hns3 driver.
>
> Also, this patchset contains some optimization related to reset.
Series applied, thank you.
Powered by blists - more mailing lists