Home
last modified time | relevance | path

Searched full:modelled (Results 1 – 25 of 67) sorted by relevance

123

/Linux-v5.10/Documentation/gpu/
Dtegra.rst75 on two outputs don't match. A display controller is modelled as a CRTC in KMS
94 content. In KMS, each window is modelled as a plane. Each display controller
105 Outputs are modelled as a composite encoder/connector pair.
/Linux-v5.10/sound/soc/
Dsoc-utils.c106 * which should be modelled. And the data flow graph also should be modelled
/Linux-v5.10/drivers/staging/fieldbus/anybuss/
DKconfig23 modelled as a regulator.
/Linux-v5.10/Documentation/userspace-api/media/mediactl/
Dmedia-controller-intro.rst14 be modelled as separate devices. A USB camera with a microphone will be
Dmedia-controller-model.rst10 hardware devices and Linux Kernel interfaces are modelled as graph
/Linux-v5.10/Documentation/devicetree/bindings/media/i2c/
Dmaxim,max9286.yaml57 The connections to the MAX9286 GMSL and its endpoint nodes are modelled
136 Each GMSL link is modelled as a child bus of an i2c bus
Dimi,rdacm2x-gmsl.yaml92 Connection to the remote GMSL endpoint are modelled using the OF graph
/Linux-v5.10/Documentation/devicetree/bindings/spmi/
Dspmi.yaml16 SPMI controllers are modelled in device tree using a generic set of
/Linux-v5.10/drivers/sh/intc/
Dvirq-debugfs.c6 * Modelled after arch/powerpc/kernel/irq.c.
/Linux-v5.10/include/uapi/linux/
Dpg.h8 driver is loosely modelled after the generic SCSI driver, sg,
/Linux-v5.10/Documentation/devicetree/bindings/display/
Darm,malidp.txt32 is modelled using the OF graph bindings specified in
/Linux-v5.10/Documentation/devicetree/bindings/usb/
Drenesas,usb3-peri.yaml58 any connector to the data bus of this controller should be modelled
/Linux-v5.10/Documentation/driver-api/media/drivers/
Dcpia2_devel.rst9 this one was modelled from.
/Linux-v5.10/Documentation/fb/
Dcirrusfb.rst57 modelled after that in atyfb and matroxfb.
/Linux-v5.10/Documentation/admin-guide/media/
Domap3isp.rst51 Each possible link in the ISP is modelled by a link in the Media controller
/Linux-v5.10/arch/arc/boot/dts/
Dvdk_axs10x_mb.dtsi85 /* PGU output directly sent to virtual LCD screen; hdmi controller not modelled */
/Linux-v5.10/Documentation/driver-api/thermal/
Dcpu-cooling-api.rst91 The detailed behaviour for f(run) could be modelled on-line. However,
/Linux-v5.10/drivers/clocksource/
Dtimer-ti-32k.c21 * Roughly modelled after the OMAP1 MPU timer code.
/Linux-v5.10/drivers/staging/media/atomisp/pci/hive_isp_css_include/device_access/
Ddevice_access.h47 * environment. Only if the host environment is modelled as on the target
/Linux-v5.10/arch/arm/mach-omap2/
Dtimer.c22 * Roughly modelled after the OMAP1 MPU timer code.
/Linux-v5.10/drivers/usb/serial/
Dbelkin_sa.h95 * It seems that the interrupt pipe is closely modelled after the
/Linux-v5.10/Documentation/devicetree/bindings/regulator/
Dqcom,smd-rpm-regulator.yaml10 The Qualcomm RPM over SMD regulator is modelled as a subdevice of the RPM.
/Linux-v5.10/include/linux/
Dnubus.h94 /* Generic NuBus interface functions, modelled after the PCI interface */
/Linux-v5.10/Documentation/devicetree/bindings/display/bridge/
Dadi,adv7511.txt86 The ADV7511 has two video ports. Their connections are modelled using the OF
Drenesas,lvds.yaml54 This device has two video ports. Their connections are modelled using the

123