Home
last modified time | relevance | path

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

/linux-6.1.9/drivers/firmware/arm_ffa/
Dsmccc.c22 enum arm_smccc_conduit conduit; in ffa_transport_init() local
27 conduit = arm_smccc_1_1_get_conduit(); in ffa_transport_init()
28 if (conduit == SMCCC_CONDUIT_NONE) { in ffa_transport_init()
33 if (conduit == SMCCC_CONDUIT_SMC) in ffa_transport_init()
/linux-6.1.9/drivers/firmware/smccc/
Dsmccc.c21 void __init arm_smccc_version_init(u32 version, enum arm_smccc_conduit conduit) in arm_smccc_version_init() argument
24 smccc_conduit = conduit; in arm_smccc_version_init()
/linux-6.1.9/arch/arm64/kernel/
Dsdei.c165 unsigned long sdei_arch_get_entry_point(int conduit) in sdei_arch_get_entry_point() argument
184 sdei_exit_mode = (conduit == SMCCC_CONDUIT_HVC) ? SDEI_EXIT_HVC : SDEI_EXIT_SMC; in sdei_arch_get_entry_point()
/linux-6.1.9/arch/arm64/include/asm/
Dsdei.h43 unsigned long sdei_arch_get_entry_point(int conduit);
/linux-6.1.9/drivers/firmware/psci/
Dpsci.c264 static void set_conduit(enum arm_smccc_conduit conduit) in set_conduit() argument
266 switch (conduit) { in set_conduit()
274 WARN(1, "Unexpected PSCI conduit %d\n", conduit); in set_conduit()
277 psci_conduit = conduit; in set_conduit()
/linux-6.1.9/include/linux/
Darm_sdei.h16 #define sdei_arch_get_entry_point(conduit) (0) argument
Darm-smccc.h225 void __init arm_smccc_version_init(u32 version, enum arm_smccc_conduit conduit);
/linux-6.1.9/drivers/firmware/
Darm_sdei.c960 int conduit; in sdei_probe() local
962 conduit = sdei_get_conduit(pdev); in sdei_probe()
987 sdei_entry_point = sdei_arch_get_entry_point(conduit); in sdei_probe()
/linux-6.1.9/Documentation/powerpc/
Dhvcs.rst230 act as a conduit for data transfer to and from the tty device. They do not
282 almost all data writes. When hvcs is being used as a tty conduit to tunnel
548 Q: Can I use /dev/hvcs* as a conduit to another partition and use a tty
553 In order to get a tty conduit working between the two partitions the HMC
565 read or write to /dev/hvcs*. Now you have a tty conduit between two
/linux-6.1.9/Documentation/networking/dsa/
Ddsa.rst59 would get two interfaces for the same conduit: master netdev, and "cpu" netdev
228 drivers. Such network devices are also often referred to as conduit network
424 interface can only exclusively be used as a conduit interface. Sending packets
/linux-6.1.9/Documentation/networking/
Dswitchdev.rst88 the physical port and provides a conduit for control traffic to/from the