Home
last modified time | relevance | path

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

/linux/Documentation/leds/
H A 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
H A Dleds-cht-wcove.rst27 The rise and fall times must be the same value.
/linux/Documentation/devicetree/bindings/i2c/
H A Di2c-mux-ltc4306.txt24 - ltc,downstream-accelerators-enable: Enables the rise time accelerators
26 - ltc,upstream-accelerators-enable: Enables the rise time accelerators
/linux/Documentation/ABI/testing/
H A Dsysfs-class-led-driver-lm353327 Set the pattern generator fall and rise times (0..7), where:
/linux/Documentation/devicetree/bindings/memory-controllers/
H A Dmvebu-devbus.txt92 address and data to DEV_WEn rise.
100 data after DEV_WEn rise.
/linux/arch/arm64/boot/dts/rockchip/
H A Dpx30-ringneck.dtsi413 * Hardware CS has a very slow rise time of about 6us,
415 * With cs-gpios we have a rise time of about 20ns.
H A Drk3399-gru-scarlet.dtsi262 /* These are relatively safe rise/fall times. */
294 /* These are relatively safe rise/fall times; TODO: measure */
H A Drk3399-gru.dtsi417 /* These are relatively safe rise/fall times */
427 /* These are relatively safe rise/fall times */
H A Dpx30-evb.dts443 /* These are relatively safe rise/fall times; TODO: measure */
/linux/Documentation/filesystems/
H A Dlocks.rst35 for example. This gave rise to some other subtle problems if sendmail was
/linux/Documentation/driver-api/gpio/
H A Dintro.rst108 value (after the appropriate rise time passes), you know some other component is
/linux/drivers/gpu/drm/mediatek/
H A Dmtk_hdmi_v2.c457 static inline void mtk_hdmi_i2s_sck_edge_rise(struct mtk_hdmi *hdmi, bool rise) in mtk_hdmi_i2s_sck_edge_rise() argument
459 if (rise) in mtk_hdmi_i2s_sck_edge_rise()
/linux/Documentation/fb/
H A Dudlfb.rst53 * It's not clear what the future of fbdev is, given the rise of KMS/DRM.
/linux/Documentation/arch/m68k/
H A Dbuddha-driver.rst140 All the timings have in common: Select and IOR/IOW rise at
/linux/arch/arm/boot/dts/rockchip/
H A Drk3288-veyron.dtsi337 /* 100kHz since 4.7k resistors don't rise fast enough */
/linux/arch/arm/boot/dts/microchip/
H A Dat91-sama5d2_xplained.dts460 * Trigger can be configured on falling, rise
H A Dat91-sama5d2_icp.dts419 * Trigger can be configured on falling, rise
/linux/Documentation/process/
H A Dstable-api-nonsense.rst183 - The quality of the driver will rise as the maintenance costs (to the
/linux/arch/arm64/boot/dts/qcom/
H A Dsc7280-idp.dtsi534 qcom,hs-rise-fall-time-bp = <0>;
H A Dqcm6490-shift-otter.dts966 qcom,hs-rise-fall-time-bp = <5430>;
/linux/Documentation/hwmon/
H A Ddme1737.rst214 duty-cycle. If any of the temperatures rise above the auto_point3_temp value,
/linux/Documentation/ABI/stable/
H A Dsysfs-driver-speakup289 and most others, this causes the pitch of the voice to rise
/linux/Documentation/iio/
H A Dadxl345.rst244 acceleration must rise above the threshold and then fall below it within the
/linux/tools/memory-model/Documentation/
H A Dexplanation.txt312 shared memory, do not give rise to events. Thus, arithmetic and
463 index value loaded by the first. Pointer indirection also gives rise
512 code like the above. However, macro expansions can easily give rise
2376 rise directly to any machine instructions in the object code; rather,
2609 from the READ_ONCE() to the WRITE_ONCE() gives rise to an rcu-link