Home
last modified time | relevance | path

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

12345678910>>...16

/Linux-v5.4/include/linux/
Dqcom_scm.h44 extern bool qcom_scm_pas_supported(u32 peripheral);
45 extern int qcom_scm_pas_init_image(u32 peripheral, const void *metadata,
47 extern int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr,
49 extern int qcom_scm_pas_auth_and_reset(u32 peripheral);
50 extern int qcom_scm_pas_shutdown(u32 peripheral);
81 static inline bool qcom_scm_pas_supported(u32 peripheral) { return false; } in qcom_scm_pas_supported() argument
82 static inline int qcom_scm_pas_init_image(u32 peripheral, const void *metadata, in qcom_scm_pas_init_image() argument
84 static inline int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr, in qcom_scm_pas_mem_setup() argument
87 qcom_scm_pas_auth_and_reset(u32 peripheral) { return -ENODEV; } in qcom_scm_pas_auth_and_reset() argument
88 static inline int qcom_scm_pas_shutdown(u32 peripheral) { return -ENODEV; } in qcom_scm_pas_shutdown() argument
/Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/Documentation/devicetree/bindings/phy/
Dmeson-gxl-usb3-phy.txt10 - and peripheral mode/OTG detection
11 - clock-names: must contain "phy" and "peripheral"
14 - peripheral mode/OTG detection
15 - reset-names: must contain "phy" and "peripheral"
28 clock-names = "phy", "peripheral";
30 reset-names = "phy", "peripheral";
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>;
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-platform-phy-rcar-gen3-usb210 "host" - switching mode from peripheral to host.
11 "peripheral" - switching mode from host to peripheral.
15 "peripheral" - The mode is peripheral now.
Dsysfs-platform-renesas_usb310 "host" - switching mode from peripheral to host.
11 "peripheral" - switching mode from host to peripheral.
15 "peripheral" - The mode is peripheral now.
/Linux-v5.4/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
/Linux-v5.4/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.txt4 physical memory chunks visible as a contiguous region to DMA-capable peripheral
13 System MMUs are in many to one relation with peripheral devices, i.e. single
14 peripheral device might have multiple System MMUs (usually one for each bus
15 master), but one System MMU can handle transactions from only one peripheral
16 device. The relation between a System MMU and the peripheral device needs to be
17 defined in device node of the peripheral device.
27 For information on assigning System MMU controller to its peripheral devices,
41 of peripheral device this SYSMMU belongs to).
/Linux-v5.4/drivers/firmware/
Dqcom_scm.h52 extern bool __qcom_scm_pas_supported(struct device *dev, u32 peripheral);
53 extern int __qcom_scm_pas_init_image(struct device *dev, u32 peripheral,
55 extern int __qcom_scm_pas_mem_setup(struct device *dev, u32 peripheral,
57 extern int __qcom_scm_pas_auth_and_reset(struct device *dev, u32 peripheral);
58 extern int __qcom_scm_pas_shutdown(struct device *dev, u32 peripheral);
Dqcom_scm-32.c449 bool __qcom_scm_pas_supported(struct device *dev, u32 peripheral) in __qcom_scm_pas_supported() argument
455 in = cpu_to_le32(peripheral); in __qcom_scm_pas_supported()
464 int __qcom_scm_pas_init_image(struct device *dev, u32 peripheral, in __qcom_scm_pas_init_image() argument
474 request.proc = cpu_to_le32(peripheral); in __qcom_scm_pas_init_image()
485 int __qcom_scm_pas_mem_setup(struct device *dev, u32 peripheral, in __qcom_scm_pas_mem_setup() argument
496 request.proc = cpu_to_le32(peripheral); in __qcom_scm_pas_mem_setup()
508 int __qcom_scm_pas_auth_and_reset(struct device *dev, u32 peripheral) in __qcom_scm_pas_auth_and_reset() argument
514 in = cpu_to_le32(peripheral); in __qcom_scm_pas_auth_and_reset()
523 int __qcom_scm_pas_shutdown(struct device *dev, u32 peripheral) in __qcom_scm_pas_shutdown() argument
529 in = cpu_to_le32(peripheral); in __qcom_scm_pas_shutdown()
Dqcom_scm-64.c263 bool __qcom_scm_pas_supported(struct device *dev, u32 peripheral) in __qcom_scm_pas_supported() argument
269 desc.args[0] = peripheral; in __qcom_scm_pas_supported()
279 int __qcom_scm_pas_init_image(struct device *dev, u32 peripheral, in __qcom_scm_pas_init_image() argument
286 desc.args[0] = peripheral; in __qcom_scm_pas_init_image()
296 int __qcom_scm_pas_mem_setup(struct device *dev, u32 peripheral, in __qcom_scm_pas_mem_setup() argument
303 desc.args[0] = peripheral; in __qcom_scm_pas_mem_setup()
314 int __qcom_scm_pas_auth_and_reset(struct device *dev, u32 peripheral) in __qcom_scm_pas_auth_and_reset() argument
320 desc.args[0] = peripheral; in __qcom_scm_pas_auth_and_reset()
330 int __qcom_scm_pas_shutdown(struct device *dev, u32 peripheral) in __qcom_scm_pas_shutdown() argument
336 desc.args[0] = peripheral; in __qcom_scm_pas_shutdown()
Dqcom_scm.c181 bool qcom_scm_pas_supported(u32 peripheral) in qcom_scm_pas_supported() argument
190 return __qcom_scm_pas_supported(__scm->dev, peripheral); in qcom_scm_pas_supported()
206 int qcom_scm_pas_init_image(u32 peripheral, const void *metadata, size_t size) in qcom_scm_pas_init_image() argument
229 ret = __qcom_scm_pas_init_image(__scm->dev, peripheral, mdata_phys); in qcom_scm_pas_init_image()
249 int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr, phys_addr_t size) in qcom_scm_pas_mem_setup() argument
257 ret = __qcom_scm_pas_mem_setup(__scm->dev, peripheral, addr, size); in qcom_scm_pas_mem_setup()
271 int qcom_scm_pas_auth_and_reset(u32 peripheral) in qcom_scm_pas_auth_and_reset() argument
279 ret = __qcom_scm_pas_auth_and_reset(__scm->dev, peripheral); in qcom_scm_pas_auth_and_reset()
292 int qcom_scm_pas_shutdown(u32 peripheral) in qcom_scm_pas_shutdown() argument
300 ret = __qcom_scm_pas_shutdown(__scm->dev, peripheral); in qcom_scm_pas_shutdown()
/Linux-v5.4/Documentation/devicetree/bindings/display/panel/
Dsharp,lq101r1sx01.txt7 Each of the DSI channels controls a separate DSI peripheral. The peripheral
9 peripheral and controls the device. The 'link2' property contains a phandle
10 to the peripheral driven by the second link (DSI-LINK2, right or odd).
20 - reg: DSI virtual channel of the peripheral
23 - link2: phandle to the DSI peripheral on the secondary link. Note that the
/Linux-v5.4/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
87 - clocks: Should reference the peripheral and host clocks
89 "pclk" for the peripheral clock
Dcdns-usb3.txt16 "peripheral" - interrupt used by device driver
22 - dr_mode: Should be one of "host", "peripheral" or "otg".
38 interrupt-names = "host", "peripheral", "otg";
/Linux-v5.4/Documentation/devicetree/bindings/dma/
Datmel-xdma.txt15 - bit 14: DIF, destination interface identifier, used to get the peripheral
17 - bit 30-24: PERID, peripheral identifier.
37 - bit 14: DIF, destination interface identifier, used to get the peripheral
39 - bit 30-24: PERID, peripheral identifier.
/Linux-v5.4/Documentation/devicetree/bindings/mfd/
Dqcom,spmi-pmic.txt40 Required properties for peripheral child nodes:
41 - compatible: Should contain "qcom,xxx", where "xxx" is a peripheral name.
43 Optional properties for peripheral child nodes:
50 example below the rtc device node represents a peripheral of pm8941
51 SID = 0. The regulator device node represents a peripheral of pm8941 SID = 1.
/Linux-v5.4/drivers/clk/qcom/
DKconfig79 Say Y if you want to use peripheral devices such as UART, SPI,
95 Say Y if you want to use peripheral devices such as UART, SPI,
102 Say Y if you want to use peripheral devices such as UART, SPI,
117 Say Y if you want to use peripheral devices such as UART, SPI,
125 Say Y if you want to use peripheral devices such as UART, SPI,
140 Say Y if you want to use peripheral devices such as UART, SPI,
155 Say Y if you want to use peripheral devices such as UART, SPI,
179 Say Y if you want to use peripheral devices such as UART, SPI,
195 Say Y if you want to use peripheral devices such as UART, SPI,
203 Say Y if you want to use peripheral devices such as UART, SPI,
[all …]
/Linux-v5.4/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-v5.4/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

12345678910>>...16