| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | as3711.txt | 23 feedback used:
24 - su2-feedback-voltage : voltage feedback is used
25 - su2-feedback-curr1 : CURR1 input used for current feedback
26 - su2-feedback-curr2 : CURR2 input used for current feedback
27 - su2-feedback-curr3 : CURR3 input used for current feedback
28 - su2-feedback-curr-auto: automatic current feedback selection
36 If "su2-feedback-curr-auto" is selected, one or more of the following properties
38 - su2-auto-curr1 : use CURR1 input for current feedback
39 - su2-auto-curr2 : use CURR2 input for current feedback
40 - su2-auto-curr3 : use CURR3 input for current feedback
[all …]
|
| /openbmc/linux/drivers/hid/ |
| H A D | Kconfig | 121 bool "ACRUX force feedback support"
125 Say Y here if you want to enable force feedback support for ACRUX
179 tristate "Betop Production Inc. force feedback support"
183 Say Y here if you want to enable force feedback support for devices by
198 force feedback effects and LEDs on the device.
299 bool "DragonRise Inc. force feedback"
303 Say Y here if you want to enable force feedback support for DragonRise Inc.
307 tristate "EMS Production Inc. force feedback support"
310 Say Y here if you want to enable force feedback support for devices by
393 bool "Holtek On Line Grip force feedback support"
[all …]
|
| H A D | hid-tmff.c | 3 * Force feedback support for various HID compliant devices by ThrustMaster:
8 * on 2003-01-25 from the Logitech force feedback driver,
199 hid_info(hid, "force feedback for ThrustMaster devices by Zinx Verituse <zinx@epicsol.org>\n"); in tmff_init()
251 { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb653), /* RGT Force Feedback CLUTCH Raging Wheel */
253 { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb654), /* FGT Force Feedback Wheel */
255 { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb65a), /* F430 Force Feedback Wheel */
|
| /openbmc/webui-vue/src/views/SecurityAndAccess/Certificates/ |
| H A D | ModalGenerateCsr.vue | 37 <b-form-invalid-feedback role="alert">
39 </b-form-invalid-feedback>
61 <b-form-invalid-feedback role="alert">
63 </b-form-invalid-feedback>
80 <b-form-invalid-feedback role="alert">
82 </b-form-invalid-feedback>
97 <b-form-invalid-feedback role="alert">
99 </b-form-invalid-feedback>
116 <b-form-invalid-feedback role="alert">
118 </b-form-invalid-feedback>
[all …]
|
| /openbmc/linux/drivers/input/ |
| H A D | ff-core.c | 3 * Force feedback support for Linux input subsystem
86 * input_ff_upload() - upload effect into force-feedback device
201 * input_ff_erase - erase a force-feedback effect from device
206 * This function erases a force-feedback effect from specified device.
231 * This function erases all force-feedback effects associated with
254 * input_ff_event() - generic handler for force-feedback events
294 * input_ff_create() - create force-feedback device
295 * @dev: input device supporting force-feedback
298 * This function allocates all necessary memory for a force feedback
356 * input_ff_destroy() - frees force feedback portion of input device
[all …]
|
| /openbmc/phosphor-fan-presence/monitor/example/ |
| H A D | config.json | 10 "object's feedback speed is adjusted by a factor of 1.45 and offset",
44 "The second fan in the system has one sensor(single rotor) feedback",
93 "feedback using the default 'timebased' method that allows it to",
99 "difference in target PWM versus the RPM feedback of the sensor to",
133 "sensors that can be used to trust the tach feedback reading or",
136 "one of them shows a non-zero feedback speed. At any time all fan",
139 "one of them reports a non-zero feedback speed."
|
| /openbmc/qemu/include/standard-headers/linux/ |
| H A D | input.h | 179 #define EVIOCSFF _IOW('E', 0x80, struct ff_effect) /* send a force effect to a force feedback devi…
286 * Values describing the status of a force-feedback effect
303 * struct ff_replay - defines scheduling of the force-feedback effect
313 * struct ff_trigger - defines what triggers the force-feedback effect
323 * struct ff_envelope - generic force-feedback effect envelope
330 * envelope force-feedback core will convert to positive/negative
342 * struct ff_constant_effect - defines parameters of a constant force-feedback effect
352 * struct ff_ramp_effect - defines parameters of a ramp force-feedback effect
364 * struct ff_condition_effect - defines a spring or friction force-feedback effect
385 * struct ff_periodic_effect - defines parameters of a periodic force-feedback effect
[all …]
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | input.h | 182 #define EVIOCSFF _IOW('E', 0x80, struct ff_effect) /* send a force effect to a force feedback devi…
289 * Values describing the status of a force-feedback effect
306 * struct ff_replay - defines scheduling of the force-feedback effect
316 * struct ff_trigger - defines what triggers the force-feedback effect
326 * struct ff_envelope - generic force-feedback effect envelope
333 * envelope force-feedback core will convert to positive/negative
345 * struct ff_constant_effect - defines parameters of a constant force-feedback effect
355 * struct ff_ramp_effect - defines parameters of a ramp force-feedback effect
367 * struct ff_condition_effect - defines a spring or friction force-feedback effect
388 * struct ff_periodic_effect - defines parameters of a periodic force-feedback effect
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | adi,max77857.yaml | 38 description: Top feedback resistor value in ohms for external feedback.
43 description: Bottom feedback resistor value in ohms for external feedback.
|
| H A D | rohm,bd71847-regulator.yaml | 105 # connected to feedback-pin (over suitable resistors) is getting popular
138 Feedback-pin has pull-up connection to adjust voltage range. This is
141 rohm,feedback-pull-up-r1-ohms:
143 Feedback-pin has pull-up connection to adjust voltage range. This is
146 rohm,feedback-pull-up-r2-ohms:
148 Feedback-pin has pull-up connection to adjust voltage range. This is
|
| H A D | rohm,bd71837-regulator.yaml | 110 # connected to feedback-pin (over suitable resistors) is getting popular
143 Feedback-pin has pull-up connection to adjust voltage range. This is
146 rohm,feedback-pull-up-r1-ohms:
148 Feedback-pin has pull-up connection to adjust voltage range. This is
151 rohm,feedback-pull-up-r2-ohms:
153 Feedback-pin has pull-up connection to adjust voltage range. This is
|
| /openbmc/webui-vue/src/views/Settings/Network/ |
| H A D | ModalIpv4.vue | 22 <b-form-invalid-feedback role="alert">
29 </b-form-invalid-feedback>
44 <b-form-invalid-feedback role="alert">
51 </b-form-invalid-feedback>
68 <b-form-invalid-feedback role="alert">
75 </b-form-invalid-feedback>
|
| /openbmc/linux/drivers/staging/rtl8192u/ |
| H A D | r819xU_cmdpkt.h | 19 /* 1. RX side: TX feedback packet. */
24 /* Change tx feedback info field. */
25 /*------TX Feedback Info Field */
36 /*------TX Feedback Info Field */
88 /* 5. Multi packet feedback status. */
129 /* 6. Debug feedback message. */
|
| /openbmc/linux/Documentation/mm/ |
| H A D | multigen_lru.rst | 46 categorized based on additional factors, and a feedback loop can
103 ``folio->flags`` and therefore has a negligible cost. A feedback loop
140 was accessed multiple times through file descriptors and the feedback
142 this end, the feedback loop uses the first tier as the baseline, for
181 Rmap/PT walk feedback
193 forms a feedback loop between the eviction and the aging.
213 A feedback loop modeled after the Proportional-Integral-Derivative
261 * Bloom filters for rmap/PT walk feedback
262 * PID controller for refault feedback
268 Within the eviction, the PID controller uses refaults as the feedback
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | adi,max98388.yaml | 13 The MAX98388 is a mono Class-D speaker amplifier with I/V feedback.
32 description: slot number of the voltage feedback monitor
39 description: slot number of the current feedback monitor
47 For cases where a single combined channel for the I/V feedback data
|
| /openbmc/linux/drivers/gpu/drm/amd/amdgpu/ |
| H A D | amdgpu_pll.c | 70 * amdgpu_pll_get_fb_ref_div - feedback and ref divider calculation
76 * @fb_div_max: feedback divider maximum
78 * @fb_div: resulting feedback divider
81 * Calculate feedback and reference divider for a given post divider. Makes
96 /* get matching reference and feedback divider */ in amdgpu_pll_get_fb_ref_div()
114 * @fb_div_p: resulting feedback divider
115 * @frac_fb_div_p: fractional part of the feedback divider
140 /* determine allowed feedback divider range */ in amdgpu_pll_compute()
224 /* get the feedback and reference divider for the optimal value */ in amdgpu_pll_compute()
|
| /openbmc/linux/samples/hid/ |
| H A D | hid_surface_dial.c | 5 * and depending on the chosen resolution enable or not the haptic feedback:
7 * without haptic feedback
9 * feedback
58 "and depending on the chosen resolution enable or not the haptic feedback:\n" in usage()
60 " without haptic feedback\n" in usage()
62 " feedback\n" in usage()
|
| /openbmc/phosphor-fan-presence/docs/control/fanctl/ |
| H A D | README.md | 41 - Get the current fan target and feedback speeds for all rotors
75 - Get the current fan target and feedback speeds for all rotors:
81 TARGET SENSOR TARGET(RPM) FEEDBACK SENSOR FEEDBACK(RPM)
108 FAN TARGET(RPM) FEEDBACK(RPM) PRESENT FUNCTIONAL
|
| /openbmc/webui-vue/docs/guide/quickstart/ |
| H A D | forms.md | 19 pairs form controls with a legend or label, helper text, invalid/valid feedback
20 text, and visual validation state feedback. Learn more about commonly used form
37 `<b-form-invalid-feedback>` component.
65 <b-form-invalid-feedback role="alert">
69 </b-form-invalid-feedback>
|
| /openbmc/linux/include/linux/iio/frequency/ |
| H A D | ad9523.h | 119 * @pll1_feedback_div: PLL1 10-bit Feedback N divider.
122 * @osc_in_feedback_en: PLL1 feedback path, local feedback from
127 * @pll2_ndiv_a_cnt: PLL2 Feedback N-divider, A Counter, range 0..4.
128 * @pll2_ndiv_b_cnt: PLL2 Feedback N-divider, B Counter, range 0..63.
|
| /openbmc/linux/drivers/staging/media/atomisp/pci/isp/kernels/tnr/tnr3/ |
| H A D | ia_css_tnr3_types.h | 43 * 3. One maximum feedback threshold value for each plane
47 unsigned int maxfb_y; /** Maximum Feedback Gain for Y */
48 unsigned int maxfb_u; /** Maximum Feedback Gain for U */
49 unsigned int maxfb_v; /** Maximum Feedback Gain for V */
|
| /openbmc/linux/drivers/input/joystick/iforce/ |
| H A D | iforce-main.c | 53 { 0x05ef, 0x8886, "Boeder Force Feedback Wheel", btn_wheel, abs_wheel, ff_iforce },
54 …{ 0x05ef, 0x8888, "AVB Top Shot Force Feedback Racing Wheel", btn_wheel, abs_wheel, ff_iforce }, /…
58 { 0x06f8, 0x0001, "Guillemot Race Leader Force Feedback", btn_wheel, abs_wheel, ff_iforce }, //?
59 …{ 0x06f8, 0x0001, "Guillemot Jet Leader Force Feedback", btn_joystick, abs_joystick_rudder, ff_ifo…
60 { 0x06f8, 0x0004, "Guillemot Force Feedback Racing Wheel", btn_wheel, abs_wheel, ff_iforce }, //?
62 { 0x06d6, 0x29bc, "Trust Force Feedback Race Master", btn_wheel, abs_wheel, ff_iforce },
178 /* Enable force feedback */ in iforce_open()
201 /* Disable force feedback playback */ in iforce_close()
313 * Disable spring, enable force feedback. in iforce_init_device()
|
| /openbmc/u-boot/drivers/clk/sifive/ |
| H A D | wrpll-cln28hpc.c | 120 * __wrpll_calc_fbdiv() - return feedback fixed divide value
123 * The internal feedback path includes a fixed by-two divider; the
124 * external feedback path does not. Return the appropriate divider
125 * value (2 or 1) depending on whether internal or external feedback
133 * Return: 2 if internal feedback is enabled or 1 if external feedback
264 WARN(1, "%s: external feedback mode not currently supported", in analogbits_wrpll_configure_for_rate()
365 "external feedback mode not yet supported"); in analogbits_wrpll_calc_output_rate()
|
| /openbmc/linux/drivers/net/ethernet/chelsio/ |
| H A D | Kconfig | 37 Please send feedback to <linux-bugs@chelsio.com>.
64 Please send feedback to <linux-bugs@chelsio.com>.
87 Please send feedback to <linux-bugs@chelsio.com>.
128 Please send feedback to <linux-bugs@chelsio.com>.
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | intel-hfi.rst | 4 Hardware-Feedback Interface for scheduling on Intel Hardware
10 Intel has described the Hardware Feedback Interface (HFI) in the Intel 64 and
18 The Hardware Feedback Interface
21 The Hardware Feedback Interface provides to the operating system information
|