Home
last modified time | relevance | path

Searched refs:SCI (Results 1 – 25 of 25) sorted by relevance

/linux/Documentation/devicetree/bindings/arm/keystone/
A Dti,k3-sci-common.yaml7 title: Common K3 TI-SCI bindings
16 through the TI-SCI protocol.
21 over the TI-SCI protocol. The following are some of the common properties
29 Should be a phandle to the TI-SCI System Controller node
34 Should contain the TI-SCI device id corresponding to the device. Please
42 - description: TI-SCI processor id for the remote processor device
43 - description: TI-SCI host id to which processor control ownership
A Dti,sci.yaml7 title: TI-SCI controller device node bindings
25 The TI-SCI node describes the Texas Instrument's System Controller entity node.
29 relationship between the TI-SCI parent node to the child node.
47 made available from TI-SCI controller.
55 Specifies the mailboxes used to communicate with TI-SCI Controller
56 made available from TI-SCI controller.
/linux/Documentation/devicetree/bindings/soc/ti/
A Dsci-pm-domain.yaml7 title: TI-SCI generic power domain node bindings
20 through a protocol called TI System Control Interface (TI-SCI protocol).
22 This PM domain node represents the global PM domain managed by the TI-SCI
23 controller. Since this relies on the TI SCI protocol to communicate with
24 the TI-SCI controller, it must be a child of the TI-SCI controller node.
33 The two cells represent values that the TI-SCI controller defines.
A Dk3-ringacc.yaml55 description: TI-SCI RM subtype for GP ring range
59 description: phandle on TI-SCI compatible System controller node
63 description: TI-SCI device id of the ring accelerator
/linux/arch/sh/kernel/cpu/sh3/
A Dsetup-sh770x.c29 DMAC, SCIF0, SCIF2, SCI, ADC_ADI, enumerator
40 INTC_VECT(SCI, 0x4e0), INTC_VECT(SCI, 0x500),
41 INTC_VECT(SCI, 0x520), INTC_VECT(SCI, 0x540),
69 { 0xfffffee4, 0, 16, 4, /* IPRB */ { WDT, REF, SCI, 0 } },
/linux/Documentation/devicetree/bindings/clock/
A Dti,sci-clk.yaml7 title: TI-SCI clock controller node bindings
17 through a protocol called TI System Control Interface (TI-SCI protocol).
19 This clock controller node uses the TI SCI protocol to perform various clock
21 node must be a child node of the associated TI-SCI system controller node.
33 The two cells represent values that the TI-SCI controller defines.
/linux/Documentation/devicetree/bindings/reset/
A Dti,sci-reset.yaml7 title: TI-SCI reset controller node bindings
17 through a protocol called TI System Control Interface (TI-SCI protocol).
19 This reset controller node uses the TI SCI protocol to perform the reset
21 node of the associated TI-SCI system controller node.
33 The two cells represent values that the TI-SCI controller defines.
/linux/Documentation/ABI/testing/
A Dsysfs-firmware-acpi100 the System Control Interrupt (SCI), which appears
105 special driver support. So while the SCI handles a few
119 To figure out where all the SCI's are coming from,
169 sci The number of times the ACPI SCI
172 sci_not The number of times the ACPI SCI
175 gpe_all count of SCI caused by GPEs.
/linux/drivers/soc/ti/
A DKconfig54 tristate "TI SCI PM Domains Driver"
59 the TI SCI protocol.
/linux/drivers/clk/keystone/
A DKconfig24 Forces the TI SCI clock driver to probe available clocks from the
/linux/Documentation/devicetree/bindings/dma/ti/
A Dk3-udma.yaml82 description: phandle to TI-SCI compatible System controller node
86 description: TI-SCI device id of UDMAP
/linux/arch/arm64/boot/dts/ti/
A Dk3-am64.dtsi83 <0x00 0x44043000 0x00 0x44043000 0x00 0x00000fe0>, /* TI SCI DEBUG */
/linux/arch/arm/boot/dts/
A Dintegratorap-im-pd1.dts56 /* Also used for the Smart Card Interface SCI */
/linux/Documentation/arm64/
A Dacpi_object_usage.rst655 APEI requires the equivalent of an SCI and an NMI on ARMv8. The SCI is used
661 Since there is no direct equivalent of the x86 SCI or NMI, arm64 handles
662 these slightly differently. The SCI is handled as a high priority interrupt;
/linux/drivers/reset/
A DKconfig235 tristate "TI System Control Interface (TI-SCI) reset driver"
/linux/Documentation/admin-guide/
A Ddevices.txt1293 74 char SCI bridge
1294 0 = /dev/SCI/0 SCI device 0
1295 1 = /dev/SCI/1 SCI device 1
1298 Currently for Dolphin Interconnect Solutions' PCI-SCI
2678 8 = /dev/ttySC0 SCI serial port (SuperH) - port 0
2679 9 = /dev/ttySC1 SCI serial port (SuperH) - port 1
2680 10 = /dev/ttySC2 SCI serial port (SuperH) - port 2
2681 11 = /dev/ttySC3 SCI serial port (SuperH) - port 3
/linux/Documentation/x86/x86_64/
A Dboot-options.rst213 Set up ACPI SCI interrupt.
/linux/Documentation/watchdog/
A Dwatchdog-parameters.rst310 0 = RESET(*) 1 = SMI 2 = NMI 3 = SCI
/linux/drivers/tty/serial/
A DKconfig655 tristate "SuperH SCI(F) serial port support"
661 int "Maximum number of SCI(F) serial ports" if EXPERT
671 bool "Support for console on SuperH SCI(F)" if EXPERT
677 bool "Support for early console on SuperH SCI(F)" if EXPERT
/linux/drivers/spi/
A DKconfig788 tristate "SuperH SCI SPI controller"
792 SPI driver for SuperH SCI blocks.
/linux/drivers/acpi/
A DKconfig444 SCI, mainly the corrected errors.
/linux/Documentation/userspace-api/ioctl/
A Dioctl-number.rst294 'w' all CERN SCI driver
/linux/arch/x86/
A DKconfig2739 bool "OLPC XO-1 SCI extras"
2744 Add support for SCI-based features of the OLPC XO-1 laptop:
2753 bool "OLPC XO-1.5 SCI extras"
2757 Add support for SCI-based features of the OLPC XO-1.5 laptop:
/linux/
A Dmodules.builtin.modinfo1 …SCI protocol�irq_ti_sci_intr.author=Lokesh Vutla <lokeshvutla@ticom>�irq_ti_sci_inta.license=GPL v…
16 …i_sci.author=Nishanth Menon�ti_sci.description=TI System Control Interface(SCI) driver�ti_sci.lice…
/linux/Documentation/power/
A Dpci.rst236 Control Interrupt (SCI) to notify the kernel of the event. Then, the SCI

Completed in 52 milliseconds