/openbmc/linux/drivers/net/ethernet/qlogic/qed/ |
H A D | qed_mcp.h | 18a69e36 Tue Mar 28 07:12:53 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Send pf-flr as part of initialization
During HW initialization, driver would set various registers to their needed values - but it assumes all registers start at their reset-value, so there's no need to re-configure a register's default value.
This assumption might be incorrect, e.g., in case of preboot driver running and initializing the driver prior to our driver.
To overcome this, we now ask management firmware to initiate a PF-flr early during the initialization sequence. That would return everything in the PF's scope back to default and prevent previous configurations from still being applied.
Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net> 18a69e36 Tue Mar 28 07:12:53 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Send pf-flr as part of initialization During HW initialization, driver would set various registers to their needed values - but it assumes all registers start at their reset-value, so there's no need to re-configure a register's default value. This assumption might be incorrect, e.g., in case of preboot driver running and initializing the driver prior to our driver. To overcome this, we now ask management firmware to initiate a PF-flr early during the initialization sequence. That would return everything in the PF's scope back to default and prevent previous configurations from still being applied. Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | qed_hsi.h | 18a69e36 Tue Mar 28 07:12:53 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Send pf-flr as part of initialization
During HW initialization, driver would set various registers to their needed values - but it assumes all registers start at their reset-value, so there's no need to re-configure a register's default value.
This assumption might be incorrect, e.g., in case of preboot driver running and initializing the driver prior to our driver.
To overcome this, we now ask management firmware to initiate a PF-flr early during the initialization sequence. That would return everything in the PF's scope back to default and prevent previous configurations from still being applied.
Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net> 18a69e36 Tue Mar 28 07:12:53 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Send pf-flr as part of initialization During HW initialization, driver would set various registers to their needed values - but it assumes all registers start at their reset-value, so there's no need to re-configure a register's default value. This assumption might be incorrect, e.g., in case of preboot driver running and initializing the driver prior to our driver. To overcome this, we now ask management firmware to initiate a PF-flr early during the initialization sequence. That would return everything in the PF's scope back to default and prevent previous configurations from still being applied. Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | qed_mcp.c | 18a69e36 Tue Mar 28 07:12:53 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Send pf-flr as part of initialization
During HW initialization, driver would set various registers to their needed values - but it assumes all registers start at their reset-value, so there's no need to re-configure a register's default value.
This assumption might be incorrect, e.g., in case of preboot driver running and initializing the driver prior to our driver.
To overcome this, we now ask management firmware to initiate a PF-flr early during the initialization sequence. That would return everything in the PF's scope back to default and prevent previous configurations from still being applied.
Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net> 18a69e36 Tue Mar 28 07:12:53 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Send pf-flr as part of initialization During HW initialization, driver would set various registers to their needed values - but it assumes all registers start at their reset-value, so there's no need to re-configure a register's default value. This assumption might be incorrect, e.g., in case of preboot driver running and initializing the driver prior to our driver. To overcome this, we now ask management firmware to initiate a PF-flr early during the initialization sequence. That would return everything in the PF's scope back to default and prevent previous configurations from still being applied. Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | qed_dev.c | 18a69e36 Tue Mar 28 07:12:53 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Send pf-flr as part of initialization
During HW initialization, driver would set various registers to their needed values - but it assumes all registers start at their reset-value, so there's no need to re-configure a register's default value.
This assumption might be incorrect, e.g., in case of preboot driver running and initializing the driver prior to our driver.
To overcome this, we now ask management firmware to initiate a PF-flr early during the initialization sequence. That would return everything in the PF's scope back to default and prevent previous configurations from still being applied.
Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net> 18a69e36 Tue Mar 28 07:12:53 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Send pf-flr as part of initialization During HW initialization, driver would set various registers to their needed values - but it assumes all registers start at their reset-value, so there's no need to re-configure a register's default value. This assumption might be incorrect, e.g., in case of preboot driver running and initializing the driver prior to our driver. To overcome this, we now ask management firmware to initiate a PF-flr early during the initialization sequence. That would return everything in the PF's scope back to default and prevent previous configurations from still being applied. Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|