[PATCH] NFC: fdp: i2c: Check for NULL prior to dereference

217 WARN_ON_ONCE(1); 218 return IRQ_NONE; " Reported-by: Dan Carpenter <dan.carpen...@oracle.com> Signed-off-by: Fabio Estevam <fabio.este...@freescale.com> --- drivers/nfc/fdp/i2c.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

[PATCH] brcmfmac: of: Include "of.h" header file

From: Fabio Estevam <fabio.este...@nxp.com> Include "of.h" header file to fix the following sparse warning: drivers/net/wireless/broadcom/brcm80211/brcmfmac/of.c:27:6: warning: symbol 'brcmf_of_probe' was not declared. Should it be static? Signed-off-by: Fabio Estevam <fa

brcm4330 fails to load on newer kernels

timeout (100): clkctl 0x50 So wlan0 never appears here. Does anyone have any suggestions about these different behaviours? Thanks, Fabio Estevam -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majo

Re: brcm4330 fails to load on newer kernels

the kernels I tested. Now I just need it to load brcmfmac module automatically, but this is a a separate issue I will investigate. Thanks a lot for your help! Fabio Estevam -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to major

BRCM4339 NVRAM file

from linux-firmware git tree, but could not find the nvram file: brcmfmac4339-sdio.txt. Does anyone know where brcmfmac4339-sdio.txt can be found? Thanks, Fabio Estevam -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@

Re: brcm4330 fails to load on newer kernels

Hi Arend, On Wed, Jul 27, 2016 at 5:51 PM, Arend van Spriel <arend.vanspr...@broadcom.com> wrote: > On 27-07-16 00:35, Fabio Estevam wrote: >> Hi, >> >> On a imx6sl-warp board with a brcm4330 I get the following results >> depending on the kernel version: >>

brcmfmac43430-sdio.bin in linux-firmware

-firmware repository? Thanks, Fabio Estevam -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: brcmfmac43430-sdio.bin in linux-firmware

Hi Arend, On Wed, Aug 24, 2016 at 4:22 PM, Arend Van Spriel wrote: >> Is this something you could help? > > I could, but this is handled by Cypress now. I have asked for firmware > release tag so I can release it. Excellent, thanks for your help!

Re: brcmfmac43430-sdio.bin in linux-firmware

Hi Arend, On Wed, Aug 24, 2016 at 4:22 PM, Arend Van Spriel wrote: > I could, but this is handled by Cypress now. I have asked for firmware > release tag so I can release it. Have you had a chance to release brcmfmac43430-sdio.bin? Thanks!

Re: brcmfmac43430-sdio.bin in linux-firmware

Hi Arend, On Wed, Aug 24, 2016 at 4:22 PM, Arend Van Spriel wrote: > I could, but this is handled by Cypress now. I have asked for firmware > release tag so I can release it. I see brcmfmac43430-sdio.bin in linux-firmware git tree now. Thanks a lot for your help!

Re: brcmfmac43430-sdio.bin in linux-firmware

Hi Arend, On Sat, Aug 6, 2016 at 12:15 PM, Fabio Estevam <feste...@gmail.com> wrote: > Hi, > > I managed to get Wifi working on a imx7 warp board, which has a BCM43430 > device. > > I used the firmware from the RaspberryPi repository: > https://github.com/RPi-Distro/f

Re: [PATCH 21/26] iwlwifi: mvm: print base HW address during init

On Tue, Jun 27, 2017 at 2:06 PM, Kalle Valo wrote: > "crouded sniffer logs", what's that? I think Luca meant 'crowded'.

Re: brcmfmac experiment for a specific use case - tx throughput maximization for slow CPU with glomming

Hi Jörg, On Thu, Jun 1, 2017 at 3:37 AM, Jörg Krause wrote: > I'm experiencing low throughput with a BCM43362 wifi chip attached via > SDIO to an i.MX28 [1,2]. After disabling some Kernel debug features I'm > getting now a TCP throughput of 12.5 Mbps for the wifi

[PATCH] ath10k: snoc: Remove owner assignment from platform_driver

From: Fabio Estevam <fabio.este...@nxp.com> Structure platform_driver does not need to set the owner field, as this will be populated by the driver core. Generated by scripts/coccinelle/api/platform_no_drv_owner.cocci. Signed-off-by: Fabio Estevam <fabio.este...@nxp.com> ---

Re: AP6335 with mainline kernel

Hi Arend, On Tue, Dec 5, 2017 at 12:58 PM, Vanessa Maegima wrote: > Hi Arend, > > Sorry for this! > > I updated the folder on https://drive.google.com/drive/folders/1fosahjL > N1KI5NKS59_aPZdHLpENPFHtK > > Thanks! Any ideas, please? Thanks

Re: Build iw for 32bit ARM

Hi Jakov, On Mon, Sep 3, 2018 at 11:20 AM, Jakov Simunic wrote: > Hi Steve, > We are building with ptxdist, we have a compiler for arm > (arm-linux-gnueabihf-gcc), I am not a total novice in this, and have already > written some ptxdist rules, but haven't done it with non-autoconfizzed >

Re: [PATCH 1/2] nfc: st21nfca: Check for devm_kzalloc() failure

Hi Samuel, Maybe this patch series got forgotten? On Sat, Mar 24, 2018 at 10:44 AM, Fabio Estevam <feste...@gmail.com> wrote: > From: Fabio Estevam <fabio.este...@nxp.com> > > devm_kzalloc() may fail, so we should better check for error and > propagate the error i

[PATCH 2/2] nfc: st21nfca: Remove unnecessary devm_kzalloc() cast

From: Fabio Estevam <fabio.este...@nxp.com> There is no need to use cast for the returned value from memory allocation functions, so remove the unnecessary cast. Detected via Coccinelle script: scripts/coccinelle/api/alloc/alloc_cast.cocci. Signed-off-by: Fabio Estevam <fabio.este..

[PATCH 1/2] nfc: st21nfca: Check for devm_kzalloc() failure

From: Fabio Estevam <fabio.este...@nxp.com> devm_kzalloc() may fail, so we should better check for error and propagate the error in the case of allocation failure. This avoids a potential NULL pointer dereference later on. Signed-off-by: Fabio Estevam <fabio.este...@nxp.com> ---

Re: AP6335 with mainline kernel

Hi Arend, On Wed, Nov 28, 2018 at 2:11 PM Arend Van Spriel wrote: > Does it mean there is a regression in 4.20 for this board? I haven't tested it with 4.20 yet. >> Only change I needed was the one suggested by Arend in the nvram file: >> changed boardflags3 entry.from 0x08101188 to 0x101188.

Re: AP6335 with mainline kernel

Hi Cameron, On Sat, Nov 17, 2018 at 5:10 PM Fabio Estevam wrote: > Could you please test the following patch against mainline that > implements this suggestion? > http://dark-code.bulix.org/4m18pb-507579 I finally managed to get Wifi working on the imx7d-pico-pi board using mainli

Re: AP6335 with mainline kernel

Hi Arend, On Wed, Nov 28, 2018 at 2:23 PM Fabio Estevam wrote: > I am not sure if I can access this signal via scope. Good news! I managed to make mx7d to generate the 32kHz clock and now Wifi works with the default nvram file value: boardflags3 0x08101188 Thanks a lot for your help!

Re: AP6335 with mainline kernel

ermail/linux-arm-kernel/2018-November/616048.html Thanks, Fabio Estevam

Re: AP6335 with mainline kernel

>; > }; Could you please test the following patch against mainline that implements this suggestion? http://dark-code.bulix.org/4m18pb-507579 Thanks, Fabio Estevam