Searched full:upon (Results 1 – 25 of 297) sorted by relevance
12345678910>>...12
| /Documentation/hwmon/ |
| D | nct6775.rst | 25 Datasheet: Available from Nuvoton upon request
33 Datasheet: Available from Nuvoton upon request
41 Datasheet: Available from Nuvoton upon request
49 Datasheet: Available from Nuvoton upon request
57 Datasheet: Available from Nuvoton upon request
65 Datasheet: Available from Nuvoton upon request
73 Datasheet: Available from Nuvoton upon request
81 Datasheet: Available from Nuvoton upon request
89 Datasheet: Available from Nuvoton upon request
|
| D | sch5636.rst | 20 their own custom hwmon solution based upon the SCH5636.
37 microcontroller is available upon request. Please mail me if you want a copy.
|
| D | sch5627.rst | 12 Datasheet: Application Note available upon request
34 protocol for communicating with the microcontroller is available upon
|
| D | nsa320.rst | 14 Datasheet: Not available, driver was reverse engineered based upon the
56 read twice corrupting the output. The above analysis is based upon a sample
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 44 which will be ORed into PMCDR upon suspend, and cleared from PMCDR
45 upon resume. The first two cells are as described for fsl,mpc8578-pmc.
52 hardware does not have DEVDISR2) upon a request for permanent device
|
| /Documentation/watchdog/ |
| D | hpwdt.rst | 42 kdumptimeout Minimum timeout in seconds to apply upon receipt of an NMI
58 Upon receipt of an NMI from the iLO, the hpwdt driver will initiate a
60 upon the user to have properly configured the system for kdump.
62 The default Linux kernel behavior upon panic is to print a kernel tombstone
|
| /Documentation/arch/arm/nwfpe/ |
| D | notes.rst | 11 often uses an stfe instruction to save f4 on the stack upon entry to a
15 then made a function call. Upon return from the function call the number in
|
| /Documentation/arch/powerpc/ |
| D | cxlflash.rst | 143 driver. Upon successful open, the user receives a file descriptor
254 LUN and will fail if invoked upon a LUN that is not in virtual
255 mode. Upon success, an updated last LBA is returned to the user
275 DK_CXLFLASH_USER_VIRTUAL ioctls. Upon success, the resource handle
287 not explicitly released via the DK_CXLFLASH_RELEASE ioctl. Upon
300 forks. Upon success, the child process (which invoked the ioctl)
348 is re-established upon successful recovery.
352 by seeing all 0xF's on an MMIO read. Upon encountering this, the
397 the target port to host the LUN and a desired size in 4K blocks. Upon
406 target port and LUN ID. Upon success, the LUN geometry associated with
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 19 caching it in memory. Upon resume device drivers using the firmware API will
47 * Upon suspend any pending non-uevent firmware requests are killed to avoid
|
| D | lookup-order.rst | 19 is issued or the custom firmware loading is relied upon for firmware
|
| /Documentation/locking/ |
| D | hwspinlock.rst | 106 Upon a successful return from this function, preemption is disabled so
122 Upon a successful return from this function, preemption and the local
138 Upon a successful return from this function, preemption is disabled,
189 Upon a successful return from this function, preemption is disabled so
206 Upon a successful return from this function, preemption and the local
222 Upon a successful return from this function, preemption is disabled,
279 Upon a successful return from this function, preemption and local
291 Upon a successful return from this function, preemption is reenabled,
|
| /Documentation/driver-api/ |
| D | mailbox.rst | 59 * dependent upon the protocol. This is just an example.
99 dc_async->cl.knows_txdone = false; /* depending upon protocol */
109 dc_sync->cl.knows_txdone = false; /* depending upon protocol */
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-st | 11 appear in sysfs as its presence is conditional upon debug
|
| D | sysfs-bus-platform-devices-occ-hwmon | 9 from the first error is saved, until it's cleared upon read. The OCC hwmon driver, running on
|
| D | sysfs-platform-intel-pmc | 19 a platform "global reset" upon consequent platform reset,
|
| D | sysfs-bus-iio-sps30 | 16 Period can be changed by writing a new value here. Upon reading
|
| /Documentation/security/ |
| D | credentials.rst | 13 object acts upon another:
17 Objects are things in the system that may be acted upon directly by
48 carried out when an object is acted upon.
52 A subject is an object that is acting upon another object.
60 given to it by a task that called ``fcntl(F_SETOWN)`` upon it. In this case,
71 group list for when it is acting upon a file - which are quite separate
77 Linux has a number of actions available that a subject may perform upon an
86 When a subject acts upon an object, a security calculation is made. This
224 to the server, regardless of who is actually doing a read or a write upon it.
|
| /Documentation/devicetree/bindings/arm/ux500/ |
| D | power_domain.txt | 6 The implementation of PM domains for UX500 are based upon the generic PM domain
|
| /Documentation/driver-api/mei/ |
| D | hdcp.rst | 18 upon request ME FW will configure the port as authenticated and supply
|
| /Documentation/devicetree/bindings/input/ |
| D | input-reset.txt | 5 sysrq driver. Upon holding the keys for a specified amount of time (if
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,pbs.yaml | 15 upon request.
|
| /Documentation/devicetree/bindings/arm/cirrus/ |
| D | cirrus,ep9301.yaml | 22 Computer (SBC) based upon the Cirrus EP9302 ARM9 CPU
|
| /Documentation/gpu/rfc/ |
| D | i915_vm_bind.rst | 30 * Support capture of persistent mappings in the dump upon GPU error.
141 be pinned in memory when VM is made active (ie., upon an execbuf call with
180 Where GPU page faults are not available, kernel driver upon buffer invalidation
191 worker (like upon bind completion). User can wait on a user fence with a new
207 of and act upon resources created by another process (debugged) and attached
|
| /Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 23 check the actual protections being applied upon mmap/mprotect calls.
|
| /Documentation/arch/x86/x86_64/ |
| D | fred.rst | 57 context upon event delivery and return. Thus it avoids the problem of
89 The current stack level could be unchanged or go higher upon FRED
|
12345678910>>...12