| /Linux-v5.4/drivers/gpio/ |
| D | gpio-mt7621.c | 115 u32 rise, fall, high, low; in mediatek_gpio_irq_unmask() local
118 rise = mtk_gpio_r32(rg, GPIO_REG_REDGE); in mediatek_gpio_irq_unmask()
122 mtk_gpio_w32(rg, GPIO_REG_REDGE, rise | (BIT(pin) & rg->rising)); in mediatek_gpio_irq_unmask()
136 u32 rise, fall, high, low; in mediatek_gpio_irq_mask() local
139 rise = mtk_gpio_r32(rg, GPIO_REG_REDGE); in mediatek_gpio_irq_mask()
144 mtk_gpio_w32(rg, GPIO_REG_REDGE, rise & ~BIT(pin)); in mediatek_gpio_irq_mask()
|
| D | gpio-stmpe.c | 293 u8 rise = NOT_SUPPORTED_IDX; in stmpe_dbg_show_one() local
316 rise = !!(ret & mask); in stmpe_dbg_show_one()
341 rise_values[rise], in stmpe_dbg_show_one()
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-led-driver-sc27xx | 7 hardware pattern, which is used to configure the rise time,
12 format, we should set brightness as 0 for rise stage, fall
|
| D | sysfs-class-led-driver-lm3533 | 25 Set the pattern generator fall and rise times (0..7), where:
|
| /Linux-v5.4/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-ltc4306.txt | 24 - ltc,downstream-accelerators-enable: Enables the rise time accelerators
26 - ltc,upstream-accelerators-enable: Enables the rise time accelerators
|
| D | i2c-rk3x.txt | 36 - i2c-scl-rising-time-ns : Number of nanoseconds the SCL signal takes to rise
|
| D | i2c.txt | 51 Number of nanoseconds the SCL signal takes to rise; t(r) in the I2C
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | cs42l42.txt | 30 - cirrus,ts-dbnc-rise : Debounce the rising edge of TIP_SENSE_PLUG. With no
101 cirrus,ts-dbnc-rise = <0x05>;
|
| /Linux-v5.4/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru-kevin.dts | 184 /* These are relatively safe rise/fall times. */
200 /* These are relatively safe rise/fall times. */
|
| D | rk3399-gru-chromebook.dtsi | 259 /* These are relatively safe rise/fall times */
275 /* These are relatively safe rise/fall times */
|
| D | rk3399-gru-scarlet.dtsi | 261 /* These are relatively safe rise/fall times. */
293 /* These are relatively safe rise/fall times; TODO: measure */
|
| D | rk3399-gru.dtsi | 385 /* These are relatively safe rise/fall times */
395 /* These are relatively safe rise/fall times */
|
| /Linux-v5.4/Documentation/devicetree/bindings/memory-controllers/ |
| D | mvebu-devbus.txt | 92 address and data to DEV_WEn rise.
100 data after DEV_WEn rise.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | locks.txt | 31 for example. This gave rise to some other subtle problems if sendmail was
|
| /Linux-v5.4/Documentation/driver-api/gpio/ |
| D | intro.rst | 120 value (after the appropriate rise time passes), you know some other component is
|
| D | legacy.rst | 437 value (after the appropriate rise time passes), you know some other component
|
| /Linux-v5.4/Documentation/fb/ |
| D | udlfb.rst | 53 * It's not clear what the future of fbdev is, given the rise of KMS/DRM.
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | at91-sama5d2_xplained.dts | 393 * Trigger can be configured on falling, rise
|
| D | rk3288-veyron.dtsi | 362 /* 100kHz since 4.7k resistors don't rise fast enough */
|
| /Linux-v5.4/Documentation/m68k/ |
| D | buddha-driver.rst | 140 All the timings have in common: Select and IOR/IOW rise at
|
| /Linux-v5.4/Documentation/process/ |
| D | stable-api-nonsense.rst | 183 - The quality of the driver will rise as the maintenance costs (to the
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | dme1737.rst | 214 duty-cycle. If any of the temperatures rise above the auto_point3_temp value,
|
| /Linux-v5.4/drivers/staging/speakup/ |
| D | sysfs-driver-speakup | 278 and most others, this causes the pitch of the voice to rise
|
| /Linux-v5.4/tools/memory-model/Documentation/ |
| D | explanation.txt | 311 shared memory, do not give rise to events. Thus, arithmetic and
462 index value loaded by the first. Pointer indirection also gives rise
|
| /Linux-v5.4/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 1248 rise too much.
|
