1
0
Fork 0
remarkable-linux/drivers/net/wireless/broadcom
Arend Van Spriel a5cf79c3c3 brcmfmac: use brcmf_chip_name() to store name in revinfo
The chip id can either be four or five digits. For the chip name either
the hexadecimal value needs to be taken (four digits) or the decimal
value (five digits). The function brcmf_chip_name() does this conversion
so use it to store the name in driver revision info.

Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
Reviewed-by: Franky Lin <franky.lin@broadcom.com>
Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
(cherry picked from commit 756a2b3908 upstream)
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
2021-06-17 15:49:55 +02:00
..
b43 b43/leds: Ensure NUL-termination of LED name string 2018-09-05 09:26:39 +02:00
b43legacy b43legacy/leds: Ensure NUL-termination of LED name string 2018-09-05 09:26:39 +02:00
brcm80211 brcmfmac: use brcmf_chip_name() to store name in revinfo 2021-06-17 15:49:55 +02:00
Kconfig brcm80211: move under broadcom vendor directory 2015-11-18 11:24:22 +02:00
Makefile brcm80211: move under broadcom vendor directory 2015-11-18 11:24:22 +02:00