https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #12 from Yunchao He ---
(In reply to Ilia Mirkin from comment #9)
> "Color-renderable" means "is it legal to use this format". It does NOT mean
> "the driver allows rendering to this format".
I am not a driver
https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #13 from Yunchao He ---
(In reply to Tapani Pälli from comment #11)
> (In reply to Yunchao He from comment #10)
> > (In reply to Tapani Pälli from comment #8)
> > > What comes to conformance, you should refer
https://bugs.freedesktop.org/show_bug.cgi?id=106517
--- Comment #3 from arkadiusz.hi...@intel.com ---
Hey,
Is this request for an freedesktop account at the same time? Because you need
one to get the commit rights.
Here's the guide to follow:
https://bugs.freedesktop.org/show_bug.cgi?id=99923
--- Comment #31 from sephirot...@gmail.com ---
Created attachment 139728
--> https://bugs.freedesktop.org/attachment.cgi?id=139728=edit
Shaders dump
Here is the shaders dump.
hitman_error is with the glitch
hitman_ok is without the glitch
I
Am 24.05.2018 um 02:31 schrieb Qiang Yu:
On Wed, May 23, 2018 at 11:44 PM, Daniel Vetter wrote:
On Wed, May 23, 2018 at 3:52 PM, Qiang Yu wrote:
On Wed, May 23, 2018 at 5:29 PM, Christian König
wrote:
Am 18.05.2018 um
Am 24.05.2018 um 03:38 schrieb Qiang Yu:
[SNIP]
Adding fence is done already, and I did wait it before unmap. But then
I see when
the buffer is shared between processes, the "perfect wait" is just
wait the fence
from this process's task, so it's better to also distinguish fences.
If so, I just
On Thu, May 24, 2018 at 8:27 AM, Christian König
wrote:
> Am 24.05.2018 um 02:31 schrieb Qiang Yu:
>>
>> On Wed, May 23, 2018 at 11:44 PM, Daniel Vetter wrote:
>>>
>>> On Wed, May 23, 2018 at 3:52 PM, Qiang Yu wrote:
On Wed,
Hi Maruthi,
FYI, the error/warning still remains.
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: 647c022484a10b3cffd6b1beed48ab63541b1ce5
commit: 2a6630b1095609b26a205b7c537594f3cde99c0a [114/487] ASoC: AMD: enable
ACP3x drivers build
config:
we may use rockchip_phy_typec struct in other driver, so split
it to separate header.
Signed-off-by: Lin Huang
---
Changes in v2:
- None
Changes in v3:
- None
Changes in v4:
- None
Changes in v5:
- None
Changes in v6:
- new patch here
Changes in v7:
- move new element to
On 2018-05-16 21:57, Stephen Boyd wrote:
Quoting Sandeep Panda (2018-05-14 22:52:42)
diff --git
a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
new file mode 100644
index 000..b82bb56
--- /dev/null
+++
With bus-type/bus-width properties in the endpoint nodes, the video-
interface of the connection can be specified for cases where the
heuristic fails to select the correct output mode. This can happen
e.g. if not all RGB pins are routed on the PCB; the driver has no
way of knowing this, and needs
Start list of actual chips compatible with "lvds-encoder".
Reviewed-by: Laurent Pinchart
Reviewed-by: Rob Herring
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/display/bridge/lvds-transmitter.txt | 8 +++-
This fits better with the drm_bridge callbacks for when this
driver becomes a drm_bridge.
Suggested-by: Laurent Pinchart
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/i2c/tda998x_drv.c | 64 ++-
1 file
From: Philipp Zabel
DLC provides a wide range of display solutions.
Website: http://www.dlcdisplay.com/
Signed-off-by: Philipp Zabel
Signed-off-by: Marco Felsch
Reviewed-by: Rob Herring
---
On Wed, May 16, 2018 at 10:05 AM, Souptick Joarder wrote:
> On Fri, May 11, 2018 at 2:52 PM, Russell King - ARM Linux
> wrote:
>> On Thu, May 10, 2018 at 08:34:48PM +0530, Souptick Joarder wrote:
>>> Use new return type vm_fault_t for fault handler in
This patch makes RC_CORE to be selected with this driver.
sil_sii8620 driver calls remote controller interfaces directly
so RC_CORE should be enabled mandatorily.
And some boards not using remote controller device don't really
need to know that RC_CORE config should be enabled to use sil_sii8620
2018년 05월 23일 19:59에 Marek Szyprowski 이(가) 쓴 글:
> Dear all,
>
> This patchset enables support for 2 more hardware windows in Exynos5433
> Decon's, what gives us 2 more overlay planes. This require enabling
> a few more clocks to get it working properly.
>
> My merge plan for this patchset:
>
From: Chris Zhong
We may support training outside firmware, so we need support
dpcd read/write to get the message or do some setting with
display.
Signed-off-by: Chris Zhong
Signed-off-by: Lin Huang
Reviewed-by: Sean Paul
This enables reuse of the machinery for the case where a drm_bridge
needs to do the same work via different interfaces.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/i2c/tda998x_drv.c | 36
1 file changed, 28 insertions(+), 8 deletions(-)
On 21/05/18 09:39, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Building for a 32-bit target results in warnings from casting
> between a 32-bit pointer and a 64-bit integer. Fix the warnings
> by casting those pointers to uintptr_t first.
If want to do training outside DP Firmware, need phy voltage swing
and pre_emphasis value.
Signed-off-by: Lin Huang
Reviewed-by: Rob Herring
---
Changes in v2:
- None
Changes in v3:
- modify property description and add this property to Example
Changes in
From: Philipp Zabel
This patch adds support for DLC DLC0700YZG-1 1024x600 LVDS panels
to the simple-panel driver.
Signed-off-by: Philipp Zabel
[m.fel...@pengutronix.de: fix typo in compatible dt-binding]
[m.fel...@pengutronix.de: add property
(We analyzed the crash and added the result below.)
We report the crash:
"KASAN: use-after-free Read in vgacon_invert_region"
This crash was found in v4.17-rc3. Specifically, memory access (read
operation) is invalid and which is detected by KASAN.
Analysis:
The function "vt_do_resize"
On Mon, 2018-04-30 at 11:18 +0100, Lee Jones wrote:
> On Fri, 27 Apr 2018, matthias@kernel.org wrote:
>
> > From: Matthias Brugger
> >
> > The MMSYS subsystem includes clocks and drm components.
> > This patch adds a MFD device to probe both drivers from the same
> >
On 05/18/2018 11:28 AM, Qiang Yu wrote:
> GP is a processor for OpenGL vertex shader
> processing.
>
> Signed-off-by: Qiang Yu
[...]
> +int lima_gp_init(struct lima_ip *ip)
> +{
> + struct lima_device *dev = ip->dev;
> + int err;
> +
> + lima_gp_print_version(ip);
It's GCC's -Wpointer-arith.
I'm stealing your code for another project that happened to have it on
by default. I'm trying to look for opportunities to contribute back
positive changes :-)
On Wed, May 23, 2018 at 11:09:28AM +0200, Daniel Vetter wrote:
> On Tue, May 22, 2018 at 11:33:35AM +0300,
On 23/05/18 12:00, Oleksandr Andrushchenko wrote:
> On 05/23/2018 12:19 PM, Juergen Gross wrote:
>> On 21/05/18 09:39, Oleksandr Andrushchenko wrote:
>>> From: Oleksandr Andrushchenko
>>>
>>> Building for a 32-bit target results in warnings from casting
>>>
On 05/18/2018 11:28 AM, Qiang Yu wrote:
> From: Lima Project Developers
>
> Signed-off-by: Qiang Yu
> Signed-off-by: Neil Armstrong
> Signed-off-by: Simon Shields
> Signed-off-by: Heiko Stuebner
On Wed, May 23, 2018 at 04:34:07PM +0200, Noralf Trønnes wrote:
> This is the first step in getting generic fbdev emulation.
> A drm_fb_helper_funcs.fb_probe function is added which uses the
> DRM client API to get a framebuffer backed by a dumb buffer.
>
> A transitional hack for tinydrm is
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #5 from Ricardo Ribalda ---
Created attachment 139734
--> https://bugs.freedesktop.org/attachment.cgi?id=139734=edit
dmesg 100k
--
You are receiving this mail because:
You are the assignee for the
On 24/05/18 01:03, Tony Lindgren wrote:
> Hi all,
>
> I bisected the n900 LCD issue to commit 24aac6011f70 ("drm: omapdrm:
> sdi: Allocate the sdi private data structure dynamically"). Reverting
> this patch makes LCD work for me again on n900.
>
> Any ideas?
This should help to get the SDI
The EC can expose a CEC bus, this patch adds the CEC related definitions
needed by the cros-ec-cec driver.
Signed-off-by: Neil Armstrong
Tested-by: Enric Balletbo i Serra
---
include/linux/mfd/cros_ec_commands.h | 85
On 24/05/2018 11:11, Hans Verkuil wrote:
> On 24/05/18 10:54, Neil Armstrong wrote:
>> The EC can expose a CEC bus, this patch adds the CEC related definitions
>> needed by the cros-ec-cec driver.
>>
>> Signed-off-by: Neil Armstrong
>> Tested-by: Enric Balletbo i Serra
Hi All,
The new Google "Fizz" Intel-based ChromeOS device is gaining CEC support
through it's Embedded Controller, to enable the Linux CEC Core to communicate
with it and get the CEC Physical Address from the correct HDMI Connector, the
following must be added/changed:
- Add the CEC sub-device
On 24/05/18 11:57, Neil Armstrong wrote:
> The EC can expose a CEC bus, this patch adds the CEC related definitions
> needed by the cros-ec-cec driver.
>
> Signed-off-by: Neil Armstrong
> Tested-by: Enric Balletbo i Serra
Reviewed-by: Hans
Hi all,
I bisected the n900 LCD issue to commit 24aac6011f70 ("drm: omapdrm:
sdi: Allocate the sdi private data structure dynamically"). Reverting
this patch makes LCD work for me again on n900.
Any ideas?
Regards,
Tony
___
dri-devel mailing list
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:21 EEST Kieran Bingham wrote:
> Calculate the top and bottom fields for the interlaced frames and
> utilise the extended display list command feature to implement the
> auto-field operations. This allows the DU to update the VSP2
On Fri, 11 May 2018, Dhinakaran Pandiyan wrote:
> Entry corresponding to 220 us setup time was missing. I am not aware of
> any specific bug this fixes, but this could potentially result in enabling
> PSR on a panel with a higher setup time requirement than
Am Donnerstag, den 24.05.2018, 10:43 +0200 schrieb Lucas Stach:
> Hi Tomi,
>
> Am Donnerstag, den 24.05.2018, 11:39 +0300 schrieb Tomi Valkeinen:
> > Hi Lucas,
> >
> > On 23/05/18 11:53, Lucas Stach wrote:
> >
> > > > With each run, I can see buffers being left lying around,
> > > > visible
> >
https://bugs.freedesktop.org/show_bug.cgi?id=104063
--- Comment #4 from taij...@posteo.de ---
What kernel version are you using? For me it stopped at some point - 4.16 is
fine.
--
You are receiving this mail because:
You are the assignee for the
On Mon, May 21, 2018 at 05:02:23PM +0200, Jernej Škrabec wrote:
> Hi,
>
> Dne ponedeljek, 21. maj 2018 ob 10:12:53 CEST je Maxime Ripard napisal(a):
> > On Sat, May 19, 2018 at 08:31:24PM +0200, Jernej Skrabec wrote:
> > > Expand HDMI PHY clock driver to support second clock parent.
> > >
> > >
On Wed, May 23, 2018 at 01:27:17PM +0100, Liviu Dudau wrote:
> On Wed, May 23, 2018 at 11:34:32AM +0200, Maarten Lankhorst wrote:
> > Op 18-05-18 om 17:17 schreef Liviu Dudau:
> > > Due to the fact that writeback connectors behave in a special way
> > > in DRM (they always report being
https://bugs.freedesktop.org/show_bug.cgi?id=106639
Bug ID: 106639
Summary: System display has noise when amdgpu module is being
loaded
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux
Hi Benson,
On 24/05/2018 07:47, Benson Leung wrote:
> Hi Neil, Hi Stefan,
>
> On Fri, May 18, 2018 at 03:05:02PM +0200, Neil Armstrong wrote:
>> The EC can expose a CEC bus, this patch adds the CEC related definitions
>> needed by the cros-ec-cec driver.
>> Having a 16 byte mkbp event size makes
On Thu, May 24, 2018 at 11:16:05AM +0200, Daniel Vetter wrote:
> On Wed, May 23, 2018 at 04:34:07PM +0200, Noralf Trønnes wrote:
> > +int drm_fb_helper_generic_probe(struct drm_fb_helper *fb_helper,
> > + struct drm_fb_helper_surface_size *sizes)
> > +{
> > + struct
On Wed, May 23, 2018 at 04:34:02PM +0200, Noralf Trønnes wrote:
> This patchset adds generic fbdev emulation for drivers that supports GEM
> based dumb buffers which support .gem_prime_vmap and gem_prime_mmap. An
> API is begun to support in-kernel clients in general.
>
> The CMA helper drivers
On 2018-05-23 11:39, Andrzej Hajda wrote:
*snip*
> Panels are managed by dsi host only if dsi host implements it, and it is
> up to dsi host author, it is not mandatory. The only case I am aware of
> is exynos-dsi. I guess most developers are not aware of the problem, or
> they do not care, or
On 24/05/18 11:57, Neil Armstrong wrote:
> The EC can expose a CEC bus, thus add the cros-ec-cec MFD sub-device
> when the CEC feature bit is present.
>
> Signed-off-by: Neil Armstrong
> Reviewed-by: Enric Balletbo i Serra
For whatever it
Hi Dave,
Three fixes for vmwgfx. Two are cc'd stable and fix host logging and its
error paths on 32-bit VMs. One is a fix for a hibernate flaw
introduced with the 4.17 merge window.
The following changes since commit 91ba9f28a3de97761c2b5fd5df5d88421268e507:
drm/vmwgfx: Set dmabuf_size when
The EC can expose a CEC bus, thus add the cros-ec-cec MFD sub-device
when the CEC feature bit is present.
Signed-off-by: Neil Armstrong
Reviewed-by: Enric Balletbo i Serra
---
drivers/mfd/cros_ec_dev.c | 16
1 file
https://bugs.freedesktop.org/show_bug.cgi?id=106597
taij...@posteo.de changed:
What|Removed |Added
Attachment #139723|0 |1
is obsolete|
On 24.05.2018 11:32, Inki Dae wrote:
> This patch makes RC_CORE to be selected with this driver.
>
> sil_sii8620 driver calls remote controller interfaces directly
> so RC_CORE should be enabled mandatorily.
>
> And some boards not using remote controller device don't really
> need to know that
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")
DP firmware uses fixed phy config values to do training, but some
boards need to adjust these values to fit for their unique hardware
design. So get phy config values from dts and use software link training
instead of relying on firmware, if software training fail, keep firmware
training as a
the phy config values used to fix in dp firmware, but some boards
need change these values to do training and get the better eye diagram
result. So support that in phy driver.
Signed-off-by: Chris Zhong
Signed-off-by: Lin Huang
---
Changes in v2:
-
On Wed, May 23, 2018 at 10:53:33AM +0200, Daniel Vetter wrote:
> On Sun, May 20, 2018 at 09:22:31AM +0300, Haneen Mohammed wrote:
> > On Wed, May 16, 2018 at 08:56:21PM -0300, Rodrigo Siqueira wrote:
> > > This commit adds the essential infrastructure for around CRTCs which
> > > is composed of: a
On Wed, May 23, 2018 at 10:48:15AM +0200, Daniel Vetter wrote:
> On Tue, May 22, 2018 at 09:27:07AM +0100, Russell King wrote:
> > On Tue, May 22, 2018 at 10:53:49AM +1000, Dave Airlie wrote:
> > > Sorry I missed this, just fell between the cracks,
> > >
> > > Any reason you can't/don't use git
On 2018-05-23 14:38, Andrzej Hajda wrote:
> On 23.05.2018 12:46, Peter Rosin wrote:
>> On 2018-05-23 11:39, Andrzej Hajda wrote:
>>
>> *snip*
>>
>>> Panels are managed by dsi host only if dsi host implements it, and it is
>>> up to dsi host author, it is not mandatory. The only case I am aware of
On Wed, May 23, 2018 at 7:58 PM, Qiang Yu wrote:
> On Thu, May 24, 2018 at 1:24 AM, Rob Herring wrote:
>> On Fri, May 18, 2018 at 05:27:58PM +0800, Qiang Yu wrote:
>>> From: Lima Project Developers
>>>
>>> Signed-off-by: Qiang
On 24/05/18 10:55, Neil Armstrong wrote:
> The ChromeOS Embedded Controller can expose a CEC bus, this patch add the
> driver for such feature of the Embedded Controller.
>
> This driver is part of the cros-ec MFD and will be add as a sub-device when
> the feature bit is exposed by the EC.
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #6 from Ricardo Ribalda ---
Eventhough it is not comparable, for reference: this is the result with fgrlx.
root@qt5022:~# time clpeak
Platform: AMD Accelerated Parallel Processing
Device: AMD G-T56N
On 24/05/18 10:54, Neil Armstrong wrote:
> The EC can expose a CEC bus, this patch adds the CEC related definitions
> needed by the cros-ec-cec driver.
>
> Signed-off-by: Neil Armstrong
> Tested-by: Enric Balletbo i Serra
> ---
>
In non device-tree world, we can need to get the notifier by the driver
name directly and eventually defer probe if not yet created.
This patch adds a variant of the get function by using the device name
instead and will not create a notifier if not yet created.
But the i915 driver exposes at
Hi Tomi,
Am Donnerstag, den 24.05.2018, 11:39 +0300 schrieb Tomi Valkeinen:
> Hi Lucas,
>
> On 23/05/18 11:53, Lucas Stach wrote:
>
> > > With each run, I can see buffers being left lying around, visible
> > > in
> > > both omapdrm's and etnaviv's 'gem' debugfs file. And they're
> > > there
> >
The EC can expose a CEC bus, thus add the cros-ec-cec MFD sub-device
when the CEC feature bit is present.
Signed-off-by: Neil Armstrong
Reviewed-by: Enric Balletbo i Serra
---
drivers/mfd/cros_ec_dev.c | 16
1 file
Hi Jani,
I was able to update my kernel to 4.6 which has the DRM_DP_AUX_CHARDEV in the
Kconfig file linux-4.6\drivers\gpu\drm. Though I also add DRM_DP_AUX_CHARDEV=y
in kernel config. When invoke uname -r, I could see that the kernel is now 4.6.
How can I verify the DRM_DP_AUX_CHARDEV takes
On Mon, May 14, 2018 at 9:56 PM, Daniel Vetter wrote:
> On Thu, May 10, 2018 at 02:51:38PM -0400, Sean Paul wrote:
>> On Thu, May 10, 2018 at 07:58:11PM +0530, Souptick Joarder wrote:
>> > Hi Sean,
>> >
>> > On Mon, Apr 16, 2018 at 8:32 PM, Souptick Joarder
On Thu, May 24, 2018 at 5:41 PM, Christian König
wrote:
> Am 24.05.2018 um 11:24 schrieb Qiang Yu:
>>
>> On Thu, May 24, 2018 at 2:46 PM, Christian König
>> wrote:
>> [SNIP]
>>>
>>> Because of this we have a separate tracking in amdgpu so that
Hi All,
The new Google "Fizz" Intel-based ChromeOS device is gaining CEC support
through it's Embedded Controller, to enable the Linux CEC Core to communicate
with it and get the CEC Physical Address from the correct HDMI Connector, the
following must be added/changed:
- Add the CEC sub-device
This patchs adds the cec_notifier feature to the intel_hdmi part
of the i915 DRM driver. It uses the HDMI DRM connector name to differentiate
between each HDMI ports.
The changes will allow the i915 HDMI code to notify EDID and HPD changes
to an eventual CEC adapter.
Signed-off-by: Neil Armstrong
On Wed, May 23, 2018 at 12:56:25PM +0300, Jani Nikula wrote:
> On Wed, 23 May 2018, Daniel Vetter wrote:
> > On Tue, May 22, 2018 at 11:33:35AM +0300, Jani Nikula wrote:
> >> On Mon, 21 May 2018, Maya Rashish wrote:
> >> > In drm_dp_i2c_drain_msg we do msg.buffer
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #21 from Lukas Wunner ---
Okay so the reason the HDA controller doesn't suspend is because the
codec_powered bitmask is not null:
snd_hda_intel :01:00.1: azx_runtime_idle: !power_save_controller = 0,
The ChromeOS Embedded Controller can expose a CEC bus, this patch add the
driver for such feature of the Embedded Controller.
This driver is part of the cros-ec MFD and will be add as a sub-device when
the feature bit is exposed by the EC.
The controller will only handle a single logical address
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:19 EEST Kieran Bingham wrote:
> Extended display list headers allow pre and post command lists to be
> executed by the VSP pipeline. This provides the base support for
> features such as AUTO_FLD (for interlaced support) and
On Wed, May 23, 2018 at 04:34:09PM +0200, Noralf Trønnes wrote:
> This switches the CMA helper drivers that use its fbdev emulation over
> to the generic fbdev emulation. It's the first phase of using generic
> fbdev. A later phase will use DRM client callbacks for the
> lastclose/hotplug/remove
On Thu, 24 May 2018, John Sledge wrote:
> I was able to update my kernel to 4.6 which has the DRM_DP_AUX_CHARDEV
> in the Kconfig file linux-4.6\drivers\gpu\drm. Though I also
> add DRM_DP_AUX_CHARDEV=y in kernel config. When invoke uname -r, I
> could see that the kernel
On Wed, May 23, 2018 at 10:24 AM, Rob Herring wrote:
> On Fri, May 18, 2018 at 05:27:58PM +0800, Qiang Yu wrote:
>> From: Lima Project Developers
>>
>> Signed-off-by: Qiang Yu
>> Signed-off-by: Heiko Stuebner
On Wed, May 23, 2018 at 5:36 PM, Ben Skeggs wrote:
> On Thu, May 24, 2018 at 8:48 AM, Kees Cook wrote:
>> On Thu, Apr 26, 2018 at 4:25 PM, Kees Cook wrote:
>>> On Thu, Mar 15, 2018 at 7:05 PM, Ben Skeggs
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #24 from Lukas Wunner ---
(In reply to taijian from comment #22)
> $ grep . /sys/bus/hdaudio/devices/hdaudioC1D0/widgets/*/power_caps
> /sys/bus/hdaudio/devices/hdaudioC1D0/widgets/01/power_caps:0xc009
On 23/05/18 13:36, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Building for a 32-bit target results in warnings from casting
> between a 32-bit pointer and a 64-bit integer. Fix the warnings
> by casting those pointers to uintptr_t first.
On Wed, May 23, 2018 at 11:15:18AM +0200, Daniel Vetter wrote:
> On Mon, May 21, 2018 at 10:04:23PM -0300, Rodrigo Siqueira wrote:
> > This series of patches add a centralized initialization mechanism, a
> > single CRTC with a plane, an encoder, and extra module information.
> >
> > Changes in
This patchs adds the cec_notifier feature to the intel_hdmi part
of the i915 DRM driver. It uses the HDMI DRM connector name to differentiate
between each HDMI ports.
The changes will allow the i915 HDMI code to notify EDID and HPD changes
to an eventual CEC adapter.
Signed-off-by: Neil Armstrong
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:14 EEST Kieran Bingham wrote:
> Both vsp1_dl_list_commit() and __vsp1_dl_list_put() walk the display
> list chain referencing the nodes as children, when in reality they are
> siblings.
>
> Update the terminology to 'dl_next' to
Am 24.05.2018 um 11:24 schrieb Qiang Yu:
On Thu, May 24, 2018 at 2:46 PM, Christian König
wrote:
[SNIP]
Because of this we have a separate tracking in amdgpu so that we not only
know who is using which BO, who is using which VM.
amdgpu's VM implementation seems too
Hi Kieran,
Thank you for the patch.
On Thursday, 3 May 2018 16:36:12 EEST Kieran Bingham wrote:
> The pixel format is 'unsupported'. Fix the small debug message which
> incorrectly declares this.
>
> Signed-off-by: Kieran Bingham
Reviewed-by: Laurent
This patch makes RC_CORE to be selected with this driver.
sil_sii8620 driver calls remote controller interfaces directly
so RC_CORE should be enabled mandatorily.
And some boards not using remote controller device don't really
need to know that RC_CORE config should be enabled to use sil_sii8620
On 05/24/2018 10:32 AM, Daniel Vetter wrote:
On Wed, May 23, 2018 at 11:45:00PM +0200, Thomas Hellstrom wrote:
Hi, Noralf.
A couple of issues below:
On 05/23/2018 04:34 PM, Noralf Trønnes wrote:
This the beginning of an API for in-kernel clients.
First out is a way to get a framebuffer
On Wed, May 23, 2018 at 04:34:11PM +0200, Noralf Trønnes wrote:
> This adds a drm_fbdev_generic_setup() function that sets up generic
> fbdev emulation with client callbacks for lastclose, hotplug and
> remove/unregister.
>
> Signed-off-by: Noralf Trønnes
> ---
>
In non device-tree world, we can need to get the notifier by the driver
name directly and eventually defer probe if not yet created.
This patch adds a variant of the get function by using the device name
instead and will not create a notifier if not yet created.
But the i915 driver exposes at
On Thu, May 24, 2018 at 2:46 PM, Christian König
wrote:
> Am 24.05.2018 um 03:38 schrieb Qiang Yu:
>
> [SNIP]
>
> Adding fence is done already, and I did wait it before unmap. But then
> I see when
> the buffer is shared between processes, the "perfect wait" is just
>
https://bugs.freedesktop.org/show_bug.cgi?id=106597
Lukas Wunner changed:
What|Removed |Added
Attachment #139688|0 |1
is obsolete|
Hi CK,
On Thu, 2018-05-24 at 09:26 +0800, CK Hu wrote:
> Hi, Stu:
>
> On Wed, 2018-05-23 at 17:28 +0800, Stu Hsieh wrote:
> > On Wed, 2018-05-23 at 13:23 +0800, CK Hu wrote:
> > > Hi, Stu:
> > >
> > > I've some inline comment.
> > >
> > > On Wed, 2018-05-23 at 10:25 +0800, Stu Hsieh wrote:
> >
Hi!
I naively thought that since there was support for both nxp,tda19988 (in
the tda998x driver) and the atmel-hlcdc, things would be a smooth ride.
But it wasn't, so I started looking around and realized I had to fix
things.
In v1 and v2 I fixed things by making the atmel-hlcdc driver a master
Dear all,
I just noticed that replying to my earlier email thread failed, and that
I thereby created a new thread. The original thread is the following one:
https://lkml.org/lkml/2018/2/16/274
I am sorry for the confusion!
Best,
Norbert
On 05/23/2018 08:22 AM, Norbert Manthey wrote:
> The
This serie adds support for the DLC Display Co. DLC0700YZG-1 7.0" WSVGA
TFT LCD panel. The customer isn't listed as vendor so we have to add the
vendor prefix too.
Philipp Zabel (2):
dt-bindings: Add vendor prefix for DLC Display Co., Ltd.
gpu: drm/panel: Add DLC DLC0700YZG-1 panel
This makes this driver work with all(?) drivers that are not
componentized and instead expect to connect to a panel/bridge. That
said, the only one tested is atmel-hlcdc.
This hooks the relevant work function previously called by the encoder
and the component also to the bridge, since the encoder
On 24/05/18 10:54, Neil Armstrong wrote:
> In non device-tree world, we can need to get the notifier by the driver
> name directly and eventually defer probe if not yet created.
>
> This patch adds a variant of the get function by using the device name
> instead and will not create a notifier if
On Thu, Apr 26, 2018 at 4:25 PM, Kees Cook wrote:
> On Thu, Mar 15, 2018 at 7:05 PM, Ben Skeggs wrote:
>> On 14 March 2018 at 21:08, Thierry Reding wrote:
>>> On Tue, Mar 13, 2018 at 11:24:11AM -0500, Gustavo A. R. Silva wrote:
This prepares for being a drm_bridge which will not register the
encoder. That makes the connector the better choice.
Reviewed-by: Laurent Pinchart
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
1 file changed, 1
Hi Lucas,
2018-05-23 14:08 GMT+02:00 Tomi Valkeinen :
> On 23/05/18 11:53, Lucas Stach wrote:
> > Hi Tomi,
> >
> > Am Mittwoch, den 23.05.2018, 11:40 +0300 schrieb Tomi Valkeinen:
> >> Hi Lucas,
> >>
> >> Julien has written an X driver for OMAP5 SoC (which has Vivante's
>
1 - 100 of 204 matches
Mail list logo