Searched full:change (Results 1 – 25 of 892) sorted by relevance
12345678910>>...36
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-xhci_hcd | 31 This dbc_idVendor attribute lets us change the idVendor field
35 disabled state to prevent USB device descriptor change while
44 This dbc_idProduct attribute lets us change the idProduct field
48 disabled state to prevent USB device descriptor change while
56 This dbc_bcdDevice attribute lets us change the bcdDevice field
60 disabled state to prevent USB device descriptor change while
69 This attribute lets us change the bInterfaceProtocol field
73 disabled state to prevent USB descriptor change while
|
| D | usb-charger-uevent | 25 UDEV change /devices/soc0/usbphynop1 (platform)
26 ACTION=change
42 KERNEL change /devices/soc0/usbphynop1 (platform)
43 ACTION=change
|
| D | sysfs-platform-renesas_usb3 | 7 The file can show/change the drd mode of usb.
9 Write the following string to change the mode:
|
| D | sysfs-platform-phy-rcar-gen3-usb2 | 7 The file can show/change the phy mode for role swap of usb.
9 Write the following strings to change the mode:
|
| D | sysfs-ocfs2 | 46 This file is read-only. Its contents may change as
62 the cluster stack in use. The contents may change
85 If there are mounted filesystems, attempts to change the
|
| D | sysfs-bus-iio-dac-ltc2688 | 9 - change dither parameters (eg: frequency, phase...);
62 useful when one wants to change the DAC output codes. The way it should
66 - change out_voltageY_raw0 and out_voltageY_raw1;
|
| D | sysfs-memory-page-offline | 15 this might change.
40 this might change.
|
| /Documentation/devicetree/bindings/usb/ |
| D | qcom,pmic-typec.yaml | 33 - description: Type-C CC state change
35 - description: Type-C VBUS state change
38 - description: Type-C Try.Src Try.Snk state change
50 - const: or-rid-detect-change
52 - const: cc-state-change
54 - const: vbus-change
119 interrupt-names = "or-rid-detect-change",
121 "cc-state-change",
123 "vbus-change",
|
| /Documentation/devicetree/bindings/ |
| D | ABI.rst | 13 frozen for all time. Grant said there are ways to change bindings that
16 truly needs an incompatible change, then change the compatible string
30 the old binding. ie. add additional properties, but don't change the
|
| /Documentation/scsi/ |
| D | ChangeLog.ips | 1 IBM ServeRAID driver Change Log
21 4.80.21 - Change memcpy() to copy_to_user() in NVRAM Page 5 IOCTL path
40 4.71.00 - Change all memory allocations to not use GFP_DMA flag
97 - Change version to 3.60 to coincide with ServeRAID release
106 -- this required the interface to the utilities to change
|
| /Documentation/networking/ |
| D | failover.rst | 13 unregister/link change/name change events on slave pci ethernet devices
|
| D | net_dim.rst | 22 change moderation parameters for a channel, usually by performing an analysis on
25 to the previous sample and if required, it can decide to change some of the
30 the algorithm might decide not to change anything. The configuration fields are
51 bandwidth reduces. If there is no change in bandwidth, the packet rate is
53 In case there is no change in the packet rate as well, the interrupt rate is
91 it should change interrupt moderation parameters. The driver should provide two
117 decides to make a change in the interrupt moderation parameters. This callback
133 /* Callback for net DIM to schedule on a decision to change moderation */
|
| /Documentation/process/ |
| D | maintainer-soc.rst | 79 files. Even if a change is compatible in both directions, this may require
82 Usually the branch that includes a driver change will also include the
83 corresponding change to the devicetree binding description, to ensure they are
85 warnings in the "make dtbs_check" step. If a devicetree change depends on
96 header is required, and change them to the named representation in a
102 * Change the bindings in a shared immutable branch that is used as the base for
103 both the driver change and the devicetree changes
138 If in any doubt about a devicetree change, reach out to the devicetree
|
| D | applying-patches.rst | 32 and what new version the patch will change the source tree into. These
52 unlabeled patch was generated against) you should change into your kernel
128 a change in the middle of the file but for some reasons a few lines have
139 When patch encounters a change that it can't fix up with fuzz it rejects it
141 read this file to see exactly what change couldn't be applied, so you can
164 of the change (in this example it needed to move 7 lines from where it
165 expected to make the change to make it fit).
175 fuzz its way through. This will generate a ``.rej`` file with the change that
180 then patch detected that the change contained in the patch seems to have
286 $ cd ~/linux-5.6 # change to kernel source dir
[all …]
|
| /Documentation/sound/designs/ |
| D | jack-injection.rst | 10 validate ALSA userspace changes. For example, we change the audio
12 change works as expected and if the change introduce the regression,
28 change the state by hardware events anymore, we could inject plugin or
33 and will change by future hardware events.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-uevent.rst | 80 UEVENT[1192521009.711215] change@/block/dm-3
81 ACTION=change
97 UEVENT[1192521132.989927] change@/block/dm-3
98 ACTION=change
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-enum-mbus-code.rst | 115 - The driver allows the application to try to change the default colorspace
122 - The driver allows the application to try to change the default transform function.
129 - The driver allows the application to try to change the default Y'CbCr
136 - The driver allows the application to try to change the default HSV
143 - The driver allows the application to try to change the default
|
| D | selection-api-examples.rst | 7 (A video capture device is assumed; change
8 ``V4L2_BUF_TYPE_VIDEO_CAPTURE`` for other devices; change target to
57 A video output device is assumed; change ``V4L2_BUF_TYPE_VIDEO_OUTPUT``
|
| /Documentation/devicetree/bindings/regulator/ |
| D | samsung,s5m8767.yaml | 37 change in SOC. The different possible values are:
61 mode change in SOC. The different possible values are:
86 mode change in SOC. The different possible values are:
|
| /Documentation/arch/x86/ |
| D | intel-hfi.rst | 28 These capabilities may change at runtime as a result of changes in the
31 some models, capabilities are set at boot time and never change. On others,
32 capabilities may change every tens of milliseconds. For instance, a remote
33 mechanism may be used to lower Thermal Design Power. Such change can be
|
| /Documentation/driver-api/hte/ |
| D | hte.rst | 14 change; upon detecting the change they can automatically store the timestamp at
47 - Monitors GPIO line change.
48 - Detects the state change on GPIO line.
|
| /Documentation/filesystems/ |
| D | gfs2-uevents.rst | 36 3. CHANGE
39 The CHANGE uevent is used in two places. One is when reporting the
44 The other CHANGE uevent is used to inform of the completion
53 Because the CHANGE uevent was used (in early versions of gfs_controld)
|
| /Documentation/ |
| D | atomic_bitops.txt | 20 {set,clear,change}_bit()
25 test_and_{set,clear,change}_bit()
|
| /Documentation/hwmon/ |
| D | lm77.rst | 37 was 80 degrees C, and the hysteresis was 75 degrees C, and you change
39 automatically change to 85 degrees C.
|
| /Documentation/devicetree/ |
| D | changesets.rst | 23 2. A number of DT tree change calls, of_changeset_attach_node(),
27 All the change operations are recorded in the of_changeset 'entries'
|
12345678910>>...36