Home
last modified time | relevance | path

Searched refs:conduit (Results 1 – 11 of 11) sorted by relevance

/Linux-v4.19/drivers/firmware/
Dpsci.c63 .conduit = PSCI_CONDUIT_NONE,
216 static void set_conduit(enum psci_conduit conduit) in set_conduit() argument
218 switch (conduit) { in set_conduit()
226 WARN(1, "Unexpected PSCI conduit %d\n", conduit); in set_conduit()
229 psci_ops.conduit = conduit; in set_conduit()
Darm_sdei.c928 int conduit; in sdei_probe() local
930 conduit = sdei_get_conduit(pdev); in sdei_probe()
957 sdei_entry_point = sdei_arch_get_entry_point(conduit); in sdei_probe()
/Linux-v4.19/arch/arm64/kernel/
Dsdei.c140 unsigned long sdei_arch_get_entry_point(int conduit) in sdei_arch_get_entry_point() argument
158 sdei_exit_mode = (conduit == CONDUIT_HVC) ? SDEI_EXIT_HVC : SDEI_EXIT_SMC; in sdei_arch_get_entry_point()
Dcpu_errata.c206 switch (psci_ops.conduit) { in enable_smccc_arch_workaround_1()
285 switch (psci_ops.conduit) { in arm64_update_smccc_conduit()
315 switch (psci_ops.conduit) { in arm64_set_ssbd_mitigation()
344 switch (psci_ops.conduit) { in has_ssbd_mitigation()
/Linux-v4.19/arch/arm64/include/asm/
Dsdei.h40 unsigned long sdei_arch_get_entry_point(int conduit);
/Linux-v4.19/include/linux/
Dpsci.h48 enum psci_conduit conduit; member
Darm_sdei.h18 #define sdei_arch_get_entry_point(conduit) (0) argument
/Linux-v4.19/arch/arm/mm/
Dproc-v7-bugs.c85 switch (psci_ops.conduit) { in cpu_v7_spectre_init()
/Linux-v4.19/Documentation/powerpc/
Dhvcs.txt227 act as a conduit for data transfer to and from the tty device. They do not
279 almost all data writes. When hvcs is being used as a tty conduit to tunnel
536 Q: Can I use /dev/hvcs* as a conduit to another partition and use a tty
541 In order to get a tty conduit working between the two partitions the HMC
553 read or write to /dev/hvcs*. Now you have a tty conduit between two
/Linux-v4.19/Documentation/networking/dsa/
Ddsa.txt61 would get two interfaces for the same conduit: master netdev, and "cpu" netdev
93 drivers. Such network devices are also often referred to as conduit network
280 interface can only exclusively be used as a conduit interface. Sending packets
/Linux-v4.19/Documentation/networking/
Dswitchdev.txt77 the physical port and provides a conduit for control traffic to/from the