| /linux/drivers/gpio/ |
| A D | gpio-mt7621.c | 113 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()
|
| A D | gpio-mlxbf2.c | 292 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()
|
| A 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/Documentation/leds/ |
| A 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/Documentation/devicetree/bindings/i2c/ |
| A 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
|
| A D | renesas,rcar-i2c.yaml | 101 Number of nanoseconds the SCL signal takes to rise; t(r) in the I2C
|
| A D | i2c-rk3x.yaml | 82 Number of nanoseconds the SCL signal takes to rise
|
| A D | i2c.txt | 45 Number of nanoseconds the SCL signal takes to rise; t(r) in the I2C
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A D | cs42l42.txt | 31 - cirrus,ts-dbnc-rise : Debounce the rising edge of TIP_SENSE_PLUG. With no
109 cirrus,ts-dbnc-rise = <0x05>;
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| A D | rk3399-gru-kevin.dts | 185 /* These are relatively safe rise/fall times. */
201 /* These are relatively safe rise/fall times. */
|
| A D | rk3399-gru-chromebook.dtsi | 435 /* These are relatively safe rise/fall times */
451 /* These are relatively safe rise/fall times */
|
| A D | rk3399-gru-scarlet.dtsi | 263 /* These are relatively safe rise/fall times. */
295 /* These are relatively safe rise/fall times; TODO: measure */
|
| A D | rk3399-gru.dtsi | 390 /* These are relatively safe rise/fall times */
400 /* These are relatively safe rise/fall times */
|
| A D | px30-evb.dts | 440 /* These are relatively safe rise/fall times; TODO: measure */
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-class-led-driver-lm3533 | 27 Set the pattern generator fall and rise times (0..7), where:
|
| /linux/Documentation/devicetree/bindings/phy/ |
| A D | phy-stm32-usbphyc.yaml | 114 description: Enables the FS rise/fall tuning option
118 description: Enables the HS rise/fall reduction feature
|
| /linux/Documentation/devicetree/bindings/memory-controllers/ |
| A D | mvebu-devbus.txt | 92 address and data to DEV_WEn rise.
100 data after DEV_WEn rise.
|
| /linux/Documentation/filesystems/ |
| A D | locks.rst | 35 for example. This gave rise to some other subtle problems if sendmail was
|
| /linux/Documentation/driver-api/gpio/ |
| A D | intro.rst | 120 value (after the appropriate rise time passes), you know some other component is
|
| /linux/Documentation/fb/ |
| A D | udlfb.rst | 53 * It's not clear what the future of fbdev is, given the rise of KMS/DRM.
|
| /linux/Documentation/m68k/ |
| A D | buddha-driver.rst | 140 All the timings have in common: Select and IOR/IOW rise at
|
| /linux/arch/arm/boot/dts/ |
| A D | at91-sama5d2_icp.dts | 377 * Trigger can be configured on falling, rise
|
| A D | rk3288-veyron.dtsi | 333 /* 100kHz since 4.7k resistors don't rise fast enough */
|
| A D | at91-sama5d2_xplained.dts | 458 * Trigger can be configured on falling, rise
|
| /linux/Documentation/process/ |
| A D | stable-api-nonsense.rst | 183 - The quality of the driver will rise as the maintenance costs (to the
|