Home
last modified time | relevance | path

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

12345678910>>...16

/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/include/linux/
Dqcom_scm.h72 extern int qcom_scm_pas_init_image(u32 peripheral, const void *metadata,
74 extern int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr,
76 extern int qcom_scm_pas_auth_and_reset(u32 peripheral);
77 extern int qcom_scm_pas_shutdown(u32 peripheral);
78 extern bool qcom_scm_pas_supported(u32 peripheral);
126 static inline int qcom_scm_pas_init_image(u32 peripheral, const void *metadata, in qcom_scm_pas_init_image() argument
128 static inline int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr, in qcom_scm_pas_mem_setup() argument
130 static inline int qcom_scm_pas_auth_and_reset(u32 peripheral) in qcom_scm_pas_auth_and_reset() argument
132 static inline int qcom_scm_pas_shutdown(u32 peripheral) { return -ENODEV; } in qcom_scm_pas_shutdown() argument
133 static inline bool qcom_scm_pas_supported(u32 peripheral) { return false; } in qcom_scm_pas_supported() argument
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/Documentation/ABI/testing/
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.
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.
/kernel/linux/linux-5.10/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 …]
Dste-u300-syscon-clock.txt21 0 0 Slow peripheral bridge clock
28 1 0 Fast peripheral bridge clock
31 1 5 MMC interface peripheral (silicon) clock
Darmada3700-periph-clock.txt3 Marvell Armada 37xx SoCs provide peripheral clocks which are
4 used as clock source for the peripheral of the SoC.
9 The peripheral clock consumer should specify the desired clock by
Dlpc1850-cgu.txt4 peripheral blocks of the LPC18xx. Each independent clock is called
51 and APB peripheral blocks #0 and #2
56 9 BASE_APB1_CLK Base clock for APB peripheral block # 1
57 10 BASE_APB3_CLK Base clock for APB peripheral block # 3
/kernel/linux/linux-5.10/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 {
/kernel/linux/linux-5.10/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
60 - clocks: Should reference the peripheral and the AHB clocks
62 "pclk" for the peripheral clock
88 - clocks: Should reference the peripheral and host clocks
90 "pclk" for the peripheral clock
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/
Datmel-xdma.txt13 - bit 14: DIF, destination interface identifier, used to get the peripheral
15 - bit 30-24: PERID, peripheral identifier.
35 - bit 14: DIF, destination interface identifier, used to get the peripheral
37 - bit 30-24: PERID, peripheral identifier.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dqcom,spmi-pmic.txt42 Required properties for peripheral child nodes:
43 - compatible: Should contain "qcom,xxx", where "xxx" is a peripheral name.
45 Optional properties for peripheral child nodes:
52 example below the rtc device node represents a peripheral of pm8941
53 SID = 0. The regulator device node represents a peripheral of pm8941 SID = 1.
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/drivers/clk/qcom/
DKconfig89 Say Y if you want to use peripheral devices such as UART, SPI,
124 Say Y if you want to use peripheral devices such as UART, SPI,
131 Say Y if you want to use peripheral devices such as UART, SPI,
139 Say Y if you want to use peripheral devices such as UART, SPI,
154 Say Y if you want to use peripheral devices such as UART, SPI,
162 Say Y if you want to use peripheral devices such as UART, SPI,
185 Say Y if you want to use peripheral devices such as UART, SPI,
200 Say Y if you want to use peripheral devices such as UART, SPI,
224 Say Y if you want to use peripheral devices such as UART, SPI,
240 Say Y if you want to use peripheral devices such as UART, SPI,
[all …]
/kernel/linux/linux-5.10/sound/soc/adi/
DKconfig14 ASoC driver for the Analog Devices AXI-I2S softcore peripheral.
22 ASoC driver for the Analog Devices AXI-SPDIF softcore peripheral.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/
Dk3-dw-mshc.txt22 - hisilicon,peripheral-syscon: phandle of syscon used to control peripheral.
62 hisilicon,peripheral-syscon = <&ao_ctrl>;
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/
Datmel-quadspi.txt13 - clocks: Should reference the peripheral clock and the QSPI system
15 - clock-names: Should contain "pclk" for the peripheral clock and "qspick"
/kernel/linux/linux-5.10/Documentation/i2c/busses/
Di2c-ismt.rst43 00:13.0 System peripheral: Intel Corporation Centerton SMBus 2.0 Controller 0
44 00:13.1 System peripheral: Intel Corporation Centerton SMBus 2.0 Controller 1
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/spmi/
Dqcom,spmi-pmic-arb.txt33 single interrupt entry for the peripheral interrupt
40 cell 2: peripheral ID for requested interrupt (0-255)
41 cell 3: the requested peripheral interrupt (0-7)

12345678910>>...16