On Tue, Sep 25, 2018 at 10:13:33AM +0100, Damian Kos wrote:
> From: Quentin Schulz
>
> dp_get_lane_status is pretty generic and can be used for other means,
> so let's make it "public".
>
> This adds drm_dp_get_lane_status to the header file and add the appropriate
> EXPORT_SYMBOL for it so that
Hi, Heiko:
Hi, Heiko:
Hi, Heiko:
Reviewed-by: zhengyang
So far we always encountered socs with 2 output crtcs needing the driver
to tell the hdmi block which output to connect to. But there also exist
socs with only one crtc like the rk3228, rk3328 and rk3368.
So adapt the register field t
Hi, Heiko:
Reviewed-by: zhengyang
When using special phy handling operations we'll often need access to
the rockchip_hdmi struct.
As the chip-data that occupies the phy_data pointer initially gets
assigned to the rockchip_hdmi struct, we can now re-use this phy_data
pointer to hold the refer
Hi, Heiko:
Reviewed-by: zhengyang
In some IP implementations the reading of the phy-type may be broken.
One example are the Rockchip rk3228 and rk3328 socs that use a separate
vendor-type phy from Innosilicon but still report the HDMI20_TX type.
So allow the glue driver to force the vendor-p
Hi, Heiko:
Reviewed-by: zhengyang
Some variants of the dw-hdmi on Rockchip socs use a separate phy block
accessed via the generic phy framework, so allow them to be included
if such a phy reference is found.
Signed-off-by: Heiko Stuebner
Tested-by: Robin Murphy
---
drivers/gpu/drm/rockchip
On 12.09.2018 14:47, Heiko Stuebner wrote:
> In some IP implementations the reading of the phy-type may be broken.
> One example are the Rockchip rk3228 and rk3328 socs that use a separate
> vendor-type phy from Innosilicon but still report the HDMI20_TX type.
>
> So allow the glue driver to force
On Thu, Sep 27, 2018 at 3:50 PM Sean Paul wrote:
> What's different in your in-development driver that's causing you to hit
> this?
I think Andrzej answered it well, but I couldn't see what I did
different from the Exynos driver, so I was puzzled that it would
still work, but as it turns out tha
Den 28.09.2018 09.34, skrev Alexey Brodkin:
Hi Noralf,
On Sat, 2018-09-08 at 15:46 +0200, Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client
https://bugs.freedesktop.org/show_bug.cgi?id=108094
Bug ID: 108094
Summary: [CI][BAT] KBL-G: Test assertion failure function
amdgpu_command_submission_compute_nop
Product: DRI
Version: DRI git
Hardware: Other
Am Mittwoch, 12. September 2018, 14:47:34 CEST schrieb Heiko Stuebner:
> The rk3228/rk3229 and rk3328 socs started using a new type of hdmi-phy
> from Innosilicon that resides completely separate from the dw-hdmi block
> and gets accessed via mmio.
>
> Additionally the rk3328 dw-hdmi does not repo
Since "drm/fb: Stop leaking physical address", the default behaviour of
the DRM fbdev emulation is to set the smem_base to 0 and pass the new
FBINFO_HIDE_SMEM_START flag.
The main reason is to avoid leaking physical addresse to user-space, and
it follows a general move over the kernel code to avoi
https://bugs.freedesktop.org/show_bug.cgi?id=108095
Bug ID: 108095
Summary: Window becomes partially transparent for short time
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: n
Hi, Dave
I realize this is probably too late for the next merge window. If that's the
case, then
we can just postpone it for 4.21.
Mostly code reorganizations and optimizations for vmwgfx.
- Move TTM code that's only used by vmwgfx to vmwgfx
- Break out the vmwgfx buffer- and resource validation
Hi Lee,
Am Montag, 10. September 2018, 16:49:24 CEST schrieb Lee Jones:
> On Tue, 14 Aug 2018, Enric Balletbo i Serra wrote:
>
> > The "atomic" API allows us to configure PWM period and duty_cycle and
> > enable it in one call.
> >
> > The patch also moves the pwm_init_state just before any use
On 27.09.2018 23:23, Noralf Trønnes wrote:
> Den 27.09.2018 23.08, skrev Stefan Agner:
>> On 08.09.2018 15:46, Noralf Trønnes wrote:
>>> The CMA helper is already using the drm_fb_helper_generic_probe part of
>>> the generic fbdev emulation. This patch makes full use of the generic
>>> fbdev emulat
https://bugs.freedesktop.org/show_bug.cgi?id=108095
--- Comment #1 from Michel Dänzer ---
Please attach the corresponding Xorg log file and the outputs of dmesg and
glxinfo.
--
You are receiving this mail because:
You are the assignee for the bug.___
The target definition for a630 didn't set a reasonable
value for inactive_period so it defaulted to zero and
we were essentially powering down after every submission.
Set it back to the default value to keep the GPU from
bouncing too much during regular workloads.
Signed-off-by: Jordan Crouse
---
To avoid possible issues during GMU init make sure to vote the bus
quota to a reasonable level before starting the sequence. Also
remove the bus vote during power off to avoid leaking power we don't
need.
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/adreno/a6xx_gmu.c | 10 ++
1 f
On Wed, 2018-09-26 at 19:37 +0300, Ville Syrjälä wrote:
> On Wed, Sep 26, 2018 at 05:25:35PM +0300, Eugeniy Paltsev wrote:
> > If driver/HW doesn't support vblank functionality (for example
> > UDL driver, ARCPGU driver, ...) we always have vblank->time == 0.
> > In result we always provide zero ti
UDL doesn't support vblank functionality so we don't need to
initialize vblank here (we are able to send page flip
completion events even without vblank initialization)
Moreover current drm_vblank_init call with num_crtcs > 0 causes
sending DRM_EVENT_FLIP_COMPLETE event with zero timestamp every
t
https://bugs.freedesktop.org/show_bug.cgi?id=108095
--- Comment #2 from Paul Menzel ---
Created attachment 141778
--> https://bugs.freedesktop.org/attachment.cgi?id=141778&action=edit
Linux 4.14.55 messages
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=108095
--- Comment #3 from Paul Menzel ---
Created attachment 141779
--> https://bugs.freedesktop.org/attachment.cgi?id=141779&action=edit
/var/log/gdm/:0.log
--
You are receiving this mail because:
You are the assignee for the bug.
v2:
Call amdgpu_bo_va_op_raw directly in amdgpu_bo_alloc_and_map_raw
Move amdgpu_bo_alloc_and_map_raw into C file to avoid including
unistd.h in amdgpu_test.h
Signed-off-by: Andrey Grodzovsky
---
tests/amdgpu/amdgpu_test.h | 59 +---
tests/amdgpu/basic_tes
Seems like AI and RV requires uncashed memory mapping to be able
to pickup value written to memory by CPU after the WAIT_REG_MEM
command was already launched.
.
Enable the test for AI and RV.
v2:
Update commit description.
Signed-off-by: Andrey Grodzovsky
---
tests/amdgpu/deadlock_tests.c | 13
Den 28.09.2018 16.11, skrev Stefan Agner:
On 27.09.2018 23:23, Noralf Trønnes wrote:
Den 27.09.2018 23.08, skrev Stefan Agner:
On 08.09.2018 15:46, Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full
On 28.09.2018 16:57, Noralf Trønnes wrote:
> Den 28.09.2018 16.11, skrev Stefan Agner:
>> On 27.09.2018 23:23, Noralf Trønnes wrote:
>>> Den 27.09.2018 23.08, skrev Stefan Agner:
On 08.09.2018 15:46, Noralf Trønnes wrote:
> The CMA helper is already using the drm_fb_helper_generic_probe pa
Hi Souptick,
Thank you for the patch.
On Thursday, 27 September 2018 09:34:18 EEST Souptick Joarder wrote:
> On Tue, Sep 18, 2018 at 10:05 PM Souptick Joarder wrote:
> > convert drm_atomic_helper_suspend/resume() to use
> > drm_mode_config_helper_suspend/resume().
> >
> > remove suspend_state fi
Hi Ulrich,
Thank you for the review. Patches have however landed upstream already, so I
can't add any Reviewed-by tag anymore. I will submit a follow-up patch, unless
you would prefer doing it yourself.
On Wednesday, 26 September 2018 18:55:14 EEST Ulrich Hecht wrote:
> Thank you for your patch
Hi Souptick,
On Friday, 28 September 2018 18:05:18 EEST Laurent Pinchart wrote:
> On Thursday, 27 September 2018 09:34:18 EEST Souptick Joarder wrote:
> > On Tue, Sep 18, 2018 at 10:05 PM Souptick Joarder wrote:
> >> convert drm_atomic_helper_suspend/resume() to use
> >> drm_mode_config_helper_sus
Instead of allocating a fake IOMMU domain for all Exynos DRM components,
simply reuse the default IOMMU domain of the already selected DMA device.
This allows some design changes in IOMMU framework without breaking IOMMU
support in Exynos DRM.
Signed-off-by: Marek Szyprowski
---
Inki:
If possible
On 2018-09-28 5:09 PM, Marek Szyprowski wrote:
Instead of allocating a fake IOMMU domain for all Exynos DRM components,
simply reuse the default IOMMU domain of the already selected DMA device.
This allows some design changes in IOMMU framework without breaking IOMMU
support in Exynos DRM.
Revi
On Wed, Sep 26, 2018 at 09:41:52PM +0200, Hans de Goede wrote:
> This cleanups 2 things:
>
> 1) The first time we loop over the crtc-s, to compare framebuffers, fb1 may
> get set to NULL by the fb1 = CRTC_FB(crtci); statement and then we call
> to_vbox_framebuffer() on it. The result of this call
https://bugzilla.kernel.org/show_bug.cgi?id=201273
Bug ID: 201273
Summary: Fatal error during GPU init amdgpu
Product: Drivers
Version: 2.5
Kernel Version: 4.18.9 4.18.10 and possibly earlier
Hardware: x86-64
OS: Linux
https://bugzilla.kernel.org/show_bug.cgi?id=201275
Bug ID: 201275
Summary: Power consumption RX460 idle raised from 7 W to 13 W
Product: Drivers
Version: 2.5
Kernel Version: 4.18.10
Hardware: All
OS: Linux
Tr
Hi Jordan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robclark/msm-next]
[also build test ERROR on v4.19-rc5 next-20180928]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
https://bugzilla.kernel.org/show_bug.cgi?id=201275
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
On Fri, Sep 28, 2018 at 09:59:11AM +1000, Dave Airlie wrote:
> Hi Greg,
>
> Looks like a pretty normal week for graphics,
>
> core: syncobj fix, panel link regression revert
> amd: suspend/resume fixes, EDID emulation fix
> mali-dp: NV12 writeback and vblank reset fixes
> etnaviv: DMA setup fix
>
From: Ville Syrjälä
We aren't supposed to force a stop+start between every i2c msg
when performing multi message transfers. This should eg. cause
the DDC segment address to be reset back to 0 between writing
the segment address and reading the actual EDID extension block.
To quote the E-DDC spec
From: Ville Syrjälä
Make the code a bit easier to read by providing symbolic names
for the reply_type (ACK vs. NAK). Also clean up some brace stuff
while at it.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/drm_dp_mst_topology.c | 26 +-
include/drm/drm_dp_helper.h
From: Ville Syrjälä
Decode the NAK reply fields to make it easier to parse the logs.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/drm_dp_mst_topology.c | 65 ++-
include/drm/drm_dp_helper.h | 1 +
2 files changed, 65 insertions(+), 1 deletion(-)
From: Ville Syrjälä
Consult the I2C_M_STOP flag to determine whether to set the MOT bit or
not. Makes it possible to send multiple messages in one go with
stop+start generated between the messages (as opposed nothing or
repstart depending on whether thr address/rw changed).
Not sure anyone has a
From: Ville Syrjälä
Make sure i2c msgs we're asked to transfer conform to the
requirements of REMOTE_I2C_READ. We were only checking that the
last message is a read, but we must also check that the preceding
messages are all writes. Also check that the length of each
message isn't too long.
Sign
https://bugzilla.kernel.org/show_bug.cgi?id=201275
--- Comment #2 from Alex Deucher (alexdeuc...@gmail.com) ---
Git bisect howto:
https://www.kernel.org/doc/html/v4.18/admin-guide/bug-bisect.html
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
Adopt the SPDX license identifier headers to ease license compliance
management.
Signed-off-by: Fabio Estevam
---
drivers/gpu/drm/imx/dw_hdmi-imx.c | 5 +
drivers/gpu/drm/imx/imx-drm-core.c | 11 +--
drivers/gpu/drm/imx/imx-ldb.c | 10 +-
drivers/gpu/drm/im
https://bugs.freedesktop.org/show_bug.cgi?id=108037
Öyvind Saether changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi,
Sergey Suloev already reported this NULL pointer dereference [1]. Now he was
able to provide a Kernel config and i'm able to reproduce it with a Raspberry
Pi 3 (arm64) and Linux 4.19-rc5. It seems like a invalid config [2] for vc4,
but nevertheless the driver shouldn't crash at boot.
[
https://bugzilla.kernel.org/show_bug.cgi?id=201275
--- Comment #3 from quirin.blae...@freenet.de ---
Am 28.09.18 um 20:14 schrieb bugzilla-dae...@bugzilla.kernel.org:
> https://bugzilla.kernel.org/show_bug.cgi?id=201275
>
> --- Comment #2 from Alex Deucher (alexdeuc...@gmail.com) ---
> Git bisect
Hi Ville,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on sof-driver-fuweitax/master]
[also build test WARNING on v4.19-rc5 next-20180928]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On Mon, Aug 27, 2018 at 8:55 PM Rob Herring wrote:
>
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Bartlomiej Zolnierkiewicz
> Cc: dri-devel@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org
> Sign
In preparation to remove the node name pointer from struct device_node,
convert printf users to use the %pOFn format specifier.
For drm_modes.c, the full node path is already printed out, so printing
just the node name a 2nd time is redundant and can be removed.
Cc: Gustavo Padovan
Cc: Maarten L
This adds just enough performance counter support to measure the
clock. We don't have linux kernel drivers for the clock driving the
HW, and this was useful for determining that the V3D HW is running on
a slow clock, not that the driver was slow.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/v
Fixes an oops reading this debugfs entry on BCM7278.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/v3d/v3d_debugfs.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/v3d/v3d_debugfs.c
b/drivers/gpu/drm/v3d/v3d_debugfs.c
index d48008adb085..eb2b2d2
Once we push the job, the scheduler could run it and free it. So, if
we want to reference their fences, we need to grab them before then.
I haven't seen this happen in many days of conformance test runtime,
but let's still close the race.
Signed-off-by: Eric Anholt
Fixes: 57692c94dcbe ("drm/v3d:
Since this is UAPI, it's good to document what exactly the guarantees
we're providing are.
Signed-off-by: Eric Anholt
---
include/uapi/drm/v3d_drm.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/uapi/drm/v3d_drm.h b/include/uapi/drm/v3d_drm.h
index 7b6627783608..f446656
Add the device tree bindings for Truly NT35597 panel driver. This panel
driver supports both single DSI and dual DSI.
However, this patch series supports only dual DSI.
Changes in v9:
- None
Reviewed-by: Linus Walleij
Reviewed-by: Sean Paul
Signed-off-by: Abhinav Kumar
---
.../devicetree/b
Add support for Truly NT35597 panel driver used in MSM reference
platforms. This panel driver supports both single DSI and dual
DSI modes.
However, this patch series adds support only for dual DSI mode.
Changes in v9:
- Sorted headers alphabetically
- Remove void type for commands
- Reduce number
https://bugzilla.kernel.org/show_bug.cgi?id=201275
Dieter Nützel (die...@nuetzel-hh.de) changed:
What|Removed |Added
CC||die...@nuetzel-hh.d
https://bugs.freedesktop.org/show_bug.cgi?id=108096
Bug ID: 108096
Summary: [amd-staging-drm-next] SDDM screen corruption (not
useable) with RX580, amdgpu, dc=1 (of course),
regression
Product: DRI
Version: unspec
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #1 from Dieter Nützel ---
Created attachment 141787
--> https://bugs.freedesktop.org/attachment.cgi?id=141787&action=edit
SDDM corruption 4.18.0-rc1 (with some recognizable parts)
--
You are receiving this mail because:
You are t
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #2 from Dieter Nützel ---
Created attachment 141788
--> https://bugs.freedesktop.org/attachment.cgi?id=141788&action=edit
SDDM corruption 4.19.0-rc1
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #3 from Dieter Nützel ---
Created attachment 141789
--> https://bugs.freedesktop.org/attachment.cgi?id=141789&action=edit
dmesg-4.18.0-rc1-1.g7262353-default+.log
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #4 from Dieter Nützel ---
Created attachment 141790
--> https://bugs.freedesktop.org/attachment.cgi?id=141790&action=edit
dmesg-4.18.0-rc1-1.g7262353-default+.log3
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #5 from Dieter Nützel ---
Created attachment 141791
--> https://bugs.freedesktop.org/attachment.cgi?id=141791&action=edit
dmesg-4.19.0-rc1-1.g7262353-default+.log-25.10
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=108096
Dieter Nützel changed:
What|Removed |Added
Attachment #141791|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #7 from Dieter Nützel ---
Created attachment 141793
--> https://bugs.freedesktop.org/attachment.cgi?id=141793&action=edit
Xorg.0.log.25.09
--
You are receiving this mail because:
You are the assignee for the bug._
65 matches
Mail list logo
