Age | Commit message (Collapse) | Author |
|
PCIe switch/bridge downstream port. This fixes an issue where a device would
show up 32 times if the PCIe port does not terminate configuration requests
targeted at device numbers 1-31 as required by the spec and the PCIe device
does not filter requests based on its own device number. Linux, NetBSD and
FreeBSD (to some extent) already do this.
This should fix an issue seen on Ampere Altra where the BMC's PCI bridge
and USB controller would show up multiple times.
ok jsg@
|
|
Thanks to Sven M. Hallberg.
|
|
Enabling 40MHz too early can cause firmware sysassert 0x05 on 5300 devices
when we send the initial AUTH frame to kick off association. At this point
we haven't negotiated 11n mode yet (this happens later during the association
sequence), so perhaps firmware saw an inconsistent configuration state?
It is unclear why this problem did not seem to affect any other devices.
Reported by Christian Schulte on misc@
|
|
From Alex Deucher
2b7d9fd0f3725135b40571d6a44bbbaeead132fe in linux 5.15.y/5.15.47
97e50305542f384741a5b45699aba349fe9fca73 in mainline linux
|
|
From Brian Norris
cab7cd86f9e81834c407e043844779f21653ff3c in linux 5.15.y/5.15.47
e54a4424925a27ed94dff046db3ce5caf4b1e748 in mainline linux
|
|
From Yury Norov
b2d359f095883d10b33e74a4a404363d2312830d in linux 5.15.y/5.15.47
525d6515604eb1373ce5e6372a6b6640953b2d6a in mainline linux
|
|
From Lijo Lazar
e0199ce728fb98a96a20136a5edb11c160d3151f in linux 5.15.y/5.15.47
b0f4d663fce6a4232d3c20ce820f919111b1c60b in mainline linux
|
|
From Gong Yuanjun
7b7fba107b2c4ec7673d0f45bdbb9d1af697d9b9 in linux 5.15.y/5.15.47
a2b28708b645c5632dc93669ab06e97874c8244f in mainline linux
|
|
From David Galiffi
10ef82d6e0af5536ec64770c07f6bbabfdd6977c in linux 5.15.y/5.15.47
49947b906a6bd9668eaf4f9cf691973c25c26955 in mainline linux
|
|
discussed with and partly from kettenis@
|
|
tx interrupts.
Special treatment of Server Base System Architecture (SBSA) generic UART
devices is required as presence of the interrupt trigger level register
is not guaranteed. Therefore treat such devices of having a 1-byte FIFO.
ok visa@
|
|
From Jani Nikula
35511d4fdd6b82c887ef038278fd808d7c7f98de in linux 5.15.y/5.15.46
0ea917819d12fed41ea4662cc26ffa0060a5c354 in mainline linux
|
|
From Dave Airlie
70276460e914d560e96bfc208695a872fe9469c9 in linux 5.15.y/5.15.46
31ab27b14daaa75541a415c6794d6f3567fea44a in mainline linux
|
|
From Nathan Chancellor
d50d1c703bbd8930d11e5bc01e2cc3c8dcda8f4b in linux 5.15.y/5.15.46
58606220a2f1407a7516c547f09a1ba7b4350a73 in mainline linux
|
|
From Jani Nikula
96db9afa4958bbaee77995eb0c84e08cdcce74ae in linux 5.15.y/5.15.46
3aefc722ff52076407203b6af9713de567993adf in mainline linux
|
|
From Linus Torvalds
710051ebb77b785d637417564be7fed4c13c6ce0 in linux 5.15.y/5.15.46
47f15561b69e226bfc034e94ff6dbec51a4662af in mainline linux
|
|
From Sathishkumar S
5005002b2e12e9ac4b58e59354d38a4106906f87 in linux 5.15.y/5.15.46
cdf4c8ec39872a61a58d62f19b4db80f0f7bc586 in mainline linux
|
|
From Sathishkumar S
c525d3385f6d34d6dcce89ebe019314d83f23873 in linux 5.15.y/5.15.46
138292f1dc00e7e0724f44769f9da39cf2f3bf0b in mainline linux
|
|
From Alice Wong
b305469ed00420e53c66064b554531d6fbd98d5b in linux 5.15.y/5.15.46
ab0cd4a9ae5b4679b714d8dbfedc0901fecdce9f in mainline linux
|
|
From Alex Deucher
a2c87348acebd9bacedfe20cf82341928751ff91 in linux 5.15.y/5.15.46
b95b5391684b39695887afb4a13cccee7820f5d6 in mainline linux
|
|
From Evan Quan
ae488dafe074e420ccf361b2633f7fbc314eaedf in linux 5.15.y/5.15.46
555238d92ac32dbad2d77ad2bafc48d17391990c in mainline linux
|
|
From Steven Price
978e3d023256bfaf34a0033d40c94e8a8e70cf3c in linux 5.15.y/5.15.46
4b674dd69701c2e22e8e7770c1706a69f3b17269 in mainline linux
|
|
From Haohui Mai
7719a8044bf66b9f59818e50b0c7877e1397e7f4 in linux 5.15.y/5.15.46
7dba6e838e741caadcf27ef717b6dcb561e77f89 in mainline linux
|
|
From Keita Suzuki
a5ce7051db044290b1a95045ff03c249005a3aa4 in linux 5.15.y/5.15.46
f3fa2becf2fc25b6ac7cf8d8b1a2e4a86b3b72bd in mainline linux
|
|
From Saaem Rizvi
d0d266c2f689d6113fe0d43d1b1fc105157c7443 in linux 5.15.y/5.15.46
5d5af34072c8b11f60960c3bea57ff9de5877791 in mainline linux
|
|
required for 5.15.46 inteldrm
|
|
This change fixes bugs concerning the transition into the hold/drag state
after double taps or two- or three-finger taps. In addition, it ensures
that button events properly match the logical button state when tap inputs
and button inputs overlap.
|
|
the StarFive VisionFive board.
ok patrick@
|
|
pin.
ok jsg@
|
|
controller. There are various incarnations of the controller. This diff
only adds support for the "V1"/"CDNS3" version as found on the StarFive
JH7100 SoC. Further changes may be needed to support controllers integrated
on other SoCs.
ok jsg@
|
|
From Gustavo A. R. Silva
195fffbf8291a84580762ac6e3101489954d0216 in linux 5.15.y/5.15.45
336feb502a715909a8136eb6a62a83d7268a353b in mainline linux
|
|
|
|
From Alex Deucher
62e9bd20035b53ff6c679499c08546d96c6c60a7 in mainline linux
|
|
mvneta only supports coalescing tx completions by count, so this
uses the txmit value or half the ring as the threshold, whichever
is lower.
rx coalescing has a threshold on the number of packets, and a max
time it will wait before interrupting. however, it also has a
threshold for how many spare/empty descriptors there are on the
ring too. we use this latter threshold to have the chip interrupt
as soon as it uses the allocation that the rx ring moderation has
granted, and then first two to otherwise rate limit rx to about 4k
interrupts per second.
ok patrick@
|
|
unbreaks the build on bigendian archs.
found by deraadt@
|
|
mvneta does interrupt coalescing based on time as counted by these
clocks, so being able to ask how fast they tick is useful.
lots of help and ok kettenis@
|
|
Problem reported by Chris Narkiewicz who owns such a device.
Johannes Berg provided helpful hints regarding the reason for
the firmware error seen by Chris.
|
|
on a Star Labs StarLite Mk IV laptop the audio device is subclass audio
not hd audio, so azalia does not match
reported and tested by Chris Narkiewicz
ok deraadt@
|
|
some of them are 16 bit, so check frequently.
now i can see what packets my apu1 is dropping in hardware.
ok claudio@
|
|
|
|
ok kevlo@
|
|
|
|
link state changes still take the kernel lock, but packet processing
is unlocked now.
|
|
this is another big step toward making the code mpsafe, and makes
a bunch of ring operations such as dmamap syncs and register updates
get done once for the ring rather than for every packet.
|
|
the interrupt handler is still under kernel lock, but at least you
can queue packets from another cpu concurrently.
|
|
|
|
|
|
this is a big step toward making the code mpsafe, and makes a bunch
of ring operations such as dmamap syncs and register updates per
start/completion call rather than per packet.
|
|
mvneta counters are read to clear, so we accumulate them over time.
they are also mostly 32bit, except for 2 of them, so this handles
all the 32bit counters in a loop and deals with the 64bit ones as
exceptions.
i can see rx drops now, but not the rx rx counters yet. i'll figure
it out.
this is mostly inspired by em(4).
|
|
this leads to better (and shorter) code.
ok patrick@
|