summaryrefslogtreecommitdiffstats
path: root/target/linux/qualcommax
Commit message (Collapse)AuthorAgeFilesLines
...
* qualcommax: set phy-mode to sgmii for QCA8081Chukun Pan2024-03-184-0/+4
| | | | | | | The dp5 node uses psgmii by default, corrected the phy-mode to sgmii for the qca8081 phy. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* qualcommax: dts: cleanup whitespaceChukun Pan2024-03-188-19/+20
| | | | | | | Replace blanks with tabs, remove extra blank lines. Also add new lines as appropriate. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* qualcommax: ipq807x: fix LEDs on Buffalo WXR-5950AX12INAGAKI Hiroshi2024-03-171-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Buffalo WXR-5590AX12, some LEDs don't have "function" property and only "color" property is available for the newer binding of LED on Linux Kernel. 2e659930d3 ("qualcommax: drop redundant label with new LED color/function format") removes "label" property from LEDs, then, multiple "<color>:" (ex.: "white:"/"red:") will be appeared as LED names and renamed to "<color>:_<num>" ("ex.: "white:_1", "green:_2", ...) by kernel. logs: [ 5.372863] leds-gpio leds: Led white: renamed to white:_1 due to name collision [ 5.375796] leds-gpio leds: Led red: renamed to red:_1 due to name collision /sys/class/leds: root@OpenWrt:/# ls /sys/class/leds/ red: red:power white: white:power red:_1 red:wlan white:_1 white:wlan Fix this issue by adding missing "function" property to LEDs on Buffalo WXR-5950AX12. Note: there are no appropriate functions in dt-bindings/leds/common.h for some LEDs, so use the hardcoded strings for them instead. Fixes: 2e659930d3 ("qualcommax: drop redundant label with new LED color/function format") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* qualcommax: ipq807x: fix LEDs on QNAP QHora-301WINAGAKI Hiroshi2024-03-172-6/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On QNAP QHora-301W, all LEDs don't have "function" property and only "color" property is available for the newer binding of LED on Linux Kernel. 2e659930d3 ("qualcommax: drop redundant label with new LED color/function format") removes "label" property from LEDs, then, multiple "<color>:" (ex.: "amber:"/"green:"/"red:") will be appeared as LED names and renamed to "<color>:_<num>" ("ex.: "green:_1", "green:_2", ...) by kernel. logs: [ 4.246494] leds-gpio leds: Led green: renamed to green:_1 due to name collision [ 4.248978] leds-gpio leds: Led green: renamed to green:_2 due to name collision [ 4.256345] leds-gpio leds: Led green: renamed to green:_3 due to name collision [ 4.263770] leds-gpio leds: Led green: renamed to green:_4 due to name collision [ 4.271105] leds-gpio leds: Led amber: renamed to amber:_1 due to name collision [ 4.278487] leds-gpio leds: Led green: renamed to green:_5 due to name collision [ 4.285856] leds-gpio leds: Led amber: renamed to amber:_2 due to name collision [ 4.293257] leds-gpio leds: Led green: renamed to green:_6 due to name collision [ 4.300616] leds-gpio leds: Led amber: renamed to amber:_3 due to name collision [ 4.308002] leds-gpio leds: Led green: renamed to green:_7 due to name collision [ 4.315384] leds-gpio leds: Led amber: renamed to amber:_4 due to name collision [ 4.322760] leds-gpio leds: Led green: renamed to green:_8 due to name collision [ 4.330135] leds-gpio leds: Led amber: renamed to amber:_5 due to name collision /sys/class/leds: amber: amber:_4 green:_2 green:_6 amber:_1 green:_5 green:_3 green:_7 amber:_2 green: green:_4 green:_8 amber:_3 green:_1 green:_5 red: Fix this issue by adding missing "function" (and "function-enumerator") property to LEDs on QNAP QHora-301W. Note: there are no appropriate functions in dt-bindings/leds/common.h for some LEDs, so use the hardcoded strings for them instead. Fixes: 2e659930d3 ("qualcommax: drop redundant label with new LED color/function format") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* qualcommax: ipq60xx: mango-dvk: fix QCA8081 reset timingsMantas Pucka2024-03-151-0/+2
| | | | | | | Add missing reset delay properties for QCA8081 PHY. Without delays PHY operation is unreliable. Signed-off-by: Mantas Pucka <mantas@8devices.com>
* qualcommax: ipq60xx: add support for netgear wax214Dirk Buchwalder2024-03-055-0/+194
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Netgear WAX214 is a 802.11 ax dual-band AP with PoE. (similar to Engenius EWS357APV3) Specifications: • CPU: Qualcomm IPQ6010 Quad core Cortex-A53 • RAM: 512MB of DDR3 • Storage: 128MB NAND (Macronix MX30UF1G18AC) • Ethernet: 1x 1G RJ45 port (QCA8072) PoE • WIFI: 2.4GHz: Qualcomm QCN5022 2x2 802.11b/g/n/ax 574 Mbps PHY rate 5GHz: Qualcomm QCN5052 2x2 802.11a/b/g/n/ac/ax 1201 PHY rate • LEDs: 4 x GPIO-controlled LEDs - 1 Power LED (orange) - 1 LAN LED (blue) - 1 WIFI 5g LED (blue) - 1 WIFI 2g LED (blue) black_small_square Buttons: 1x soft reset black_small_square Power: 12V DC jack or PoE (802.3af ) An populated serial header is onboard, format is 1.25mm 4p (DF13A-4P-1.25H) RX/TX is working, bootwait is active, secure boot is not enabled. The root password of the stock firmware is unknown, but failsafe mode can be entered to reset the password. Installation Instructions: - obtain serial access - stop auto boot (press "4", Entr boot command line interface) - setenv active_fw 0 (to boot from the primary rootfs, or set to 1 to boot from the secondary rootfs partition) - saveenv - tftpboot the initramfs image - bootm - copy openwrt-qualcommax-ipq60xx-netgear_wax214-squashfs-factory.ubi to the device - write the image to the NAND: - cat /proc/mtd and look for rootfs partition (should be mtd11, or mtd12 if you choose active_fw 1) - ubiformat /dev/mtd11 -f -y openwrt-qualcommax-ipq60xx-netgear_wax214-squashfs-factory.ubi - reboot Note: the firmware is senao-based. But I was unable to build a valid senao-header into the image. Maybe they changed the header format and senaoFW isn't working any more. Signed-off-by: Dirk Buchwalder <buchwalder@posteo.de>
* qualcommax: enable DEBUG_BUGVERBOSERobert Marko2024-03-011-0/+2
| | | | | | | | | | Enable DEBUG_BUGVERBOSE by default on qualcommax as without it once BUG() is called we will not get any output other than "------------[ cut here ]------------" which is not usefull at all, so since we dont have kernel size constraints lets enable it by default. Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: ipq807x: add support for Linksys MX5300Paweł Owoc2024-02-236-2/+567
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware specification: ======== SoC: Qualcomm IPQ8072A Flash: 512MB (Winbond W29N04GZBIBA) RAM: 1GB (2x Nanya DDR3L NT5CC256M16ER-EK) Ethernet: 5x 10/100/1000Mbps (Qualcomm QCA8075) WiFi1: 5GHz ac 4x4 (Qualcomm QCA9984 + Skyworks SKY85746-11) - channels 100-169 WiFi2: 5GHz ax 4x4 (Qualcomm QCN5054 + Skyworks SKY85755-11) - channels 36-64 WiFi3: 2.4GHz ax 4x4 (Qualcomm QCN5024 + Skyworks SKY8340-11) IoT: Bluetooth 5, Zigbee and Thread (Qualcomm QCA4024 + Skyworks SE2433T-R) IoT Flash: 4MB (Macronix MX25R3235F) RTC: ST M41T00S LED: 1x RGB status (NXP PCA9633) USB: 1x USB 3.0 Button: WPS, Reset Flash instructions: ======== 1. Manually upgrade firmware using openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin image. More details can be found here: https://www.linksys.com/hk/support-article?articleNum=274497 After first boot check actual partition: - fw_printenv -n boot_part and install firmware on second partition using command in case of 2: - mtd -r -e kernel -n write openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin kernel and in case of 1: - mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin alt_kernel 2. Installation using serial connection from OEM firmware (default login: root, password: admin): - fw_printenv -n boot_part In case of 2: - flash_erase /dev/mtd21 0 0 nandwrite -p /dev/mtd21 openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin or in case of 1: - flash_erase /dev/mtd23 0 0 nandwrite -p /dev/mtd23 openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin After first boot install firmware on second partition: - mtd -r -e kernel -n write openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin kernel or: - mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin alt_kernel 3. Installation from initramfs image using USB FAT32 formatted drive: Stop u-boot and run: - usb start && fatload usb 0:1 $loadaddr openwrt-qualcommax-ipq807x-linksys_mx5300-initramfs-uImage.itb && bootm $loadaddr Write firmware to the flash from initramfs: - mtd -e kernel -n write openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin kernel and: - mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq807x-linksys_mx5300-squashfs-factory.bin alt_kernel 4. Back to the OEM firmware: - mtd -e kernel -n write FW_MX5300_1.1.9.200251_prod.img kernel and: - mtd -r -e alt_kernel -n write FW_MX5300_1.1.9.200251_prod.img alt_kernel 5. USB recovery: - fw_setenv usbimage 'openwrt-qualcommax-ipq807x-linksys_mx5300-initramfs-uImage.itb' fw_setenv bootusb 'usb start && fatload usb 0:1 $loadaddr $usbimage && bootm $loadaddr' fw_setenv bootcmd 'run bootusb; aq_load_fw && if test $auto_recovery = no; then bootipq; elif test $boot_part = 1; then run bootpart1; else run bootpart2; fi' Notes: ======== IoT device is accesible over spi. Not yet supported. Signed-off-by: Paweł Owoc <frut3k7@gmail.com> Reviewed-by: Robert Marko <robimarko@gmail.com>
* qualcommax: ipq807x: add patch for QUP4 SPI nodeRobert Marko2024-02-234-5/+43
| | | | | | | Add node to support the QUP4 SPI controller inside of IPQ8074. Some devices use this bus to communicate to a Bluetooth controller. Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: ipq807x: reordering, combine the same commandsPaweł Owoc2024-02-231-3/+1
| | | | | | Reordering, combine the same commands for ipq807x devices Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
* qualcommax: ipq60xx: Add 8devices Mango DVKMantas Pucka2024-02-215-0/+437
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8devices Mango DVK is a single board computer / devkit for 8devices Mango system-on-module (SoM). Specifications: * CPU: Qualcomm IPQ6010 Quad core Cortex-A53 1.8GHz * RAM: 512 MB * Storage: * 32 MB serial NOR flash (on SoM) * 256 MB parallel NAND flash (on DVK) * Ethernet: * 2x1G RJ45 ports(QCA8072 or QCA8075) * 1x2.5G RJ45 port (QCA8081) * 1xSFP (shares SGMII with QCA8081) * Switch: Qualcomm Atheros IPQ6010 * WLAN: * 2.4GHz: QCN5121 2x2 802.11b/g/n/ax 574 Mbps PHY rate * 5GHz: QCN5152 2x2 802.11a/n/ac/ax 1201 Mbps PHY rate * USB: * 1x USB3.0 Type-A port * 1x USB2.0 available at mini PCIe slot * PCIe: 1x mini PCIe slot 1xLane Gen3 (8GT/s) * SD/eMMC (on a single shared bus - only one can be active): * micro SD slot * eMMC module connector * LEDs: * Green power led (not controllable) * Green 2.4GHz radio led (GPIO 67) * Green 5GHz radio led (GPIO 66) * Buttons: * 1x (WPS GPIO79) button * GPIOs: 2.54mm header brings out 18 GPIOs (1.8V level) * UART: 4-pin UART header (3.3V level) * 115200 8N1, 3.3V-Tx-Rx-GND (3.3V is pin 1 close to boot-switch SW2) * Power: * PoE IN on 2.5G port (passive 24-48V) * DC power terminal (12-58V) Installation instructions: Vendor image format is compatible with squashfs-sysupgrade image. Run: sysupgrade -n -F openwrt-qualcommax-ipq60xx-8devices_mango-dvk-squashfs-sysupgrade.bin Signed-off-by: Mantas Pucka <mantas@8devices.com>
* qualcommax: ipq60xx: set correct PHY mode for port 0-4Mantas Pucka2024-02-211-4/+4
| | | | | | | | | | | | | | [port 8ed390a (qualcommax: set correct PHY mode for port 0-4) to ipq60xx] Port 0-4 have the mode set to SGMII instead of PSGMII. Now that we use he upstream qca807x driver, this conflicts with the qca SSDK driver that expects the mode to be PSGMII as for not integrated driver, it does refer to the real PHY mode. Update the entry for port 0-4 to PSGMII to solve warning from qca SSDK in ipq6018-ess.dtsi. Signed-off-by: Mantas Pucka <mantas@8devices.com>
* qualcommax: ipq807x: skip factory.ubi image for MX4200Paweł Owoc2024-02-211-2/+0
| | | | | | Skip building not used factory.ubi image Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
* qualcommax: ipq807x: remove duplicated sysupgrade image definitionsPaweł Owoc2024-02-212-8/+5
| | | | | | Image sysupgrade.bin is defined by default and there is no need to define it. Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
* qualcommax: ipq807x: fix variable definitionPaweł Owoc2024-02-212-8/+8
| | | | | | | | Fix variable definition, prevent displaying warnings: - warning: overriding recipe for target - warning: ignoring old recipe for target Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
* qualcommax: backport more changes for ipq6018 and ipq8074Chukun Pan2024-02-1948-126/+1810
| | | | | | | | - Mark patches as upstream - Backport more upstream changes - Handle conflicts and refresh patches Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* qualcommax: ipq807x: wax630: correct UNIPHY2 MAC modeRobert Marko2024-02-171-1/+1
| | | | | | | | UNIPHY2 on the WAX630 is connected to a QCA8081 PHY which is only 2.5G and it does not support using USXGMII at all but rather only SGMII or SGMII+. Tested-by: Kristian Skramstad <kristian+github@83.no> Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: ipq807x: correct PHY mode for AQRRobert Marko2024-02-174-0/+5
| | | | | | | | | | | | | | Interfaces that have AQR-s attached to them are using USXGMII and not just the default SGMII. This was fine until SSDK added some sanity checking and now on Qnap 301W it would fail with: [ 24.740197] nss-dp 3a001800.dp5 10g-1 (uninitialized): failed to connect to phy device [ 24.740264] nss-dp: probe of 3a001800.dp5 failed with error -14 Since this is not Qnap 301W specific lets fix it subtarget wide by declaring the correct PHY mode for 10G AQR-s. Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: ipq807x: 301w: correct PHY mode for AQRRobert Marko2024-02-171-0/+2
| | | | | | | | | | | | | Interfaces that have AQR-s attached to them are using USXGMII and not just the default SGMII. This was fine until SSDK added some sanity checking and now on Qnap 301W it would fail with: [ 24.740197] nss-dp 3a001800.dp5 10g-1 (uninitialized): failed to connect to phy device [ 24.740264] nss-dp: probe of 3a001800.dp5 failed with error -14 So, lets fix 10G AQR ports by declaring the correct PHY mode. Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: AW1000: add qca8081 PHY LED configurationChukun Pan2024-02-162-0/+14
| | | | | | | | Since we can configure the PHY LED of the qca8081, add a configuration for this device. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn> Reviewed-by: Robert Marko <robimarko@gmail.com>
* qualcommax: AW1000: sync qca807x PHY dts changesChukun Pan2024-02-161-14/+27
| | | | | | | | | The dts of Arcadyan AW1000 forgot to convert qca807x PHY to PHY package implementation. This commit fix it. Fixes: 0ab4b92 ("qualcommax: convert qca807x PHY to PHY package implementation") Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn> Reviewed-by: Robert Marko <robimarko@gmail.com>
* ipq807x: add support for CMCC RM2-6Chukun Pan2024-02-156-4/+335
| | | | | | | | | | | | | | | | | | Hardware specifications: SoC: Qualcomm IPQ8070A RAM: 512MB of DDR3 Flash: 256MB Micron NAND Ethernet: 2x 1G RJ45 port WiFi1: QCN5024 2x2 2.4GHz WiFi2: QCN5054 2x2 5GHz Fan: 1x GPIO controlled Button: Reset, WPS Flash instructions: Upload factory.bin in stock firmware's upgrade page. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn> Reviewed-by: Robert Marko <robimarko@gmail.com>
* qualcommax: ipq807x: MX4200 convert qca807x PHY to new implementationPaweł Owoc2024-02-151-15/+22
| | | | | | | Convert qca807x PHY to new implementation like for other devices. Signed-off-by: Paweł Owoc <frut3k7@gmail.com> Reviewed-by: Robert Marko <robimarko@gmail.com>
* qualcommax: remove usage of malibu_first_phy_addrRobert Marko2024-02-152-19/+0
| | | | | | | | Now that Malibu (QCA807x) PHY is using the upstream driver, we dont need support to define address of the first PHY in package, so remove the malibu_first_phy_addr DTS property. Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: apply special PHY LEDs configuration for Xiaomi AX9000Christian Marangi2024-02-112-0/+52
| | | | | | | | | Xiaomi AX9000 apply a special PHY LEDs configuration where the unique green LED for each qca807x PHY port is turned on also on 1000Mbps link. Apply this special configuration to reflect original implementation. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: apply special PHY LEDs configuration for Xiaomi AX3600Christian Marangi2024-02-112-1/+64
| | | | | | | | | | | | Xiaomi AX3600 apply a special PHY LEDs configuration where the unique green LED for each qca807x PHY port is turned on also on 1000Mbps link. Apply this special configuration to reflect original implementation. Also enable CONFIG_PHYLIB_LEDS to actually expose the PHY LEDs if defined in DT. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: convert qca807x PHY to PHY package implementationChristian Marangi2024-02-1112-144/+244
| | | | | | | | Convert every qca807x PHY definition in DT to new PHY package implementation to correctly support applying fixup for the correct PHY mode. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: set correct PHY mode for port 0-4Christian Marangi2024-02-111-4/+4
| | | | | | | | | | | | Port 0-4 have the mode set to SGMII instead of PSGMII. Now that we use the upstream qca807x driver, this conflicts with the qca SSDK driver that expects the mode to be PSGMII as for not integrated driver, it does refer to the real PHY mode. Update the entry for port 0-4 to PSGMII to solve warning from qca SSDK in ipq8074-ess.dtsi. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: enable qca807x PHY driverChristian Marangi2024-02-111-0/+1
| | | | | | | | IPQ807x have integrated qca8074 PHY supported by the upstream qca807x driver. Enable it to use it instead of the downstream qca SSDK variant. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: fix wrong PHY node definition for Buffalo WXR-5950AX12Christian Marangi2024-02-111-23/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit d737ae99cb36 ("qualcommax: Fix Buffalo WXR-5950AX12 Ethernet DTS") reverted the switch bmp to the original OEM definition and added the malibu_first_phy_addr property. Problem is that OEM bmp definition is wrong and actually doesn't make sense, probably caused by copy-paste of the QCOM reference DTS without actually setting real values. What actually fixed the regression was adding the malibu_first_phy_addr as without it the MALIBU PHY was actually not correctly configured and the Aquantia PHY were actually configured as MALIBU PHY. Fix all these wrong PHY definition. The BPM is reverted and the following fixes are applied: - Drop ESS_PORT1 as it's not actually attached in HW. - Move ESS_PORT5 AGAIN from lan to wan. This refer to the first Aquantia PHY that is labelled "wan" - Move ESS_PORT6 AGAIN from wan to lan. This refer to the second Aquantia PHY that is labelled "lan1". Also PHY tag in MDIO node are renumbered to start from 0 following the tagging standard used also in other dts and the not attached one (reg 0x18 and reg 0x1c) are correctly dropped. Definition for port@1 in phyinfo is dropped as it doesn't exist. dp nodes are updated to reference the new PHY tag numbering. Fixes: d737ae99cb36 ("qualcommax: Fix Buffalo WXR-5950AX12 Ethernet DTS") Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: refresh kernel patchesChristian Marangi2024-02-097-7/+7
| | | | | | | | | Refresh kernel patches changed from the just introduced ipq60xx new subtarget. Patch automatically refreshed with make target/linux/refresh. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: move generic image recipes to target MakefileRobert Marko2024-02-092-25/+25
| | | | | | | These recipes are generic and will be used for other subtargets, so lets move them to the target Makefile so they can reused. Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: add ipq60xx supportMantas Pucka2024-02-0930-1/+2085
| | | | | | | | | | | | | Introduce support for the Qualcomm IPQ60xx SoC. WiFi support still has to be handled and correctly fix hence this is currently marked as source-only to have a solid base to progress on correct support of this and hope Upstream QUIC publish newers ath11k drivers for this SoC. Co-developed-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Mantas Pucka <mantas@8devices.com> [ improve commit description, add SoB for Robert, make it source-only ] Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: convert to new LED color/function format where possibleChristian Marangi2024-02-074-5/+14
| | | | | | | | Initial conversion to new LED color/function format and drop label format where possible. The same label is composed at runtime. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: drop redundant label with new LED color/function formatChristian Marangi2024-02-077-51/+0
| | | | | | | | | Drop redundant label with new LED color/function format declared. This was needed previously when the new format wasn't supported by leds.sh functions script. Now that is supported this property can be removed in favor of the new format. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: enable PHYLIB LED supportRobert Marko2024-02-051-0/+4
| | | | | | | | CONFIG_PHYLIB_LEDS is required in order for phylib to probe the DT for LEDs attached to PHY-s. Fixes: 75ad5c2 ("qualcommax: switch to qca8081 upstream PHY driver") Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: enable back QCA808X PHY driverChristian Marangi2024-02-021-0/+1
| | | | | | | | | Commit 997acc7f86ca ("generic: 6.1: backport at803x split patches") didn't enable back QCA808x PHY driver after the introduction of the at803x driver split. Fixes: 997acc7f86ca ("generic: 6.1: backport at803x split patches") Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: dts: add reset delay to qca8081 phyChukun Pan2024-01-308-1/+12
| | | | | | | | The qca8081 phy needs to set the reset delay time, otherwise it will not be detected by the mdio bus. Fixes: 75ad5c2 ("qualcommax: switch to qca8081 upstream PHY driver") Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* qualcommax: switch to qca8081 upstream PHY driverChristian Marangi2024-01-275-0/+68
| | | | | | | | Switch to qca8081 upstream PHY. Update every device that have LEDs attached to the qca8081 PHY to follow new way of defining the LEDs and add original OEM configuration. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: 301w: provide AQR FW via NVMEM cellsRobert Marko2024-01-261-1/+97
| | | | | | | | | In order to get rid of having to modify U-boot bootcmd and having U-boot load the Aquantia PHY-s firmware lets use some of the free space on SPI-NOR to add a second ethphyfw partition and be able to load AQR FW via NVMEM cells. Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: 301w: correct AQR reset GPIO-sRobert Marko2024-01-261-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It seems that the reset GPIO-s defined for the two AQR PHY-s are actually reversed. Manually testing confirmed that GPIO44 is actually reset GPIO of AQR at 0, while GPIO59 is reset of AQR at 8: root@OpenWrt:~# mdio 9* DEV PHY-ID LINK 0x00 0x00000000 down 0x08 0x00000000 down 0x10 0x004dd0b1 down 0x11 0x004dd0b1 down 0x12 0x004dd0b1 down 0x13 0x004dd0b1 up 0x14 0x004dd0b1 down 0x15 0x04820a05 down root@OpenWrt:~# gpioset gpiochip0 44=0 root@OpenWrt:~# mdio 9* DEV PHY-ID LINK 0x08 0x00000000 down 0x10 0x004dd0b1 down 0x11 0x004dd0b1 down 0x12 0x004dd0b1 down 0x13 0x004dd0b1 up 0x14 0x004dd0b1 down 0x15 0x04820a05 down root@OpenWrt:~# gpioset gpiochip0 44=1 root@OpenWrt:~# mdio 9* DEV PHY-ID LINK 0x00 0x00000000 down 0x08 0x00000000 down 0x10 0x004dd0b1 down 0x11 0x004dd0b1 down 0x12 0x004dd0b1 down 0x13 0x004dd0b1 up 0x14 0x004dd0b1 down 0x15 0x04820a05 down root@OpenWrt:~# gpioset gpiochip0 59=0 root@OpenWrt:~# mdio 9* DEV PHY-ID LINK 0x00 0x00000000 down 0x10 0x004dd0b1 down 0x11 0x004dd0b1 down 0x12 0x004dd0b1 down 0x13 0x004dd0b1 up 0x14 0x004dd0b1 down 0x15 0x04820a05 down root@OpenWrt:~# gpioset gpiochip0 59=1 root@OpenWrt:~# mdio 9* DEV PHY-ID LINK 0x00 0x00000000 down 0x08 0x00000000 down 0x10 0x004dd0b1 down 0x11 0x004dd0b1 down 0x12 0x004dd0b1 down 0x13 0x004dd0b1 up 0x14 0x004dd0b1 down 0x15 0x04820a05 down Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: 301w: populate AQR firmware nameRobert Marko2024-01-261-0/+2
| | | | | | | | | | Now that we have support for firmware loading via the kernel driver, it makes sense to populate the firmware name as well, so if its present the driver can load it. In later patches, loading the FW via NVMEM will be added as well. Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: refresh 6.1 patchesÁlvaro Fernández Rojas2024-01-2613-28/+28
| | | | | | | | Refresh patches for Linux 6.1 which no longer apply cleanly after adding ipq4019 MDIO MDC rate fix pending patches. Fixes: 53f338be43e0 ("generic: 6.1: add pending patch for ipq4019 MDIO MDC rate fix") Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ipq807x: add support for loading Aquantia FW from NVMEM for NBG7815Christian Marangi2024-01-251-0/+12
| | | | | | | Add support for loading Aquantia FW from NVMEM for Zyxel NBG7815 restoring correct functionality of the 10g port. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* qualcommax: add SMP affinity scriptRobert Marko2024-01-221-0/+36
| | | | | | | | | By default Linux will default to most IRQ-s being mapped to core 0 which during high loads will completely swamp the core 0, so lets add the widely used script that has been floating around forums for a long time to try and optimize the IRQ mapping a bit. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ipq807x: prpl-haze: enable LED driver on device treeCheWei Chien2024-01-152-1/+50
| | | | | | | Enable LED driver LP5562 on HAZE device tree and include its kernel module package on default package for HAZE. Signed-off-by: CheWei Chien <chewei.chien@wnc.com.tw>
* ipq807x: use devinfo MAC for Linksys MX4200Paweł Owoc2024-01-152-0/+31
| | | | | | Some devices (MX42CF) have a wrong MAC address configuration. The correct one is located only on the devinfo partition. Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
* ipq807x: fix whitespace usagePaweł Owoc2024-01-153-9/+9
| | | | | | Replace with tab and remove unused whitespaces Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
* qualcommax: Fix Buffalo WXR-5950AX12 wifi MACSamir Ibradžić2024-01-061-0/+4
| | | | | | | | | | | | | | | | | | | | | Currently, WiFi interfaces on WXR-5950AX12 / WXR-6000AX12 devices come up with some MAC addresses inconsistent with vendor and Ethernet addresses. This adds a hotplug override in order to make it consistent with what is in u-boot env as well as OAM firmware where 1st radio MAC is set at Ethernet MAC + 8, and 2nd radio mac at Ethernet MAC + 16. fw_printenv | grep addr ethaddr=68:e1:dc:xx:xx:d8 ipaddr=192.168.11.1 wlan0addr=68:e1:dc:xx:xx:e0 wlan1addr=68:e1:dc:xx:xx:e8 wlan2addr=00:00:00:00:00:00 For OEM bootlog and MAC assagnment check https://openwrt.org/toh/buffalo/wxr-5950ax12#openwrt_uimage_tftp_bootlog Tested-by: Samir Ibradžić <sibradzic@gmail.com> # Buffalo WXR-6000AX12P Signed-off-by: Samir Ibradžić <sibradzic@gmail.com>
* ipq807x: add support for Linksys MX4200 V1 and V2Mohammad Sayful Islam2024-01-068-0/+524
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Linksys MX4200 is a 802.11ax Tri-band router/AP. Specifications: * CPU: Qualcomm IPQ8174 Quad core Cortex-A53 1.4GHz * RAM: 512MB of DDR3 * Storage: 512Mb NAND * Ethernet: 4x1G RJ45 ports (QCA8075) * WLAN: * 2.4GHz: Qualcomm QCN5024 2x2 802.11b/g/n/ax 574 Mbps PHY rate * 5GHz: Qualcomm QCN5054 2x2@80MHz or 2x2@160MHz 802.11a/b/g/n/ac/ax 2402 PHY rate * 5GHz: Qualcomm QCN5054 4x4@80MHz or 2x2@160MHz 802.11a/b/g/n/ac/ax 2402 PHY rate * LED-s: * RGB system led * Buttons: 1x Soft reset 1x WPS * Power: 12V DC Jack Installation instructions: Open Linksys Web UI - http://192.168.1.1/ca or http://10.65.1.1/ca depending on your setup. Login with your admin password. The default password can be found on a sticker under the device. To enter into the support mode, click on the “CA” link and the bottom of the page. Open the “Connectivity” menu and upload the squash-factory image with the “Choose file” button. Click start. Ignore all the prompts and warnings by click “yes” in all the popups. The Wifi radios are turned off by default. To configure the router, you will need to connect your computer to the LAN port of the device. Then you would need to write openwrt to the other partition for it to work - First Check booted partition fw_printenv -n boot_part - Then install Openwrt to the other partition if booted in slot 1: mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq807x-linksys_mx4200v(X)-squashfs-factory.bin alt_kernel - If in slot 2: mtd -r -e kernel -n write openwrt-qualcommax-ipq807x-linksys_mx4200v(X)-squashfs-factory.bin kernel Replace (X) with your model version either 1 or 2 Signed-off-by: Mohammad Sayful Islam <sayf.mohammad01@gmail.com> Reviewed-by: Robert Marko <robimarko@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-15 17:07:53 +0000