Home
last modified time | relevance | path

Searched +full:simple +full:- +full:framebuffer (Results 1 – 25 of 157) sorted by relevance

1234567

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/
Dsimple-framebuffer.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Simple Framebuffer Device Tree Bindings
10 - Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
11 - Hans de Goede <hdegoede@redhat.com>
14 A simple frame-buffer describes a frame-buffer setup by firmware or
20 sub-nodes of the chosen node (*). Simplefb nodes must be named
21 framebuffer@<address>.
[all …]
/kernel/linux/linux-5.10/arch/x86/kernel/
Dsysfb.c1 // SPDX-License-Identifier: GPL-2.0-or-later
4 * Copyright (c) 2012-2013 David Herrmann <dh.herrmann@gmail.com>
8 * Simple-Framebuffer support for x86 systems
9 * Create a platform-device for any available boot framebuffer. The
10 * simple-framebuffer platform device is already available on DT systems, so
12 * platform device compatible with the "simple-framebuffer" DT object. If
13 * the framebuffer is incompatible, we instead create a legacy
14 * "vesa-framebuffer", "efi-framebuffer" or "platform-framebuffer" device and
16 * to pick these devices up without messing with simple-framebuffer drivers.
19 * If CONFIG_X86_SYSFB is not selected, we never register "simple-framebuffer"
[all …]
Dsysfb_simplefb.c1 // SPDX-License-Identifier: GPL-2.0-or-later
4 * Copyright (c) 2012-2013 David Herrmann <dh.herrmann@gmail.com>
8 * simple-framebuffer probing
9 * Try to convert "screen_info" into a "simple-framebuffer" compatible mode.
26 /* try parsing x86 screen_info into a simple-framebuffer mode struct */
34 type = si->orig_video_isVGA; in parse_mode()
40 if (si->lfb_depth == f->bits_per_pixel && in parse_mode()
41 si->red_size == f->red.length && in parse_mode()
42 si->red_pos == f->red.offset && in parse_mode()
43 si->green_size == f->green.length && in parse_mode()
[all …]
/kernel/linux/linux-4.19/arch/x86/kernel/
Dsysfb.c3 * Copyright (c) 2012-2013 David Herrmann <dh.herrmann@gmail.com>
12 * Simple-Framebuffer support for x86 systems
13 * Create a platform-device for any available boot framebuffer. The
14 * simple-framebuffer platform device is already available on DT systems, so
16 * platform device compatible with the "simple-framebuffer" DT object. If
17 * the framebuffer is incompatible, we instead create a legacy
18 * "vesa-framebuffer", "efi-framebuffer" or "platform-framebuffer" device and
20 * to pick these devices up without messing with simple-framebuffer drivers.
23 * If CONFIG_X86_SYSFB is not selected, we never register "simple-framebuffer"
24 * platform devices, but only use legacy framebuffer devices for
[all …]
Dsysfb_simplefb.c3 * Copyright (c) 2012-2013 David Herrmann <dh.herrmann@gmail.com>
12 * simple-framebuffer probing
13 * Try to convert "screen_info" into a "simple-framebuffer" compatible mode.
30 /* try parsing x86 screen_info into a simple-framebuffer mode struct */
38 type = si->orig_video_isVGA; in parse_mode()
44 if (si->lfb_depth == f->bits_per_pixel && in parse_mode()
45 si->red_size == f->red.length && in parse_mode()
46 si->red_pos == f->red.offset && in parse_mode()
47 si->green_size == f->green.length && in parse_mode()
48 si->green_pos == f->green.offset && in parse_mode()
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/
Dsimple-framebuffer.txt1 Simple Framebuffer
3 A simple frame-buffer describes a frame-buffer setup by firmware or
7 Since simplefb nodes represent runtime information they must be sub-nodes of
8 the chosen node (*). Simplefb nodes must be named "framebuffer@<address>".
24 then the chosen node's stdout-path property should point to it, or to the
28 It is advised that devicetree files contain pre-filled, disabled framebuffer
34 If pre-filled framebuffer nodes are used, the firmware may need extra
37 see e.g. simple-framebuffer-sunxi.txt .
40 - compatible: "simple-framebuffer"
41 - reg: Should contain the location and size of the framebuffer memory.
[all …]
Dsimple-framebuffer-sunxi.txt1 Sunxi specific Simple Framebuffer bindings
3 This binding documents sunxi specific extensions to the simple-framebuffer
4 bindings. The sunxi simplefb u-boot code relies on the devicetree containing
5 pre-populated simplefb nodes.
7 These extensions are intended so that u-boot can select the right node based
12 - compatible: "allwinner,simple-framebuffer"
13 - allwinner,pipeline, one of:
14 "de_be0-lcd0"
15 "de_be1-lcd1"
16 "de_be0-lcd0-hdmi"
[all …]
/kernel/linux/linux-5.10/include/linux/platform_data/
Dsimplefb.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * simplefb.h - Simple Framebuffer Device
30 * Data-Format for Simple-Framebuffers
31 * @name: unique 0-terminated name that can be used to identify the mode
34 * @fourcc: 32bit DRM four-CC code (see drm_fourcc.h)
47 * Simple-Framebuffer description
48 * If the arch-boot code creates simple-framebuffers without DT support, it
49 * can pass the width, height, stride and format via this platform-data object.
50 * The framebuffer location must be given as IORESOURCE_MEM resource.
/kernel/linux/linux-4.19/include/linux/platform_data/
Dsimplefb.h2 * simplefb.h - Simple Framebuffer Device
34 * Data-Format for Simple-Framebuffers
35 * @name: unique 0-terminated name that can be used to identify the mode
38 * @fourcc: 32bit DRM four-CC code (see drm_fourcc.h)
51 * Simple-Framebuffer description
52 * If the arch-boot code creates simple-framebuffers without DT support, it
53 * can pass the width, height, stride and format via this platform-data object.
54 * The framebuffer location must be given as IORESOURCE_MEM resource.
/kernel/linux/linux-4.19/drivers/gpu/drm/
Ddrm_gem_framebuffer_helper.c2 * drm gem framebuffer helper functions
12 #include <linux/dma-buf.h>
13 #include <linux/dma-fence.h>
39 * drm_gem_fb_get_obj() - Get GEM object backing the framebuffer
40 * @fb: Framebuffer
47 * Pointer to &drm_gem_object for the given framebuffer and plane index or NULL
56 return fb->obj[plane]; in drm_gem_fb_get_obj()
71 return ERR_PTR(-ENOMEM); in drm_gem_fb_alloc()
76 fb->obj[i] = obj[i]; in drm_gem_fb_alloc()
80 DRM_DEV_ERROR(dev->dev, "Failed to init framebuffer: %d\n", in drm_gem_fb_alloc()
[all …]
/kernel/linux/linux-5.10/drivers/video/fbdev/
Dsimplefb.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Simplest possible simple frame-buffer driver, as a platform device
8 * Copyright (C) 2001 Richard Zidlicky <rz@linux-m68k.org>
29 .id = "simple",
36 .height = -1,
37 .width = -1,
47 u32 *pal = info->pseudo_palette; in simplefb_setcolreg()
48 u32 cr = red >> (16 - info->var.red.length); in simplefb_setcolreg()
49 u32 cg = green >> (16 - info->var.green.length); in simplefb_setcolreg()
50 u32 cb = blue >> (16 - info->var.blue.length); in simplefb_setcolreg()
[all …]
/kernel/linux/linux-5.10/drivers/firmware/google/
Dframebuffer-coreboot.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * framebuffer-coreboot.c
5 * Memory based framebuffer accessed through coreboot table.
7 * Copyright 2012-2013 David Herrmann <dh.herrmann@gmail.com>
29 struct lb_framebuffer *fb = &dev->framebuffer; in framebuffer_probe()
33 .width = fb->x_resolution, in framebuffer_probe()
34 .height = fb->y_resolution, in framebuffer_probe()
35 .stride = fb->bytes_per_line, in framebuffer_probe()
40 if (fb->bits_per_pixel == formats[i].bits_per_pixel && in framebuffer_probe()
41 fb->red_mask_pos == formats[i].red.offset && in framebuffer_probe()
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/
Ddrm_gem_framebuffer_helper.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * drm gem framebuffer helper functions
8 #include <linux/dma-buf.h>
9 #include <linux/dma-fence.h>
10 #include <linux/dma-resv.h>
43 * drm_gem_fb_get_obj() - Get GEM object backing the framebuffer
44 * @fb: Framebuffer
51 * Pointer to &drm_gem_object for the given framebuffer and plane index or NULL
60 return fb->obj[plane]; in drm_gem_fb_get_obj()
76 fb->obj[i] = obj[i]; in drm_gem_fb_init()
[all …]
/kernel/linux/linux-4.19/drivers/video/fbdev/
Dsimplefb.c2 * Simplest possible simple frame-buffer driver, as a platform device
7 * Copyright (C) 2001 Richard Zidlicky <rz@linux-m68k.org>
37 .id = "simple",
44 .height = -1,
45 .width = -1,
55 u32 *pal = info->pseudo_palette; in simplefb_setcolreg()
56 u32 cr = red >> (16 - info->var.red.length); in simplefb_setcolreg()
57 u32 cg = green >> (16 - info->var.green.length); in simplefb_setcolreg()
58 u32 cb = blue >> (16 - info->var.blue.length); in simplefb_setcolreg()
62 return -EINVAL; in simplefb_setcolreg()
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/amlogic/
Dmeson-gx.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
12 #include <dt-bindings/gpio/gpio.h>
13 #include <dt-bindings/interrupt-controller/irq.h>
14 #include <dt-bindings/interrupt-controller/arm-gic.h>
15 #include <dt-bindings/power/meson-gxbb-power.h>
16 #include <dt-bindings/thermal/thermal.h>
19 interrupt-parent = <&gic>;
20 #address-cells = <2>;
21 #size-cells = <2>;
23 reserved-memory {
[all …]
/kernel/linux/linux-4.19/drivers/firmware/google/
Dframebuffer-coreboot.c2 * framebuffer-coreboot.c
4 * Memory based framebuffer accessed through coreboot table.
6 * Copyright 2012-2013 David Herrmann <dh.herrmann@gmail.com>
37 struct lb_framebuffer *fb = &dev->framebuffer; in framebuffer_probe()
41 .width = fb->x_resolution, in framebuffer_probe()
42 .height = fb->y_resolution, in framebuffer_probe()
43 .stride = fb->bytes_per_line, in framebuffer_probe()
48 if (fb->bits_per_pixel == formats[i].bits_per_pixel && in framebuffer_probe()
49 fb->red_mask_pos == formats[i].red.offset && in framebuffer_probe()
50 fb->red_mask_size == formats[i].red.length && in framebuffer_probe()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/
Dxilinx.txt10 Each IP-core has a set of parameters which the FPGA designer can use to
20 properties of the device node. In general, device nodes for IP-cores
23 (name): (generic-name)@(base-address) {
24 compatible = "xlnx,(ip-core-name)-(HW_VER)"
27 interrupt-parent = <&interrupt-controller-phandle>;
29 xlnx,(parameter1) = "(string-value)";
30 xlnx,(parameter2) = <(int-value)>;
33 (generic-name): an open firmware-style name that describes the
36 (ip-core-name): the name of the ip block (given after the BEGIN
38 and all underscores '_' converted to dashes '-'.
[all …]
/kernel/linux/linux-4.19/arch/arm/boot/dts/
Dsun4i-a10.dtsi5 * This file is dual-licensed: you can use it either under the terms
44 #include <dt-bindings/thermal/thermal.h>
45 #include <dt-bindings/dma/sun4i-a10.h>
46 #include <dt-bindings/clock/sun4i-a10-ccu.h>
47 #include <dt-bindings/reset/sun4i-a10-ccu.h>
50 #address-cells = <1>;
51 #size-cells = <1>;
52 interrupt-parent = <&intc>;
59 #address-cells = <1>;
60 #size-cells = <1>;
[all …]
Dsun5i-a10s.dtsi4 * Maxime Ripard <maxime.ripard@free-electrons.com>
6 * This file is dual-licensed: you can use it either under the terms
49 #include <dt-bindings/dma/sun4i-a10.h>
52 interrupt-parent = <&intc>;
59 #address-cells = <1>;
60 #size-cells = <1>;
63 framebuffer@2 {
64 compatible = "allwinner,simple-framebuffer",
65 "simple-framebuffer";
66 allwinner,pipeline = "de_be0-lcd0-hdmi";
[all …]
/kernel/linux/linux-4.19/Documentation/fb/
Dudlfb.txt7 DisplayLink chips provide simple hline/blit operations with some compression,
8 pairing that with a hardware framebuffer (16MB) on the other end of the
9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
13 result with a local shadow of the remote hardware framebuffer to identify
15 pixels line-by-line via USB bulk transfers.
18 does not require any acks - the effect is very low latency that
20 non-gaming and non-video applications.
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
32 Advantages of supporting DisplayLink chips with kernel framebuffer interface:
35 one-to-one with the fbdev interface, making the driver quite small and
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dsun5i-a10s.dtsi4 * Maxime Ripard <maxime.ripard@free-electrons.com>
6 * This file is dual-licensed: you can use it either under the terms
47 #include <dt-bindings/dma/sun4i-a10.h>
55 #address-cells = <1>;
56 #size-cells = <1>;
59 framebuffer-lcd0-hdmi {
60 compatible = "allwinner,simple-framebuffer",
61 "simple-framebuffer";
62 allwinner,pipeline = "de_be0-lcd0-hdmi";
70 display-engine {
[all …]
Dsun4i-a10.dtsi5 * This file is dual-licensed: you can use it either under the terms
44 #include <dt-bindings/thermal/thermal.h>
45 #include <dt-bindings/dma/sun4i-a10.h>
46 #include <dt-bindings/clock/sun4i-a10-ccu.h>
47 #include <dt-bindings/reset/sun4i-a10-ccu.h>
50 #address-cells = <1>;
51 #size-cells = <1>;
52 interrupt-parent = <&intc>;
59 #address-cells = <1>;
60 #size-cells = <1>;
[all …]
/kernel/linux/linux-4.19/arch/arm64/boot/dts/allwinner/
Dsun50i-a64.dtsi6 * This file is dual-licensed: you can use it either under the terms
45 #include <dt-bindings/clock/sun50i-a64-ccu.h>
46 #include <dt-bindings/clock/sun8i-de2.h>
47 #include <dt-bindings/clock/sun8i-r-ccu.h>
48 #include <dt-bindings/interrupt-controller/arm-gic.h>
49 #include <dt-bindings/reset/sun50i-a64-ccu.h>
50 #include <dt-bindings/reset/sun8i-de2.h>
51 #include <dt-bindings/reset/sun8i-r-ccu.h>
54 interrupt-parent = <&gic>;
55 #address-cells = <1>;
[all …]
/kernel/linux/linux-5.10/Documentation/fb/
Dudlfb.rst7 DisplayLink chips provide simple hline/blit operations with some compression,
8 pairing that with a hardware framebuffer (16MB) on the other end of the
9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
13 result with a local shadow of the remote hardware framebuffer to identify
15 pixels line-by-line via USB bulk transfers.
18 does not require any acks - the effect is very low latency that
20 non-gaming and non-video applications.
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
32 Advantages of supporting DisplayLink chips with kernel framebuffer interface:
35 one-to-one with the fbdev interface, making the driver quite small and
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/
Dxilinx.txt10 Each IP-core has a set of parameters which the FPGA designer can use to
20 properties of the device node. In general, device nodes for IP-cores
23 (name): (generic-name)@(base-address) {
24 compatible = "xlnx,(ip-core-name)-(HW_VER)"
27 interrupt-parent = <&interrupt-controller-phandle>;
29 xlnx,(parameter1) = "(string-value)";
30 xlnx,(parameter2) = <(int-value)>;
33 (generic-name): an open firmware-style name that describes the
36 (ip-core-name): the name of the ip block (given after the BEGIN
38 and all underscores '_' converted to dashes '-'.
[all …]

1234567