Home
last modified time | relevance | path

Searched refs:VSP (Results 1 – 17 of 17) sorted by relevance

/linux/drivers/video/fbdev/kyro/
H A DSTG4000VTG.c159 if ((pTiming->HSP > 0) && (pTiming->VSP < 0)) { /* +hsync -vsync */ in SetupVTG()
161 } else if ((pTiming->HSP < 0) && (pTiming->VSP > 0)) { /* -hsync +vsync */ in SetupVTG()
163 } else if ((pTiming->HSP < 0) && (pTiming->VSP < 0)) { /* -hsync -vsync */ in SetupVTG()
165 } else if ((pTiming->HSP > 0) && (pTiming->VSP > 0)) { /* +hsync -vsync */ in SetupVTG()
H A Dfbdev.c315 par->HSP, par->VSP, &par->PIXCLK) < 0) in kyro_dev_video_mode_set()
472 if (par->VSP == 1) in kyrofb_check_var()
526 par->VSP = (info->var.sync & FB_SYNC_VERT_HIGH_ACT) ? 1 : 0; in kyrofb_set_par()
/linux/Documentation/devicetree/bindings/media/
H A Drenesas,fcp.yaml18 There are three types of FCP: FCP for Codec (FCPC), FCP for VSP (FCPV) and
26 - renesas,fcpv # FCP for VSP
32 - const: renesas,fcpv # Generic FCP for VSP fallback
88 # R8A7795 (R-Car H3) FCP for VSP-D1
H A Drenesas,vsp1.yaml7 title: Renesas VSP Video Processing Engine
13 The VSP is a video processing engine that supports up-/down-scaling, alpha
47 A phandle referencing the FCP that handles memory accesses for the VSP.
/linux/drivers/gpu/drm/renesas/rcar-du/
H A DKconfig72 bool "R-Car DU VSP Compositor Support" if ARM
77 Enable support to expose the R-Car VSP Compositor as KMS planes.
/linux/Documentation/devicetree/bindings/display/
H A Drenesas,rzg2l-du.yaml72 - description: phandle to VSP instance that serves the DU channel
73 - description: Channel index identifying the LIF instance in that VSP
H A Drenesas,du.yaml90 - description: phandle to VSP instance that serves the DU channel
91 - description: Channel index identifying the LIF instance in that VSP
/linux/include/video/
H A Dkyro.h28 s32 VSP; /* Ver Sync Polarity */ member
/linux/Documentation/virt/hyperv/
H A Dvmbus.rst44 Hyper-V uses the terms "VSP" and "VSC" in describing synthetic
45 devices. "VSP" refers to the Hyper-V code that implements a
55 between the VSP and the VSC. Channels are bi-directional and used
110 unique to each VSP/VSC pair.
125 Messages passed between the VSP and VSC are control messages. For
279 the corresponding VSP. It allocates guest memory for the channel
284 Once the ring buffer is set up, the device driver and VSP exchange
287 VSC and the VSP on the Hyper-V host. The setup messages may also
H A Dvpci.rst62 VMBus connection to the vPCI VSP on the Hyper-V host. That
64 exchange messages with the vPCI VSP for the purpose of setting
/linux/drivers/media/platform/renesas/
H A DKconfig73 the codec, VSP and FDP modules.
/linux/arch/arm64/boot/dts/qcom/
H A Dsm7225-fairphone-fp4.dts71 /* Dummy regulator until PM6150L has LCDB VSP/VSN support */
/linux/drivers/gpu/drm/radeon/
H A Dnid.h881 #define VSP(x) ((x) << 0) macro
H A Dni_dpm.c3357 reg |= (VSP(ni_pi->cac_weights->vsp) | in ni_initialize_hardware_cac_manager()
/linux/drivers/iommu/
H A DKconfig505 and a few signal processors, including VSP(video), GSP(graphic),
/linux/drivers/pinctrl/renesas/
H A Dpfc-r8a7779.c1144 PINMUX_IPSR_GPSR(IP7_14_13, VSP),
H A Dpfc-r8a7790.c1433 PINMUX_IPSR_GPSR(IP11_17_15, VSP),