https://bugs.freedesktop.org/show_bug.cgi?id=104611
Alex Deucher changed:
What|Removed |Added
Component|DRM/Radeon |DRM/AMDgpu
--
You are receiving this ma
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #17 from Bong Cosca ---
Disabling hardware acceleration isn't exactly the workaround I was looking for.
I use modesetting with "AccelMethod" "none" just to make this work and I am
forced to use Win10 to do 3D animation stuff which is
Hi Jernej,
Thank you for th epatch.
On Wednesday, 10 January 2018 21:25:04 EET Jernej Skrabec wrote:
> Parts of PHY code could be useful also for custom PHYs. For example,
> Allwinner A83T has custom PHY which is probably Synopsys gen2 PHY
> with few additional memory mapped registers, so most of
From: Sergei Shtylyov
According to the latest revision 2.00 of the R-Car gen2 manual, the LVDS
must be enabled and the bias crcuit enabled after the LVDS I/O pins are
enabled, not before. Fix the gen2 LVDS startup sequence accordingly.
While at it, also fix the comment preceding the first LVDCR0
The internal LVDS encoder now has DT bindings separate from the DU. Port
the device tree over to the new model.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Remove the DU reg-names property
---
.../boot/dts/renesas/r8a7795-es1-salvator-x.dts| 3 +-
arch/arm64/boot/dts/renesas/r8
The internal LVDS encoder now has DT bindings separate from the DU. Port
the device tree over to the new model.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Remove the DU reg-names property
---
arch/arm/boot/dts/r8a7793-gose.dts | 10 +++---
arch/arm/boot/dts/r8a7793.dtsi | 3
The DU DT bindings have been updated to drop the reg-names property.
Update the r8a7792 device tree accordingly.
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7792.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/boot/dts/r8a7792.dtsi b/arch/arm/boot/dts/r8a7792.dtsi
i
Hello,
This patch series addresses a design mistake that dates back from the initial
DU support. Support for the LVDS encoders, which are IP cores separate from
the DU, was bundled in the DU driver. Worse, both the DU and LVDS were
described through a single DT node.
To fix the, patches 01/12 and
The LVDS encoders used to be described in DT as part of the DU. They now
have their own DT node, linked to the DU using the OF graph bindings.
This allows moving internal LVDS encoder support to a separate driver
modelled as a DRM bridge. Backward compatibility is retained as legacy
DT is patched l
The DU DT bindings have been updated to drop the reg-names property.
Update the r8a7792 device tree accordingly.
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7794.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/boot/dts/r8a7794.dtsi b/arch/arm/boot/dts/r8a7794.dtsi
i
The internal LVDS encoder now has DT bindings separate from the DU. Port
the device tree over to the new model.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Remove the DU reg-names property
---
arch/arm/boot/dts/r8a7790-lager.dts | 22 ++
arch/arm/boot/dts/r8a7790.dtsi
The internal LVDS encoder now has DT bindings separate from the DU. Port
the device tree over to the new model.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Remove the DU reg-names property
---
arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts | 3 +-
arch/arm64/boot/dts/renesas/r8
The internal LVDS encoders now have their own DT bindings, representing
them as part of the DU is deprecated.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Remove the LVDS reg range from the example
- Remove the reg-names property
---
.../devicetree/bindings/display/renesas,du.txt
The HDMI encoder is connected to the RGB output of the DU, which is
port@0, not port@1. Fix the incorrect DT description.
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7791-porter.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/r8a7791-porter.
The internal LVDS encoder now has DT bindings separate from the DU. Port
the device tree over to the new model.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Remove the DU reg-names property
---
arch/arm/boot/dts/r8a7791-koelsch.dts | 10 --
arch/arm/boot/dts/r8a7791-porter.dt
The internal LVDS encoders now have their own DT bindings. Before
switching the driver infrastructure to those new bindings, implement
backward-compatibility through live DT patching.
Patching is disabled and will be enabled along with support for the new
DT bindings in the DU driver.
Signed-off-
The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add
corresponding device tree bindings.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Move the SoC name before the IP name in compatible strings
- Rename parallel input to parallel RGB input
- Fixed "renesas,r8a7743-lvds
Instead of drivers duplicating the drm_atomic_helper_check() code to be
able to normalize the zpos they can use the normalize_zpos flag to let the
drm core to do it.
Signed-off-by: Peter Ujfalusi
---
drivers/gpu/drm/drm_atomic_helper.c | 6 ++
include/drm/drm_device.h| 8
Planes with identical zpos value will result undefined behavior:
disappearing planes, screen flickering and it is not supported by the
hardware.
Use normalized zpos to make sure that we don't encounter invalid
configuration.
Signed-off-by: Peter Ujfalusi
CC: Tomi Valkeinen
---
drivers/gpu/drm/
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_device->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Thierry Reding
---
drivers/gpu/drm/tegra/drm.c | 27 +++
1 file changed, 3 inserti
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_device->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Inki Dae
CC: Joonyoung Shim
CC: Seung-Woo Kim
CC: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_drm_d
The dt binding for Xilinx display pipeline. The pipeline can be
composed with multiple and different types of sub-devices. This node
is to represent the entire pipeline as a single entity.
Signed-off-by: Hyun Kwon
---
v2
- Remove linux specific terms
- Elaborate details, ex regarding port binding
Add drm properties for global alpha, output color, background color,
and test pattern generation.
Signed-off-by: Hyun Kwon
---
v2
- Split from the original patch
- Some props are important feature to be included
---
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 193 +++
This add a dt binding for ZynqMP DP subsystem.
Signed-off-by: Hyun Kwon
---
v2
- Group multiple ports under 'ports'
- Replace linux specific terms with generic hardware descriptions
---
---
.../bindings/display/xlnx/xlnx,zynqmp-dpsub.txt| 98 ++
1 file changed, 98 inserti
Xilinx has various platforms for display, where users can create
using multiple IPs in the programmable FPGA fabric, or where
some hardened piepline is available on the chip. Furthermore,
hardened pipeline can also interact with soft logics in FPGA.
The Xilinx DRM KMS is to integrate multiple subd
Add drm properties for DisplayPort synchronous mode and bpc
configurations.
Signed-off-by: Hyun Kwon
---
v2
- Split from the original patch
---
---
drivers/gpu/drm/xlnx/zynqmp_dp.c | 116 ++-
1 file changed, 114 insertions(+), 2 deletions(-)
diff --git a/driv
Xilinx ZynqMP has a hardened display pipeline. The pipeline can
be logically partitioned into 2 parts: display controller and
DisplayPort encoder / transmitter. This driver handles the display
controller part of the pipeline that handles buffer management and
blending.
Signed-off-by: Hyun Kwon
--
This is a wrapper around the ZynqMP Display and DisplayPort drivers.
Signed-off-by: Hyun Kwon
---
- Change the SPDX identifier format
---
---
drivers/gpu/drm/xlnx/Kconfig| 11 +++
drivers/gpu/drm/xlnx/Makefile | 3 +
drivers/gpu/drm/xlnx/zynqmp_dpsub.c | 149
This driver creates DRM encoder and connector for ZynqMP DisplayPort.
Signed-off-by: Hyun Kwon
---
v2
- Change the SPDX identifier format
- Split drm properties into a separate patch
---
---
drivers/gpu/drm/xlnx/zynqmp_dp.c | 1738 ++
drivers/gpu/drm/xlnx/zynq
https://bugs.freedesktop.org/show_bug.cgi?id=104599
--- Comment #3 from Mario Kleiner ---
This is running the new GNOME based Ubuntu GUI with Gnome-Shell Wayland, right?
With "Windows control did not work" you mean it doesn't respond to
mouse-clicks?
In that case it is known bugs/limitations in
https://bugs.freedesktop.org/show_bug.cgi?id=103917
--- Comment #2 from Vedran Miletić ---
Last week I rechecked, but all I got on master was non-working mouse clicks
(weird, I know) under Wayland and crashes under Xorg. I'll recheck again.
--
You are receiving this mail because:
You are the as
https://bugzilla.kernel.org/show_bug.cgi?id=198123
--- Comment #14 from Bill Fraser (bill.fra...@gmail.com) ---
(In reply to Daniel Vetter from comment #13)
> Created attachment 273575 [details]
> test patch on top of b8e2b0199cc377617dc238f5106352c06dcd3fa2, v2
That patch fixes it for me!
--
Y
https://bugs.freedesktop.org/show_bug.cgi?id=104599
--- Comment #1 from zebulon ---
Created attachment 136679
--> https://bugs.freedesktop.org/attachment.cgi?id=136679&action=edit
uncorrupted desktop
To give you a better idea of the corruption, here is a screenshot of the
desktop in normal cir
On 01/12/2018 05:11 AM, Dave Airlie wrote:
this work is based on the virtio_wl driver in the ChromeOS kernel by
Zach Reizner, currently at:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-4.4/drivers/virtio/virtio_wl.c
There's two features missing in this patch when
The V3D engine has various hardware counters which might be interesting
to userspace performance analysis tools.
Expose new ioctls to create/destroy a performance monitor object and
query the counter values of this perfmance monitor.
Note that a perfomance monitor is given an ID that is only vali
Hi Laurent,
On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart
wrote:
> This patch series addresses a design mistake that dates back from the initial
> DU support. Support for the LVDS encoders, which are IP cores separate from
> the DU, was bundled in the DU driver. Worse, both the DU and LVDS we
Am 11.01.2018 um 17:53 schrieb Lucas Stach:
This adds lockdep asserts to the reservation functions which state in their
documentation that obj->lock must be held. Allows builds with PROVE_LOCKING
enabled to check that the locking requirements are met.
Signed-off-by: Lucas Stach
Reviewed-by: C
Both patches
Tested-by: Andrey Grodzovsky
Acked-by: Andrey Grodzovsky
Andrey
On 01/12/2018 01:14 AM, Roger He wrote:
if ttm_get_pages or ttm_mem_global_alloc_page fail, should not update
global memory count.
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_page_alloc.c | 6 --
https://bugs.freedesktop.org/show_bug.cgi?id=104597
Bug ID: 104597
Summary: Compton weird colors
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
[Fair warning: This is pure conjecture right now.]
In
commit b8e2b0199cc377617dc238f5106352c06dcd3fa2
Author: Peter Rosin
Date: Tue Jul 4 12:36:57 2017 +0200
drm/fb-helper: factor out pseudo-palette
Peter extracted the pseudo palette computation, but seems to have done
an off-by-one. I s
After some discussion and failed patch sets trying to convey
the right timing information between the display engine and
a bridge using the connector, I try instead to use an optional
timing information container in the bridge itself, so that
display engines can retrieve it from any bridge and use
On Fri, Jan 12, 2018 at 11:38:03AM +0200, Peter Ujfalusi wrote:
> Hi,
>
> The first patch is adding a flag to drm_device that drivers can set if they
> want
> the zpos to be normalized.
If we go with the flag it should imo be put into struct drm_mode_config.
> Then convert exynos, tegra, sti an
Quoting Thierry Reding (2018-01-11 22:22:46)
> From: Thierry Reding
>
> This set of patches adds support for fences to Tegra DRM and complements
> the fence FD support for Nouveau. Technically this isn't necessary for a
> fence-based synchronization loop with Nouveau because the KMS core takes
>
On 01/12/2018 01:18 PM, Linus Walleij wrote:
This extends the dumb VGA DAC bridge to handle the THS8134A
and THS8134B VGA DACs in addition to those already handled.
We assign the proper timing data to the pointer inside the
bridge struct so display controllers that need to align their
timings
On 01/12/2018 01:18 PM, Linus Walleij wrote:
After some discussion and failed patch sets trying to convey
the right timing information between the display engine and
a bridge using the connector, I try instead to use an optional
timing information container in the bridge itself, so that
display
On 01/12/2018 01:18 PM, Linus Walleij wrote:
This adds device tree bindings for the Texas Instruments
THS8134, THS8134A and THS8134B VGA DACs by extending and
renaming the existing bindings for THS8135.
These DACs are used for the VGA outputs on the ARM reference
designs such as Integrator, Ve
https://bugs.freedesktop.org/show_bug.cgi?id=104599
--- Comment #2 from Tapani Pälli ---
possible duplicate for bug #104536 .. the symptoms look a lot worse though
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
On 01/12/2018 01:18 PM, Linus Walleij wrote:
If the bridge has a too strict setup time for the incoming
signals, we may not be fast enough and then we need to
compensate by outputting the signal on the inverse clock
edge so it is for sure stable when the bridge samples it.
Since bridges in dif
https://bugs.freedesktop.org/show_bug.cgi?id=101900
--- Comment #21 from Direx ---
Alex, thanks a lot for taking a look at this. I also think that everything is
already in place and just a tiny piece is missing or going wrong (with a big
impact though). I'd like to help you sort that out.
(In re
https://bugs.freedesktop.org/show_bug.cgi?id=104598
--- Comment #1 from Christoph Haag ---
Created attachment 136677
--> https://bugs.freedesktop.org/attachment.cgi?id=136677&action=edit
xorg log with the pageflip failures
RX 480, radv master and amdvlk, xf86-video-amdgpu master
This happens
This extends the dumb VGA DAC bridge to handle the THS8134A
and THS8134B VGA DACs in addition to those already handled.
We assign the proper timing data to the pointer inside the
bridge struct so display controllers that need to align their
timings to the bridge can pick it up and work from there.
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_device->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Benjamin Gaignard
CC: Vincent Abriou
---
drivers/gpu/drm/sti/sti_drv.c | 23 ++-
1 fi
Change reservation_object_get_fences_rcu to make the exclusive fence
pointer optional.
If not specified the exclusive fence is put into the fence array as
well.
This is helpful for a couple of cases where we need all fences in a
single array.
Signed-off-by: Christian König
---
drivers/dma-buf/
Am 11.01.2018 um 21:17 schrieb Thierry Reding:
From: Thierry Reding
struct device is forward-declared twice. Remove the second instance.
Signed-off-by: Thierry Reding
Reviewed-by: Christian König
---
include/drm/drm_prime.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/
Hi Geert,
On Friday, 12 January 2018 11:49:28 EET Geert Uytterhoeven wrote:
> On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart wrote:
> > The internal LVDS encoders now have their own DT bindings, representing
> > them as part of the DU is deprecated.
> >
> > Signed-off-by: Laurent Pinchart
> >
Hi Vladimir,
On Friday, 12 January 2018 11:54:57 EET Vladimir Zapolskiy wrote:
> On 01/12/2018 02:58 AM, Laurent Pinchart wrote:
> > The internal LVDS encoders now have their own DT bindings, representing
> > them as part of the DU is deprecated.
> >
> > Signed-off-by: Laurent Pinchart
> >
> > -
This adds device tree bindings for the Texas Instruments
THS8134, THS8134A and THS8134B VGA DACs by extending and
renaming the existing bindings for THS8135.
These DACs are used for the VGA outputs on the ARM reference
designs such as Integrator, Versatile and RealView.
Cc: devicet...@vger.kernel
https://bugs.freedesktop.org/show_bug.cgi?id=104596
Christoph Haag changed:
What|Removed |Added
Summary|GPU hang with janusvr |[apitrace] GPU hang with
Hi Laurent,
On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart
wrote:
> The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add
> corresponding device tree bindings.
>
> Signed-off-by: Laurent Pinchart
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/bridge/renesas
On Thu, Jan 11, 2018 at 10:44:17PM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> Export some more of the helpers in order to allow drivers to more fine-
> grainedly select which helpers to use. This gives drivers an easy way to
> reuse a lot of the code in the helpers while at the same
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_device->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Inki Dae
CC: Joonyoung Shim
CC: Seung-Woo Kim
CC: Kyungmin Park
Acked-by: Daniel Vetter
---
drivers/gp
Planes with identical zpos value will result undefined behavior:
disappearing planes, screen flickering and it is not supported by the
hardware.
Use normalized zpos to make sure that we don't encounter invalid
configuration.
Signed-off-by: Peter Ujfalusi
CC: Tomi Valkeinen
Acked-by: Daniel Vett
Hi Biju,
On Friday, 12 January 2018 14:59:53 EET Biju Das wrote:
> Hi,
>
> > Subject: [PATCH 01/10] dt-bindings: display: renesas: Add R-Car LVDS
> > encoder DT bindings
> >
> > The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add
> > corresponding device tree bindings.
> >
> >
Hi,
Changes since v1:
- normalize_zpos flag moved to drm_mode_config
- Added comment to note the side effect of normalization and updated the comment
for normalized_zpos in the header file as well.
- Added Acked-by from Daniel to patch 2-6 but not for patch 1 as I'm not sure if
the comments I
https://bugzilla.kernel.org/show_bug.cgi?id=198123
--- Comment #11 from Bill Fraser (bill.fra...@gmail.com) ---
- The red color looks to be the right shade, but it's hard to say without any
other colors to reference it against.
- With that patch, loading the 'ast' driver results in screen corrupt
https://bugs.freedesktop.org/show_bug.cgi?id=104599
Bug ID: 104599
Summary: corrupted desktop graphics with latest git intel
driver
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Instead of drivers duplicating the drm_atomic_helper_check() code to be
able to normalize the zpos they can use the normalize_zpos flag to let the
drm core to do it.
Signed-off-by: Peter Ujfalusi
---
drivers/gpu/drm/drm_atomic_helper.c | 11 +++
include/drm/drm_mode_config.h | 8 +
Hi Geert,
On Friday, 12 January 2018 11:45:56 EET Geert Uytterhoeven wrote:
> On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart wrote:
> > The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add
> > corresponding device tree bindings.
> >
> > Signed-off-by: Laurent Pinchart
> >
> >
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_device->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Thierry Reding
Acked-by: Daniel Vetter
---
drivers/gpu/drm/tegra/drm.c | 27 +++
If the bridge has a too strict setup time for the incoming
signals, we may not be fast enough and then we need to
compensate by outputting the signal on the inverse clock
edge so it is for sure stable when the bridge samples it.
Since bridges in difference to panels does not expose their
connector
On Thu, 11 Jan 2018 16:35:08 -0800
Eric Anholt wrote:
> Could we add some docs for get_values? Like:
Sure.
>
> /*
> * Returns the values of the performance counters tracked by this
> * perfmon (as an array of ncounters u64 values).
> *
> * No implicit synchronization is performed, so the
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_device->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Benjamin Gaignard
CC: Vincent Abriou
Acked-by: Daniel Vetter
---
drivers/gpu/drm/sti/sti_drv.c | 24 +++-
Set the drm_device->normalize_zpos and call drm_atomic_helper_check() from
rcar_du_atomic_check() instead of re implementing the function locally.
Signed-off-by: Peter Ujfalusi
CC: Laurent Pinchart
Acked-by: Daniel Vetter
---
drivers/gpu/drm/rcar-du/rcar_du_kms.c | 11 ++-
1 file chang
https://bugs.freedesktop.org/show_bug.cgi?id=104596
Bug ID: 104596
Summary: GPU hang with janusvr (non-VR mode too)
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Hi Laurent,
On 01/12/2018 02:58 AM, Laurent Pinchart wrote:
> The internal LVDS encoders now have their own DT bindings, representing
> them as part of the DU is deprecated.
>
> Signed-off-by: Laurent Pinchart
> ---
> .../devicetree/bindings/display/renesas,du.txt | 26
> +-
On 11.01.2018 14:51, Philippe CORNU wrote:
> Hi Brian & All *DSI DRM experts*,
>
> 1) Re-reading this patch, I realize that the returned value of
> dw_mipi_dsi_host_transfer() is not correct: we should return the number
> of transfered/received bytes...
>
> so I think there are two solutions: fix
Am 12.01.2018 um 07:14 schrieb Roger He:
if ttm_get_pages or ttm_mem_global_alloc_page fail, should not update
global memory count.
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_page_alloc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/t
Hi Geert,
On Friday, 12 January 2018 12:13:18 EET Geert Uytterhoeven wrote:
> On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart wrote:
> > The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add
> > corresponding device tree bindings.
> >
> > Signed-off-by: Laurent Pinchart
> >
> >
From: Fengguang Wu
drivers/gpu/drm/i915/i915_pmu.c:795:34-40: ERROR: application of sizeof to
pointer
sizeof when applied to a pointer typed expression gives the size of
the pointer
Generated by: scripts/coccinelle/misc/noderef.cocci
Fixes: 109ec558370f ("drm/i915/pmu: Only enumerate availa
Hi Laurent,
On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart
wrote:
> The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add
> corresponding device tree bindings.
>
> Signed-off-by: Laurent Pinchart
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/bridge/renesas
Hi Laurent,
On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart
wrote:
> The internal LVDS encoders now have their own DT bindings, representing
> them as part of the DU is deprecated.
>
> Signed-off-by: Laurent Pinchart
FWIW, you're not really deprecating the LVDS part, but removing it completel
Free up a pasid after all fences signaled.
v2: also handle the case when we can't allocate a fence array.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c | 82 +
drivers/gpu/drm/amd/amdgpu/amdgpu_ids.h | 2 +
2 files changed, 84 insert
Hi Geert,
On Friday, 12 January 2018 11:47:03 EET Geert Uytterhoeven wrote:
> On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart wrote:
> > This patch series addresses a design mistake that dates back from the
> > initial DU support. Support for the LVDS encoders, which are IP cores
> > separate fr
Hi Geert,
On Friday, 12 January 2018 12:09:45 EET Geert Uytterhoeven wrote:
> On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart wrote:
> > The internal LVDS encoders now have their own DT bindings. Before
> > switching the driver infrastructure to those new bindings, implement
> > backward-compati
Hi Laurent,
On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart
wrote:
> The internal LVDS encoders now have their own DT bindings. Before
> switching the driver infrastructure to those new bindings, implement
> backward-compatibility through live DT patching.
>
> Patching is disabled and will be e
Hello!
On 1/12/2018 4:26 AM, Laurent Pinchart wrote:
After the recent correction of the R-Car gen3 LVDCR1 value, already similar
enough at their ends rcar_du_lvdsenc_start_gen{2|3}() started asking for a
merge and it's becoming actually necessary with the addition the R-Car V3M
(R8A77970) supp
Am 12.01.2018 um 07:14 schrieb Roger He:
add input parameter for ttm_dma_unpopulate.
when ttm_dma_pool_get_pages or ttm_mem_global_alloc_page fail, don't
call ttm_mem_global_free_page to update global memory count.
Signed-off-by: Roger He
Good catch, but that doesn't looks correct to me.
See
On 1/12/2018 4:13 AM, Laurent Pinchart wrote:
Add support for the R-Car V3M (R8A77970) SoC to the DU driver (this SoC
has only 1 display port). Note that there are some differences with the
other R-Car gen3 SoCs in the LVDS encoder part, e.g. LVDPLLCR has the same
layout as on the R-Car ge
Start to always allocate a pasid for each VM.
v2: use dev_warn when we run out of PASIDs
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 43 ++---
1 file changed, 29 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/
https://bugs.freedesktop.org/show_bug.cgi?id=101900
--- Comment #22 from letha...@gmail.com ---
Thank you for the printks.
If the code is only ran at initialization of gpu:
could this explain the lpcm noise issue?: The reserved bandwidth at gpu init
isn't enough anymore when video+more audio com
2018-01-12 14:21 GMT+01:00 Peter Ujfalusi :
> Instead of re-implementing the drm_atomic_helper_check() locally with just
> adding drm_atomic_normalize_zpos() into it, set the
> drm_device->normalize_zpos.
>
Acked-by: Benjamin Gaignard
> Signed-off-by: Peter Ujfalusi
> CC: Benjamin Gaignard
> C
On Fri, Jan 12, 2018 at 4:48 AM, Daniel Vetter wrote:
> [Fair warning: This is pure conjecture right now.]
>
> In
>
> commit b8e2b0199cc377617dc238f5106352c06dcd3fa2
> Author: Peter Rosin
> Date: Tue Jul 4 12:36:57 2017 +0200
>
> drm/fb-helper: factor out pseudo-palette
>
> Peter extracted
Hi,
On 2018-01-12 16:07, Benjamin Gaignard wrote:
> 2018-01-12 14:21 GMT+01:00 Peter Ujfalusi :
>> Instead of re-implementing the drm_atomic_helper_check() locally with just
>> adding drm_atomic_normalize_zpos() into it, set the
>> drm_device->normalize_zpos.
>>
>
> Acked-by: Benjamin Gaignard
drm_format_info does not describe the number of bits used for the alpha
channel. That information is useful in a central place like drm_fourcc.c
where it can be queried by the drivers that want to determine if 'alpha
blending' is to be enabled or not.
Signed-off-by: Ayan Kumar Halder
Reviewed-by:
Hi Fabrizio,
On Friday, 12 January 2018 16:00:31 EET Fabrizio Castro wrote:
> Hi Laurent,
>
> > Subject: Re: [PATCH 01/10] dt-bindings: display: renesas: Add R-Car LVDS
> > encoder DT bindings
> > On Friday, 12 January 2018 14:59:53 EET Biju Das wrote:
> >> Hi,
> >>
> >>> Subject: [PATCH 01/10]
On 12/01/2018 13:31, kbuild test robot wrote:
From: Fengguang Wu
drivers/gpu/drm/i915/i915_pmu.c:795:34-40: ERROR: application of sizeof to
pointer
sizeof when applied to a pointer typed expression gives the size of
the pointer
Generated by: scripts/coccinelle/misc/noderef.cocci
Fixes:
On Fri, Jan 12, 2018 at 02:21:16PM +, Ayan Halder wrote:
> drm_format_info does not describe the number of bits used for the alpha
> channel. That information is useful in a central place like drm_fourcc.c
> where it can be queried by the drivers that want to determine if 'alpha
> blending' is
Hi Sergei,
On Friday, 12 January 2018 11:23:00 EET Sergei Shtylyov wrote:
> On 1/12/2018 4:13 AM, Laurent Pinchart wrote:
> >> Add support for the R-Car V3M (R8A77970) SoC to the DU driver (this SoC
> >> has only 1 display port). Note that there are some differences with the
> >> other R-Car g
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #16 from Vedran Miletić ---
(In reply to Bong Cosca from comment #14)
> I have the same setup and I'm experiencing the same symptoms. 7400K on Asus
> A68HM-K with VGA/DVI-D output on ArchLinux 4.14.12 Xorg 1.19.6, colored
> noise (som
On Fri, Jan 12, 2018 at 09:31:16PM +0800, kbuild test robot wrote:
> From: Fengguang Wu
>
> drivers/gpu/drm/i915/i915_pmu.c:795:34-40: ERROR: application of sizeof to
> pointer
>
> sizeof when applied to a pointer typed expression gives the size of
> the pointer
>
> Generated by: scripts/coc
1 - 100 of 203 matches
Mail list logo
