Add binding info for peripherals that support dual-channel DSI. Add
corresponding optional bindings for DSI host controllers that may
be configured in this mode.
Signed-off-by: Archit Taneja
---
.../devicetree/bindings/display/mipi-dsi-bus.txt | 77 ++
1 file changed, 77 in
On Wed 2017-11-29 22:08:56, Sean Paul wrote:
> This patch adds a new optional connector property to allow userspace to enable
> protection over the content it is displaying. This will typically be
> implemented
> by the driver using HDCP.
>
> The property is a tri-state with the following values:
https://bugs.freedesktop.org/show_bug.cgi?id=104090
Michel Dänzer changed:
What|Removed |Added
CC||harry.wentl...@amd.com,
On Mon, Dec 04, 2017 at 09:48:18PM +0100, Daniel Vetter wrote:
> In
>
> commit 613051dac40da1751ab269572766d3348d45a197
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:06 2016 +0100
>
> drm: locking&new iterators for connector_list
>
> we've went to extreme lengths to make sure connector
On Mon, Dec 04, 2017 at 11:33:21PM +0100, Hans de Goede wrote:
> Add a comment to the DRM_PANEL_ORIENTATION_QUIRKS documenting that the
> reason for a separate Kconfig for this is because
> drm_panel_orientation_quirks.c code is shared with fbdev.
>
> Suggested-by: Bartlomiej Zolnierkiewicz
> Sig
https://bugs.freedesktop.org/show_bug.cgi?id=101900
--- Comment #12 from letha...@gmail.com ---
- bumping this thread.
kernel 4.15-rc2 with dc activated for polaris
Still no HBR amdgpu's.
Tried with RX480 & RX550
But i have some worse experience than Direx:
- Stereo works fine
- dolby ac3 wor
Hi Nick,
On Tuesday, 5 December 2017 05:22:28 EET Nick Bowler wrote:
> On 2017-12-04 21:34 +0200, Laurent Pinchart wrote:
> > On Monday, 4 December 2017 21:30:01 EET Nick Bowler wrote:
> >> On 2017-12-04 21:06 +0200, Laurent Pinchart wrote:
> >>> As you reported that the PLL lock failure message i
Hi Stephen,
On Tuesday, 5 December 2017 04:45:50 EET Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 36a46da90212 ("drm: rcar-du: Add R8A7743 support")
> cdd907001572 ("drm: rcar-du: Add R8A7745 support")
> 7912dee7775e ("drm: rcar-du: Implement system suspend/resume support")
> cf05f7
Hi Alex,
Am Montag, den 04.12.2017, 16:47 -0500 schrieb Alex Deucher:
> On Fri, Dec 1, 2017 at 10:55 AM, Christian König
> > wrote:
> > Am 01.12.2017 um 16:28 schrieb Lucas Stach:
> > >
> > > Hi all,
> > >
> > > so this is the first step to make the marvelous AMDGPU scheduler useable
> > > for
Hi Philippe,
On 2017年12月01日 18:07, Philippe CORNU wrote:
Hi Nickey,
On 12/01/2017 10:11 AM, Nickey Yang wrote:
Hi Philippe,
On 2017年12月01日 16:32, Philippe CORNU wrote:
Dear Nickey,
Many thanks for your patch.
I am sorry to say that but you can not add my "Acked-by" to this patch
because
On Tuesday 05 December 2017 10:45 AM, Sean Paul wrote:
This patch adds the framework required to add HDCP support to intel
connectors. It implements Aksv loading from fuse, and parts 1/2/3
of the HDCP authentication scheme.
Note that without shim implementations, this does not actually impleme
On 2017-12-04 13:33 -0500, Nick Bowler wrote:
> On 2017-12-04 10:04 +, Jose Abreu wrote:
> > Hmmm, my first thought was that audio is being configured first
> > because of the phy lock wait time, I've seen this happening before.
> >
> > Lets try this:
> > - Disable all alsa clients (e.g. pulsea
On 2017-12-04 10:04 +, Jose Abreu wrote:
> On 03-12-2017 05:20, Nick Bowler wrote:
> > I brought the original test equipment back to the setup so I can
> > see the video and pink bar again. The symptoms remain the same
> > (unexpected size, pink bar, and no audio).
> >
>
> Can you tell me whic
Hi Joonas,
Quoting Joonas Lahtinen :
On Mon, 2017-11-27 at 16:17 -0600, Gustavo A. R. Silva wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
I have to say I'm totally not sold on regexps matching comment
contents. Was somethi
Hi,
On 2017-12-04 21:06 +0200, Laurent Pinchart wrote:
> As you reported that the PLL lock failure message is not printed, the
> failure can only come from either the extra delay introduced by the
> above loop, or from reading the HDMI_PHY_STAT0 register.
>
> How many iterations of the for loop e
Hi Jose,
On Mon, 2017-12-04 at 17:24 +, Jose Abreu wrote:
> On 04-12-2017 16:00, Alexey Brodkin wrote:
> >
> > [30.763] (II) armada(0): etnaviv: Xv: using YUY2 format intermediate
> > YUV target
> >
>
> I'm wondering if this means that target format for UDL is YUV ...
>
> But anyway,
On 2017-12-04 21:34 +0200, Laurent Pinchart wrote:
> On Monday, 4 December 2017 21:30:01 EET Nick Bowler wrote:
> > On 2017-12-04 21:06 +0200, Laurent Pinchart wrote:
> > > As you reported that the PLL lock failure message is not printed, the
> > > failure can only come from either the extra delay
Hi Jose,
On Mon, 2017-12-04 at 14:02 +, Jose Abreu wrote:
> On 04-12-2017 13:16, Alexey Brodkin wrote:
> >
> > Option "kmsdev" "/dev/dri/card1"
>
> Which drm driver uses /dev/dri/card0? I'm seing drmOpen code and
> if you don't specify the busID it will fallback for the firs
If the firmware fails to load then ->fini() will be called before the
device has been initialised, causing the kernel to hang while trying
to write to a register. Add a test in ->fini() to avoid this issue.
This fixes a kernel hang on tegra124.
Fixes: b17de35a2ebbe ("drm/nouveau/bar: implement b
Hello,
I'm trying to use DisplayLink USB2.0-to-HDMI adapter as the one and only
video output and I want to get Xserver working on top of that.
I'm not very familiar with all the parts of Linux GPU/video stack
(especially its user-space counterpart) so my assumptions might be wrong
in that case pl
When neither HDMI nor DP is supported such as on the tegra124, the
sor->clk_out is not initialised and remains NULL. In this case, the
parent clock can't be assigned to it so revert to the previous
behaviour of assigning it to the main sor->clock instead.
This fixes a kernel hang on tegra124.
Fi
Hi Jose,
On Mon, 2017-12-04 at 11:50 +, Jose Abreu wrote:
> Hi Alexey,
>
> On 04-12-2017 11:32, Alexey Brodkin wrote:
> >
> > My first [probably incorrect] assumption is Xserver requires fbdev
> > (/dev/fbX)
> > and it cannot use DRI video card natively. Is that correct?
> >
> >
>
> Xser
crtc_state is being null checked in a previous code block, which implies
that such pointer might be null.
crtc_state is dereferenced in drm_atomic_helper_check_plane_state, hence
there is a potential null pointer dereference.
Fix this by warning-on and returning -EINVAL in case crtc_state is null
Hi Jose,
On Mon, 2017-12-04 at 15:55 +, Jose Abreu wrote:
> On 04-12-2017 14:53, Alexey Brodkin wrote:
> >
> > Full log you may find below.
>
> Sorry but I meant /var/log/Xorg.0.log file.
Ooops... sorry... here is it.
-Alexey
# cat /var/log/Xorg.0.log
[30.345]
X.Org X Server 1.19.
On Mon, Nov 27, 2017 at 12:21:10PM -0500, Alex Deucher wrote:
> On AMD GPUs, we use several mechanisms to fetch the vbios
> rom depending on the platform. We try to read the rom
> back via the rom BAR and fall back to other methods in
> some cases. This leads to spurious error messages
> from the
https://bugs.freedesktop.org/show_bug.cgi?id=103829
Marta Löfstedt changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #4 from Marta Löfst
On 12/05/2017 06:15 AM, Sean Paul wrote:
> This patch adds a new optional connector property to allow userspace to enable
> protection over the content it is displaying. This will typically be
> implemented
> by the driver using HDCP.
>
> The property is a tri-state with the following values:
> -
101 - 127 of 127 matches
Mail list logo
