| /Linux-v6.1/drivers/gpio/ |
| D | gpio-mt7621.c | 112 u32 rise, fall, high, low; in mediatek_gpio_irq_unmask() local
117 rise = mtk_gpio_r32(rg, GPIO_REG_REDGE); in mediatek_gpio_irq_unmask()
121 mtk_gpio_w32(rg, GPIO_REG_REDGE, rise | (BIT(pin) & rg->rising)); in mediatek_gpio_irq_unmask()
135 u32 rise, fall, high, low; in mediatek_gpio_irq_mask() local
138 rise = mtk_gpio_r32(rg, GPIO_REG_REDGE); in mediatek_gpio_irq_mask()
143 mtk_gpio_w32(rg, GPIO_REG_REDGE, rise & ~BIT(pin)); in mediatek_gpio_irq_mask()
|
| D | gpio-mlxbf2.c | 290 bool rise = false; in mlxbf2_gpio_irq_set_type() local
296 rise = true; in mlxbf2_gpio_irq_set_type()
299 rise = true; in mlxbf2_gpio_irq_set_type()
315 if (rise) { in mlxbf2_gpio_irq_set_type()
|
| D | gpio-stmpe.c | 296 u8 rise = NOT_SUPPORTED_IDX; in stmpe_dbg_show_one() local
319 rise = !!(ret & mask); in stmpe_dbg_show_one()
344 rise_values[rise], in stmpe_dbg_show_one()
|
| /Linux-v6.1/Documentation/leds/ |
| D | leds-sc27xx.rst | 12 hardware pattern, which is used to configure the rise time,
17 format, we should set brightness as 0 for rise stage, fall
|
| /Linux-v6.1/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.txt | 45 Number of nanoseconds the SCL signal takes to rise; t(r) in the I2C
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-class-led-driver-lm3533 | 27 Set the pattern generator fall and rise times (0..7), where:
|
| /Linux-v6.1/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru-kevin.dts | 185 /* These are relatively safe rise/fall times. */
201 /* These are relatively safe rise/fall times. */
|
| D | rk3399-gru-chromebook.dtsi | 450 /* These are relatively safe rise/fall times */
466 /* These are relatively safe rise/fall times */
|
| D | rk3399-gru-scarlet.dtsi | 263 /* These are relatively safe rise/fall times. */
295 /* These are relatively safe rise/fall times; TODO: measure */
|
| D | rk3399-gru.dtsi | 418 /* These are relatively safe rise/fall times */
428 /* These are relatively safe rise/fall times */
|
| D | px30-evb.dts | 440 /* These are relatively safe rise/fall times; TODO: measure */
|
| /Linux-v6.1/Documentation/devicetree/bindings/memory-controllers/ |
| D | mvebu-devbus.txt | 92 address and data to DEV_WEn rise.
100 data after DEV_WEn rise.
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | locks.rst | 35 for example. This gave rise to some other subtle problems if sendmail was
|
| /Linux-v6.1/Documentation/driver-api/gpio/ |
| D | intro.rst | 120 value (after the appropriate rise time passes), you know some other component is
|
| /Linux-v6.1/Documentation/fb/ |
| D | udlfb.rst | 53 * It's not clear what the future of fbdev is, given the rise of KMS/DRM.
|
| /Linux-v6.1/Documentation/m68k/ |
| D | buddha-driver.rst | 140 All the timings have in common: Select and IOR/IOW rise at
|
| /Linux-v6.1/arch/arm/boot/dts/ |
| D | at91-sama5d2_icp.dts | 375 * Trigger can be configured on falling, rise
|
| D | rk3288-veyron.dtsi | 333 /* 100kHz since 4.7k resistors don't rise fast enough */
|
| D | at91-sama5d2_xplained.dts | 460 * Trigger can be configured on falling, rise
|
| /Linux-v6.1/Documentation/process/ |
| D | stable-api-nonsense.rst | 183 - The quality of the driver will rise as the maintenance costs (to the
|
| /Linux-v6.1/Documentation/hwmon/ |
| D | dme1737.rst | 214 duty-cycle. If any of the temperatures rise above the auto_point3_temp value,
|
| /Linux-v6.1/Documentation/ABI/stable/ |
| D | sysfs-driver-speakup | 281 and most others, this causes the pitch of the voice to rise
|
| /Linux-v6.1/Documentation/dev-tools/ |
| D | coccinelle.rst | 240 giving rise to an error.
|
| /Linux-v6.1/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
510 code like the above. However, macro expansions can easily give rise
2189 rise directly to any machine instructions in the object code; rather,
2422 from the READ_ONCE() to the WRITE_ONCE() gives rise to an rcu-link
|
