summaryrefslogtreecommitdiffstats
path: root/sys/dev
AgeCommit message (Collapse)AuthorFilesLines
2013-11-11Replace most of our formating functions to convert IPv4/6 addresses frommpi1-2/+5
network to presentation format to inet_ntop(). The few remaining functions will be soon converted. ok mikeb@, deraadt@ and moral support from henning@
2013-11-11bump the ring sizes up.dlg1-3/+3
ok yasuoka@
2013-11-11replace things like "start + interval > ticks" withdlg3-6/+6
"ticks - start > interval" because the latter copes with ticks wrapping. pointed out by guenther@
2013-11-11replace disksort with bufqs.dlg2-13/+9
i havent had any tests, so if there's any fallout ill deal with it when people hit it. i wont feel guilty about it at all though.
2013-11-11drm/i915/hsw: Disable L3 caching of atomic memory operations.jsg2-2/+13
Otherwise using any atomic memory operation will lock up the GPU due to a Haswell hardware bug. v2: Use the _MASKED_BIT_ENABLE macro. Drop drm parameter definition. From Francisco Jerez 018e31d2bd17a8bc95e1d1ca519650f2418b6010 in ubuntu 3.8 f3fc4884ebe6ae649d3723be14b219230d3b7fd2 in mainline linux
2013-11-11drm/i915: Don't enable the cursor on a disable pipejsg1-3/+5
On HSW enabling a plane on a disabled pipe may hang the entire system. And there's no good reason for doing it ever, so just don't. v2: Move the crtc active checks to intel_crtc_cursor_{set,move} to avoid confusing people during modeset From Ville Syrjala f6c0873963a9b8ea1d94541e0e219e6ea090012b in ubuntu 3.8 f2f5f771c5fc0fa252cde3d0d0452dcc785cc17a in mainline linux
2013-11-11drm/i915: do not update cursor in crtc mode setjsg1-10/+1
The cursor is disabled before crtc mode set in crtc disable (and we assert this is the case), and enabled afterwards in crtc enable. Do not update it in crtc mode set. On HSW enabling a plane on a disabled pipe may hang the entire system. And there's no good reason for doing it ever, so just don't. v2: Add note about HSW hangs - vsyrjala From Jani Nikula 0be01fc195fd4ea1aec1f8be7c03ca8f920a9486 in ubuntu 3.8 cc173961a68034c1171a421f0dbed39edfb60880 in mainline linux
2013-11-11drm/i915: Fix context sizes on HSWjsg2-11/+10
With updates to the spec, we can actually see the context layout, and how many dwords are allocated. That table suggests we need 70720 bytes per HW context. Rounded up, this is 18 pages. Looking at what lives after the current 4 pages we use, I can't see too much important (mostly it's d3d related), but there are a couple of things which look scary. I am hopeful this can explain some of our odd HSW failures. v2: Make the context only 17 pages. The power context space isn't used ever, and execlists aren't used in our driver, making the actual total 66944 bytes. v3: Add a comment to the code. (Jesse & Paulo) From Ben Widawsky 6bab5ce3f3224d3c1fcc92ed9184392558ae3df4 in ubuntu 3.8 a0de80a0e07032a111230ec92eca563f9d93648d in mainline linux
2013-11-10Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti2-11/+9
Okay mpi@
2013-11-09In our USB world, timeouts are in milliseconds, so use timeout_add_msec()mpi3-15/+9
coherently through all our controller drivers and kill the mstohz() macro. ok pirofti@
2013-11-09Reduce the differences between our controller drivers and initializempi1-7/+3
the timeout task in the *_timeout() routine. It now becomes obvious that the allocx/freex hooks can be merged. ok pirofti@
2013-11-09recognise Realtek ALC221jsg1-1/+4
2013-11-09enable snooping on Intel 8 Series HD Audiojsg1-1/+2
2013-11-09add Intel 8 series kt (amt serial over lan)jsg1-1/+8
2013-11-09more rate matching hubsjsg1-1/+3
2013-11-09regenjsg4-6/+41
2013-11-09add some more 4th gen Intel Core devicesjsg1-1/+6
2013-11-08advertise the ring sizes through the stack. specifically:dlg1-9/+9
- set the sndq size to the tx ring size so tx mitigation can hopefully kick in - advertise the size of the rx ring to mclgeti - only uses jumbo clusters. mtu is about what the ip stack will do for transmitted packets, we should happily receive packets up to the size the hardware supports. the point of mclgeti was to make it possible to do so without wasting too much memory. ok yasuoka@ uebayasi@
2013-11-08Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti2-10/+9
Okay mpi@
2013-11-08syncsthen2-2/+7
2013-11-08add ID for Areca ARC-1214sthen1-1/+2
2013-11-07In polling mode since r1.101 we could end up dereferencing anmpi1-9/+11
uninitialized variable in case the transfer we were waiting for timed out; problem reported by oga@bitrig. So bring uhci_waitintr() in sync with its equivalent in ohci(4) and ehci(4), stop using an uhci_xfer, do not dereference it and set the correct status of the transfer.
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti2-15/+13
Okay mpi@
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti4-29/+21
Okay mpi@
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-5/+3
Okay mpi@
2013-11-07Kill sc_dying. Nobody was using it anyway.pirofti1-4/+1
"just kill it" mpi@
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-8/+6
Okay mpi@
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti2-7/+6
Tested and okay mpi@.
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-7/+5
Testing and okay mpi@.
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-5/+4
Okay yuo@
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti6-77/+69
Okay mpi@
2013-11-07Make sure to mark the controller as dying in order to stop processingmpi1-1/+2
any transfer when autoconf(9) asks for it. This brings uhci(4) in sync with ohci(4) and ehci(4). ok pirofti@
2013-11-07Remove isoc_len from the transfer descriptor, it is assigned once butmpi2-8/+4
never read.
2013-11-07Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti2-28/+24
Okay mpi@
2013-11-07add a simplistic version of WARN_ON_ONCE() that doesn't warnjsg4-9/+9
reduces the diff to linux and avoids a clang warning brad mentioned ok kettenis@ brad@
2013-11-06pull the event ack handling out of mpii_event_process into mpii_event_donedlg1-1/+12
so we can use it in multiple places.
2013-11-06Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-10/+9
Okay mpi@
2013-11-06Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-23/+26
Okay mpi@
2013-11-06Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-20/+18
Tested and okay mpi@
2013-11-06Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-13/+12
Okay mpi@
2013-11-06Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti1-15/+14
Okay mpi@
2013-11-06Make usbd_free_xfer return void, since no callers use the return value.jeremy3-9/+9
OK mpi@
2013-11-06Replace sc_dying in favour of usbd_is_dying() and usbd_deactivate().pirofti3-16/+15
Okay mpi@
2013-11-06Add support for the RTS5229 card reader to rtsx(4).stsp4-30/+145
From Pedro Martelletto.
2013-11-06teach the side-effect free drivers about the partition they are dealingderaadt2-3/+21
by passing a start/length in the HIB_INIT op. Then rebase all hibernate-time block offsets to be relative to the start of that partition. This simplifies things a lot. ok mlarkin
2013-11-06regenstsp2-2/+7
2013-11-06Add RTS5229 Card Reader PCI ID. From Pedro Martelletto.stsp1-1/+2
2013-11-06Call the new MD hook before and after setting the power state of a device.mpi1-5/+17
This is actually a noop on all arches but ACPI ones, where it deals with Power Resources. ok kettenis@, deraadt@
2013-11-06Add support for Power Resources for Dx states and the necessary hookmpi5-76/+296
for PCI devices. This hook should be called twice, before and after changing the power state of a PCI device. Before setting the device to the new state, the ACPI layer will notify every power resources linked to the device for that state and make sure they are turned "_ON". After changing the state of the device, it will decrement the reference of every power resources linked to that device for the old state and turn them "_OFF" if they are no longer referenced. This fixes the no-USB after resume problem seen on various ThinkPad, problem initialy diagnosed with Alexander Polakov. ok kettenis@, deraadt@
2013-11-06dont leak ccbs in mpii_sas_remove_device. detaching lots (like, 1000) ofdlg1-1/+3
things could run you out of command slots without this.
Copyright © 1996 – 2026 Jason A. Donenfeld. All Rights Reverse Engineered.