| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/timer/ |
| D | samsung,exynos4210-mct.yaml | 4 $id: http://devicetree.org/schemas/timer/samsung,exynos4210-mct.yaml#
7 title: Samsung Exynos SoC Multi Core Timer (MCT)
13 The Samsung's Multi Core Timer (MCT) module includes two main blocks, the
18 one CPU local timer instantiated in MCT for every CPU in the system.
24 - samsung,exynos4210-mct
25 - samsung,exynos4412-mct
28 - axis,artpec8-mct
29 - samsung,exynos3250-mct
30 - samsung,exynos5250-mct
31 - samsung,exynos5260-mct
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/ |
| D | samsung,exynos4210-mct.yaml | 4 $id: http://devicetree.org/schemas/timer/samsung,exynos4210-mct.yaml#
7 title: Samsung Exynos SoC Multi Core Timer (MCT)
13 The Samsung's Multi Core Timer (MCT) module includes two main blocks, the
18 one CPU local timer instantiated in MCT for every CPU in the system.
23 - samsung,exynos4210-mct
24 - samsung,exynos4412-mct
32 - pattern: "^(fin_pll|mct)$"
33 - pattern: "^(fin_pll|mct)$"
52 For MCT block that uses a per-processor interrupt for local timers, such
53 as ones compatible with "samsung,exynos4412-mct", only one local timer
[all …]
|
| /kernel/linux/linux-5.10/drivers/clocksource/ |
| D | exynos_mct.c | 2 /* linux/arch/arm/mach-exynos4/mct.c
7 * Exynos4 MCT(Multi-Core Timer) support
147 panic("MCT hangs after writing %d (offset:0x%lx)\n", value, offset); in exynos4_mct_write()
164 * that the upper and lower half match. Note that reading the MCT can be quite
208 .name = "mct-frc",
309 .name = "mct-comp",
373 /* enable MCT tick interrupt */ in exynos4_mct_tick_start()
384 /* Clear the MCT tick interrupt */ in exynos4_mct_tick_clear()
429 * Mct would generate interrupt periodically in exynos4_mct_tick_isr()
503 panic("%s: unable to ioremap mct address space\n", __func__); in exynos4_timer_resources()
[all …]
|
| /kernel/linux/linux-6.6/drivers/clocksource/ |
| D | exynos_mct.c | 2 /* linux/arch/arm/mach-exynos4/mct.c
7 * Exynos4 MCT(Multi-Core Timer) support
153 panic("MCT hangs after writing %d (offset:0x%lx)\n", value, offset); in exynos4_mct_write()
170 * that the upper and lower half match. Note that reading the MCT can be quite
214 .name = "mct-frc",
322 .name = "mct-comp",
386 /* enable MCT tick interrupt */ in exynos4_mct_tick_start()
397 /* Clear the MCT tick interrupt */ in exynos4_mct_tick_clear()
442 * Mct would generate interrupt periodically in exynos4_mct_tick_isr()
516 panic("%s: unable to ioremap mct address space\n", __func__); in exynos4_timer_resources()
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/serial/ |
| D | mct_u232.h | 3 * Definitions for MCT (Magic Control Technology) USB-RS232 Converter Driver
7 * This driver is for the device MCT USB-RS232 Converter (25 pin, Model No.
9 * Model No. U232-P9). See http://www.mct.com.tw/products/product_us232.html
22 #define MCT_U232_PID 0x0210 /* Original MCT Product Id */
30 /* Belkin badge the MCT U232-P9 as the F5U109 */
63 * the MCT-supplied Windows driver whenever the baud rate changes.
83 * Actually, there are two of them, MCT website calls them "Philips solution"
84 * and "Intel solution". They are the regular MCT and "Sitecom" for us.
174 * MCT-supplied Windows98 driver (U2SPORT.VXD, "File version: 1.21P.0104 for
337 * SniffUSB observations (Nov 2003): With the MCT-supplied Windows98 driver
[all …]
|
| D | mct_u232.c | 3 * MCT (Magic Control Technology Corp.) USB RS232 Converter Driver
58 * All of the device info needed for the MCT USB-RS232 converter.
74 .description = "MCT U232",
201 /* Mimic the MCT-supplied Windows driver (version 1.21P.0104), which in mct_u232_set_baud_rate()
|
| /kernel/linux/linux-6.6/drivers/usb/serial/ |
| D | mct_u232.h | 3 * Definitions for MCT (Magic Control Technology) USB-RS232 Converter Driver
7 * This driver is for the device MCT USB-RS232 Converter (25 pin, Model No.
9 * Model No. U232-P9). See http://www.mct.com.tw/products/product_us232.html
22 #define MCT_U232_PID 0x0210 /* Original MCT Product Id */
30 /* Belkin badge the MCT U232-P9 as the F5U109 */
63 * the MCT-supplied Windows driver whenever the baud rate changes.
83 * Actually, there are two of them, MCT website calls them "Philips solution"
84 * and "Intel solution". They are the regular MCT and "Sitecom" for us.
174 * MCT-supplied Windows98 driver (U2SPORT.VXD, "File version: 1.21P.0104 for
337 * SniffUSB observations (Nov 2003): With the MCT-supplied Windows98 driver
[all …]
|
| D | mct_u232.c | 3 * MCT (Magic Control Technology Corp.) USB RS232 Converter Driver
59 * All of the device info needed for the MCT USB-RS232 converter.
75 .description = "MCT U232",
202 /* Mimic the MCT-supplied Windows driver (version 1.21P.0104), which in mct_u232_set_baud_rate()
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/samsung/ |
| D | exynos54xx.dtsi | 76 mct: timer@101c0000 { label
77 compatible = "samsung,exynos5420-mct",
78 "samsung,exynos4210-mct";
|
| D | exynos5260.dtsi | 335 mct: timer@100b0000 { label
336 compatible = "samsung,exynos5260-mct",
337 "samsung,exynos4210-mct";
340 clock-names = "fin_pll", "mct";
|
| D | exynos4210.dtsi | 283 mct: timer@10050000 { label
284 compatible = "samsung,exynos4210-mct";
287 clock-names = "fin_pll", "mct";
|
| D | exynos5410.dtsi | 318 &mct {
320 clock-names = "fin_pll", "mct";
|
| D | exynos3250.dtsi | 444 compatible = "samsung,exynos3250-mct",
445 "samsung,exynos4210-mct";
456 clock-names = "fin_pll", "mct";
|
| D | exynos4x12.dtsi | 297 compatible = "samsung,exynos4412-mct";
300 clock-names = "fin_pll", "mct";
|
| D | exynos5250.dtsi | 244 compatible = "samsung,exynos5250-mct",
245 "samsung,exynos4210-mct";
248 clock-names = "fin_pll", "mct";
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | exynos54xx.dtsi | 76 mct: timer@101c0000 { label
77 compatible = "samsung,exynos4210-mct";
|
| D | exynos5260.dtsi | 181 mct: timer@100b0000 { label
182 compatible = "samsung,exynos4210-mct";
185 clock-names = "fin_pll", "mct";
|
| D | exynos4210.dtsi | 111 mct: timer@10050000 { label
112 compatible = "samsung,exynos4210-mct";
115 clock-names = "fin_pll", "mct";
|
| D | exynos5410.dtsi | 322 &mct {
324 clock-names = "fin_pll", "mct";
|
| D | exynos4412.dtsi | 249 compatible = "samsung,exynos4412-mct";
252 clock-names = "fin_pll", "mct";
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | usb-serial.rst | 371 MCT USB Single Port Serial Adapter U232
374 This driver is for the MCT USB-RS232 Converter (25 pin, Model No.
377 the manufacturer's web-site: http://www.mct.com.tw.
|
| /kernel/linux/linux-6.6/Documentation/usb/ |
| D | usb-serial.rst | 371 MCT USB Single Port Serial Adapter U232
374 This driver is for the MCT USB-RS232 Converter (25 pin, Model No.
377 the manufacturer's web-site: http://www.mct.com.tw.
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/exynos/ |
| D | exynos850.dtsi | 168 compatible = "samsung,exynos850-mct",
169 "samsung,exynos4210-mct";
184 clock-names = "fin_pll", "mct";
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/tesla/ |
| D | fsd.dtsi | 937 compatible = "tesla,fsd-mct", "samsung,exynos4210-mct";
956 clock-names = "fin_pll", "mct";
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/clock/ |
| D | samsung,exynos5433-clock.yaml | 37 # CMU_PERIS which generates clocks for PMU/TMU/MCT/WDT/RTC/SECKEY/TZPC IPs
|