| /Linux-v6.6/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 | 293 bool rise = false; in mlxbf2_gpio_irq_set_type() local
299 rise = true; in mlxbf2_gpio_irq_set_type()
302 rise = true; in mlxbf2_gpio_irq_set_type()
318 if (rise) { in mlxbf2_gpio_irq_set_type()
|
| D | gpio-stmpe.c | 298 u8 rise = NOT_SUPPORTED_IDX; in stmpe_dbg_show_one() local
321 rise = !!(ret & mask); in stmpe_dbg_show_one()
346 rise_values[rise], in stmpe_dbg_show_one()
|
| /Linux-v6.6/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
|
| D | leds-cht-wcove.rst | 27 The rise and fall times must be the same value.
|
| /Linux-v6.6/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.6/Documentation/ABI/testing/ |
| D | sysfs-class-led-driver-lm3533 | 27 Set the pattern generator fall and rise times (0..7), where:
|
| /Linux-v6.6/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 | 449 /* These are relatively safe rise/fall times */
465 /* These are relatively safe rise/fall times */
|
| D | rk3399-gru-scarlet.dtsi | 262 /* These are relatively safe rise/fall times. */
294 /* 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.6/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.6/Documentation/filesystems/ |
| D | locks.rst | 35 for example. This gave rise to some other subtle problems if sendmail was
|
| /Linux-v6.6/arch/arm64/boot/dts/freescale/ |
| D | imx8mp-dhcom-pdk3.dts | 275 /* RESET_N signal rise time ~100ms */
|
| /Linux-v6.6/Documentation/driver-api/gpio/ |
| D | intro.rst | 120 value (after the appropriate rise time passes), you know some other component is
|
| /Linux-v6.6/Documentation/fb/ |
| D | udlfb.rst | 53 * It's not clear what the future of fbdev is, given the rise of KMS/DRM.
|
| /Linux-v6.6/arch/arm/boot/dts/rockchip/ |
| D | rk3288-veyron.dtsi | 337 /* 100kHz since 4.7k resistors don't rise fast enough */
|
| /Linux-v6.6/Documentation/arch/m68k/ |
| D | buddha-driver.rst | 140 All the timings have in common: Select and IOR/IOW rise at
|
| /Linux-v6.6/arch/arm/boot/dts/microchip/ |
| D | at91-sama5d2_icp.dts | 375 * Trigger can be configured on falling, rise
|
| D | at91-sama5d2_xplained.dts | 460 * Trigger can be configured on falling, rise
|
| /Linux-v6.6/arch/arm64/boot/dts/qcom/ |
| D | sc7280-idp.dtsi | 516 qcom,hs-rise-fall-time-bp = <0>;
|
| /Linux-v6.6/Documentation/process/ |
| D | stable-api-nonsense.rst | 183 - The quality of the driver will rise as the maintenance costs (to the
|
| /Linux-v6.6/Documentation/hwmon/ |
| D | dme1737.rst | 214 duty-cycle. If any of the temperatures rise above the auto_point3_temp value,
|
