Searched full:likely (Results 1 – 25 of 294) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/bindings/net/can/ |
| D | mpc5xxx-mscan.txt | 5 Grant Likely <grant.likely@secretlab.ca>
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-ofw | 3 Contact: Grant Likely <grant.likely@arm.com>, devicetree@vger.kernel.org
|
| D | sysfs-class-android_usb | 7 The state of the USB connection. This attribute is likely
|
| D | sysfs-nvmem-cells | 13 ASCII, likely without trailing character).
|
| D | sysfs-bus-iio-sx9324 | 29 likely dictate different output. The entry is read-only.
|
| D | sysfs-devices-memory | 18 likely to be offlineable or not. Newer kernel versions return
64 that offlining will succeed. Offlining is more likely to
|
| /Documentation/hwmon/ |
| D | nsa320.rst | 55 is reduced from 100 us to less than 15 us then data pulses are likely to be
63 fan speed. As the most likely case for two accesses in quick succession is
|
| D | sch5636.rst | 30 likely see fewer temperature and fan inputs.
|
| D | ltc4215.rst | 44 undercurrent warnings. This makes it very likely that the reference
|
| /Documentation/arch/xtensa/ |
| D | atomctl.rst | 26 use the memory controllers RCW, though non-MX controllers likely
31 don't support atomic RCW memory transactions and will likely want to
|
| /Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 5 standalone chips are most likely better represented as GPIOs, although there
6 are likely to be exceptions to this rule.
|
| /Documentation/core-api/ |
| D | dma-attributes.rst | 88 You might know that the accesses are likely to be sequential or
90 between many addresses that are likely to be in different physical
105 though ARM64 patches will likely be posted soon.
|
| /Documentation/i2c/ |
| D | dma-considerations.rst | 9 DMA for it will likely add more overhead than a plain PIO transfer.
14 message size is likely applicable for DMA. Most drivers have this threshold
|
| /Documentation/misc-devices/ |
| D | ics932s401.rst | 22 This chip has 4 clock outputs--a base clock for the CPU (which is likely
|
| /Documentation/networking/ |
| D | ipsec.rst | 29 Small IP datagrams are likely to expand as a result of compression.
|
| /Documentation/driver-api/ |
| D | mailbox.rst | 9 client (especially) and controller drivers are likely going to be
10 very platform specific because the remote firmware is likely to be
|
| /Documentation/filesystems/iomap/ |
| D | porting.rst | 80 A likely complexity at this point will be converting the buffered read
104 Most likely at this point, the buffered read and write paths will still
|
| /Documentation/fb/ |
| D | sstfb.rst | 72 buffer driver, the voodoo fb will likely be /dev/fb1. if not,
163 - DO NOT use glide while the sstfb module is in, you'll most likely
186 - The 24/32 is not likely to work anytime soon, knowing that the
|
| /Documentation/admin-guide/mm/ |
| D | ksm.rst | 34 has advised to be likely candidates for merging, by using the madvise(2)
68 restricting its use to areas likely to benefit. KSM's scans may use a lot
99 significant NUMA distances, are likely to benefit from the
101 minimize memory usage, are likely to benefit from the greater
|
| /Documentation/staging/ |
| D | static-keys.rst | 40 do likely code
49 impact to the likely code path as possible.
117 do likely code
122 do likely code
|
| /Documentation/networking/device_drivers/ethernet/3com/ |
| D | 3c509.rst | 99 of the 3c509B is enabled, its link partner will very likely need to be
156 receives packets (as reported by /proc/net/dev or 'ifconfig') you likely
159 increasing you likely have a physical conflict with two devices trying to
171 likely have an unterminated network or the incorrect media transceiver selected.
|
| /Documentation/leds/ |
| D | ledtrig-usbport.rst | 29 only one LED user will most likely want to assign ports from all 3 hubs.
|
| /Documentation/admin-guide/media/ |
| D | cx88.rst | 32 cx88-cards.c. If the driver doesn't work well you likely need a new
|
| /Documentation/mm/ |
| D | vmalloced-kernel-stacks.rst | 51 most likely) needs to ensure that the stack's page table entries
125 the stack again. When handlers are called, it is likely that very little
|
| /Documentation/power/ |
| D | power_supply_class.rst | 264 Most likely, no. Such attribute can be placed in the driver itself, if
277 Most likely, no. This class is designed to export properties which are
285 voltage and so on. But full-fledged battery model is likely not subject
|
12345678910>>...12