Introduce per-plane and per-CRTC scaling filter properties to allow
userspace to select the driver's default scaling filter or
Nearest-neighbor(NN) filter for upscaling operations on CRTC and
plane.
Drivers can set up this property for a plane by calling
drm_plane_create_scaling_filter() and for a
This series is the continuation for the RFC that I posted earlier [1]
[1] RFC: https://patchwork.freedesktop.org/series/73884/
Integer scaling (IS) is a nearest-neighbor upscaling technique that
simply scales up the existing pixels by an integer (i.e., whole
number) multiplier. Nearest-neighbor (
Integer scaling (IS) is a nearest-neighbor upscaling technique that
simply scales up the existing pixels by an integer
(i.e., whole number) multiplier.Nearest-neighbor (NN) interpolation
works by filling in the missing color values in the upscaled image
with that of the coordinate-mapped nearest so
GEN >= 10 hardware supports the programmable scaler filter.
Attach scaling filter property for CRTC and plane for GEN >= 10
hardwares and program scaler filter based on the selected filter
type.
changes since v3:
* None
changes since v2:
* Use updated functions
* Add ps_ctrl var to contain the fu
When doing an atomic modeset with ALLOW_MODESET drivers are allowed to
pull in arbitrary other resources, including CRTCs (e.g. when
reconfiguring global resources).
But in nonblocking mode userspace has then no idea this happened,
which can lead to spurious EBUSY calls, both:
- when that other CR
The arm64 gcc-9 release warns about a change in the calling
conventions:
drivers/video/fbdev/mx3fb.c: In function 'sdc_init_panel':
drivers/video/fbdev/mx3fb.c:506:12: note: parameter passing for argument of
type 'struct ipu_di_signal_cfg' changed in GCC 9.1
506 | static int sdc_init_panel(stru
Hi,
On Fri, Mar 20, 2020 at 07:49:08PM +0100, Guido Günther wrote:
> This adds initial support for the NWL MIPI DSI Host controller found on i.MX8
> SoCs.
Is there anything in can do to get this into drm-misc?
Cheers,
-- Guido
>
> It adds support for the i.MX8MQ but the same IP core can also be
Hi Arnd,
Thank you for the patch.
On Wed, Apr 08, 2020 at 06:25:38PM +0200, Arnd Bergmann wrote:
> The arm64 gcc-9 release warns about a change in the calling
> conventions:
>
> drivers/video/fbdev/mx3fb.c: In function 'sdc_init_panel':
> drivers/video/fbdev/mx3fb.c:506:12: note: parameter passi
On Wed, 08 Apr 2020, Arnd Bergmann wrote:
> The arm64 gcc-9 release warns about a change in the calling
> conventions:
>
> drivers/video/fbdev/mx3fb.c: In function 'sdc_init_panel':
> drivers/video/fbdev/mx3fb.c:506:12: note: parameter passing for argument of
> type 'struct ipu_di_signal_cfg' cha
Hi Arnd.
On Wed, Apr 08, 2020 at 06:25:38PM +0200, Arnd Bergmann wrote:
> The arm64 gcc-9 release warns about a change in the calling
> conventions:
>
> drivers/video/fbdev/mx3fb.c: In function 'sdc_init_panel':
> drivers/video/fbdev/mx3fb.c:506:12: note: parameter passing for argument of
> type
Hi Guido.
We discussed this binding briefly on IRC:
19:28 port 0 is defined as
19:28 + Input port node to receive pixel data from the
19:28 + display controller. Exactly one endpoint must be
19:28 + specified.
19:28 then there's two endpoints,
On Fri, Mar 20, 202
From: Thierry Reding
Currently when a host1x device driver is unregistered, it is not
detached from the host1x controller, which means that the device
will stay around and when the driver is registered again, it may
bind to the old, stale device rather than the new one that was
created from scrat
Hi Guido.
On Fri, Mar 20, 2020 at 07:49:10PM +0100, Guido Günther wrote:
> This adds initial support for the NWL MIPI DSI Host controller found on
> i.MX8 SoCs.
>
> It adds support for the i.MX8MQ but the same IP can be found on
> e.g. the i.MX8QXP.
>
> It has been tested on the Librem 5 devkit
Hi Jani & Laurent.
On Wed, Apr 08, 2020 at 08:20:11PM +0300, Jani Nikula wrote:
> On Wed, 08 Apr 2020, Arnd Bergmann wrote:
> > The arm64 gcc-9 release warns about a change in the calling
> > conventions:
> >
> > drivers/video/fbdev/mx3fb.c: In function 'sdc_init_panel':
> > drivers/video/fbdev/m
From: Thierry Reding
In order to properly release the I2C adapter used for DDC/CI, use the
i2c_put_adapter() function provided by the I2C subsystem rather than the
put_device() function which doesn't include code to drop a reference to
the adapter's owner module.
Signed-off-by: Thierry Reding
-
Laurent Pinchart and
Jani Nikula both
suggested to make the pointer to struct ipu_di_signal_cfg const.
Fix this.
Signed-off-by: Sam Ravnborg
Fixes: 3f6c93ec9254 ("fbdev: mx3fb: avoid warning about psABI change")
Cc: Jani Nikula
Cc: Laurent Pinchart
Cc: Arnd Bergmann
Cc: Sam Ravnborg
Cc: En
Hi Thierry
On Wed, Apr 08, 2020 at 08:02:44PM +0200, Thierry Reding wrote:
> From: Thierry Reding
>
> In order to properly release the I2C adapter used for DDC/CI, use the
> i2c_put_adapter() function provided by the I2C subsystem rather than the
> put_device() function which doesn't include cod
Hi Daniel.
On Wed, Apr 08, 2020 at 02:11:47PM +0200, Daniel Vetter wrote:
> On Wed, Apr 08, 2020 at 08:57:14AM +0200, Sam Ravnborg wrote:
> > Hi Daniel.
> >
> > Finally managed to dive into this..
> >
> > Maybe I need more coffee, it is still morning here.
> > But alas this patch triggered a few
On configurations with 64-bit dma_addr_t but 32-bit resource_size_t,
there is now a warning:
drivers/gpu/drm/drm_bufs.c: In function 'drm_addmap_core':
drivers/gpu/drm/drm_bufs.c:328:8: error: passing argument 3 of
'dma_alloc_coherent' from incompatible pointer type
[-Werror=incompatible-pointer
Without CONFIG_DEBUG_FS, this newly added function causes a harmless
warning:
amdgpu_dm/amdgpu_dm.c: In function 'amdgpu_dm_connector_late_register':
amdgpu_dm/amdgpu_dm.c:4723:30: error: unused variable 'amdgpu_dm_connector'
[-Werror=unused-variable]
4723 | struct amdgpu_dm_connector *amdgpu_d
I ran into a randconfig link error with debugfs disabled:
arm-linux-gnueabi-ld:
drivers/gpu/drm/msm/msm_gpu.o: in function `should_dump':
msm_gpu.c:(.text+0x1cc): undefined reference to `rd_full'
Change the helper to only look at this variable if debugfs is present.
Fixes: e515af8d4a6f ("drm/ms
On Wed, Apr 8, 2020 at 3:13 PM Arnd Bergmann wrote:
>
> Without CONFIG_DEBUG_FS, this newly added function causes a harmless
> warning:
>
> amdgpu_dm/amdgpu_dm.c: In function 'amdgpu_dm_connector_late_register':
> amdgpu_dm/amdgpu_dm.c:4723:30: error: unused variable 'amdgpu_dm_connector'
> [-Wer
Signed-off-by: Sam Ravnborg
Cc: Lin Huang
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/innolux,p097pfg.txt | 24
.../display/panel/innolux,p097pfg.yaml| 56 +++
2 files changed, 56 insertions(+), 24 deletions(-)
delete mode 100644
Documen
The .txt binding explains:
"
The following optional properties only apply to
RGB and YUV input modes and
can be omitted for BT.656 input modes:
"
This constraint is not implmented in the DT Schema.
The original binding from the .txt file referenced
properties that is included in pane
osddisplays,osd101t2587-53ts is compatible with panel-simple-dsi binding,
so list the compatible in the panel-simple-dsi binding file.
v2:
- It is a DSI panel, move to -dsi binding (Tomi)
Signed-off-by: Sam Ravnborg
Reviewed-by: Tomi Valkeinen
Cc: Peter Ujfalusi
Cc: Thierry Reding
Cc: Sam R
v2:
- Fix entry in MAINTAINERS
Signed-off-by: Sam Ravnborg
Cc: Jerry Han
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../bindings/display/panel/boe,himax8279d.txt | 24
.../display/panel/boe,himax8279d.yaml | 59 +++
MAINTAINERS
v2:
- drop use of spi-slave.yaml (Maxime)
- added unevaluatedProperties (Maxime)
- added type to width/height properties (Rob)
Signed-off-by: Sam Ravnborg
Cc: Maxime Ripard
Cc: Rob Herring
Cc: Andrzej Hajda
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../bindings/display/panel/samsung,ld9
v2:
- drop address in dsi node in example (Rob)
Signed-off-by: Sam Ravnborg
Reviewed-by: Vinay Simha BN
Cc: Rob Herring
Cc: Vinay Simha BN
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/jdi,lt070me05000.txt| 31 -
.../display/panel/jdi,lt070me05000.yaml |
Several bindings specifies a "te-gpios" for tearing effect signal.
Add this to panel-common so we have a shared definition.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../devicetree/bindings/display/panel/panel-common.yaml| 7 +++
1 file changed, 7 insertions(+
v2:
- Fix entry in MAINTAINERS
Signed-off-by: Sam Ravnborg
Reviewed-by: Guido Günther
Cc: "Guido Günther"
Cc: Purism Kernel Team
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/rocktech,jh057n00900.txt| 23
.../display/panel/rocktech,jh057n00900.yaml | 57
The binding for this panel is a SPI slave.
v2:
- Drop use of spi-slave (Maxime)
- Introude unevaluatedProperties (Maxime)
- Drop reg entry in example (Rob)
Signed-off-by: Sam Ravnborg
Cc: Maxime Ripard
Cc: Rob Herring
Cc: Jonathan Bakker
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../di
v2:
- Fix entry in MAINTAINERS
- Add reg number to node name (Rob)
Signed-off-by: Sam Ravnborg
Cc: Rob Herring
Cc: Robert Chiras
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/raydium,rm67191.txt | 41 --
.../display/panel/raydium,rm67191.yaml| 75 +
Signed-off-by: Sam Ravnborg
Cc: Andrzej Hajda
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/samsung,s6e8aa0.txt | 56 ---
.../display/panel/samsung,s6e8aa0.yaml| 96 +++
2 files changed, 96 insertions(+), 56 deletions(-)
delete mode 100644
Add the lg panels that matches the panel-simple binding to
panel-simple.yaml
Signed-off-by: Sam Ravnborg
Reviewed-by: Brian Masney
Cc: Brian Masney
Cc: Alexandre Courbot
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../devicetree/bindings/display/panel/lg,acx467akm-7.txt | 7 ---
.../devic
Rob wrote:
Uhhh, it's looking for dsi-controller(@.*)? which is not the common
case found in dts files. We should fix that to dsi(@.*)?.
See: https://lore.kernel.org/dri-devel/2020031903.GK29911@bogus/
Fix it.
Signed-off-by: Sam Ravnborg
Cc: Linus Walleij
Cc: Rob Herring
---
Doc
v2:
- dropped use of spi-slave.yaml (Maxime)
- added unevaluatedProperties (Maxime)
Signed-off-by: Sam Ravnborg
Cc: Maxime Ripard
Cc: Marek Belisko
Cc: H. Nikolaus Schaller
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../bindings/display/panel/tpo,td.yaml| 65 +++
..
v2:
- Drop use of spi-slave.yaml (Maxime)
- Introduce unevaluatedProperties (Maxime)
Signed-off-by: Sam Ravnborg
Reviewed-by: Paul Cercueil
Cc: Maxime Ripard
Cc: Paul Cercueil
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../panel/kingdisplay,kd035g6-54nt.txt| 42
.../pa
kingdisplay,kd097d04 matches the panel-simple-dsi binding.
The only difference is that enable-gpios is now an optional
property.
Signed-off-by: Sam Ravnborg
Cc: Nickey Yang
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/kingdisplay,kd097d04.txt| 22 ---
.../disp
v2:
- Dropped spi-slave (Maxime)
- Added unevaluatedProperties (Maxime)
- Deleted needless compatible from example (Rob)
Signed-off-by: Sam Ravnborg
Reviewed-by: Heiko Schocher
Cc: Maxime Ripard
Cc: Rob Herring
Cc: Heiko Schocher
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../bindings/d
Both port and ports names may be used.
port - for a single port
ports - if there is more than one port in sub-nodes
Fixes the following warning:
advantech,idk-2121wr.example.dt.yaml: panel-lvds: 'port' is a required property
advantech,idk-2121wr.yaml needs several ports, so uses a ports node.
Si
Signed-off-by: Sam Ravnborg
Reviewed-by: Douglas Anderson
Cc: Douglas Anderson
Cc: Sandeep Panda
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/innolux,p120zdg-bf1.txt | 22 --
.../display/panel/innolux,p120zdg-bf1.yaml| 43 +++
2 files changed, 43
As the binding matches panel-simple, added the compatible to the
panel-simple list.
With this change enable-gpios is now optional.
Signed-off-by: Sam Ravnborg
Cc: Chris Zhong
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/innolux,p079zca.txt | 22 ---
.../bi
Updating this binding identified an issue in the example in
the allwinner,sun6i-a31-mipi-dsi binding.
Fix the example so no new warnings are introduced.
v2:
- fix example in allwinner,sun6i-a31-mipi-dsi (Rob)
Signed-off-by: Sam Ravnborg
Cc: Rob Herring
Cc: Maxime Ripard
Cc: Thierry Reding
C
Convert remaining(*) panel bindings to DT Schema.
To prepare for the migration a preparation
patch was required:
- te-gpios is now added to panel-common - as this
property is used by a few bindings.
The original author of the panel bindings are listed as maintainer
in the DT Schema. In the few
v2:
- Fix entry in MAINTAINERS
Signed-off-by: Sam Ravnborg
Cc: Linus Walleij
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/arm,versatile-tft-panel.txt | 31 ---
.../panel/arm,versatile-tft-panel.yaml| 51 +++
MAINTAINERS
Signed-off-by: Sam Ravnborg
Reviewed-by: Linus Walleij
Cc: Linus Walleij
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/samsung,s6d16d0.txt | 30 --
.../display/panel/samsung,s6d16d0.yaml| 56 +++
2 files changed, 56 insertions(+), 30 deletio
This binding describes a panel with a secondary channel.
v2:
- add check for required properties if link2 is present (Rob)
Signed-off-by: Sam Ravnborg
Cc: Rob Herring
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/sharp,lq101r1sx01.txt | 49 ---
.../display/panel/s
v2:
- drop use of spi-slave.yaml (Maxime)
- add unevaluatedProperties (Maxime)
- rename node in example to panel (Rob)
Signed-off-by: Sam Ravnborg
Reviewed-by: Tomi Valkeinen
Cc: Tomi Valkeinen
Cc: Rob Herring
Cc: Maxime Ripard
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../bindings/dis
Signed-off-by: Sam Ravnborg
Reviewed-by: Marco Franchi
Cc: Marco Franchi
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../bindings/display/panel/seiko,43wvf1g.txt | 23 -
.../bindings/display/panel/seiko,43wvf1g.yaml | 49 +++
2 files changed, 49 insertions(+), 23 deletion
v2:
- Add min/maxItems to mode-gpios (Rob)
- Fix bug in description, mode is up to three gpios (Rob)
Signed-off-by: Sam Ravnborg
Cc: Rob Herring
Cc: Tony Lindgren
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/sharp,ls037v7dw01.txt | 43
.../display/panel/sh
v2:
- use "ic2" node name in example (Rob)
Signed-off-by: Sam Ravnborg
Cc: Rob Herring
Cc: Stefan Mavrodiev
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/olimex,lcd-olinuxino.txt| 42 ---
.../display/panel/olimex,lcd-olinuxino.yaml | 70 +++
MAINTA
v2:
- dropped use of spi-slave.yaml (Maxime)
- added unevaluatedProperties (Maxime)
Signed-off-by: Sam Ravnborg
Cc: Maxime Ripard
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/sitronix,st7789v.txt| 37 ---
.../display/panel/sitronix,st7789v.yaml | 63
Signed-off-by: Sam Ravnborg
Cc: Peter Rosin
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/sharp,lq150x1lg11.txt | 36
.../display/panel/sharp,lq150x1lg11.yaml | 58 +++
2 files changed, 58 insertions(+), 36 deletions(-)
delete mode 100644
D
Signed-off-by: Sam Ravnborg
Cc: Marek Belisko
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/startek,startek-kd050c.txt | 4 ---
.../display/panel/startek,startek-kd050c.yaml | 33 +++
2 files changed, 33 insertions(+), 4 deletions(-)
delete mode 100644
Documenta
There are no more references to simple-panel.txt.
Delete it.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: Sam Ravnborg
---
Documentation/devicetree/bindings/display/panel/simple-panel.txt | 1 -
1 file changed, 1 deletion(-)
delete mode 100644
Documentation/devicetree/bindings/display/
v2:
- drop use of spi-slave.yaml (Maxime)
- added unevaluatedProperties (maxime)
Signed-off-by: Sam Ravnborg
Cc: Maxime Ripard
Cc: Tomi Valkeinen
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../display/panel/lgphilips,lb035q02.txt | 33 ---
.../display/panel/lgphilips,lb035q02.y
Tomi noticed that several DSI panels was wrongly
described in panel-simple.yaml.
Move them to panel-simple-dsi.yaml where they belong.
Signed-off-by: Sam Ravnborg
Cc: Tomi Valkeinen
---
.../bindings/display/panel/panel-simple-dsi.yaml | 8
.../devicetree/bindings/display/panel
For samsung there was two AMOLED panels with the same
description.
Collect them in one binding file.
Signed-off-by: Sam Ravnborg
Cc: Hoegeun Kwon
Cc: Thierry Reding
Cc: Sam Ravnborg
---
.../panel/samsung,amoled-mipi-dsi.yaml| 65 +++
.../display/panel/samsung,s6e3ha2.t
The txt binding specified the property "power-supply".
But the example and the actual implementation in the linux-kernel
uses "avdd-supply".
So the binding is adjusted to use avdd-supply as this seems
to be the correct choice.
There are no DT files in the linux kernel to check.
Signed-off-by: Sam
Hi Sam,
Thank you for the patch.
On Wed, Apr 08, 2020 at 08:29:26PM +0200, Sam Ravnborg wrote:
> Laurent Pinchart and
> Jani Nikula both
> suggested to make the pointer to struct ipu_di_signal_cfg const.
>
> Fix this.
>
> Signed-off-by: Sam Ravnborg
> Fixes: 3f6c93ec9254 ("fbdev: mx3fb: avoi
Hi David.
On Tue, Mar 24, 2020 at 05:45:25PM +0800, David Lu wrote:
> Add bindings documentation for BOE TV105WUM-NW0 10.5" WUXGA TFT LCD
> panel.
>
> Signed-off-by: David Lu
> Change-Id: I450c0e52aae080728d4794bdffc50bb0d2f39f40
I dropped the Change-Id while applying.
Applied to drm-misc-next
Hi David.
On Tue, Mar 24, 2020 at 03:57:34PM +0800, David Lu wrote:
> Add entries for BOE TV105WUM-NW0 10.5" WUXGA TFT LCD panel.
>
> Signed-off-by: David Lu
> Change-Id: I5b1cef259de5fb498220dcc47baa035083c41667
Deleted Change-Id, and updated subject as suggested by Nicholas.
Applied to drm-mis
The 'imply' statement does not prevent MLX5 to be built-in and fail
when VXLAN=m:
aarch64-linux-ld: drivers/net/ethernet/mellanox/mlx5/core/main.o: in function
`mlx5_init_once':
main.c:(.text+0x7cc): undefined reference to `mlx5_vxlan_create'
main.c:(.text+0x958): undefined reference to `mlx5_vxl
The 'imply' selection means the driver can still be a loadable
module even if the main driver is built-in, leading to a link
error:
aarch64-linux-ld: drivers/net/ethernet/cavium/thunder/nicvf_main.o: in function
`nicvf_remove':
nicvf_main.c:(.text+0x25c): undefined reference to `cavium_ptp_put'
a
The 'imply' keyword no longer does what it was originally
introduced for:
lio_ethtool.c:(.text+0xba8): undefined reference to `ptp_clock_index'
Use a dependency instead.
Fixes: cd7aeb1f9706 ("LiquidIO VF: s/select/imply/ for PTP_1588_CLOCK")
Signed-off-by: Arnd Bergmann
---
drivers/net/etherne
arm-linux-gnueabi-ld: drivers/gpu/drm/rcar-du/rcar_du_crtc.o: in function
`rcar_du_crtc_atomic_enable':
rcar_du_crtc.c:(.text+0xad4): undefined reference to `rcar_lvds_clk_enable'
arm-linux-gnueabi-ld: drivers/gpu/drm/rcar-du/rcar_du_crtc.o: in function
`rcar_du_crtc_atomic_disable':
rcar_du_crtc
Hi everyone,
I've just restarted doing randconfig builds on top of mainline Linux and
found a couple of regressions with missing dependency from the recent
change in the "imply" keyword in Kconfig, presumably these two patches:
3a9dd3ecb207 kconfig: make 'imply' obey the direct dependency
def2fbf
Using 'imply' does not work here, it still cause the same build
failure:
arm-linux-gnueabi-ld: drivers/gpu/drm/bridge/sil-sii8620.o: in function
`sii8620_remove':
sil-sii8620.c:(.text+0x1b8): undefined reference to `extcon_unregister_notifier'
arm-linux-gnueabi-ld: drivers/gpu/drm/bridge/sil-sii8
The 'imply' statement does not seem to have an effect, as it's
still possible to turn the CMM code into a loadable module
in a randconfig build, leading to a link error:
arm-linux-gnueabi-ld: drivers/gpu/drm/rcar-du/rcar_du_crtc.o: in function
`rcar_du_crtc_atomic_enable':
rcar_du_crtc.c:(.text+0
On Wed, Apr 08, 2020 at 05:45:55PM +0200, Mauro Carvalho Chehab wrote:
> Several references got broken due to txt to ReST conversion.
>
> Several of them can be automatically fixed with:
>
> scripts/documentation-file-ref-check --fix
>
> Reviewed-by: Mathieu Poirier #
> hwtracing/coresig
On Wed, Apr 8, 2020 at 10:38 PM Nicolas Pitre wrote:
> On Wed, 8 Apr 2020, Arnd Bergmann wrote:
> > I have created workarounds for the Kconfig files, which now stop using
> > imply and do something else in each case. I don't know whether there was
> > a bug in the kconfig changes that has led to a
drm_fbdev_generic_setup() was changed to be a void return, but the stub
was left returning 0.
./include/drm/drm_fb_helper.h: In function ‘drm_fbdev_generic_setup’:
./include/drm/drm_fb_helper.h:450:9: warning: ‘return’ with a value, in
function returning void [-Wreturn-type]
./include/drm/drm_fb_
On Wed, Apr 8, 2020 at 5:24 PM Chris Wilson wrote:
>
> drm_fbdev_generic_setup() was changed to be a void return, but the stub
> was left returning 0.
>
> ./include/drm/drm_fb_helper.h: In function ‘drm_fbdev_generic_setup’:
> ./include/drm/drm_fb_helper.h:450:9: warning: ‘return’ with a value, in
Hi Dave and Daniel,
Couple display fixes, including vswing table and display TypeC
port in TBT mode fix for ICL+
A few GT/GEM alloc/reloc fixes with one to flush all the
reloc_gpu batch which has cc:stable #5.2
Here goes drm-intel-next-fixes-2020-04-08:
- Flush all the reloc_gpu batch (Chris)
-
It was removed in:
Author: Christian König
Date: Wed Sep 25 11:38:50 2019 +0200
drm/ttm: remove pointers to globals
Signed-off-by: Maya Rashish
---
include/drm/ttm/ttm_bo_driver.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/drm/ttm/ttm_bo_driver.h b/include/drm/ttm/ttm_bo
Hi Dave, Daniel,
Fixes for 5.7.
The following changes since commit 3148a6a0ef3cf93570f30a477292768f7eb5d3c3:
drm/amdkfd: kfree the wrong pointer (2020-04-01 14:44:22 -0400)
are available in the Git repository at:
git://people.freedesktop.org/~agd5f/linux tags/amd-drm-fixes-5.7-2020-04-08
This can happen if userspace doesn't issue any 3D ioctls before
closing the DRM fd.
Fixes: 72b48ae800da ("drm/virtio: enqueue virtio_gpu_create_context
after the first 3D ioctl")
Signed-off-by: Gurchetan Singh
---
drivers/gpu/drm/virtio/virtgpu_kms.c | 17 ++---
1 file changed, 6 ins
Daniel noted[1] that commit d606dc9a6323 ("drm: kirin: Add
register connect helper functions in drm init") was unnecessary
and incorrect, as drm_dev_register does register connectors for
us.
Thus, this patch reverts the change as suggested by Daniel.
[1]:
https://lore.kernel.org/lkml/CAKMK7uHr5U
Hello,
This small patch series enables usage of the simple-bridge driver with
the DRM bridge connector helper (drm_bridge_connector.c). Patch 1/2
starts by simplifying the driver by delegating DDC handling to the next
bridge in the chain, and patch 2/2 makes the connector creation
optional.
I wil
Make the connector creation optional to enable usage of the
simple-bridge with the DRM bridge connector helper.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/bridge/simple-bridge.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/bridge/simple
Instead of poking into the DT node of the next bridge for its DDC bus
and implementing the .get_modes() and .detect() connector operations
manually, retrieve the next bridge in the chain and delegate these
operations to it.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/bridge/simple-bridge
Hello,
This patch series enables usage of the adv7511 driver with the DRM
bridge connector helper (drm_bridge_connector.c).
Patch 1/4 and 2/4 start by splitting EDID read and connector creation to
separate functions to ease review of 3/4 and 4/4. Patch 3/4 performs the
bulk of the work by impleme
Now that the driver supports all the connector-related bridge
operations, make the connector creation optional. This enables usage of
the adv7511 with the DRM bridge connector helper.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 13 +
1 file chan
To prepare for the implementation of the DRM bridge connector
operations, move EDID read out of adv7511_get_modes() to a separate
function.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 23 ++--
1 file changed, 16 insertions(+), 7 deletions(-)
Implement the bridge connector-related .get_edid(), .detect() and
.hpd_notify() operations, and report the related bridge capabilities.
Output status detection is implemented using the same backend as for the
DRM connector, but requires making mode retrieval at detection time
optional as no pointe
To prepare for making the connector creation optional, move the related
code out of adv7511_bridge_attach() to a separate function.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 62 +---
1 file changed, 40 insertions(+), 22 deletions(-)
diff
On Wed, Mar 25, 2020 at 1:17 AM Kalyan Thota wrote:
>
> This change adds support to configure dspp blocks in
> the dpu driver.
>
> Macro description of the changes coming in this patch.
> 1) Add dspp definitions in the hw catalog.
> 2) Add capability to reserve dspp blocks in the display data path
The delayed delete list is per device which might be very huge. And in
a heavy workload test, the list might always not be empty. That will
trigger any RCU stall warnings or softlockups in non-preemptible kernels
Lets do schedule out if possible in that case.
Signed-off-by: xinhui pan
---
driver
The init VExpress variants currently instantiates a 'muxfpga' driver for
the sole purpose of getting a regmap for it. There's no reason to
instantiate a driver and doing so just complicates things. The muxfpga
driver also isn't unregistered properly on module unload. Let's
just simplify all this th
Add a missing MODULE_DEVICE_TABLE entry to fix module autoloading.
Cc: Eric Anholt
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Rob Herring
---
drivers/gpu/drm/pl111/pl111_drv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/pl111/pl111_drv.c
b/drivers/gpu/drm/pl111/
Since the VExpress setup in pl111_vexpress.c is now just a single
function call, let's move it into pl111_versatile.c and we can further
simplify pl111_versatile_init() by moving the other pieces for VExpress
into pl111_vexpress_clcd_init().
Cc: Eric Anholt
Cc: dri-devel@lists.freedesktop.org
Sig
Thanks for the patch, Daniel!
On Tue, 7 Apr 2020 at 19:00, Daniel Vetter wrote:
>
> The uapi is the same on 32 and 64 bit, but the number isnt. Everyone
> who botched this please re-read:
>
> https://www.kernel.org/doc/html/v5.4-preprc-cpu/ioctl/botching-up-ioctls.html
>
> Also, the type argumen
Hello Randy,
On Wed, 8 Apr 2020 at 09:50, Randy Dunlap wrote:
>
> From: Randy Dunlap
>
> Fix documentation warnings in dma-buf.[hc]:
Thank you for your patch; I will apply it to drm-misc tree.
>
> ../drivers/dma-buf/dma-buf.c:678: warning: Function parameter or member
> 'importer_ops' not des
101 - 193 of 193 matches
Mail list logo
