Searched refs:asserted (Results 1 – 25 of 114) sorted by relevance
12345
/linux-6.1.9/Documentation/devicetree/bindings/bus/ |
D | nvidia,tegra20-gmi.txt | 46 If omitted it will be asserted with data. 56 - nvidia,snor-muxed-width: Number of cycles MUX address/data asserted on the 58 - nvidia,snor-hold-width: Number of cycles CE stays asserted after the 61 - nvidia,snor-adv-width: Number of cycles during which ADV stays asserted. 63 - nvidia,snor-ce-width: Number of cycles before CE is asserted. 65 - nvidia,snor-we-width: Number of cycles during which WE stays asserted. 67 - nvidia,snor-oe-width: Number of cycles during which OE stays asserted. 69 - nvidia,snor-wait-width: Number of cycles before READY is asserted.
|
D | qcom,ebi2.txt | 78 drive the data bus after OE is de-asserted, in order to avoid contention on 84 WE is asserted until CS is asserted. With a hold of 1 (value = 0), the CS 100 assertion, with respect to the cycle where ADV (address valid) is asserted.
|
/linux-6.1.9/drivers/reset/ |
D | reset-uniphier.c | 317 int ret, asserted; in uniphier_reset_status() local 326 asserted = !!(val & BIT(p->bit)); in uniphier_reset_status() 329 asserted = !asserted; in uniphier_reset_status() 331 return asserted; in uniphier_reset_status()
|
/linux-6.1.9/Documentation/ABI/testing/ |
D | sysfs-driver-ge-achc | 14 1 means the reset line is asserted, 0 means it's not 15 asserted. The file is read and writable.
|
/linux-6.1.9/Documentation/devicetree/bindings/iio/adc/ |
D | adi,ad7780.yaml | 46 specified, it will be asserted during driver probe. As the 53 the ad778x chips. If specified, it will be asserted during 61 for the ad778x chips. If specified, it will be asserted
|
D | maxim,max1241.yaml | 38 specified, the /SHDN pin will be asserted between conversions,
|
/linux-6.1.9/Documentation/devicetree/bindings/reset/ |
D | st,stih407-picophyreset.yaml | 17 The actual action taken when softreset is asserted is hardware dependent. 18 However, when asserted it may not be possible to access the hardware's
|
D | st,sti-softreset.txt | 9 The actual action taken when softreset is asserted is hardware dependent. 10 However, when asserted it may not be possible to access the hardware's
|
D | st,stih407-powerdown.yaml | 19 The actual action taken when powerdown is asserted is hardware dependent. 20 However, when asserted it may not be possible to access the hardware's
|
D | img,pistachio-reset.txt | 8 The actual action taken when soft reset is asserted is hardware dependent. 9 However, when asserted it may not be possible to access the hardware's
|
D | ti,tps380x-reset.yaml | 16 reset input (MR). The RESET output remains asserted for the factory
|
/linux-6.1.9/Documentation/devicetree/bindings/pci/ |
D | xilinx-nwl-pcie.txt | 18 "msi1, msi0": interrupt asserted when an MSI is received 19 "intx": interrupt asserted when a legacy interrupt is received 20 "misc": interrupt asserted when miscellaneous interrupt is received
|
/linux-6.1.9/Documentation/devicetree/bindings/input/ |
D | gpio-keys.yaml | 71 Specifies whether the key should wake the system when asserted, when 77 EV_ACT_ANY - both asserted and deasserted 78 EV_ACT_ASSERTED - asserted
|
/linux-6.1.9/Documentation/devicetree/bindings/mmc/ |
D | mmc-pwrseq-simple.yaml | 26 contains a list of GPIO specifiers. The reset GPIOs are asserted 28 They will be de-asserted right after the power has been provided to the
|
/linux-6.1.9/Documentation/hwmon/ |
D | adm9240.rst | 90 Temperature alarm is asserted once the temperature exceeds the high limit, 114 - low speed alarm will be asserted if fan speed is 127 - alarm will be asserted 161 An alarm is asserted for any voltage going below or above the set limits. 172 An alarm is asserted when the CI pin goes active high. The ADM9240
|
D | lm93.rst | 103 signals. I.e. when #P1_PROCHOT is asserted, the LM93 will automatically 124 which 1 indicates #VRD_HOT is asserted and 0 indicates it is negated. These 254 If the #PROCHOT or #VRDHOT signals are asserted while bound to a PWM output 298 vrdhot<n> 0 means negated, 1 means asserted 303 pwm_auto_prochot_ramp ramp time per step when #PROCHOT asserted 304 pwm_auto_vrdhot_ramp ramp time per step when #VRDHOT asserted
|
/linux-6.1.9/drivers/clk/baikal-t1/ |
D | Kconfig | 50 can be directly asserted/de-asserted (PCIe and DDR sub-domains).
|
/linux-6.1.9/Documentation/driver-api/ |
D | reset.rst | 88 That is, an assert causes the reset line to be asserted immediately, and a 100 will actually cause the reset line to be asserted. 103 The API only guarantees that the reset line can not be asserted as long as any 130 reset line is asserted.
|
/linux-6.1.9/Documentation/devicetree/bindings/memory-controllers/ |
D | mvebu-devbus.txt | 64 DEV_OEn and DEV_CSn are asserted at the same cycle. 73 DEV_OEn and DEV_CSn are de-asserted at the same cycle 76 DEV_OEn is always de-asserted the next cycle after
|
/linux-6.1.9/Documentation/devicetree/bindings/pinctrl/ |
D | mediatek,mt6797-pinctrl.yaml | 132 cycle when asserted (high pulse width adjustment). Valid arguments 139 when asserted (high pulse width adjustment). Valid arguments are
|
/linux-6.1.9/Documentation/devicetree/bindings/spi/ |
D | cdns,qspi-nor-peripheral-props.yaml | 25 outputs are de-asserted between transactions.
|
/linux-6.1.9/Documentation/devicetree/bindings/eeprom/ |
D | microchip,93lc46b.yaml | 38 specifies the GPIO that needs to be asserted prior to each access
|
/linux-6.1.9/Documentation/devicetree/bindings/watchdog/ |
D | arm,sp805.yaml | 15 when the next interrupt would be triggered, the reset signal is asserted.
|
/linux-6.1.9/Documentation/firmware-guide/acpi/ |
D | lpit.rst | 31 residency, or system time spent with the SLP_S0# signal asserted.
|
/linux-6.1.9/Documentation/devicetree/bindings/rtc/ |
D | microchip,mfps-rtc.yaml | 30 RTC_MATCH, asserted when the content of the Alarm register is equal
|
12345