Home
last modified time | relevance | path

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

/Linux-v5.10/drivers/gpio/
Dgpio-mt7621.c115 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()
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-v5.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-v5.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.txt45 Number of nanoseconds the SCL signal takes to rise; t(r) in the I2C
/Linux-v5.10/Documentation/devicetree/bindings/sound/
Dcs42l42.txt30 - cirrus,ts-dbnc-rise : Debounce the rising edge of TIP_SENSE_PLUG. With no
101 cirrus,ts-dbnc-rise = <0x05>;
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-class-led-driver-lm353327 Set the pattern generator fall and rise times (0..7), where:
/Linux-v5.10/arch/arm64/boot/dts/rockchip/
Drk3399-gru-kevin.dts184 /* These are relatively safe rise/fall times. */
200 /* These are relatively safe rise/fall times. */
Drk3399-gru-chromebook.dtsi259 /* These are relatively safe rise/fall times */
275 /* These are relatively safe rise/fall times */
Drk3399-gru-scarlet.dtsi261 /* These are relatively safe rise/fall times. */
293 /* These are relatively safe rise/fall times; TODO: measure */
Drk3399-gru.dtsi385 /* These are relatively safe rise/fall times */
395 /* These are relatively safe rise/fall times */
/Linux-v5.10/Documentation/devicetree/bindings/memory-controllers/
Dmvebu-devbus.txt92 address and data to DEV_WEn rise.
100 data after DEV_WEn rise.
/Linux-v5.10/Documentation/filesystems/
Dlocks.rst35 for example. This gave rise to some other subtle problems if sendmail was
/Linux-v5.10/Documentation/driver-api/gpio/
Dintro.rst120 value (after the appropriate rise time passes), you know some other component is
Dlegacy.rst437 value (after the appropriate rise time passes), you know some other component
/Linux-v5.10/Documentation/fb/
Dudlfb.rst53 * It's not clear what the future of fbdev is, given the rise of KMS/DRM.
/Linux-v5.10/arch/arm/boot/dts/
Drk3288-veyron.dtsi333 /* 100kHz since 4.7k resistors don't rise fast enough */
Dat91-sama5d2_icp.dts364 * Trigger can be configured on falling, rise
Dat91-sama5d2_xplained.dts458 * Trigger can be configured on falling, rise
/Linux-v5.10/Documentation/m68k/
Dbuddha-driver.rst140 All the timings have in common: Select and IOR/IOW rise at
/Linux-v5.10/Documentation/process/
Dstable-api-nonsense.rst183 - The quality of the driver will rise as the maintenance costs (to the
/Linux-v5.10/Documentation/hwmon/
Ddme1737.rst214 duty-cycle. If any of the temperatures rise above the auto_point3_temp value,
/Linux-v5.10/Documentation/ABI/stable/
Dsysfs-driver-speakup281 and most others, this causes the pitch of the voice to rise
/Linux-v5.10/tools/memory-model/Documentation/
Dexplanation.txt311 shared memory, do not give rise to events. Thus, arithmetic and
462 index value loaded by the first. Pointer indirection also gives rise
2132 rise directly to any machine instructions in the object code; rather,
2365 from the READ_ONCE() to the WRITE_ONCE() gives rise to an rcu-link
/Linux-v5.10/Documentation/admin-guide/laptops/
Dthinkpad-acpi.rst1249 rise too much.