| /linux/sound/soc/codecs/ |
| A D | cs35l56-sdw.c | 65 ret = cs35l56_sdw_poll_mem_status(peripheral, in cs35l56_sdw_slow_read() 74 sdw_read_no_pm(peripheral, reg + i); in cs35l56_sdw_slow_read() 77 ret = cs35l56_sdw_poll_mem_status(peripheral, in cs35l56_sdw_slow_read() 118 struct sdw_slave *peripheral = context; in cs35l56_sdw_read() local 181 struct sdw_slave *peripheral = context; in cs35l56_sdw_gather_write() local 381 cs35l56_sdw_init(peripheral); in cs35l56_sdw_update_status() 420 if (peripheral->unattach_request) { in cs35l56_sdw_handle_unattach() 429 peripheral->unattach_request = 0; in cs35l56_sdw_handle_unattach() 510 struct device *dev = &peripheral->dev; in cs35l56_sdw_probe() 519 cs35l56->sdw_peripheral = peripheral; in cs35l56_sdw_probe() [all …]
|
| A D | cs42l42-sdw.c | 210 false, peripheral, CS42L42_SDW_MEM_ACCESS_STATUS); in cs42l42_sdw_poll_status() 223 struct sdw_slave *peripheral = context; in cs42l42_sdw_read() local 233 ret = sdw_read_no_pm(peripheral, reg); in cs42l42_sdw_read() 254 ret = cs42l42_sdw_poll_status(peripheral, in cs42l42_sdw_read() 273 struct sdw_slave *peripheral = context; in cs42l42_sdw_write() local 313 struct sdw_slave_prop *prop = &peripheral->prop; in cs42l42_sdw_read_prop() 364 cs42l42_sdw_init(peripheral); in cs42l42_sdw_update_status() 437 if (!peripheral->unattach_request) in cs42l42_sdw_handle_unattach() 448 peripheral->unattach_request = 0; in cs42l42_sdw_handle_unattach() 519 struct device *dev = &peripheral->dev; in cs42l42_sdw_probe() [all …]
|
| /linux/drivers/rtc/ |
| A D | rtc-meson.c | 66 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 D | ti-gpmc.rst | 24 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 D | mipi-dsi-bus.txt | 15 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/ABI/testing/ |
| A D | sysfs-platform-phy-rcar-gen3-usb2 | 11 - "host" - switching mode from peripheral to host. 12 - "peripheral" - switching mode from host to peripheral. 17 - "peripheral" - The mode is peripheral now.
|
| A D | sysfs-platform-renesas_usb3 | 11 - "host" - switching mode from peripheral to host. 12 - "peripheral" - switching mode from host to peripheral. 17 - "peripheral" - The mode is peripheral now.
|
| /linux/Documentation/devicetree/bindings/clock/ |
| A D | pistachio-clock.txt | 4 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/Documentation/devicetree/bindings/phy/ |
| A D | hix5hd2-phy.txt | 11 - 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 D | phy-hi6220-usb.txt | 7 - hisilicon,peripheral-syscon: phandle of syscon used to control phy. 15 hisilicon,peripheral-syscon = <&sys_ctrl>;
|
| /linux/Documentation/devicetree/bindings/iommu/ |
| A D | samsung,sysmmu.yaml | 14 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/memory-controllers/ |
| A D | mc-peripheral-props.yaml | 4 $id: http://devicetree.org/schemas/memory-controllers/mc-peripheral-props.yaml# 10 Many Memory Controllers need to add properties to peripheral devices. 13 to be defined in the peripheral node because they are per-peripheral 38 - $ref: intel,ixp4xx-expansion-peripheral-props.yaml#
|
| /linux/Documentation/devicetree/bindings/usb/ |
| A D | atmel-usb.txt | 10 - 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
|
| /linux/Documentation/devicetree/bindings/spi/ |
| A D | spi-peripheral-props.yaml | 4 $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 123 - $ref: arm,pl022-peripheral-props.yaml# 124 - $ref: cdns,qspi-nor-peripheral-props.yaml# 125 - $ref: fsl,dspi-peripheral-props.yaml# 126 - $ref: samsung,spi-peripheral-props.yaml# 127 - $ref: nvidia,tegra210-quad-peripheral-props.yaml#
|
| /linux/include/linux/firmware/qcom/ |
| A D | qcom_scm.h | 75 int qcom_scm_pas_init_image(u32 peripheral, const void *metadata, size_t size, 78 int qcom_scm_pas_mem_setup(u32 peripheral, phys_addr_t addr, phys_addr_t size); 79 int qcom_scm_pas_auth_and_reset(u32 peripheral); 80 int qcom_scm_pas_shutdown(u32 peripheral); 81 bool qcom_scm_pas_supported(u32 peripheral);
|
| /linux/Documentation/devicetree/bindings/display/panel/ |
| A D | jdi,lpm102a188a.yaml | 17 Each of the DSI channels controls a separate DSI peripheral. The peripheral 18 driven by the first link (DSI-LINK1) is considered the primary peripheral 20 peripheral driven by the second link (DSI-LINK2). 43 phandle to the DSI peripheral on the secondary link. Note that the
|
| A D | sharp,lq101r1sx01.yaml | 17 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). 49 phandle to the DSI peripheral on the secondary link. Note that the
|
| /linux/drivers/spi/ |
| A D | spi-geni-qcom.c | 461 struct gpi_spi_config peripheral = {}; in setup_gsi_xfer() local 467 peripheral.set_config = true; in setup_gsi_xfer() 476 peripheral.cmd = SPI_DUPLEX; in setup_gsi_xfer() 478 peripheral.cmd = SPI_TX; in setup_gsi_xfer() 479 peripheral.rx_len = 0; in setup_gsi_xfer() 481 peripheral.cmd = SPI_RX; in setup_gsi_xfer() 495 peripheral.pack_en = true; in setup_gsi_xfer() 499 &peripheral.clk_src, &peripheral.clk_div); in setup_gsi_xfer() 510 if (peripheral.cmd & SPI_RX) { in setup_gsi_xfer() 535 if (peripheral.cmd & SPI_RX) in setup_gsi_xfer() [all …]
|
| /linux/Documentation/devicetree/bindings/dma/ |
| A D | atmel-xdma.txt | 15 - 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/Documentation/devicetree/bindings/i2c/ |
| A D | i2c-atr.yaml | 27 addresses must be available, not used by any other peripheral. Each 28 remote peripheral is assigned an alias from the pool, and transactions to 29 that address will be forwarded to the remote peripheral, with the address 30 translated to the remote peripheral's real address. This property is not
|
| /linux/Documentation/devicetree/bindings/net/can/ |
| A D | st,stm32-bxcan.yaml | 24 Primary mode of the bxCAN peripheral is only relevant if the chip has 27 Not to be used if the peripheral is in single CAN configuration. 34 Secondary mode of the bxCAN peripheral is only relevant if the chip 37 Not to be used if the peripheral is in single CAN configuration. 70 secondary) in dual CAN peripheral configuration.
|
| /linux/drivers/i2c/busses/ |
| A D | i2c-qcom-geni.c | 518 struct gpi_i2c_config *peripheral; in geni_i2c_gpi() local 545 peripheral->rx_len = msg->len; in geni_i2c_gpi() 546 peripheral->op = op; in geni_i2c_gpi() 554 peripheral->set_config = 0; in geni_i2c_gpi() 555 peripheral->multi_msg = true; in geni_i2c_gpi() 602 peripheral.clk_div = itr->clk_div; in geni_i2c_gpi_xfer() 603 peripheral.set_config = 1; in geni_i2c_gpi_xfer() 604 peripheral.multi_msg = false; in geni_i2c_gpi_xfer() 611 peripheral.stretch = 0; in geni_i2c_gpi_xfer() 613 peripheral.stretch = 1; in geni_i2c_gpi_xfer() [all …]
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A D | adi,max98363.yaml | 16 SoundWire peripheral device ID of MAX98363 is 0x3*019f836300 17 where * is the peripheral device unique ID decoded from pin. 18 It supports up to 10 peripheral devices(0x0 to 0x9).
|
| /linux/drivers/clk/qcom/ |
| A D | Kconfig | 65 Say Y if you want to use peripheral devices such as SD/UFS. 451 Say Y if you want to use multimedia devices or peripheral 467 Say Y if you want to use multimedia devices or peripheral 728 QRU1000 devices. Say Y if you want to use peripheral 793 Say Y if you want to use peripheral devices such as UART, 802 Say Y if you want to use peripheral devices such as UART, 810 Say Y if you want to use peripheral devices such as UART, 992 Say Y if you want to use peripheral devices such as UART, 1001 Say Y if you want to use peripheral devices such as UART, 1010 Say Y if you want to use peripheral devices such as UART, [all …]
|
| /linux/Documentation/firmware-guide/acpi/ |
| A D | extcon-intel-int3496.rst | 12 between an USB host and an USB peripheral controller. 23 the USB peripheral controller, write 1 to mux to the peripheral
|