Home
last modified time | relevance | path

Searched refs:peripheral (Results 1 – 25 of 473) sorted by relevance

12345678910>>...19

/linux/drivers/rtc/
A Drtc-meson.c66 struct regmap *peripheral; /* peripheral registers */ member
92 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SDI, in meson_rtc_send_bit()
125 regmap_read(rtc->peripheral, RTC_ADDR1, &tmp); in meson_rtc_get_data()
139 regmap_update_bits(rtc->peripheral, RTC_ADDR0, val, 0); in meson_rtc_get_bus()
143 if (!regmap_read_poll_timeout(rtc->peripheral, RTC_ADDR1, val, in meson_rtc_get_bus()
215 regmap_write(rtc->peripheral, RTC_REG4, in meson_rtc_write_static()
220 regmap_update_bits(rtc->peripheral, RTC_ADDR0, in meson_rtc_write_static()
224 return regmap_read_poll_timeout(rtc->peripheral, RTC_REG4, tmp, in meson_rtc_write_static()
318 rtc->peripheral = devm_regmap_init_mmio(dev, base, in meson_rtc_probe()
320 if (IS_ERR(rtc->peripheral)) { in meson_rtc_probe()
[all …]
/linux/Documentation/driver-api/memory-devices/
A Dti-gpmc.rst24 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
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
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
49 on understanding of gpmc timings, peripheral timings, available
54 gpmc timing dependency on peripheral timings:
[all …]
/linux/Documentation/devicetree/bindings/display/
A Dmipi-dsi-bus.txt15 The following assumes that only a single peripheral is connected to a DSI
39 DSI peripheral
58 that the peripheral responds to.
80 an input endpoint of the DSI peripheral.
89 - (4) is an example of a peripheral on a I2C control bus connected to a
101 /* peripheral responds to virtual channel 0 */
102 peripheral@0 {
117 /* peripheral responds to virtual channels 0 and 2 */
118 peripheral@0 {
133 /* peripheral responds to virtual channels 1, 2 and 3 */
[all …]
/linux/Documentation/devicetree/bindings/clock/
A Dpistachio-clock.txt4 Pistachio has four clock controllers (core clock, peripheral clock, peripheral
47 The peripheral clock controller generates clocks for the DDR, ROM, and other
48 peripherals. The peripheral system clock ("periph_sys") generated by the core
49 clock controller is the input clock to the peripheral clock controller.
53 - reg: Must contain the base address and length of the peripheral clock
58 - clock-names: Must include "periph_sys", the peripheral system clock generated
74 The peripheral general control block generates system interface clocks and
75 resets for various peripherals. It also contains miscellaneous peripheral
76 control registers. The system clock ("sys") generated by the peripheral clock
81 - reg: Must contain the base address and length of the peripheral general
[all …]
A Dstericsson,u8500-clks.yaml18 control management unit) clocks and PRCC (peripheral reset and
50 description: A subnode with two clock cells for PRCC (peripheral
51 reset and clock controller) peripheral clocks. The first cell indicates
64 description: A subnode with two clock cells for PRCC (peripheral reset
79 PRCC (peripheral reset and clock controller). The first cell indicates
/linux/Documentation/ABI/testing/
A Dsysfs-platform-phy-rcar-gen3-usb211 - "host" - switching mode from peripheral to host.
12 - "peripheral" - switching mode from host to peripheral.
17 - "peripheral" - The mode is peripheral now.
A Dsysfs-platform-renesas_usb311 - "host" - switching mode from peripheral to host.
12 - "peripheral" - switching mode from host to peripheral.
17 - "peripheral" - The mode is peripheral now.
/linux/drivers/spi/
A Dspi-geni-qcom.c377 peripheral.set_config = true; in setup_gsi_xfer()
386 peripheral.cmd = SPI_DUPLEX; in setup_gsi_xfer()
388 peripheral.cmd = SPI_TX; in setup_gsi_xfer()
389 peripheral.rx_len = 0; in setup_gsi_xfer()
391 peripheral.cmd = SPI_RX; in setup_gsi_xfer()
404 peripheral.cs = spi_slv->chip_select; in setup_gsi_xfer()
405 peripheral.pack_en = true; in setup_gsi_xfer()
409 &peripheral.clk_src, &peripheral.clk_div); in setup_gsi_xfer()
420 if (peripheral.cmd & SPI_RX) { in setup_gsi_xfer()
445 if (peripheral.cmd & SPI_RX) in setup_gsi_xfer()
[all …]
/linux/Documentation/devicetree/bindings/phy/
A Dhix5hd2-phy.txt11 - hisilicon,peripheral-syscon: phandle of syscon used to control peripheral.
12 - hisilicon,power-reg: offset and bit number within peripheral-syscon,
20 hisilicon,peripheral-syscon = <&peripheral_ctrl>;
A Dphy-hi3798cv200-combphy.txt6 registers in peripheral controller, e.g. PERI_COMBPHY0_CFG and
21 peripheral controller, as a 3 integers tuple:
27 - The device node should be a child of peripheral controller that contains
29 Refer to arm/hisilicon/hisilicon.txt for the parent peripheral controller
34 perictrl: peripheral-controller@8a20000 {
A Dphy-hi6220-usb.txt7 - hisilicon,peripheral-syscon: phandle of syscon used to control phy.
15 hisilicon,peripheral-syscon = <&sys_ctrl>;
A Dphy-hisi-inno-usb2.txt7 - reg: Should be the address space for PHY configuration register in peripheral
16 The INNO USB2 PHY device should be a child node of peripheral controller that
29 perictrl: peripheral-controller@8a20000 {
/linux/include/linux/
A Dqcom_scm.h71 extern int qcom_scm_pas_init_image(u32 peripheral, const void *metadata,
73 extern int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr,
75 extern int qcom_scm_pas_auth_and_reset(u32 peripheral);
76 extern int qcom_scm_pas_shutdown(u32 peripheral);
77 extern bool qcom_scm_pas_supported(u32 peripheral);
/linux/Documentation/devicetree/bindings/iommu/
A Dsamsung,sysmmu.yaml14 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/devicetree/bindings/usb/
A Datmel-usb.txt10 - 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
92 - clocks: Should reference the peripheral and host clocks
94 "pclk" for the peripheral clock
A Dcdns,usb3.yaml41 - const: peripheral
46 enum: [host, otg, peripheral]
98 interrupt-names = "host", "peripheral", "otg";
/linux/Documentation/devicetree/bindings/display/panel/
A Dsharp,lq101r1sx01.yaml17 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).
42 phandle to the DSI peripheral on the secondary link. Note that the
/linux/Documentation/devicetree/bindings/dma/
A Datmel-xdma.txt14 - bit 14: DIF, destination interface identifier, used to get the peripheral
16 - bit 30-24: PERID, peripheral identifier.
36 - bit 14: DIF, destination interface identifier, used to get the peripheral
38 - bit 30-24: PERID, peripheral identifier.
/linux/drivers/clk/qcom/
A DKconfig106 Say Y if you want to use peripheral devices such as UART, SPI,
141 Say Y if you want to use peripheral devices such as UART, SPI,
148 Say Y if you want to use peripheral devices such as UART, SPI,
332 Say Y if you want to use multimedia devices or peripheral
339 Say Y if you want to use multimedia devices or peripheral
557 Say Y if you want to use peripheral devices such as UART,
587 Say Y if you want to use peripheral devices such as UART,
595 Say Y if you want to use peripheral devices such as UART,
602 Say Y if you want to use peripheral devices such as UART,
610 Say Y if you want to use peripheral devices such as UART,
[all …]
/linux/Documentation/devicetree/bindings/mfd/
A Dqcom,spmi-pmic.txt55 Required properties for peripheral child nodes:
56 - compatible: Should contain "qcom,xxx", where "xxx" is a peripheral name.
58 Optional properties for peripheral child nodes:
65 example below the rtc device node represents a peripheral of pm8941
66 SID = 0. The regulator device node represents a peripheral of pm8941 SID = 1.
/linux/Documentation/devicetree/bindings/input/
A Dti,nspire-keypad.txt6 - reg: Physical base address of the peripheral and length of memory mapped
9 - interrupts: The interrupt number for the peripheral.
16 - clocks: The clock this peripheral is attached to.
/linux/Documentation/devicetree/bindings/serial/
A Dfsl-imx-uart.yaml63 Indicate that the hardware attached to the peripheral inverts the signal
64 transmitted, and that the peripheral should invert its output using the
70 Indicate that the hardware attached to the peripheral inverts the signal
71 received, and that the peripheral should invert its input using the
/linux/Documentation/firmware-guide/acpi/
A Dextcon-intel-int3496.rst12 between an USB host and an USB peripheral controller.
23 the USB peripheral controller, write 1 to mux to the peripheral
/linux/Documentation/devicetree/bindings/sound/
A Damlogic,aiu.yaml30 - description: AIU peripheral clock
31 - description: I2S peripheral clock
35 - description: SPDIF peripheral clock
/linux/sound/soc/adi/
A DKconfig13 ASoC driver for the Analog Devices AXI-I2S softcore peripheral.
21 ASoC driver for the Analog Devices AXI-SPDIF softcore peripheral.

Completed in 29 milliseconds

12345678910>>...19