Home
last modified time | relevance | path

Searched full:peripheral (Results 1 – 25 of 1017) sorted by relevance

12345678910>>...41

/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/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/devicetree/bindings/clock/
Dpistachio-clock.txt4 Pistachio has four clock controllers (core clock, peripheral clock, peripheral
44 Peripheral clock controller:
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
71 Peripheral general control:
74 The peripheral general control block generates system interface clocks and
75 resets for various peripherals. It also contains miscellaneous peripheral
[all …]
Dmvebu-gated-clock.txt4 peripheral clocks to be gated to save some power. The clock consumer
11 ID Clock Peripheral
28 ID Clock Peripheral
55 ID Clock Peripheral
82 ID Clock Peripheral
96 ID Clock Peripheral
123 ID Clock Peripheral
133 ID Clock Peripheral
149 22 pdma Peripheral DMA
156 ID Clock Peripheral
/kernel/linux/linux-5.10/drivers/usb/gadget/udc/
DKconfig4 # (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 "Faraday FUSB300 USB Peripheral Controller"
113 tristate "Faraday FOTG210 USB Peripheral Controller"
123 tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
171 tristate "Renesas R8A66597 USB Peripheral Controller"
[all …]
/kernel/linux/linux-5.10/drivers/rtc/
Drtc-meson.c66 struct regmap *peripheral; /* peripheral registers */ member
71 .name = "peripheral-registers",
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()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/
Dimg,pdc-intc.txt27 shared SysWake interrupt, and remaining specifies shall be PDC peripheral
35 0-7: Peripheral interrupts
39 flags as follows (only 4 valid for peripheral interrupts):
74 <30 4 /* level */>, /* Peripheral 0 (RTC) */
75 <29 4 /* level */>, /* Peripheral 1 (IR) */
76 <31 4 /* level */>; /* Peripheral 2 (WDT) */
82 * An SoC peripheral that is wired through the PDC.
88 // Interrupt source Peripheral 0
89 interrupts = <0 /* Peripheral 0 (RTC) */
/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/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/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/include/linux/mfd/
Dsta2x11-mfd.h204 #define APBREG_PWAC 0x20 /* Peripheral Write Access Control reg */
205 #define APBREG_PRAC 0x40 /* Peripheral Read Access Control reg */
206 #define APBREG_PCG 0x60 /* Peripheral Clock Gating Reg */
207 #define APBREG_PUR 0x80 /* Peripheral Under Reset Reg */
208 #define APBREG_EMU_PCG 0xA0 /* Emulator Peripheral Clock Gating Reg */
216 #define APBREG_PWAC_SARAC 0x120 /* Peripheral Write Access Control reg */
217 #define APBREG_PRAC_SARAC 0x140 /* Peripheral Read Access Control reg */
218 #define APBREG_PCG_SARAC 0x160 /* Peripheral Clock Gating Reg */
219 #define APBREG_PUR_SARAC 0x180 /* Peripheral Under Reset Reg */
220 #define APBREG_EMU_PCG_SARAC 0x1A0 /* Emulator Peripheral Clock Gating Reg */
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/
Ddrm_mipi_dsi.c241 * @dsi: DSI peripheral device
321 * @dsi: DSI peripheral
336 * @dsi: DSI peripheral
488 * mipi_dsi_shutdown_peripheral() - sends a Shutdown Peripheral command
489 * @dsi: DSI peripheral device
508 * mipi_dsi_turn_on_peripheral() - sends a Turn On Peripheral command
509 * @dsi: DSI peripheral device
529 * the payload in a long packet transmitted from the peripheral back to the
531 * @dsi: DSI peripheral device
553 * mipi_dsi_compression_mode() - enable/disable DSC on the peripheral
[all …]
/kernel/linux/linux-5.10/include/linux/mmc/
Dsh_mmcif.h18 * 1000 : Peripheral clock / 512
19 * 0111 : Peripheral clock / 256
20 * 0110 : Peripheral clock / 128
21 * 0101 : Peripheral clock / 64
22 * 0100 : Peripheral clock / 32
23 * 0011 : Peripheral clock / 16
24 * 0010 : Peripheral clock / 8
25 * 0001 : Peripheral clock / 4
26 * 0000 : Peripheral clock / 2
27 * 1111 : Peripheral clock (sup_pclk set '1')
/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/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,
/kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/
Diwl-context-info-gen3.h191 * struct iwl_prph_scratch - peripheral scratch mapping
203 * struct iwl_prph_info - peripheral information
206 * @sleep_notif: indicates the peripheral sleep status
220 * @config: context in which the peripheral would execute - a subset of
221 * capability csr register published by the peripheral
222 * @prph_info_base_addr: the peripheral information structure start address
241 * @mtr_msi_vec: the MSI which shall be generated by the peripheral after
243 * @mcr_msi_vec: the MSI which shall be generated by the peripheral after
254 * @prph_info_msi_vec: the MSI which shall be generated by the peripheral
255 * after updating the Peripheral Information structure
[all …]
/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 {
/kernel/linux/linux-5.10/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).
42 phandle to the DSI peripheral on the secondary link. Note that the
/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/userspace-api/media/
Dglossary.rst63 Hardware Peripheral
65 together make a larger user-facing functional peripheral. For
68 peripheral.
70 Also known as :term:`Peripheral`.
150 Peripheral
151 The same as :term:`Hardware Peripheral`.
165 **Serial Peripheral Interface Bus**
/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/drivers/remoteproc/
DKconfig140 tristate "Qualcomm Technology Inc ADSP Peripheral Image Loader"
152 Say y here to support the Peripheral Image Loader
173 tristate "Qualcomm Hexagon v5 Peripheral Authentication Service support"
191 tristate "Qualcomm Hexagon based WCSS Peripheral Image Loader"
204 Say y here to support the Qualcomm Peripheral Image Loader for the
223 tristate "Qualcomm WCNSS Peripheral Image Loader"
234 Say y here to support the Peripheral Image Loader for the Qualcomm
/kernel/linux/linux-5.10/drivers/firmware/
Dqcom_scm.c430 * qcom_scm_pas_init_image() - Initialize peripheral authentication service
431 * state machine for a given peripheral, using the
433 * @peripheral: peripheral id
441 int qcom_scm_pas_init_image(u32 peripheral, const void *metadata, size_t size) in qcom_scm_pas_init_image() argument
450 .args[0] = peripheral, in qcom_scm_pas_init_image()
486 * qcom_scm_pas_mem_setup() - Prepare the memory related to a given peripheral
488 * @peripheral: peripheral id
494 int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr, phys_addr_t size) in qcom_scm_pas_mem_setup() argument
501 .args[0] = peripheral, in qcom_scm_pas_mem_setup()
520 * qcom_scm_pas_auth_and_reset() - Authenticate the given peripheral firmware
[all …]

12345678910>>...41