diff options
author | Christian Lamparter <chunkeey@gmail.com> | 2020-09-03 21:24:16 +0200 |
---|---|---|
committer | Christian Lamparter <chunkeey@gmail.com> | 2020-09-05 23:26:05 +0200 |
commit | 252197f014932c03cea7c080d8ab90e0a963a281 (patch) | |
tree | 5fbb5122a5b4a09080608b6ec286b787a6e25579 /target/linux/apm821xx/Makefile | |
parent | a487e67cbc12025345f4af55f60af54f1d087005 (diff) | |
download | upstream-252197f014932c03cea7c080d8ab90e0a963a281.tar.gz upstream-252197f014932c03cea7c080d8ab90e0a963a281.tar.bz2 upstream-252197f014932c03cea7c080d8ab90e0a963a281.zip |
apm821xx: provide legacy interrupts for PCIe in DT
Devices with PCIe-Switches like the WNDR4700, MR24 and WNDAP660
need to have the interrupts property specified in the device-tree
for the legacy pci interrupt signaling method to work.
If the proper interrupt value is not specified, the default INTA
IRQ 12 is taken for all devices. This is especially bad, if the
device is setup to use INTC, because these interrupts will not
be serviced.
Russell Senior reported his experience on the MR24:
"The symptom is client devices can't see the beacons.
Wifi ifaces appear, can scan and hear other networks,
but clients can't see the MR24's SSIDs."
(The interrupts-property on the WNDAP620 was optional since it
uses INTA by default. Likewise the MX60W is in the same category)
Reported-by: Russell Senior <russell@personaltelco.net>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'target/linux/apm821xx/Makefile')
0 files changed, 0 insertions, 0 deletions