| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: I4c37af569b6011945860d2d7379e728ee69e133d
Reviewed-on: http://git.am.freescale.net:8181/34071
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Jianhua Xie <jianhua.xie@freescale.com>
Reviewed-by: Honghua Yin <Hong-Hua.Yin@freescale.com>
|
|
Require 64 bytes align.
Remove compilation warnings.
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: Ic97c690adfca42c8c9ac83de9d89b05ea32b3926
Reviewed-on: http://git.am.freescale.net:8181/33327
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Honghua Yin <Hong-Hua.Yin@freescale.com>
|
|
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: I52411e0d3cef00e5d8a3c7a45ec4fd9ac5907686
Reviewed-on: http://git.am.freescale.net:8181/33326
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Horia Ioan Geanta Neag <horia.geanta@freescale.com>
Reviewed-by: Honghua Yin <Hong-Hua.Yin@freescale.com>
|
|
CONFIG_FMAN_T4240 was eliminated.
Instead, there are now two flags representing FmanV3:
CONFIG_FMAN_V3H for FmanV3H arch and
CONFIG_FMAN_V3L for FmanV3L arch
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: Ia0de7b70a0c110e379edb38ee61779e7560979a7
Reviewed-on: http://git.am.freescale.net:8181/33329
Reviewed-by: Mandy Lavi <Mandy.Lavi@freescale.com>
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Honghua Yin <Hong-Hua.Yin@freescale.com>
|
|
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: I4110d5a606dd4d1e266fdb28d3ead1ba84382c22
Reviewed-on: http://git.am.freescale.net:8181/33328
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Mandy Lavi <Mandy.Lavi@freescale.com>
Reviewed-by: Honghua Yin <Hong-Hua.Yin@freescale.com>
|
|
This allows users to pass in additional compiler flags through the
environment variable EXTRA_CFLAGS, e.g.
make EXTRA_CFLAGS=-Wno-error
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Change-Id: I36513506ee1671c31bb076e9b73c2e8e2442cf4f
Reviewed-on: http://git.am.freescale.net:8181/33146
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Honghua Yin <Hong-Hua.Yin@freescale.com>
|
|
Several patches in drivers/crypto/caam starting with
fa9659cd4d3f40cead6263986cc235f3e67ab872 changed the API for error
source reporting.
Signed-off-by: Cristian Stoica <cristian.stoica@freescale.com>
Change-Id: I9a2339272251b0e7a67ae8fe1fede5608e1aedc9
Reviewed-on: http://git.am.freescale.net:8181/25119
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Richard Schmitt <richard.schmitt@freescale.com>
|
|
DPA Shared Ethernet has no plan to support NAPI so
far, so setup a dummy net device for NAPI.
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: I2cdd19c0aa7cfe64a0a7fb4f1397b5a0e24cc5f6
Reviewed-on: http://git.am.freescale.net:8181/21951
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Jianhua Xie <jianhua.xie@freescale.com>
Reviewed-by: Shengzhou Liu <Shengzhou.Liu@freescale.com>
|
|
Fqs back to outbound OP must have a higher priority compared
to fqs from core to outbound OP, otherwise the buffer will
be exhausted.
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: Ia4de53493d06768f86c617340927e2af4d722011
Reviewed-on: http://git.am.freescale.net:8181/21442
Reviewed-by: Jianhua Xie <jianhua.xie@freescale.com>
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Tested-by: Shengzhou Liu <Shengzhou.Liu@freescale.com>
Reviewed-by: Shengzhou Liu <Shengzhou.Liu@freescale.com>
|
|
This can avoid buffer pool is exhausted by others,
so that it can avoid deadlock for outbound OP.
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: I6fd1a604e0ae004837e02a4ac925360967da9827
Reviewed-on: http://git.am.freescale.net:8181/21441
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Jianhua Xie <jianhua.xie@freescale.com>
Reviewed-by: Shengzhou Liu <Shengzhou.Liu@freescale.com>
|
|
It maybe a hw bug.
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: I7f328e7f325e886ee1e1c2bd468117b1b043dd9a
Reviewed-on: http://git.am.freescale.net:8181/21440
Reviewed-by: Jianhua Xie <jianhua.xie@freescale.com>
Tested-by: Shengzhou Liu <Shengzhou.Liu@freescale.com>
Reviewed-by: Shengzhou Liu <Shengzhou.Liu@freescale.com>
|
|
CAPWAP stands for Control and Provisioning of Wireless Access Points.
CAPWAP is a standard, interoperable protocol that enables a controller
to manage a collection of wireless access points.
There are three drivers in Kernel Space: CAPWAP Domain driver,
CAPWAP Bridge driver and CAPWAP Tunnel driver.
CAPWAP Domain Driver implements configuration for CAPWAP Domain,
including PCD configuration and FQs setup. User must configure and
initialize CAPWAP domain before CAPWAP Tunnel and CAPWAP Bridge works.
CAPWAP Tunnel Driver is a misc device driver, which registers four
misc devices for four CAPWAP tunnels:
fsl-capwap-ctrl-dtls,
fsl-capwap-ctl-n-dtls,
fsl-capwap-data-dtls,
fsl-capwap-data-n-dtls.
The misc device provides file-operation to transmit/receive DTLS/non-DTLS
packets. For example, read from the device fsl-capwap-ctrl-dtls can receive
DTLS control packet; Write to the device fsl-capwap-ctrl-dtls can transmit
DTLS control packet.
The CAPWAP Bridge Driver is also a misc device driver; it can bridge packets
between PCIe NIC and CAPWAP data tunnels.
To support capwap drivers, there should be a shared ethernet port in dts file
to use as CAPWAP Ethernet port.
Signed-off-by: Pan Jiafei <Jiafei.Pan@freescale.com>
Change-Id: I7c99191156ebee5dd43673d20fb5c8469a780546
Reviewed-on: http://git.am.freescale.net:8181/21438
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Jianhua Xie <jianhua.xie@freescale.com>
Reviewed-by: Shengzhou Liu <Shengzhou.Liu@freescale.com>
|
