| /openbmc/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
|
| /openbmc/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]+$"
27 - const: samsung,exynosautov9-usi
28 - const: samsung,exynos850-usi
30 - samsung,exynos850-usi
51 - description: offset of SW_CONF register for this USI controller
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/exynos/ |
| H A D | exynosautov9.dtsi | 12 #include <dt-bindings/soc/samsung,exynos-usi.h>
390 usi_0: usi@103000c0 {
391 compatible = "samsung,exynosautov9-usi",
392 "samsung,exynos850-usi";
452 usi_i2c_0: usi@103100c0 {
453 compatible = "samsung,exynosautov9-usi",
454 "samsung,exynos850-usi";
481 usi_1: usi@103200c0 {
482 compatible = "samsung,exynosautov9-usi",
483 "samsung,exynos850-usi";
[all …]
|
| H A D | exynos850.dtsi | 15 #include <dt-bindings/soc/samsung,exynos-usi.h>
573 usi_uart: usi@138200c0 {
574 compatible = "samsung,exynos850-usi";
599 usi_hsi2c_0: usi@138a00c0 {
600 compatible = "samsung,exynos850-usi";
627 usi_hsi2c_1: usi@138b00c0 {
628 compatible = "samsung,exynos850-usi";
655 usi_hsi2c_2: usi@138c00c0 {
656 compatible = "samsung,exynos850-usi";
683 usi_spi_0: usi@139400c0 {
[all …]
|
| 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 */
|
| /openbmc/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.
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/marvell/ |
| H A D | marvell,kirkwood.txt | 102 "usi,topkick"
103 "usi,topkick-1281P2"
|
| /openbmc/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)
|
| /openbmc/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.
|
| /openbmc/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,
|
| /openbmc/linux/include/dt-bindings/soc/ |
| H A D | samsung,exynos-usi.h | 6 * Device Tree bindings for Samsung Exynos USI (Universal Serial Interface).
|
| /openbmc/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
|
| H A D | adding-syscalls.rst | 178 evitate di aggiungere nuovi usi al fin-troppo-generico privilegio
610 - Articolo di Michael Kerris su LWN sull'evitare nuovi usi di CAP_SYS_ADMIN:
|
| H A D | email-clients.rst | 331 - Modificate le impostazioni di Thunderbird per far si che non usi ``format=flowed``!
|
| /openbmc/linux/Documentation/sound/hd-audio/ |
| H A D | models.rst | 329 usi-headset
330 Headset support on USI machines
|
| /openbmc/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()
|
| /openbmc/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
|
| /openbmc/linux/drivers/net/wireless/ath/ath9k/ |
| H A D | pci.c | 374 0x14CD, /* USI */
379 0x14CD, /* USI */
|
| /openbmc/linux/Documentation/translations/it_IT/doc-guide/ |
| H A D | sphinx.rst | 288 incrociato quando questa ha una voce nell'indice. Se trovate degli usi di
|