| /kernel/linux/linux-5.10/drivers/hsi/clients/ |
| D | nokia-modem.c | 3 * nokia-modem.c
5 * HSI client driver for Nokia N900 modem.
41 struct nokia_modem_device *modem = (struct nokia_modem_device *)data; in do_nokia_modem_rst_ind_tasklet() local
43 if (!modem) in do_nokia_modem_rst_ind_tasklet()
46 dev_info(modem->device, "CMT rst line change detected\n"); in do_nokia_modem_rst_ind_tasklet()
48 if (modem->ssi_protocol) in do_nokia_modem_rst_ind_tasklet()
49 ssip_reset_event(modem->ssi_protocol); in do_nokia_modem_rst_ind_tasklet()
54 struct nokia_modem_device *modem = (struct nokia_modem_device *)data; in nokia_modem_rst_ind_isr() local
56 tasklet_schedule(&modem->nokia_modem_rst_ind_tasklet); in nokia_modem_rst_ind_isr()
63 struct nokia_modem_device *modem = dev_get_drvdata(dev); in nokia_modem_gpio_unexport() local
[all …]
|
| /kernel/linux/linux-4.19/drivers/hsi/clients/ |
| D | nokia-modem.c | 2 * nokia-modem.c
4 * HSI client driver for Nokia N900 modem.
54 struct nokia_modem_device *modem = (struct nokia_modem_device *)data; in do_nokia_modem_rst_ind_tasklet() local
56 if (!modem) in do_nokia_modem_rst_ind_tasklet()
59 dev_info(modem->device, "CMT rst line change detected\n"); in do_nokia_modem_rst_ind_tasklet()
61 if (modem->ssi_protocol) in do_nokia_modem_rst_ind_tasklet()
62 ssip_reset_event(modem->ssi_protocol); in do_nokia_modem_rst_ind_tasklet()
67 struct nokia_modem_device *modem = (struct nokia_modem_device *)data; in nokia_modem_rst_ind_isr() local
69 tasklet_schedule(&modem->nokia_modem_rst_ind_tasklet); in nokia_modem_rst_ind_isr()
76 struct nokia_modem_device *modem = dev_get_drvdata(dev); in nokia_modem_gpio_unexport() local
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ipa/ |
| D | ipa_qmi.c | 21 * DOC: AP/Modem QMI Handshake
23 * The AP and modem perform a "handshake" at initialization time to ensure
26 * using a service on the modem, and server to service modem requests (and
28 * complete, the AP and modem may begin IPA operation. This occurs
29 * only when the AP IPA driver, modem IPA driver, and IPA microcontroller
32 * The QMI service on the modem expects to receive an INIT_DRIVER request from
33 * the AP, which contains parameters used by the modem during initialization.
34 * The AP sends this request as soon as it is knows the modem side service
35 * is available. The modem responds to this request, and if this response
36 * contains a success result, the AP knows the modem IPA driver is ready.
[all …]
|
| D | ipa_qmi_msg.h | 17 #define IPA_QMI_INDICATION_REGISTER 0x20 /* modem -> AP request */
18 #define IPA_QMI_INIT_DRIVER 0x21 /* AP -> modem request */
19 #define IPA_QMI_INIT_COMPLETE 0x22 /* AP -> modem indication */
20 #define IPA_QMI_DRIVER_INIT_COMPLETE 0x35 /* modem -> AP request */
75 /* The AP tells the modem its platform type. We assume Android. */
116 * from the AP that affects modem initialization.
122 /* Modem header table information. This defines the IPA shared
123 * memory in which the modem may insert header table entries.
146 /* Modem memory information. This defines the location and
147 * size of memory available for the modem to use.
[all …]
|
| D | ipa_table.c | 41 * Each filter rule is associated with an AP or modem TX endpoint, though
54 * entry. Once initialized the modem and AP update the entries for
62 * 1st endpoint | 0x000123456789abc0 | DMA address for modem endpoint 2 rule
74 * and modem. The AP initializes all entries in a route table to refer to
75 * a "zero entry". Once initialized, the modem and AP are responsible for
81 * 1st modem route | 0x0001234500001100 | DMA address for first route rule
83 * 2nd modem route | 0x0001234500001140 | DMA address for second route rule
87 * Last modem route| 0x0001234500002280 | DMA address for Nth route rule
102 /* Assignment of route table entries to the modem and AP */
145 /* The modem must be allotted at least one route table entry */ in ipa_table_validate_build()
[all …]
|
| D | ipa_smp2p.c | 20 * DOC: IPA SMP2P communication with the modem
23 * the modem. The IPA driver uses this for two purposes: to enable the modem
28 * This initialization is done either by Trust Zone or by the modem. In the
29 * latter case, the modem uses an SMP2P interrupt to tell the AP IPA driver
32 * The modem is also able to inquire about the current state of the IPA
36 * clock state bit is valid. The modem will poll the valid bit until it
40 * we never receive an interrupt from the modem requesting this.
51 * @clock_query_irq: IPA interrupt triggered by modem for clock query
52 * @setup_ready_irq: IPA interrupt triggered by modem to signal GSI ready
54 * @notified: Whether modem has been notified of clock state
[all …]
|
| /kernel/linux/linux-4.19/drivers/net/hamradio/ |
| D | baycom_ser_hdx.c | 4 * baycom_ser_hdx.c -- baycom ser12 halfduplex radio modem driver.
29 * ser12: This is a very simple 1200 baud AFSK modem. The modem consists only
32 * for handling the HDLC protocol. The modem connects to a serial port,
43 * mutes audio input to the modem
133 } modem; member
180 * 0 must be used to power the modem; the modem draws its in ser12_set_divisor()
209 outb(0x0e | (!!bc->modem.ser12.tx_bit), MCR(dev->base_addr)); in ser12_tx()
210 if (bc->modem.shreg <= 1) in ser12_tx()
211 bc->modem.shreg = 0x10000 | hdlcdrv_getbits(&bc->hdrv); in ser12_tx()
212 bc->modem.ser12.tx_bit = !(bc->modem.ser12.tx_bit ^ in ser12_tx()
[all …]
|
| D | baycom_ser_fdx.c | 4 * baycom_ser_fdx.c -- baycom ser12 fullduplex radio modem driver.
29 * ser12: This is a very simple 1200 baud AFSK modem. The modem consists only
32 * for handling the HDLC protocol. The modem connects to a serial port,
37 * This modem usually draws its supply current out of the otherwise unused
41 * hsk: This is a 4800 baud FSK modem, designed for TNC use. It works fine
42 * in 'baycom-mode' :-) In contrast to the TCM3105 modem, power is
145 } modem; member
194 * 0 must be used to power the modem; the modem draws its in ser12_set_divisor()
240 bc->modem.ser12.pll_time; in ser12_rx()
245 bc->modem.ser12.pll_time += bc->baud_us; in ser12_rx()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/hamradio/ |
| D | baycom_ser_hdx.c | 5 * baycom_ser_hdx.c -- baycom ser12 halfduplex radio modem driver.
15 * ser12: This is a very simple 1200 baud AFSK modem. The modem consists only
18 * for handling the HDLC protocol. The modem connects to a serial port,
28 * mutes audio input to the modem
117 } modem; member
164 * 0 must be used to power the modem; the modem draws its in ser12_set_divisor()
193 outb(0x0e | (!!bc->modem.ser12.tx_bit), MCR(dev->base_addr)); in ser12_tx()
194 if (bc->modem.shreg <= 1) in ser12_tx()
195 bc->modem.shreg = 0x10000 | hdlcdrv_getbits(&bc->hdrv); in ser12_tx()
196 bc->modem.ser12.tx_bit = !(bc->modem.ser12.tx_bit ^ in ser12_tx()
[all …]
|
| D | baycom_ser_fdx.c | 5 * baycom_ser_fdx.c -- baycom ser12 fullduplex radio modem driver.
15 * ser12: This is a very simple 1200 baud AFSK modem. The modem consists only
18 * for handling the HDLC protocol. The modem connects to a serial port,
23 * This modem usually draws its supply current out of the otherwise unused
27 * hsk: This is a 4800 baud FSK modem, designed for TNC use. It works fine
28 * in 'baycom-mode' :-) In contrast to the TCM3105 modem, power is
130 } modem; member
179 * 0 must be used to power the modem; the modem draws its in ser12_set_divisor()
199 bc->modem.ser12.pll_time; in ser12_rx()
204 bc->modem.ser12.pll_time += bc->baud_us; in ser12_rx()
[all …]
|
| D | baycom_par.c | 5 * baycom_par.c -- baycom par96 and picpar radio modem driver.
15 * par96: This is a modem for 9600 baud FSK compatible to the G3RUH standard.
16 * The modem does all the filtering and regenerates the receiver clock.
20 * modem connects to the parallel port, hence the name. The modem
22 * polynomial to the PC. This modem is no longer available (at least
23 * from Baycom) and has been replaced by the PICPAR modem (see below).
27 * picpar: This is a redesign of the par96 modem by Henning Rech, DF9IC. The
28 * modem is protocol compatible to par96, but uses only three low
80 * modem options; bit mask
128 } modem; member
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/serial/ |
| D | qcserial.c | 41 {DEVICE_G1K(0x05c6, 0x9212)}, /* Acer Gobi Modem Device */
42 {DEVICE_G1K(0x03f0, 0x1f1d)}, /* HP un2400 Gobi Modem Device */
44 {DEVICE_G1K(0x04da, 0x250d)}, /* Panasonic Gobi Modem device */
46 {DEVICE_G1K(0x413c, 0x8172)}, /* Dell Gobi Modem device */
49 {DEVICE_G1K(0x1410, 0xa002)}, /* Novatel Gobi Modem device */
50 {DEVICE_G1K(0x1410, 0xa003)}, /* Novatel Gobi Modem device */
51 {DEVICE_G1K(0x1410, 0xa004)}, /* Novatel Gobi Modem device */
52 {DEVICE_G1K(0x1410, 0xa005)}, /* Novatel Gobi Modem device */
53 {DEVICE_G1K(0x1410, 0xa006)}, /* Novatel Gobi Modem device */
54 {DEVICE_G1K(0x1410, 0xa007)}, /* Novatel Gobi Modem device */
[all …]
|
| /kernel/linux/linux-4.19/drivers/usb/serial/ |
| D | qcserial.c | 41 {DEVICE_G1K(0x05c6, 0x9212)}, /* Acer Gobi Modem Device */
42 {DEVICE_G1K(0x03f0, 0x1f1d)}, /* HP un2400 Gobi Modem Device */
44 {DEVICE_G1K(0x04da, 0x250d)}, /* Panasonic Gobi Modem device */
46 {DEVICE_G1K(0x413c, 0x8172)}, /* Dell Gobi Modem device */
49 {DEVICE_G1K(0x1410, 0xa002)}, /* Novatel Gobi Modem device */
50 {DEVICE_G1K(0x1410, 0xa003)}, /* Novatel Gobi Modem device */
51 {DEVICE_G1K(0x1410, 0xa004)}, /* Novatel Gobi Modem device */
52 {DEVICE_G1K(0x1410, 0xa005)}, /* Novatel Gobi Modem device */
53 {DEVICE_G1K(0x1410, 0xa006)}, /* Novatel Gobi Modem device */
54 {DEVICE_G1K(0x1410, 0xa007)}, /* Novatel Gobi Modem device */
[all …]
|
| /kernel/linux/linux-4.19/drivers/usb/atm/ |
| D | Kconfig | 6 tristate "USB DSL modem support"
12 modem to your computer's USB port. You will then need to choose your
13 modem from the list below.
25 modem. In order to use your modem you will need to install the
36 Say Y here if you have an ADSL USB modem based on the Conexant
37 AccessRunner chipset. In order to use your modem you will need to
45 tristate "ADI 930 and eagle USB DSL modem"
48 Say Y here if you have an ADSL USB modem based on the ADI 930
49 or eagle chipset. In order to use your modem you will need to
57 tristate "Other USB DSL modem support"
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/atm/ |
| D | Kconfig | 7 tristate "USB DSL modem support"
12 modem to your computer's USB port. You will then need to choose your
13 modem from the list below.
25 modem. In order to use your modem you will need to install the
36 Say Y here if you have an ADSL USB modem based on the Conexant
37 AccessRunner chipset. In order to use your modem you will need to
45 tristate "ADI 930 and eagle USB DSL modem"
48 Say Y here if you have an ADSL USB modem based on the ADI 930
49 or eagle chipset. In order to use your modem you will need to
57 tristate "Other USB DSL modem support"
[all …]
|
| /kernel/linux/linux-4.19/drivers/tty/serial/8250/ |
| D | 8250_pnp.c | 28 /* Archtek SmartLink Modem 3334BT Plug & Play */
31 /* SXPro 144 External Data Fax Modem Plug & Play */
33 /* SXPro 288 External Data Fax Modem Plug & Play */
35 /* PROLiNK 1456VH ISA PnP K56flex Fax Modem */
37 /* Actiontec ISA PNP 56K X2 Fax Modem */
39 /* Rockwell 56K ACF II Fax+Data+Voice Modem */
49 /* Best Data Products Inc. Smart One 336F PnP Modem */
54 /* Boca Research 33,600 ACF Modem */
60 /* Best Data Products Inc. Smart One 336F PnP Modem */
68 /* Creative Labs Modem Blaster 28.8 DSVD PnP Voice */
[all …]
|
| /kernel/linux/linux-5.10/drivers/tty/serial/8250/ |
| D | 8250_pnp.c | 28 /* Archtek SmartLink Modem 3334BT Plug & Play */
31 /* SXPro 144 External Data Fax Modem Plug & Play */
33 /* SXPro 288 External Data Fax Modem Plug & Play */
35 /* PROLiNK 1456VH ISA PnP K56flex Fax Modem */
37 /* Actiontec ISA PNP 56K X2 Fax Modem */
39 /* Rockwell 56K ACF II Fax+Data+Voice Modem */
49 /* Best Data Products Inc. Smart One 336F PnP Modem */
54 /* Boca Research 33,600 ACF Modem */
60 /* Best Data Products Inc. Smart One 336F PnP Modem */
68 /* Creative Labs Modem Blaster 28.8 DSVD PnP Voice */
[all …]
|
| /kernel/linux/linux-5.10/drivers/acpi/ |
| D | acpi_pnp.c | 147 {"AAC000F"}, /* Archtek America Corp. Archtek SmartLink Modem 3334BT Plug & Play */
148 {"ADC0001"}, /* Anchor Datacomm BV. SXPro 144 External Data Fax Modem Plug & Play */
149 {"ADC0002"}, /* SXPro 288 External Data Fax Modem Plug & Play */
150 {"AEI0250"}, /* PROLiNK 1456VH ISA PnP K56flex Fax Modem */
151 {"AEI1240"}, /* Actiontec ISA PNP 56K X2 Fax Modem */
152 {"AKY1021"}, /* Rockwell 56K ACF II Fax+Data+Voice Modem */
155 {"BDP3336"}, /* Best Data Products Inc. Smart One 336F PnP Modem */
157 {"BRI1400"}, /* Boca Research 33,600 ACF Modem */
160 {"BDP3336"}, /* Best Data Products Inc. Smart One 336F PnP Modem */
163 {"CTL3011"}, /* Creative Labs Modem Blaster 28.8 DSVD PnP Voice */
[all …]
|
| /kernel/linux/linux-4.19/drivers/acpi/ |
| D | acpi_pnp.c | 148 {"AAC000F"}, /* Archtek America Corp. Archtek SmartLink Modem 3334BT Plug & Play */
149 {"ADC0001"}, /* Anchor Datacomm BV. SXPro 144 External Data Fax Modem Plug & Play */
150 {"ADC0002"}, /* SXPro 288 External Data Fax Modem Plug & Play */
151 {"AEI0250"}, /* PROLiNK 1456VH ISA PnP K56flex Fax Modem */
152 {"AEI1240"}, /* Actiontec ISA PNP 56K X2 Fax Modem */
153 {"AKY1021"}, /* Rockwell 56K ACF II Fax+Data+Voice Modem */
156 {"BDP3336"}, /* Best Data Products Inc. Smart One 336F PnP Modem */
158 {"BRI1400"}, /* Boca Research 33,600 ACF Modem */
161 {"BDP3336"}, /* Best Data Products Inc. Smart One 336F PnP Modem */
164 {"CTL3011"}, /* Creative Labs Modem Blaster 28.8 DSVD PnP Voice */
[all …]
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | baycom.txt | 17 therefore it supports just about every bit bang modem on a
34 This driver supports the EPP modem.
40 ser12: This is a very simple 1200 baud AFSK modem. The modem consists only
43 for handling the HDLC protocol. The modem connects to a serial port,
48 par96: This is a modem for 9600 baud FSK compatible to the G3RUH standard.
49 The modem does all the filtering and regenerates the receiver clock.
52 The PC then empties the shift register in a burst. This modem connects
53 to the parallel port, hence the name. The modem leaves the
57 picpar: This is a redesign of the par96 modem by Henning Rech, DF9IC. The modem
63 EPP: This is a high-speed modem adaptor that connects to an enhanced parallel port.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | qcom,ipa.yaml | 18 including the Application Processor (AP) and the modem. The IPA presents
31 | AP +<---. .----+ Modem |
73 - description: Modem clock query interrupt (smp2p interrupt)
74 - description: Modem setup ready interrupt (smp2p interrupt)
97 description: State bits used in by the AP to signal the modem.
109 modem-init:
112 If present, it indicates that the modem is responsible for
116 modem-remoteproc:
120 the modem subsystem. This is requied so the IPA driver can
121 receive and act on notifications of modem up/down events.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/hsi/ |
| D | nokia-modem.txt | 1 Nokia modem client bindings
3 The Nokia modem HSI client follows the common HSI client binding
5 properties are needed by the Nokia modem HSI client:
9 "nokia,n900-modem"
10 "nokia,n950-modem"
11 "nokia,n9-modem"
25 - interrupts: Should be IRQ handle for modem's reset indication
30 modem: hsi-client {
31 compatible = "nokia,n900-modem";
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/hsi/ |
| D | nokia-modem.txt | 1 Nokia modem client bindings
3 The Nokia modem HSI client follows the common HSI client binding
5 properties are needed by the Nokia modem HSI client:
9 "nokia,n900-modem"
10 "nokia,n950-modem"
11 "nokia,n9-modem"
25 - interrupts: Should be IRQ handle for modem's reset indication
30 modem: hsi-client {
31 compatible = "nokia,n900-modem";
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/hamradio/ |
| D | baycom.rst | 22 therefore it supports just about every bit bang modem on a
39 This driver supports the EPP modem.
46 ser12 This is a very simple 1200 baud AFSK modem. The modem consists only
49 for handling the HDLC protocol. The modem connects to a serial port,
54 par96 This is a modem for 9600 baud FSK compatible to the G3RUH standard.
55 The modem does all the filtering and regenerates the receiver clock.
58 The PC then empties the shift register in a burst. This modem connects
59 to the parallel port, hence the name. The modem leaves the
63 picpar This is a redesign of the par96 modem by Henning Rech, DF9IC. The modem
69 EPP This is a high-speed modem adaptor that connects to an enhanced parallel
[all …]
|
| /kernel/linux/linux-4.19/drivers/isdn/hardware/eicon/ |
| D | mdm_msg.h | 136 DLC: B2 modem configuration
139 Fields in assign DLC information element for modem protocol V.42/MNP:
148 <byte> modem protocol negotiation options
149 <byte> modem protocol options
150 <byte> modem protocol break configuration
151 <byte> modem protocol application options
175 CAI parameters used for the modem L1 configuration
185 <byte> modem line taking options
186 <byte> modem modulation negotiation parameters
187 <byte> modem modulation options
[all …]
|