Searched hist:"8804 ea9e" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/drivers/net/wireless/quantenna/qtnfmac/pcie/ |
H A D | pcie.c | 8804ea9e Fri Oct 05 05:11:45 CDT 2018 Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> qtnfmac: drop redundant data copy in control path
Command responses and events from the firmware are copied twice in control path: at first in shm core (qtnf_shm_handle_new_data) and then in pcie bus drivers (qtnf_pcie_control_rx_callback). There is no need to copy this data twice, it can be done only once in rx callbacks.
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> 8804ea9e Fri Oct 05 05:11:45 CDT 2018 Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> qtnfmac: drop redundant data copy in control path Command responses and events from the firmware are copied twice in control path: at first in shm core (qtnf_shm_handle_new_data) and then in pcie bus drivers (qtnf_pcie_control_rx_callback). There is no need to copy this data twice, it can be done only once in rx callbacks. Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
|
/openbmc/linux/drivers/net/wireless/quantenna/qtnfmac/ |
H A D | shm_ipc.h | 8804ea9e Fri Oct 05 05:11:45 CDT 2018 Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> qtnfmac: drop redundant data copy in control path
Command responses and events from the firmware are copied twice in control path: at first in shm core (qtnf_shm_handle_new_data) and then in pcie bus drivers (qtnf_pcie_control_rx_callback). There is no need to copy this data twice, it can be done only once in rx callbacks.
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> 8804ea9e Fri Oct 05 05:11:45 CDT 2018 Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> qtnfmac: drop redundant data copy in control path Command responses and events from the firmware are copied twice in control path: at first in shm core (qtnf_shm_handle_new_data) and then in pcie bus drivers (qtnf_pcie_control_rx_callback). There is no need to copy this data twice, it can be done only once in rx callbacks. Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
|
H A D | shm_ipc.c | 8804ea9e Fri Oct 05 05:11:45 CDT 2018 Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> qtnfmac: drop redundant data copy in control path
Command responses and events from the firmware are copied twice in control path: at first in shm core (qtnf_shm_handle_new_data) and then in pcie bus drivers (qtnf_pcie_control_rx_callback). There is no need to copy this data twice, it can be done only once in rx callbacks.
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> 8804ea9e Fri Oct 05 05:11:45 CDT 2018 Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> qtnfmac: drop redundant data copy in control path Command responses and events from the firmware are copied twice in control path: at first in shm core (qtnf_shm_handle_new_data) and then in pcie bus drivers (qtnf_pcie_control_rx_callback). There is no need to copy this data twice, it can be done only once in rx callbacks. Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
|