Home
last modified time | relevance | path

Searched full:hsi (Results 1 – 25 of 209) sorted by relevance

123456789

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/hsi/
Dclient-devices.txt1 Each HSI port is supposed to have one child node, which
2 symbols the remote device connected to the HSI port. The
3 following properties are standardized for HSI clients:
5 Required HSI configuration properties:
7 - hsi-channel-ids: A list of channel ids
9 - hsi-rx-mode: Receiver Bit transmission mode ("stream" or "frame")
10 - hsi-tx-mode: Transmitter Bit transmission mode ("stream" or "frame")
11 - hsi-mode: May be used instead hsi-rx-mode and hsi-tx-mode if
14 - hsi-speed-kbps: Max bit transmission speed in kbit/s
15 - hsi-flow: RX flow type ("synchronized" or "pipeline")
[all …]
Dnokia-modem.txt3 The Nokia modem HSI client follows the common HSI client binding
5 properties are needed by the Nokia modem HSI client:
12 - hsi-channel-names: Should contain the following strings
30 modem: hsi-client {
36 hsi-channel-ids = <0>, <1>, <2>, <3>;
37 hsi-channel-names = "mcsaab-control",
41 hsi-speed-kbps = <55000>;
42 hsi-mode = "frame";
43 hsi-flow = "synchronized";
44 hsi-arb-mode = "round-robin";
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/hsi/
Dclient-devices.txt1 Each HSI port is supposed to have one child node, which
2 symbols the remote device connected to the HSI port. The
3 following properties are standardized for HSI clients:
5 Required HSI configuration properties:
7 - hsi-channel-ids: A list of channel ids
9 - hsi-rx-mode: Receiver Bit transmission mode ("stream" or "frame")
10 - hsi-tx-mode: Transmitter Bit transmission mode ("stream" or "frame")
11 - hsi-mode: May be used instead hsi-rx-mode and hsi-tx-mode if
14 - hsi-speed-kbps: Max bit transmission speed in kbit/s
15 - hsi-flow: RX flow type ("synchronized" or "pipeline")
[all …]
Dnokia-modem.txt3 The Nokia modem HSI client follows the common HSI client binding
5 properties are needed by the Nokia modem HSI client:
12 - hsi-channel-names: Should contain the following strings
30 modem: hsi-client {
36 hsi-channel-ids = <0>, <1>, <2>, <3>;
37 hsi-channel-names = "mcsaab-control",
41 hsi-speed-kbps = <55000>;
42 hsi-mode = "frame";
43 hsi-flow = "synchronized";
44 hsi-arb-mode = "round-robin";
/kernel/linux/linux-5.10/drivers/hsi/
Dhsi_core.c3 * HSI core.
9 #include <linux/hsi/hsi.h>
23 return sprintf(buf, "hsi:%s\n", dev_name(dev)); in modalias_show()
35 add_uevent_var(env, "MODALIAS=hsi:%s", dev_name(dev)); in hsi_bus_uevent()
52 .name = "hsi",
103 pr_err("hsi: failed to register client: %s\n", info->name); in hsi_new_client()
118 static void hsi_scan_board_info(struct hsi_controller *hsi) in hsi_scan_board_info() argument
124 if (cl_info->info.hsi_id == hsi->id) { in hsi_scan_board_info()
125 p = hsi_find_port_num(hsi, cl_info->info.port); in hsi_scan_board_info()
214 err = hsi_of_property_parse_mode(client, "hsi-mode", &mode); in hsi_add_client_from_dt()
[all …]
Dhsi_boardinfo.c3 * HSI clients registration interface
9 #include <linux/hsi/hsi.h>
15 * hsi_board_list is only used internally by the HSI framework.
22 * hsi_register_board_info - Register HSI clients information
23 * @info: Array of HSI clients on the board
26 * HSI clients are statically declared and registered on board files.
28 * HSI clients will be automatically registered to the HSI bus once the
DKconfig3 # HSI driver configuration
5 menuconfig HSI config
6 tristate "HSI support"
12 if HSI
18 source "drivers/hsi/controllers/Kconfig"
19 source "drivers/hsi/clients/Kconfig"
21 endif # HSI
DMakefile3 # Makefile for HSI
5 obj-$(CONFIG_HSI) += hsi.o
6 hsi-objs := hsi_core.o
7 hsi-$(CONFIG_HSI_BOARDINFO) += hsi_boardinfo.o
/kernel/linux/linux-6.6/drivers/hsi/
Dhsi_core.c3 * HSI core.
9 #include <linux/hsi/hsi.h>
23 return sprintf(buf, "hsi:%s\n", dev_name(dev)); in modalias_show()
35 add_uevent_var(env, "MODALIAS=hsi:%s", dev_name(dev)); in hsi_bus_uevent()
52 .name = "hsi",
103 pr_err("hsi: failed to register client: %s\n", info->name); in hsi_new_client()
118 static void hsi_scan_board_info(struct hsi_controller *hsi) in hsi_scan_board_info() argument
124 if (cl_info->info.hsi_id == hsi->id) { in hsi_scan_board_info()
125 p = hsi_find_port_num(hsi, cl_info->info.port); in hsi_scan_board_info()
214 err = hsi_of_property_parse_mode(client, "hsi-mode", &mode); in hsi_add_client_from_dt()
[all …]
Dhsi_boardinfo.c3 * HSI clients registration interface
9 #include <linux/hsi/hsi.h>
15 * hsi_board_list is only used internally by the HSI framework.
22 * hsi_register_board_info - Register HSI clients information
23 * @info: Array of HSI clients on the board
26 * HSI clients are statically declared and registered on board files.
28 * HSI clients will be automatically registered to the HSI bus once the
DKconfig3 # HSI driver configuration
5 menuconfig HSI config
6 tristate "HSI support"
12 if HSI
18 source "drivers/hsi/controllers/Kconfig"
19 source "drivers/hsi/clients/Kconfig"
21 endif # HSI
DMakefile3 # Makefile for HSI
5 obj-$(CONFIG_HSI) += hsi.o
6 hsi-objs := hsi_core.o
7 hsi-$(CONFIG_HSI_BOARDINFO) += hsi_boardinfo.o
/kernel/linux/linux-6.6/include/linux/hsi/
Dhsi.h3 * HSI core header file.
20 /* HSI message ttype */
24 /* HSI configuration values */
42 /* HSI message status codes */
51 /* HSI port event codes */
58 * struct hsi_channel - channel resource used by the hsi clients
68 * struct hsi_config - Configuration for RX/TX HSI modules
90 * struct hsi_board_info - HSI client board info
91 * @name: Name for the HSI device
92 * @hsi_id: HSI controller id where the client sits
[all …]
/kernel/linux/linux-5.10/include/linux/hsi/
Dhsi.h3 * HSI core header file.
20 /* HSI message ttype */
24 /* HSI configuration values */
42 /* HSI message status codes */
51 /* HSI port event codes */
58 * struct hsi_channel - channel resource used by the hsi clients
68 * struct hsi_config - Configuration for RX/TX HSI modules
90 * struct hsi_board_info - HSI client board info
91 * @name: Name for the HSI device
92 * @hsi_id: HSI controller id where the client sits
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/
Dhsi.rst1 High Speed Synchronous Serial Interface (HSI)
7 High Speed Syncronous Interface (HSI) is a fullduplex, low latency protocol,
12 The HSI interface supports full duplex communication over multiple channels
40 HSI Subsystem in Linux
43 In the Linux kernel the hsi subsystem is supposed to be used for HSI devices.
44 The hsi subsystem contains drivers for hsi controllers including support for
45 multi-port controllers and provides a generic API for using the HSI ports.
47 It also contains HSI client drivers, which make use of the generic API to
48 implement a protocol used on the HSI interface. These client drivers can
51 hsi-char Device
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/
Dhsi.rst1 High Speed Synchronous Serial Interface (HSI)
7 High Speed Synchronous Interface (HSI) is a full duplex, low latency protocol,
12 The HSI interface supports full duplex communication over multiple channels
40 HSI Subsystem in Linux
43 In the Linux kernel the hsi subsystem is supposed to be used for HSI devices.
44 The hsi subsystem contains drivers for hsi controllers including support for
45 multi-port controllers and provides a generic API for using the HSI ports.
47 It also contains HSI client drivers, which make use of the generic API to
48 implement a protocol used on the HSI interface. These client drivers can
51 hsi-char Device
[all …]
/kernel/linux/linux-5.10/drivers/hsi/clients/
DKconfig3 # HSI clients configuration
6 comment "HSI clients"
10 depends on HSI && SSI_PROTOCOL && CMT_SPEECH
19 depends on HSI && SSI_PROTOCOL
29 depends on HSI && PHONET && OMAP_SSI
36 tristate "HSI/SSI character driver"
37 depends on HSI
39 If you say Y here, you will enable the HSI/SSI character driver.
41 serial communication with the cellular modem over HSI/SSI bus.
/kernel/linux/linux-6.6/drivers/hsi/clients/
DKconfig3 # HSI clients configuration
6 comment "HSI clients"
10 depends on HSI && SSI_PROTOCOL && CMT_SPEECH
19 depends on HSI && SSI_PROTOCOL
29 depends on HSI && PHONET && OMAP_SSI
36 tristate "HSI/SSI character driver"
37 depends on HSI
39 If you say Y here, you will enable the HSI/SSI character driver.
41 serial communication with the cellular modem over HSI/SSI bus.
/kernel/linux/linux-5.10/include/net/caif/
Dcaif_hsi.h16 * Maximum number of CAIF frames that can reside in the same HSI frame.
22 * HSI descriptor.
27 * Decides if HSI buffers should be prefilled with 0xFF pattern for easier
32 /* Structure describing a HSI packet descriptor. */
42 /* Size of the complete HSI packet descriptor. */
46 * Size of the complete HSI packet descriptor excluding the optional embedded
58 /* Size of the complete HSI TX buffer. */
61 /* Size of the complete HSI RX buffer. */
64 /* Bitmasks for the HSI descriptor. */
94 /* Structure implemented by the CAIF HSI driver. */
[all …]
/kernel/linux/linux-5.10/fs/hmdfs/
Dmain.c447 spin_lock(&sbi->hsi.list_lock); in hmdfs_sync_fs()
448 if (!sbi->hsi.is_executing) { in hmdfs_sync_fs()
449 sbi->hsi.is_executing = true; in hmdfs_sync_fs()
451 spin_unlock(&sbi->hsi.list_lock); in hmdfs_sync_fs()
454 list_add_tail(&item.list, &sbi->hsi.wait_list); in hmdfs_sync_fs()
455 spin_unlock(&sbi->hsi.list_lock); in hmdfs_sync_fs()
469 spin_lock(&sbi->hsi.v_lock); in hmdfs_sync_fs()
470 sbi->hsi.version++; in hmdfs_sync_fs()
472 * Attention: We put @sbi->hsi.remote_ret and @sbi->hsi.wait_count in hmdfs_sync_fs()
477 * sbi->hsi.remote_ret = 0; in hmdfs_sync_fs()
[all …]
/kernel/linux/linux-6.6/fs/hmdfs/
Dmain.c447 spin_lock(&sbi->hsi.list_lock); in hmdfs_sync_fs()
448 if (!sbi->hsi.is_executing) { in hmdfs_sync_fs()
449 sbi->hsi.is_executing = true; in hmdfs_sync_fs()
451 spin_unlock(&sbi->hsi.list_lock); in hmdfs_sync_fs()
454 list_add_tail(&item.list, &sbi->hsi.wait_list); in hmdfs_sync_fs()
455 spin_unlock(&sbi->hsi.list_lock); in hmdfs_sync_fs()
469 spin_lock(&sbi->hsi.v_lock); in hmdfs_sync_fs()
470 sbi->hsi.version++; in hmdfs_sync_fs()
472 * Attention: We put @sbi->hsi.remote_ret and @sbi->hsi.wait_count in hmdfs_sync_fs()
477 * sbi->hsi.remote_ret = 0; in hmdfs_sync_fs()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/
Dste-dma40.txt82 20: SLIMbus or HSI channel 0
83 21: SLIMbus or HSI channel 1
84 22: SLIMbus or HSI channel 2
85 23: SLIMbus or HSI channel 3
114 52: SLIMbus or HSI channel 4
115 53: SLIMbus or HSI channel 5
116 54: SLIMbus or HSI channel 6
117 55: SLIMbus or HSI channel 7
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/dma/
Dstericsson,dma40.yaml42 20: SLIMbus or HSI channel 0
43 21: SLIMbus or HSI channel 1
44 22: SLIMbus or HSI channel 2
45 23: SLIMbus or HSI channel 3
74 52: SLIMbus or HSI channel 4
75 53: SLIMbus or HSI channel 5
76 54: SLIMbus or HSI channel 6
77 55: SLIMbus or HSI channel 7
/kernel/linux/linux-6.6/drivers/hsi/controllers/
DKconfig3 # HSI controllers configuration
5 comment "HSI controllers"
9 depends on HSI && OF && ARM && COMMON_CLK
12 SSI is a legacy version of HSI. It is usually used to connect
/kernel/linux/linux-5.10/drivers/hsi/controllers/
DKconfig3 # HSI controllers configuration
5 comment "HSI controllers"
9 depends on HSI && OF && ARM && COMMON_CLK
12 SSI is a legacy version of HSI. It is usually used to connect

123456789