/linux/drivers/soc/samsung/ |
H A D | exynos-usi.c | 6 * Samsung Exynos USI driver (Universal Serial Interface). 17 #include <dt-bindings/soc/samsung,exynos-usi.h> 27 /* USIv2: USI register offsets */ 31 /* USIv2: USI register bits */ 41 enum exynos_usi_ver ver; /* USI IP-core version */ 51 void __iomem *regs; /* USI register map */ 52 struct clk_bulk_data *clks; /* USI clocks */ 54 size_t mode; /* current USI SW_CONF mode index */ 88 .compatible = "samsung,exynos850-usi", 96 * exynos_usi_set_sw_conf - Set USI block configuration mode [all …]
|
H A D | Kconfig | 27 tristate "Exynos USI (Universal Serial Interface) driver" 32 Enable support for USI block. USI (Universal Serial Interface) is an 34 ExynosAutoV9. USI block can be configured to provide one of the 37 This driver allows one to configure USI for desired protocol, which 38 is usually done in USI node in Device Tree.
|
H A D | Makefile | 7 obj-$(CONFIG_EXYNOS_USI) += exynos-usi.o
|
/linux/Documentation/devicetree/bindings/soc/samsung/ |
H A D | exynos-usi.yaml | 4 $id: http://devicetree.org/schemas/soc/samsung/exynos-usi.yaml# 7 title: Samsung's Exynos USI (Universal Serial Interface) 14 USI IP-core provides selectable serial protocol (UART, SPI or High-Speed I2C). 15 USI shares almost all internal circuits within each protocol, so only one 16 protocol can be chosen at a time. USI is modeled as a node with zero or more 22 pattern: "^usi@[0-9a-f]+$" 28 - google,gs101-usi 29 - samsung,exynosautov9-usi 30 - samsung,exynosautov920-usi 31 - const: samsung,exynos850-usi [all …]
|
/linux/arch/arm64/boot/dts/exynos/ |
H A D | exynosautov9.dtsi | 12 #include <dt-bindings/soc/samsung,exynos-usi.h> 440 usi_0: usi@103000c0 { 441 compatible = "samsung,exynosautov9-usi", 442 "samsung,exynos850-usi"; 503 usi_i2c_0: usi@103100c0 { 504 compatible = "samsung,exynosautov9-usi", 505 "samsung,exynos850-usi"; 532 usi_1: usi@103200c0 { 533 compatible = "samsung,exynosautov9-usi", 534 "samsung,exynos850-usi"; [all …]
|
H A D | exynos850.dtsi | 15 #include <dt-bindings/soc/samsung,exynos-usi.h> 650 usi_uart: usi@138200c0 { 651 compatible = "samsung,exynos850-usi"; 676 usi_hsi2c_0: usi@138a00c0 { 677 compatible = "samsung,exynos850-usi"; 705 usi_hsi2c_1: usi@138b00c0 { 706 compatible = "samsung,exynos850-usi"; 734 usi_hsi2c_2: usi@138c00c0 { 735 compatible = "samsung,exynos850-usi"; 763 usi_spi_0: usi@139400c0 { [all …]
|
H A D | exynosautov920.dtsi | 11 #include <dt-bindings/soc/samsung,exynos-usi.h> 210 usi_0: usi@108800c0 { 211 compatible = "samsung,exynosautov920-usi", 212 "samsung,exynos850-usi";
|
H A D | exynos850-pinctrl.dtsi | 121 /* USI: UART_DEBUG_0 pins */ 128 /* USI: UART_DEBUG_1 pins */ 591 /* USI: HSI2C0 */ 599 /* USI: HSI2C1 */ 607 /* USI: HSI2C2 */ 615 /* USI: SPI */
|
/linux/arch/arm64/boot/dts/exynos/google/ |
H A D | gs101.dtsi | 12 #include <dt-bindings/soc/samsung,exynos-usi.h> 378 usi1: usi@109000c0 { 379 compatible = "google,gs101-usi", "samsung,exynos850-usi"; 433 usi2: usi@109100c0 { 434 compatible = "google,gs101-usi", "samsung,exynos850-usi"; 488 usi3: usi@109200c0 { 489 compatible = "google,gs101-usi", "samsung,exynos850-usi"; 543 usi4: usi@109300c0 { 544 compatible = "google,gs101-usi", "samsung,exynos850-usi"; 598 usi5: usi@109400c0 { [all …]
|
/linux/Documentation/devicetree/bindings/i2c/ |
H A D | i2c-exynos5.yaml | 16 In case the HSI2C controller is encapsulated within USI block (it's the case 18 define USI node in device tree file, choosing "i2c" configuration. Please see 19 Documentation/devicetree/bindings/soc/samsung/exynos-usi.yaml for details.
|
/linux/Documentation/devicetree/bindings/arm/marvell/ |
H A D | marvell,kirkwood.txt | 102 "usi,topkick" 103 "usi,topkick-1281P2"
|
/linux/arch/arm/boot/dts/marvell/ |
H A D | kirkwood-topkick.dts | 9 compatible = "usi,topkick-1281P2", "usi,topkick", "marvell,kirkwood-88f6282", "marvell,kirkwood";
|
H A D | dove-cm-a510.dtsi | 70 * W: Broadcom BCM4319 802.11b/g/n (USI WM-N-BM-01 on SDIO1)
|
/linux/Documentation/spi/ |
H A D | butterfly.rst | 59 The "USI" controller, using J405, can also be used for a second SPI bus. 60 That would let you talk to the AVR using custom SPI-with-USI firmware,
|
/linux/drivers/scsi/pm8001/ |
H A D | Makefile | 5 # Copyright (C) 2008-2009 USI Co., Ltd.
|
H A D | pm8001_ctl.h | 4 * Copyright (c) 2008-2009 USI Co., Ltd.
|
H A D | pm8001_chips.h | 4 * Copyright (c) 2008-2009 USI Co., Ltd.
|
H A D | pm8001_defs.h | 4 * Copyright (c) 2008-2009 USI Co., Ltd.
|
/linux/include/dt-bindings/soc/ |
H A D | samsung,exynos-usi.h | 6 * Device Tree bindings for Samsung Exynos USI (Universal Serial Interface).
|
/linux/Documentation/translations/it_IT/process/ |
H A D | deprecated.rst | 14 In un mondo perfetto, sarebbe possibile prendere tutti gli usi di 181 tutto gli usi di "%p" nel kernel rappresentano l'hash dell'indirizzo, 182 rendendolo di fatto inutilizzabile. Nuovi usi di "%p" non dovrebbero
|
/linux/Documentation/sound/hd-audio/ |
H A D | models.rst | 329 usi-headset 330 Headset support on USI machines
|
/linux/Documentation/translations/it_IT/locking/ |
H A D | lockdep-design.rst | 40 l'uso in categorie (4 USI * n STATI + 1). 42 I quattro USI possono essere: 132 Il validatore rileva e riporta gli usi di blocchi che violano queste regole per
|
/linux/Documentation/translations/it_IT/core-api/ |
H A D | symbol-namespaces.rst | 62 diventa lo spazio dei simboli di base per tutti gli usi di EXPORT_SYMBOL()
|
/linux/Documentation/hid/ |
H A D | hid-bpf.rst | 59 An example for such a feature are the Universal Stylus Interface (USI) pens. 60 Basically, USI pens require a new kernel API because there are new
|
/linux/drivers/net/wireless/ath/ath9k/ |
H A D | pci.c | 372 0x14CD, /* USI */ 377 0x14CD, /* USI */
|