From: Ville Syrjälä
AVI infoframe can only carry none, 4:3, or 16:9 picture aspect
ratios. Return an error if the user asked for something different.
Cc: Shashank Sharma
Cc: "Lin, Jia"
Cc: Akashdeep Sharma
Cc: Jim Bride
Cc: Jose Abreu
Cc: Daniel Vetter
Cc: Emil Velikov
Cc: Thierry Reding
From: Ankit Nautiyal
We parse the EDID and add all the modes in the connector's modelist.
This adds CEA modes with aspect ratio information too, regardless of
whether user space requested this information or not.
This patch:
-prunes the modes with aspect-ratio information, from a
connector's mo
From: Ankit Nautiyal
This patch series is a re-attempt to enable aspect ratio support in
DRM layer. Currently the aspect ratio information gets lost in translation
during a user->kernel mode or vice versa.
The old patch series (https://pw-emeril.freedesktop.org/series/10850/) had
4 patches, out
From: Ankit Nautiyal
If the user-space does not support aspect-ratio, and requests for a
modeset with mode having aspect ratio bits set, then the given
user-mode must be rejected. Secondly, while preparing a user-mode from
kernel mode, the aspect-ratio info must not be given, if aspect-ratio
is n
From: Ankit Nautiyal
To enable aspect-ratio support in DRM, blindly exposing the aspect
ratio information along with mode, can break things in existing
non-atomic user-spaces which have no intention or support to use this
aspect ratio information.
To avoid this, a new drm client cap is required
From: Ville Syrjälä
commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer")
cause us to not send out any VICs in the AVI infoframes. That commit
was since reverted, but if and when we add aspect ratio handing back
we need to be more careful.
Let's handle this by considering the aspect
From: Ville Syrjälä
If the user mode would specify an aspect ratio other than 4:3 or 16:9
we now silently ignore it. Maybe a better apporoach is to return an
error? Let's try that.
Also we must be careful that we don't try to send illegal picture
aspect in the infoframe as it's only capable of s
From: Ville Syrjälä
Use drm_mode_equal_no_clocks_no_stereo() in
drm_match_hdmi_mode_clock_tolerance() for consistency as we
also use it in drm_match_hdmi_mode() and the cea mode matching
functions.
This doesn't actually change anything since the input mode
comes from detailed timings and we matc
From: Ville Syrjälä
Make mode matching less confusing by allowing the caller to specify
which parts of the modes should match via some flags.
Signed-off-by: Ville Syrjälä
Reviewed-by: Shashank Sharma
---
drivers/gpu/drm/drm_modes.c | 134 ++--
include/d
https://bugzilla.kernel.org/show_bug.cgi?id=199585
Jason Hicks (jasz...@gmail.com) changed:
What|Removed |Added
Regression|No |Yes
--- Comment #7 from
https://bugzilla.kernel.org/show_bug.cgi?id=199585
--- Comment #6 from Jason Hicks (jasz...@gmail.com) ---
Created attachment 275719
--> https://bugzilla.kernel.org/attachment.cgi?id=275719&action=edit
dmesg - second lock up
Disabled DC mode, updated grub, rebooted, and then set the monitor pow
https://bugzilla.kernel.org/show_bug.cgi?id=199585
--- Comment #5 from Jason Hicks (jasz...@gmail.com) ---
Created attachment 275717
--> https://bugzilla.kernel.org/attachment.cgi?id=275717&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=199585
--- Comment #4 from Jason Hicks (jasz...@gmail.com) ---
Created attachment 275715
--> https://bugzilla.kernel.org/attachment.cgi?id=275715&action=edit
xrandr
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=199585
Jason Hicks (jasz...@gmail.com) changed:
What|Removed |Added
Hardware|All |x86-64
--
You are rece
https://bugzilla.kernel.org/show_bug.cgi?id=199585
--- Comment #3 from Jason Hicks (jasz...@gmail.com) ---
Created attachment 275713
--> https://bugzilla.kernel.org/attachment.cgi?id=275713&action=edit
inxi -F
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=199585
--- Comment #2 from Jason Hicks (jasz...@gmail.com) ---
Created attachment 275711
--> https://bugzilla.kernel.org/attachment.cgi?id=275711&action=edit
lspci -vk
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=199585
--- Comment #1 from Jason Hicks (jasz...@gmail.com) ---
Created attachment 275709
--> https://bugzilla.kernel.org/attachment.cgi?id=275709&action=edit
kernel bug
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=199585
Bug ID: 199585
Summary: AMDGPU related kernel dump in
/home/kernel/COD/linux/mm/slub.c:296 after monitors
power off
Product: Drivers
Version: 2.5
Kernel Versi
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #66 from H4nN1baL ---
Okay, thanks for your reply. Then our problems are unrelated.
Even so let me share you some intel. Disable any BIOS configuration related to
"GART" and "PCIE Spread Spectrum"(PCIe overclock).
And keep in min
Hi ,
If you are sure that the HW worked fine before. I think you should:
1. Be sure that HW works fine now.
2. recall the driver to the point at where it works well, and then replace them
one by one to confirm component which causes the issue.
3. try to update the last VBIOS to adapt new driver.
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #65 from MirceaKitsune ---
(In reply to H4nN1baL from comment #64)
Just tested with "export MESA_EXTENSION_OVERRIDE=-GL_ARB_buffer_storage". It
did not affect the freeze triggered by playing back the Blender trace.
Also, to answer
This add a dt binding for ZynqMP DP subsystem.
Signed-off-by: Hyun Kwon
Reviewed-by: Rob Herring
---
v6
- Add more descriptions and references
- Remove the description for child node
v4
- Specify phy related descriptions
- Specify dma related descriptions
- Remove ports
- Remove child nodes for
Xilinx has various platforms for display, where users can create
using multiple IPs in the programmable FPGA fabric, or where
some hardened pipeline is available on the chip. Furthermore,
hardened pipeline can also interact with soft logics in FPGA.
The Xilinx DRM KMS module is to integrate multip
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
Ac
Hi Laurent,
On top of addressing your comments in v6, I've incorporated some
relatively small fixes in v7. I'm mainly waiting for your feedback
before committing this series, unless there's any additional review
comments. Please take a look.
Thanks,
-hyun
Hyun Kwon (5):
drm: xlnx: Xilinx DRM K
This driver creates DRM encoder and connector for ZynqMP DisplayPort.
Signed-off-by: Hyun Kwon
Acked-by: Daniel Vetter
---
v7
- Use correct number of lanes
v6
- Constify all function pointers
- Clean up the duplicated license paragraphs
- Do complete forward declaration in the header
v2
- Change
This is a wrapper around the ZynqMP Display and DisplayPort drivers.
Signed-off-by: Hyun Kwon
Acked-by: Daniel Vetter
---
v6
- Accomodate the migration of logical master from platform device to device
- Remove the duplicate license paragraphs
- Do complete forward declaration in the header
v5
-
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #64 from H4nN1baL ---
I've been having a very different problem with AMD cards. But I have reason to
think that the problem could vary from one processor/chipset to another.
My problems disappear using 'MESA_EXTENSION_OVERRIDE=-GL_A
Em Qua, 2018-04-25 às 17:29 -0700, Michel Thierry escreveu:
> On 04/25/2018 05:09 PM, Paulo Zanoni wrote:
> > Add the PCI IDs and the basic code to enable ICL. This is the
> > current
> > PCI ID list in our documentation.
> >
> > Kernel commit: d55cb4fa2cf0 ("drm/i915/icl: Add the ICL PCI IDs")
>
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #63 from MirceaKitsune ---
(In reply to iive from comment #62)
I booted my machine with the kernel parameter panic=30 as instructed. I then
waited for over two minutes to see if there's any sign of movement. Nothing
happened: The ma
https://bugzilla.kernel.org/show_bug.cgi?id=85791
--- Comment #6 from Bruno Pagani (bruno.n.pag...@gmail.com) ---
I don’t know who can change status here but this should be closed.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_
On Wed, Apr 18, 2018 at 10:31:52AM -0700, Kristian H. Kristensen wrote:
> Blending win0 with the background color doesn't seem to work
> correctly. We only get the background color, no matter the contents of
> the win0 framebuffer. However, blending pre-multiplied color with the
> default opaque b
https://bugs.freedesktop.org/show_bug.cgi?id=102646
Justin Mitzel changed:
What|Removed |Added
Summary|[dc] Screen flickering |Screen flickering under
Commit 39bf4de89ff7 ("drm/i915: Add -Wall -Wextra to our build, set
warnings to full") enabled extra warnings for i915 to spot possible
bugs in new code, and then disabled a subset of these warnings to keep
the current code building without warnings (with gcc). Enabling the
extra warnings also enab
Signed-off-by: Eric Anholt
---
airlied + danvet: this is the last change I think we need before I can
merge v3d with your acks. Sending as a diff so you don't have to look
at the whole thing again. Look good?
drivers/gpu/drm/v3d/v3d_bo.c | 10 ++
drivers/gpu/drm/v3d/v3d_gem.c | 5 ++
https://bugs.freedesktop.org/show_bug.cgi?id=106245
--- Comment #1 from Michel Dänzer ---
Does it work if you disable SME? amdgpu doesn't actually work yet with SME
enabled anyway.
It's odd that SWIOTLB fails allocating 256KB this early, but it might be due to
SME creating pressure on SWIOTLB.
On Tue, May 1, 2018 at 11:31 AM, Chen-Yu Tsai wrote:
> On Wed, May 2, 2018 at 12:17 AM, Rob Herring wrote:
>> On Mon, Apr 30, 2018 at 05:10:41PM +0530, Jagan Teki wrote:
>>> Allwinner A64 has DE2 pipeline similar to other Allwinner
>>> SOC's like A83T, H3/H5.
>>
>> 'dt-bindings: ' for the subject
On Tue, May 1, 2018 at 11:19 AM, Chen-Yu Tsai wrote:
> On Wed, May 2, 2018 at 12:16 AM, Rob Herring wrote:
>> On Mon, Apr 30, 2018 at 05:10:38PM +0530, Jagan Teki wrote:
>>> Allwinner A64 has DE2 CCU which is similar to H3/H5 SoC.
>>>
>>> Signed-off-by: Jagan Teki
>>> ---
>>> Documentation/devi
On Wed, May 2, 2018 at 12:17 AM, Rob Herring wrote:
> On Mon, Apr 30, 2018 at 05:10:41PM +0530, Jagan Teki wrote:
>> Allwinner A64 has DE2 pipeline similar to other Allwinner
>> SOC's like A83T, H3/H5.
>
> 'dt-bindings: ' for the subject prefix.
>
>>
>> Signed-off-by: Jagan Teki
>> ---
>> Docume
https://bugs.freedesktop.org/show_bug.cgi?id=105339
Gregor Münch changed:
What|Removed |Added
CC||nhaeh...@gmail.com
--- Comment #7 from G
On Mon, Apr 30, 2018 at 7:40 PM, Jagan Teki wrote:
> Allwinner 64-bit SoC like H5/A64 has DE2 CCU so enable them
> as default.
>
> Signed-off-by: Jagan Teki
> ---
> drivers/clk/sunxi-ng/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/sunxi-ng/Kconfig b/drivers/clk/
On Mon, Apr 30, 2018 at 05:10:49PM +0530, Jagan Teki wrote:
> tcon-tv on Allwinner A64 has similar behavior like Allwinner A83T.
>
> Signed-off-by: Jagan Teki
> ---
> Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documenta
On Mon, Apr 30, 2018 at 05:10:48PM +0530, Jagan Teki wrote:
> Mixer1 on Allwinner A64 has similar behavior like Allwinner A83T.
>
> Signed-off-by: Jagan Teki
> ---
> Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentat
On Mon, Apr 30, 2018 at 7:40 PM, Jagan Teki wrote:
> Allwinner 64-bit SoC like H5/A64 has DesignWare HDMI so
> enable them as default.
Should we not also enable it by default for SUN8I (A83T, H3, R40?, etc.)
> Signed-off-by: Jagan Teki
> ---
> drivers/gpu/drm/sun4i/Kconfig | 1 +
> 1 file chan
On Mon, Apr 30, 2018 at 05:10:46PM +0530, Jagan Teki wrote:
> HDMI on Allwinner A64 has similar behavior like H3/H5, so
> reuse the same dts node details for A64.
>
> Signed-off-by: Jagan Teki
> ---
> arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 28
> +++
> include/dt
On Wed, May 2, 2018 at 12:16 AM, Rob Herring wrote:
> On Mon, Apr 30, 2018 at 05:10:38PM +0530, Jagan Teki wrote:
>> Allwinner A64 has DE2 CCU which is similar to H3/H5 SoC.
>>
>> Signed-off-by: Jagan Teki
>> ---
>> Documentation/devicetree/bindings/clock/sun8i-de2.txt | 1 +
>> 1 file changed,
On Mon, Apr 30, 2018 at 05:10:45PM +0530, Jagan Teki wrote:
> HDMI PHY on Allwinner A64 has similar like H3/H5.
>
> Signed-off-by: Jagan Teki
> ---
> Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/b
On Mon, Apr 30, 2018 at 05:10:41PM +0530, Jagan Teki wrote:
> Allwinner A64 has DE2 pipeline similar to other Allwinner
> SOC's like A83T, H3/H5.
'dt-bindings: ' for the subject prefix.
>
> Signed-off-by: Jagan Teki
> ---
> Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 1 +
>
On Mon, Apr 30, 2018 at 05:10:38PM +0530, Jagan Teki wrote:
> Allwinner A64 has DE2 CCU which is similar to H3/H5 SoC.
>
> Signed-off-by: Jagan Teki
> ---
> Documentation/devicetree/bindings/clock/sun8i-de2.txt | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Rob Herring
_
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #9 from Matt Corallo ---
Switched the machine over to a 4k-PAGE_SIZE kernel and it works fine, so that
does appear to be the issue here.
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=101651
Gregor Münch changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #5 from Gregor Münc
Op 01-05-18 om 10:58 schreef Maarten Lankhorst:
> Hey,
>
> Op 30-04-18 om 16:56 schreef Daniel Vetter:
>> On Mon, Apr 30, 2018 at 04:55:24PM +0200, Daniel Vetter wrote:
>>> On Sat, Apr 28, 2018 at 12:07:04AM +0300, Laurent Pinchart wrote:
Hi Daniel,
(Removing the linux-media mailing
On Wed, Apr 25, 2018 at 09:49:38AM +0200, Geert Uytterhoeven wrote:
> Fixes: 14da3ed8dd08c581 ("devicetree/bindings: display: Document common
> panel properties")
> Signed-off-by: Geert Uytterhoeven
> ---
> Documentation/devicetree/bindings/display/panel/panel-common.txt | 2 +-
> 1 file changed,
On 2018-05-01 01:15 AM, Dave Airlie wrote:
>>
>>
>> Yes, I fixed the original false positive messages myself with the swiotlb
>> maintainer and I was CCed in fixing the recent fallout from Chris changes as
>> well.
>
> So do we have a good summary of where this at now?
>
> I'm getting reports on
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #34 from Michel Dänzer ---
While it's good to hear that xf86-video-amdgpu doesn't trigger it, the kernel
BUG is still a kernel driver bug.
--
You are receiving this mail because:
You are the assignee for the bug.___
Add device_link from panel device (supplier) to drm device (consumer)
when drm_panel_attach() is called. This patch should protect the
master drm driver if an attached panel driver unbinds while it is in
use. The device_link should make sure the drm device is unbound before
the panel driver becomes
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #33 from Öyvind Saether ---
In my case the problem was not having xorg-x11-drv-amdgpu installed (how
embarrassing) which made xorg use xorg-x11-drv-ati. Yes, really. I assumed
Fedora 28 beta installed it along with all the other driv
https://bugs.freedesktop.org/show_bug.cgi?id=104082
Michel Dänzer changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
From: Michel Dänzer
The result was printing the warning only when we were explicitly asked
not to.
Cc: sta...@vger.kernel.org
Fixes: 0176adb004065d6815a8e67946752df4cd947c5b "swiotlb: refactor
coherent buffer allocation"
Signed-off-by: Michel Dänzer
---
lib/swiotlb.c | 2 +-
1 file changed, 1
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #8 from Andrey Grodzovsky ---
I Wonder is there a way to reproduce this on x86 platform, from looking in
kflags there is no CONFIG_x86_4/16/64K_PAGES flags.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #7 from Michel Dänzer ---
(In reply to Timothy Pearson from comment #6)
> This looks like something that should be filed at bugzilla.kernel.org
> against the amdgpu driver itself. It will get more visibility by the right
> people th
On Mon, Apr 30, 2018 at 07:29:44PM +0200, Krzysztof Kozlowski wrote:
> The driver for S6E63M0 AMOLED LCD panel is not used. It does not
> support DeviceTree and respective possible users (S5Pv210 Aquila and
> Goni boards) are DeviceTree-only.
>
> Suggested-by: Marek Szyprowski
> Cc: Marek Szypro
On Mon, Apr 30, 2018 at 07:29:45PM +0200, Krzysztof Kozlowski wrote:
> The driver for LD9040 AMOLED LCD panel was superseded with DRM driver
> panel-samsung-ld9040.c. It does not support DeviceTree and respective
> possible user (Exynos4210 Universal C210) is DeviceTree-only and uses
> DRM version
On Sat, Apr 28, 2018 at 08:21:59AM +0530, Nipun Gupta wrote:
> With each bus implementing its own DMA configuration callback,
> there is no need for bus to explicitly have force_dma in its
> global structure. This patch modifies of_dma_configure API to
> accept an input parameter which specifies if
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #6 from Timothy Pearson ---
This looks like something that should be filed at bugzilla.kernel.org against
the amdgpu driver itself. It will get more visibility by the right people
there.
--
You are receiving this mail because:
You
Hey,
Op 30-04-18 om 16:56 schreef Daniel Vetter:
> On Mon, Apr 30, 2018 at 04:55:24PM +0200, Daniel Vetter wrote:
>> On Sat, Apr 28, 2018 at 12:07:04AM +0300, Laurent Pinchart wrote:
>>> Hi Daniel,
>>>
>>> (Removing the linux-media mailing list from CC as it is out of scope)
>>>
>>> You enquired o
On Mon, Apr 30, 2018 at 03:55:41PM +0100, Robin Murphy wrote:
> On 27/04/18 19:51, Linus Walleij wrote:
> > On Fri, Apr 27, 2018 at 5:02 PM, Robin Murphy wrote:
> >
> > > I dug a little bit and it seems pl111_modeset_init() is deferring because
> > > it
> > > can't find endpoint 0. And given tha
From: Colin Ian King
Trivial fix to spelling mistake in error messages
Signed-off-by: Colin Ian King
---
drivers/video/fbdev/au1100fb.c | 2 +-
drivers/video/fbdev/au1200fb.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/fbdev/au1100fb.c b/drivers/video/f
Hi,
Le mercredi 18 octobre 2017 à 16:49 +0800, Yingjoe Chen a écrit :
> Hi,
>
>
> On Fri, 2017-09-29 at 15:09 +0200, Ulrich Hecht wrote:
> > Signed-off-by: Ulrich Hecht
> > ---
> > arch/arm64/boot/dts/mediatek/Makefile|1 +
> > arch/arm64/boot/dts/mediatek/mt8173-elm-rev3.dts |
https://bugs.freedesktop.org/show_bug.cgi?id=103234
Michel Dänzer changed:
What|Removed |Added
CC||viktor.kecsk...@gmail.com
--- Comment #
https://bugs.freedesktop.org/show_bug.cgi?id=106309
Michel Dänzer changed:
What|Removed |Added
Product|xorg|DRI
Component|Driver/Radeon
71 matches
Mail list logo
