Home
last modified time | relevance | path

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

12345678910>>...27

/linux-6.1.9/drivers/rtc/
Drtc-meson.c66 struct regmap *peripheral; /* peripheral registers */ member
84 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SCLK, 0); in meson_rtc_sclk_pulse()
86 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SCLK, in meson_rtc_sclk_pulse()
92 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SDI, in meson_rtc_send_bit()
110 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SEN, 0); in meson_rtc_set_dir()
111 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SDI, 0); in meson_rtc_set_dir()
113 regmap_update_bits(rtc->peripheral, RTC_ADDR0, RTC_ADDR0_LINE_SDI, 0); in meson_rtc_set_dir()
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()
[all …]
/linux-6.1.9/Documentation/driver-api/memory-devices/
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
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-6.1.9/Documentation/devicetree/bindings/display/
Dmipi-dsi-bus.txt15 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-6.1.9/Documentation/ABI/testing/
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.
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-6.1.9/Documentation/devicetree/bindings/clock/
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 …]
/linux-6.1.9/Documentation/devicetree/bindings/phy/
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>;
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 {
Dphy-hi6220-usb.txt7 - hisilicon,peripheral-syscon: phandle of syscon used to control phy.
15 hisilicon,peripheral-syscon = <&sys_ctrl>;
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-6.1.9/Documentation/devicetree/bindings/iommu/
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-6.1.9/include/linux/
Dqcom_scm.h77 extern int qcom_scm_pas_init_image(u32 peripheral, const void *metadata,
81 extern int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr,
83 extern int qcom_scm_pas_auth_and_reset(u32 peripheral);
84 extern int qcom_scm_pas_shutdown(u32 peripheral);
85 extern bool qcom_scm_pas_supported(u32 peripheral);
/linux-6.1.9/Documentation/devicetree/bindings/usb/
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
95 - clocks: Should reference the peripheral and host clocks
97 "pclk" for the peripheral clock
Dcdns,usb3.yaml41 - const: peripheral
46 enum: [host, otg, peripheral]
98 interrupt-names = "host", "peripheral", "otg";
/linux-6.1.9/drivers/spi/
Dspi-geni-qcom.c395 struct gpi_spi_config peripheral = {}; in setup_gsi_xfer() local
399 config.peripheral_config = &peripheral; in setup_gsi_xfer()
400 config.peripheral_size = sizeof(peripheral); in setup_gsi_xfer()
401 peripheral.set_config = true; in setup_gsi_xfer()
410 peripheral.cmd = SPI_DUPLEX; in setup_gsi_xfer()
412 peripheral.cmd = SPI_TX; in setup_gsi_xfer()
413 peripheral.rx_len = 0; in setup_gsi_xfer()
415 peripheral.cmd = SPI_RX; in setup_gsi_xfer()
417 peripheral.rx_len = ((xfer->len << 3) / mas->cur_bits_per_word); in setup_gsi_xfer()
421 peripheral.rx_len = (xfer->len / bytes_per_word); in setup_gsi_xfer()
[all …]
/linux-6.1.9/Documentation/devicetree/bindings/display/panel/
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).
47 phandle to the DSI peripheral on the secondary link. Note that the
/linux-6.1.9/Documentation/devicetree/bindings/spi/
Dspi-peripheral-props.yaml4 $id: http://devicetree.org/schemas/spi/spi-peripheral-props.yaml#
10 Many SPI controllers need to add properties to peripheral devices. They could
13 need to be defined in the peripheral node because they are per-peripheral and
103 - $ref: cdns,qspi-nor-peripheral-props.yaml#
104 - $ref: samsung,spi-peripheral-props.yaml#
105 - $ref: nvidia,tegra210-quad-peripheral-props.yaml#
/linux-6.1.9/Documentation/devicetree/bindings/dma/
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-6.1.9/drivers/i2c/busses/
Di2c-qcom-geni.c510 struct gpi_i2c_config *peripheral; in geni_i2c_gpi() local
519 peripheral = config->peripheral_config; in geni_i2c_gpi()
537 peripheral->rx_len = msg->len; in geni_i2c_gpi()
538 peripheral->op = op; in geni_i2c_gpi()
546 peripheral->set_config = 0; in geni_i2c_gpi()
547 peripheral->multi_msg = true; in geni_i2c_gpi()
580 struct gpi_i2c_config peripheral = {}; in geni_i2c_gpi_xfer() local
586 config.peripheral_config = &peripheral; in geni_i2c_gpi_xfer()
587 config.peripheral_size = sizeof(peripheral); in geni_i2c_gpi_xfer()
589 peripheral.pack_enable = I2C_PACK_TX | I2C_PACK_RX; in geni_i2c_gpi_xfer()
[all …]
/linux-6.1.9/drivers/clk/qcom/
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,
156 Say Y if you want to use peripheral devices such as UART, SPI,
172 Say Y if you want to use peripheral devices such as UART, SPI,
180 Say Y if you want to use peripheral devices such as UART, SPI,
211 Say Y if you want to use peripheral devices such as UART, SPI,
226 Say Y if you want to use peripheral devices such as UART, SPI,
233 Say Y if you want to use peripheral devices such as UART, SPI,
265 Say Y if you want to use peripheral devices such as UART, SPI,
[all …]
/linux-6.1.9/Documentation/devicetree/bindings/input/
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-6.1.9/Documentation/firmware-guide/acpi/
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-6.1.9/Documentation/devicetree/bindings/serial/
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-6.1.9/sound/soc/adi/
DKconfig13 ASoC driver for the Analog Devices AXI-I2S softcore peripheral.
21 ASoC driver for the Analog Devices AXI-SPDIF softcore peripheral.
/linux-6.1.9/Documentation/devicetree/bindings/sound/
Damlogic,aiu.yaml33 - description: AIU peripheral clock
34 - description: I2S peripheral clock
38 - description: SPDIF peripheral clock

12345678910>>...27