Home
last modified time | relevance | path

Searched refs:rise (Results 1 – 25 of 31) sorted by relevance

12

/linux-5.19.10/drivers/gpio/
Dgpio-mt7621.c113 u32 rise, fall, high, low; in mediatek_gpio_irq_unmask() local
116 rise = mtk_gpio_r32(rg, GPIO_REG_REDGE); in mediatek_gpio_irq_unmask()
120 mtk_gpio_w32(rg, GPIO_REG_REDGE, rise | (BIT(pin) & rg->rising)); in mediatek_gpio_irq_unmask()
134 u32 rise, fall, high, low; in mediatek_gpio_irq_mask() local
137 rise = mtk_gpio_r32(rg, GPIO_REG_REDGE); in mediatek_gpio_irq_mask()
142 mtk_gpio_w32(rg, GPIO_REG_REDGE, rise & ~BIT(pin)); in mediatek_gpio_irq_mask()
Dgpio-mlxbf2.c292 bool rise = false; in mlxbf2_gpio_irq_set_type() local
298 rise = true; in mlxbf2_gpio_irq_set_type()
301 rise = true; in mlxbf2_gpio_irq_set_type()
317 if (rise) { in mlxbf2_gpio_irq_set_type()
Dgpio-stmpe.c296 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-5.19.10/Documentation/devicetree/bindings/sound/
Dcirrus,cs42l42.yaml74 cirrus,ts-dbnc-rise:
161 If present this sets the rate that the HS bias should rise and fall.
162 The actual rise and fall times depend on external hardware (the
163 datasheet gives several rise and fall time examples).
165 0 - Fast rise time; slow, load-dependent fall time
218 cirrus,ts-dbnc-rise = <CS42L42_TS_DBNCE_1000>;
/linux-5.19.10/Documentation/leds/
Dleds-sc27xx.rst12 hardware pattern, which is used to configure the rise time,
17 format, we should set brightness as 0 for rise stage, fall
/linux-5.19.10/Documentation/devicetree/bindings/i2c/
Di2c-mux-ltc4306.txt24 - ltc,downstream-accelerators-enable: Enables the rise time accelerators
26 - ltc,upstream-accelerators-enable: Enables the rise time accelerators
Di2c-rk3x.yaml82 Number of nanoseconds the SCL signal takes to rise
Drenesas,rcar-i2c.yaml106 Number of nanoseconds the SCL signal takes to rise; t(r) in the I2C
Di2c.txt45 Number of nanoseconds the SCL signal takes to rise; t(r) in the I2C
/linux-5.19.10/Documentation/ABI/testing/
Dsysfs-class-led-driver-lm353327 Set the pattern generator fall and rise times (0..7), where:
/linux-5.19.10/arch/arm64/boot/dts/rockchip/
Drk3399-gru-kevin.dts185 /* These are relatively safe rise/fall times. */
201 /* These are relatively safe rise/fall times. */
Drk3399-gru-chromebook.dtsi442 /* These are relatively safe rise/fall times */
458 /* These are relatively safe rise/fall times */
Drk3399-gru-scarlet.dtsi263 /* These are relatively safe rise/fall times. */
295 /* These are relatively safe rise/fall times; TODO: measure */
Drk3399-gru.dtsi418 /* These are relatively safe rise/fall times */
428 /* These are relatively safe rise/fall times */
Dpx30-evb.dts440 /* These are relatively safe rise/fall times; TODO: measure */
/linux-5.19.10/Documentation/devicetree/bindings/phy/
Dphy-stm32-usbphyc.yaml113 description: Enables the FS rise/fall tuning option
117 description: Enables the HS rise/fall reduction feature
/linux-5.19.10/Documentation/devicetree/bindings/memory-controllers/
Dmvebu-devbus.txt92 address and data to DEV_WEn rise.
100 data after DEV_WEn rise.
/linux-5.19.10/Documentation/filesystems/
Dlocks.rst35 for example. This gave rise to some other subtle problems if sendmail was
/linux-5.19.10/Documentation/driver-api/gpio/
Dintro.rst120 value (after the appropriate rise time passes), you know some other component is
/linux-5.19.10/Documentation/fb/
Dudlfb.rst53 * It's not clear what the future of fbdev is, given the rise of KMS/DRM.
/linux-5.19.10/arch/arm/boot/dts/
Drk3288-veyron.dtsi333 /* 100kHz since 4.7k resistors don't rise fast enough */
Dat91-sama5d2_icp.dts376 * Trigger can be configured on falling, rise
Dat91-sama5d2_xplained.dts458 * Trigger can be configured on falling, rise
/linux-5.19.10/Documentation/m68k/
Dbuddha-driver.rst140 All the timings have in common: Select and IOR/IOW rise at
/linux-5.19.10/Documentation/process/
Dstable-api-nonsense.rst183 - The quality of the driver will rise as the maintenance costs (to the

12