Searched full:pwrseq (Results 1 – 10 of 10) sorted by relevance
4 $id: http://devicetree.org/schemas/mmc/mmc-pwrseq-sd8787.yaml#15 - mmc-pwrseq-sd878716 - mmc-pwrseq-wilc100038 pwrseq {39 compatible = "mmc-pwrseq-sd8787";
4 $id: http://devicetree.org/schemas/mmc/mmc-pwrseq-emmc.yaml#25 const: mmc-pwrseq-emmc44 pwrseq {45 compatible = "mmc-pwrseq-emmc";
4 $id: http://devicetree.org/schemas/mmc/mmc-pwrseq-simple.yaml#19 const: mmc-pwrseq-simple58 pwrseq {59 compatible = "mmc-pwrseq-simple";
271 It was invented for MMC pwrseq-simple which could be referred to272 mmc-pwrseq-simple.yaml. But now it\'s reused as a tunable delay274 regardless of whether pwrseq-simple is used. Default to 10ms if312 mmc-pwrseq:378 mmc-pwrseq = <&sdhci0_pwrseq>;
366 mmc-pwrseq = <&wifi_pwrseq>;
25 It is recommended to declare a mmc-pwrseq on SDIO host above WFx. Without26 it, you may encounter issues during reboot. The mmc-pwrseq should be27 compatible with mmc-pwrseq-simple. Please consult28 Documentation/devicetree/bindings/mmc/mmc-pwrseq-simple.yaml for more60 For SDIO, the reset gpio should declared using a mmc-pwrseq.113 compatible = "mmc-pwrseq-simple";120 mmc-pwrseq = <&wfx_pwrseq>;
43 A handle passed by the pwrseq core to every consumer that serves as the70 register with the pwrseq subsystem by calling pwrseq_device_register().75 The main difference between pwrseq and other linux kernel providers is the77 provider driver must implement the `match()` callback and pass it to the pwrseq91 .. kernel-doc:: include/linux/pwrseq/provider.h
127 pwrseq
53 - mmc-pwrseq-simple
99 compatible = "mmc-pwrseq-emmc";