| /linux/Documentation/driver-api/memory-devices/ |
| H A D | ti-gpmc.rst | 24 functioning of the peripheral, while peripheral has another set of
25 timings. To have peripheral work with gpmc, peripheral timings has to
27 translated depends on the connected peripheral. Also there is a
32 from gpmc peripheral timings. struct gpmc_device_timings fields has to
33 be updated with timings from the datasheet of the peripheral that is
34 connected to gpmc. A few of the peripheral timings can be fed either
37 happen that timing as specified by peripheral datasheet is not present
38 in timing structure, in this scenario, try to correlate peripheral
40 field as required by peripheral, educate generic timing routine to
42 Then there may be cases where peripheral datasheet doesn't mention
[all …]
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | mipi-dsi-bus.txt | 15 The following assumes that only a single peripheral is connected to a DSI
34 conjunction with another DSI host to drive the same peripheral. Hardware
39 DSI peripheral
52 - reg: The virtual channel number of a DSI peripheral. Must be in the range
58 that the peripheral responds to.
59 - If the virtual channels that a peripheral responds to are consecutive, the
79 connected to this peripheral. Each DSI host's output endpoint can be linked to
80 an input endpoint of the DSI peripheral.
87 - (1), (2) and (3) are examples of a DSI host and peripheral on the DSI bus
89 - (4) is an example of a peripheral on a I2C control bus connected to a
[all …]
|
| /linux/drivers/rtc/ |
| H A D | rtc-meson.c | 65 struct regmap *peripheral; /* peripheral registers */ member
70 .name = "peripheral-registers",
82 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SCLK, 0); in meson_rtc_sclk_pulse()
84 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SCLK, in meson_rtc_sclk_pulse()
90 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SDI, in meson_rtc_send_bit()
108 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SEN, 0); in meson_rtc_set_dir()
109 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SDI, 0); in meson_rtc_set_dir()
111 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SDI, 0); in meson_rtc_set_dir()
123 regmap_read(rtc->peripheral, RTC_ADDR1, &tmp); in meson_rtc_get_data()
137 regmap_update_bits(rtc->peripheral, RTC_ADDR0, val, 0); in meson_rtc_get_bus()
[all …]
|
| /linux/drivers/usb/gadget/udc/ |
| H A D | Kconfig | 4 # (a) a peripheral controller, and
18 # USB Peripheral Controller Support
27 menu "USB Peripheral Controller"
47 tristate "LPC32XX USB Peripheral Controller"
81 tristate "Broadcom BCM63xx Peripheral Controller"
92 tristate "Freescale Highspeed USB DR Peripheral Controller"
106 tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
153 tristate "Renesas R8A66597 USB Peripheral Controller"
156 R8A66597 is a discrete USB host and peripheral controller chip that
168 Renesas USBHS is a discrete USB host and peripheral controller chip
[all …]
|
| /linux/drivers/clk/qcom/ |
| H A D | Kconfig | 38 Say Y if you want to use peripheral devices such as UART, SPI,
47 Say Y if you want to use peripheral devices such as USB/PCIe/EDP.
74 Say Y if you want to use peripheral devices such as UART, SPI, I2C,
92 Say Y if you want to use peripheral devices such as SD/UFS.
196 Say Y if you want to use peripheral devices such as UART, SPI,
251 Say Y if you want to use peripheral devices such as UART, SPI,
259 Say Y if you want to use peripheral devices such as UART, SPI,
267 Say Y if you want to use peripheral devices such as UART, SPI,
275 Say Y if you want to use peripheral devices such as UART, SPI,
282 Say Y if you want to use peripheral devices such as UART, SPI,
[all …]
|
| /linux/Documentation/devicetree/bindings/spi/ |
| H A D | spi-peripheral-props.yaml | 4 $id: http://devicetree.org/schemas/spi/spi-peripheral-props.yaml#
7 title: Peripheral-specific properties for a SPI bus.
10 Many SPI controllers need to add properties to peripheral devices. They could
13 properties need to be defined in the peripheral node because they are
14 per-peripheral and there can be multiple peripherals attached to a
125 - $ref: arm,pl022-peripheral-props.yaml#
126 - $ref: cdns,qspi-nor-peripheral-props.yaml#
127 - $ref: fsl,dspi-peripheral-props.yaml#
128 - $ref: samsung,spi-peripheral-props.yaml#
129 - $ref: nvidia,tegra210-quad-peripheral-props.yaml#
|
| /linux/include/linux/platform_data/ |
| H A D | sh_mmcif.h | 16 * 1000 : Peripheral clock / 512
17 * 0111 : Peripheral clock / 256
18 * 0110 : Peripheral clock / 128
19 * 0101 : Peripheral clock / 64
20 * 0100 : Peripheral clock / 32
21 * 0011 : Peripheral clock / 16
22 * 0010 : Peripheral clock / 8
23 * 0001 : Peripheral clock / 4
24 * 0000 : Peripheral clock / 2
25 * 1111 : Peripheral clock (sup_pclk set '1')
|
| /linux/Documentation/devicetree/bindings/iommu/ |
| H A D | samsung,sysmmu.yaml | 14 physical memory chunks visible as a contiguous region to DMA-capable peripheral
23 System MMUs are in many to one relation with peripheral devices, i.e. single
24 peripheral device might have multiple System MMUs (usually one for each bus
25 master), but one System MMU can handle transactions from only one peripheral
26 device. The relation between a System MMU and the peripheral device needs to be
27 defined in device node of the peripheral device.
37 For information on assigning System MMU controller to its peripheral devices,
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-renesas_usb3 | 11 - "host" - switching mode from peripheral to host.
12 - "peripheral" - switching mode from host to peripheral.
17 - "peripheral" - The mode is peripheral now.
|
| H A D | sysfs-platform-phy-rcar-gen3-usb2 | 11 - "host" - switching mode from peripheral to host.
12 - "peripheral" - switching mode from host to peripheral.
17 - "peripheral" - The mode is peripheral now.
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | atmel-usb.txt | 10 - clocks: Should reference the peripheral, host and system clocks
12 "ohci_clk" for the peripheral clock
37 - clocks: Should reference the peripheral and the UTMI clocks
39 "ehci_clk" for the peripheral clock
64 - clocks: Should reference the peripheral and the AHB clocks
66 "pclk" for the peripheral clock
95 - clocks: Should reference the peripheral and host clocks
97 "pclk" for the peripheral clock
|
| /linux/drivers/net/wireless/intel/iwlwifi/pcie/ |
| H A D | iwl-context-info-v2.h | 223 * struct iwl_prph_scratch - peripheral scratch mapping
239 * struct iwl_prph_info - peripheral information
242 * @sleep_notif: indicates the peripheral sleep status
256 * @config: context in which the peripheral would execute - a subset of
257 * capability csr register published by the peripheral
258 * @prph_info_base_addr: the peripheral information structure start address
277 * @mtr_msi_vec: the MSI which shall be generated by the peripheral after
279 * @mcr_msi_vec: the MSI which shall be generated by the peripheral after
290 * @prph_info_msi_vec: the MSI which shall be generated by the peripheral
291 * after updating the Peripheral Information structure
[all …]
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | hisilicon,hix5hd2-sata-phy.yaml | 22 hisilicon,peripheral-syscon:
23 description: Phandle of syscon used to control peripheral
27 … description: Offset and bit number within peripheral-syscon register controlling SATA power supply
30 - description: Offset within peripheral-syscon register
46 hisilicon,peripheral-syscon = <&peripheral_ctrl>;
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | st,stm32mp21-rcc.yaml | 98 - description: CK_SCMI_ICN_APB1 Peripheral bridge 1
99 - description: CK_SCMI_ICN_APB2 Peripheral bridge 2
100 - description: CK_SCMI_ICN_APB3 Peripheral bridge 3
101 - description: CK_SCMI_ICN_APB4 Peripheral bridge 4
102 - description: CK_SCMI_ICN_APB5 Peripheral bridge 5
103 - description: CK_SCMI_ICN_APBDBG Peripheral bridge for debug
104 - description: CK_SCMI_TIMG1 Peripheral bridge for timer1
105 - description: CK_SCMI_TIMG2 Peripheral bridge for timer2
|
| H A D | st,stm32mp25-rcc.yaml | 107 - description: CK_SCMI_ICN_APB1 Peripheral bridge 1
108 - description: CK_SCMI_ICN_APB2 Peripheral bridge 2
109 - description: CK_SCMI_ICN_APB3 Peripheral bridge 3
110 - description: CK_SCMI_ICN_APB4 Peripheral bridge 4
111 - description: CK_SCMI_ICN_APBDBG Peripheral bridge for debug
112 - description: CK_SCMI_TIMG1 Peripheral bridge for timer1
113 - description: CK_SCMI_TIMG2 Peripheral bridge for timer2
|
| /linux/drivers/remoteproc/ |
| H A D | Kconfig | 177 tristate "Qualcomm Technology Inc ADSP Peripheral Image Loader"
191 Say y here to support the Peripheral Image Loader
217 tristate "Qualcomm Peripheral Authentication Service support"
232 Say y here to support the TrustZone based Peripheral Image Loader for
235 Peripheral SubSystem), and SLPI (Sensor Low Power Island).
238 tristate "Qualcomm Hexagon based WCSS Peripheral Image Loader"
253 Say y here to support the Qualcomm Peripheral Image Loader for the
273 tristate "Qualcomm WCNSS Peripheral Image Loader"
285 Say y here to support the Peripheral Image Loader for loading WCNSS
287 verified and booted with the help of the Peripheral Authentication
|
| /linux/Documentation/driver-api/soundwire/ |
| H A D | bra.rst | 35 (3) The targeted Peripheral device SHALL support the optional Data
67 peripheral to deal with the previous transfer. In addition BRA
84 (1) A CRC on the 7-byte header. This CRC helps the Peripheral Device
86 bytes. The Peripheral Device provides a response in Byte 7.
152 In the case of multiple Peripheral devices attached to different
163 (1) Transfers initiated by a Peripheral Device. The BRA Initiator is
174 packet the header and footer response are provided by the Peripheral
175 Target device. On the Peripheral device, the BRA protocol is handled
182 (Host->Peripheral and Peripheral->Host). The amount of data
248 Peripheral/bus interface
[all …]
|
| /linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | sharp,lq101r1sx01.yaml | 17 Each of the DSI channels controls a separate DSI peripheral. The peripheral
19 peripheral and controls the device. The 'link2' property contains a phandle
20 to the peripheral driven by the second link (DSI-LINK2, right or odd).
49 phandle to the DSI peripheral on the secondary link. Note that the
|
| H A D | jdi,lpm102a188a.yaml | 17 Each of the DSI channels controls a separate DSI peripheral. The peripheral
18 driven by the first link (DSI-LINK1) is considered the primary peripheral
20 peripheral driven by the second link (DSI-LINK2).
43 phandle to the DSI peripheral on the secondary link. Note that the
|
| /linux/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 70 Hardware Peripheral
72 together make a larger user-facing functional peripheral. For
75 peripheral.
77 Also known as :term:`Peripheral`.
157 Peripheral
158 The same as :term:`Hardware Peripheral`.
172 **Serial Peripheral Interface Bus**
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-atr.yaml | 27 addresses must be available, not used by any other peripheral. Each
28 remote peripheral is assigned an alias from the pool, and transactions to
29 that address will be forwarded to the remote peripheral, with the address
30 translated to the remote peripheral's real address. This property is not
|
| /linux/arch/powerpc/platforms/52xx/ |
| H A D | mpc52xx_pic.c | 25 * three groups called 'critical', 'main', and 'peripheral'. The critical
28 * gpios, and the general purpose timers. Peripheral group contains the
56 * bestcomm interrupt occurs (peripheral group, irq 0) this driver determines
470 * 'peripheral'. This function reads the status register and returns the IRQ
473 * then 'peripheral'.
476 * of individual 'peripheral' interrupts. If this is the case then a special
478 * or medium priority peripheral irq has occurred.
484 * bestcomm DMA task can raise the bestcomm peripheral interrupt. When this
496 if (irq == 2) /* high priority peripheral */ in mpc52xx_get_irq()
497 goto peripheral; in mpc52xx_get_irq()
[all …]
|
| /linux/include/linux/dma/ |
| H A D | qcom-gpi-dma.h | 19 * struct gpi_spi_config - spi config for peripheral
31 * @set_config: set peripheral config
55 * struct gpi_i2c_config - i2c config for peripheral
64 * @set_config: set peripheral config
|
| /linux/drivers/usb/gadget/ |
| H A D | Kconfig | 4 # (a) a peripheral controller, and
23 PC) controlling up to 127 peripheral devices.
25 you can't connect a "to-the-host" connector to a peripheral.
27 Linux can run in the host, or in the peripheral. In both cases
29 talking to it. Peripheral controllers are often discrete silicon,
36 a USB peripheral device. Configure one hardware driver for your
37 peripheral/device side bus controller, and a "gadget driver" for
38 your peripheral protocol. (If you use modular gadget drivers,
83 (for a peripheral controller). The information in these
365 USB peripheral controller driver. Then you can use host-side
|
| /linux/drivers/i2c/busses/ |
| H A D | i2c-qcom-geni.c | 560 * @peripheral: Pointer to gpi_i2c_config
563 struct gpi_i2c_config *peripheral) in geni_i2c_gpi_multi_desc_unmap() argument
625 struct gpi_i2c_config *peripheral; in geni_i2c_gpi() local
637 peripheral = config->peripheral_config; in geni_i2c_gpi()
671 peripheral->rx_len = msgs[msg_idx].len; in geni_i2c_gpi()
672 peripheral->op = op; in geni_i2c_gpi()
680 peripheral->set_config = 0; in geni_i2c_gpi()
681 peripheral->multi_msg = true; in geni_i2c_gpi()
754 struct gpi_i2c_config peripheral = {}; in geni_i2c_gpi_xfer() local
762 config.peripheral_config = &peripheral; in geni_i2c_gpi_xfer()
[all …]
|