And I forgot to add that this is V2, I've just added .bpc.
On 30/09/2015 at 23:42:17 +0200, Alexandre Belloni wrote :
> From: Josh Wu
>
> The QiaoDian Xianshi QD43003C0-40 is a 4"3 TFT LCD panel.
>
> Timings from the OTA5180A document, ver 0.9, section
> 10.1.1:
> http://www.orientdisplay.com
From: Josh Wu
The QiaoDian Xianshi QD43003C0-40 is a 4"3 TFT LCD panel.
Timings from the OTA5180A document, ver 0.9, section
10.1.1:
http://www.orientdisplay.com/pdf/OTA5180A.pdf
Signed-off-by: Josh Wu
Signed-off-by: Alexandre Belloni
---
.../devicetree/bindings/panel/qd,qd43003c0-40.txt
Use "qiaodian" as the vendor prefix for QiaoDian Xianshi Corporation in
device tree compatible strings.
Signed-off-by: Alexandre Belloni
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes
On Wed, Sep 30 2015, kbuild test robot wrote:
> Hi Rasmus,
>
> [auto build test results on v4.3-rc3 -- if it's inappropriate base, please
> ignore]
>
>
> coccinelle warnings: (new ones prefixed by >>)
>
>>> drivers/gpu/drm/vmwgfx/vmwgfx_surface.c:771:1-13: alloc with no test,
>>> possible model
Hi Emil,
On 2015ë
09ì 30ì¼ 21:19, Emil Velikov wrote:
> Hi Inki,
>
> On 30 September 2015 at 12:21, Inki Dae wrote:
>> This patch removes unnecessary pm suspend/resume functions.
>>
>> All kms sub drivers will be controlled by top of Exynos drm driver
>> and connector dpms so these sub driv
Fix the following warnings:
CC drivers/gpu/drm/i915/intel_audio.o
drivers/gpu/drm/i915/intel_audio.c: In function âhsw_audio_codec_enableâ:
drivers/gpu/drm/i915/intel_audio.c:332:39: warning: passing argument 2 of
âaudio_rate_need_progâ discards âconstâ qualifier from pointer t
Signed-off-by: Rasmus Villemoes
---
drivers/gpu/vga/vgaarb.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/vga/vgaarb.c b/drivers/gpu/vga/vgaarb.c
index a0b433456107..3166e4bc4eb6 100644
--- a/drivers/gpu/vga/vgaarb.c
+++ b/drivers/gpu/vga/vgaarb.c
@@ -531,7 +
t thousands before
today.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/22b1819d/attachment-0001.html>
Signed-off-by: Rasmus Villemoes
---
drivers/gpu/drm/omapdrm/tcm-sita.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/omapdrm/tcm-sita.c
b/drivers/gpu/drm/omapdrm/tcm-sita.c
index efb609510540..6df1f2a1bc52 100644
--- a/drivers/gpu/drm/omapdrm/tcm-sita
Signed-off-by: Rasmus Villemoes
---
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
index 64b50409fa07..38d910ae9b21 100644
--- a/drivers/gpu/drm/v
g else entirely.
Yea, could be unrelated.
I haven't seen thousands until Today so that aspect could be to do with the
patches.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<ht
ug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/cb45abb8/attachment.html>
use:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/0290553b/attachment.html>
On 30.09.2015 20:47, Alex Deucher wrote:
> If a driver uses the cursor_set2 crtc callback rather than
> cursor_set, use that. This fixes the fbdev helper for drivers
> that use cursor_set2.
>
> Change-Id: I127d3f8e72789ba70c3648140f87c6187864e130
> Signed-off-by: Alex Deucher
I'm not very famili
read from '' (0x) (0)
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/a16562c2/attachment.html>
On 09/30/2015 03:39 PM, Dieter Nützel wrote:
> Hello Tapani,
>
> this was your patch.
> Any comments?
>
It is probably a duplicate bug for 92173. I've sent a patch to mesa-dev
which should fix the issue:
http://lists.freedesktop.org/archives/mesa-dev/2015-September/095521.html
> Thanks,
> Di
Hi,
On 2015ë
09ì 28ì¼ 01:11, Charles Keepax wrote:
> If binding failed calling exynos_dp_enable in exynos_dp_resume will
> result in several NULL pointer dereferences. It is much better to
> simply skip suspend/resume handling if bind has failed, do so by
> checking if a drm_dev exists.
Than
This patch removes unnecessary pm suspend/resume functions.
All kms sub drivers will be controlled by top of Exynos drm driver
and connector dpms so these sub drivers shouldn't have their own
pm interfaces.
Signed-off-by: Inki Dae
---
drivers/gpu/drm/exynos/exynos_dp_core.c | 23 ---
On Wed, Sep 30, 2015 at 07:36:19PM +0200, Borislav Petkov wrote:
> Right, so this fixes the issue on my box, courtesy of Joerg. WE
> basically don't disable the IRQ on MSI-enabled devices. The AMD IOMMU
> uses a barebones PCI device but not a PCI driver, which would be an
> overkill.
Well, not onl
On Thu, Oct 01, 2015 at 01:00:44AM +0800, Jiang Liu wrote:
> Thanks Joerg, that makes sense. If some driver tries to binding to the
> IOMMU device, it will trigger the scenario as you described. For
> example, Xen backend driver will try to probe all PCI devices
> if enabled. I will do more invest
o faults but after about 10 minutes it hung.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/5f8b4757/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=105051
--- Comment #9 from Tim Sammut ---
(In reply to Michel Dänzer from comment #8)
>
> That's an apple-gmux change, not a radeon driver change. Please reassign the
> component of this bug report accordingly.
Thanks, I'd be happy to, but I don't se
On Wed, Sep 30, 2015 at 03:31:34PM +0100, Rob Bradford wrote:
> Hi Shashank, some feedback below that you would be great to get
> addressed before your next version.
>
> On Wed, 2015-09-16 at 23:07 +0530, Shashank Sharma wrote:
> > BDW/SKL/BXT platforms support various Gamma correction modes
> > w
On Thu, Oct 01, 2015 at 01:00:44AM +0800, Jiang Liu wrote:
> Thanks Joerg, that makes sense. If some driver tries to binding to
> the IOMMU device, it will trigger the scenario as you described. For
> example, Xen backend driver will try to probe all PCI devices if
> enabled. I will do more investi
||
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/07cecc41/attachment.html>
From: Ville Syrjälä
If we couldn't get a high precisions vblank timestamp, we currently
store a zeroed timestamp instead and assume the next vblank irq to
get us something better. This makes sense when trying to update the
timestamp from eg. vblank enable. But if we do this from the vblank
irq
Hi Shashank, some feedback on the CSC code below.
On Thu, 2015-08-06 at 22:08 +0530, Shashank Sharma wrote:
> From: Kausal Malladi
>
> BDW/SKL/BXT support Color Space Conversion (CSC) using a 3x3 matrix
> that needs to be programmed into respective CSC registers.
>
> This patch does the follow
From: Gustavo Padovan
fimd_dp_clock_enable() was setting the always to enabled,
this patch fix this to actually use the value that is set to 'val'.
Reported-by: Emilio López
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 +-
1 file changed, 1 insertion(+), 1
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20150930/c5efb9f8/attachment.html>
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20150930/a459669a/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/4d74c49e/attachment.html>
Hi Dave,
radeon and amdgpu fixes for 4.3.
- backlight s/r fixes
- typo fix from Dan
- vm debugging fix
- remove import_gpu_mem after discussion with Daniel
The following changes since commit fd03420b5624617a708fb9b13634b41b37c22cfa:
Merge tag 'drm-intel-fixes-2015-09-24' of
git://anongit.free
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/e29289a8/attachment.html>
Hi Krzysztof,
On 09/30/2015 04:26 PM, Krzysztof Kozlowski wrote:
> On 30.09.2015 17:20, Yakir Yang wrote:
>> Hi Krzysztof,
>>
>> On 09/30/2015 03:34 PM, Krzysztof Kozlowski wrote:
>>> On 30.09.2015 16:19, Yakir Yang wrote:
Hi Krzysztof,
On 09/30/2015 01:32 PM, Krzysztof Kozlowski wr
On Wed, 30 Sep 2015, Geliang Tang wrote:
> Fix the following warnings:
>
> CC drivers/gpu/drm/i915/intel_audio.o
> drivers/gpu/drm/i915/intel_audio.c: In function âhsw_audio_codec_enableâ:
> drivers/gpu/drm/i915/intel_audio.c:332:39: warning: passing argument 2 of
> âaudio_rate_need_
Am Freitag, den 18.09.2015, 15:33 -0500 schrieb Rob Herring:
> On Fri, Sep 18, 2015 at 11:11 AM, Philipp Zabel
> wrote:
> > From: CK Hu
> >
> > Add device tree binding documentation for the display subsystem in
> > Mediatek MT8173 SoCs.
> >
> > Signed-off-by: CK Hu
> > Signed-off-by: Philipp Za
From: Jie Qiu
MT8173 HDMI hardware has a output control bit to enable/disable HDMI
output. Because of security reason, so this bit can ONLY be controlled
in ARM supervisor mode. Now the only way to enter ARM supervisor is the
ARM trusted firmware. So atf provides a API for HDMI driver to call to
From: Daniel Kurtz
This patch adds drivers for the HDMI bridge connected to the DPI0
display subsystem function block, for the HDMI DDC block, and for
the HDMI PHY to support HDMI output.
Signed-off-by: Jie Qiu
Signed-off-by: Philipp Zabel
---
drivers/gpu/drm/mediatek/Kconfig| 6
Add the device tree binding documentation for Mediatek HDMI,
HDMI PHY and HDMI DDC devices.
Signed-off-by: Philipp Zabel
---
.../bindings/drm/mediatek/mediatek,hdmi.txt| 117 +
1 file changed, 117 insertions(+)
create mode 100644
Documentation/devicetree/bindings/dr
From: Jie Qiu
Add DPI connector/encoder to support HDMI output via the
attached HDMI bridge.
Signed-off-by: Jie Qiu
Signed-off-by: Philipp Zabel
---
drivers/gpu/drm/mediatek/Makefile | 3 +-
drivers/gpu/drm/mediatek/mtk_dpi.c | 703
drivers/gpu/dr
From: CK Hu
This patch add a drm encoder/connector driver for the MIPI DSI function
block of the Mediatek display subsystem and a phy driver for the MIPI TX
D-PHY control module.
Signed-off-by: Jitao Shi
Signed-off-by: Philipp Zabel
---
Changes since v2:
- Split DSI and MIPI TX (MIPI D-PHY) d
From: CK Hu
This patch adds an initial DRM driver for the Mediatek MT8173 DISP
subsystem. It currently supports two fixed output streams from the
OVL0/OVL1 sources to the DSI0/DPI0 sinks, respectively.
Signed-off-by: CK Hu
Signed-off-by: YT Shen
Signed-off-by: Philipp Zabel
---
Changes since
From: CK Hu
Add device tree binding documentation for the display subsystem in
Mediatek MT8173 SoCs. The display function block nodes are grouped
under a display-subsystem node.
Signed-off-by: CK Hu
Signed-off-by: Philipp Zabel
---
Changes since v2:
- Grouped DISP function block nodes under t
Hi,
this is an update to the MT8173 DRM support RFC. These patches have
a build dependency on two other patches on top of v4.3-rc1:
https://patchwork.kernel.org/patch/6914941 ("iommu: Implement common IOMMU
ops for DMA mapping"), and
https://patchwork.kernel.org/patch/6928621 ("memory: mediatek: A
likely a duplicate for #92122
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/3f3334f9/attachment.html>
On 30.09.2015 17:20, Yakir Yang wrote:
> Hi Krzysztof,
>
> On 09/30/2015 03:34 PM, Krzysztof Kozlowski wrote:
>> On 30.09.2015 16:19, Yakir Yang wrote:
>>> Hi Krzysztof,
>>>
>>> On 09/30/2015 01:32 PM, Krzysztof Kozlowski wrote:
On 22.09.2015 16:37, Yakir Yang wrote:
> Both hsync/vsync po
On Wed, Sep 30, 2015 at 4:42 PM, Alexandre Belloni
wrote:
> Use "qiaodian" as the vendor prefix for QiaoDian Xianshi Corporation in
> device tree compatible strings.
>
> Signed-off-by: Alexandre Belloni
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 inse
Hi Annie,
This might add a day or two, but considering this is a long weekend in India,
you can expect the patches by mid next week.
Regards
Shashank
-Original Message-
From: Matheson, Annie J
Sent: Wednesday, September 30, 2015 10:01 PM
To: Sharma, Shashank
Cc: Bradford, Robert; Roper
On Wed, Sep 30, 2015 at 04:08:02PM +0200, Daniel Vetter wrote:
> On Wed, Sep 30, 2015 at 04:46:48PM +0300, ville.syrjala at linux.intel.com
> wrote:
> > From: Ville Syrjälä
> >
> > drm_vblank_count() returns the software counter. We should not pretend
> > it's the hw counter since we use the h
On Wed, Sep 30, 2015 at 02:29:49PM +0200, Vincent Abriou wrote:
> Drivers with software vblank counter relies on the on drm core to update
> vblank counter and they should not be concern about the warning that
> check hardware counter coherency.
>
> Further, the generic message that tracks the cur
d-pm-sysfs-files-late.patch
Type: text/x-patch
Size: 4961 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/ef5aa517/attachment-0001.bin>
On Tue, Sep 29, 2015 at 8:36 PM, Marcel Partap wrote:
> Hi,
> friend send me this screenshot over whatsapp, complaining that her
> system wouldn't start up since yesterday. What gives?
Looks like she installed some tool that attempts to change the power
state via sysfs during init which could hap
From: Ville Syrjälä
Make the 'pipe' argument to drm_vblank_count() unsigned as it is
everwhere else.
Cc: Vincent Abriou
Cc: Thierry Reding
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/drm_irq.c | 2 +-
include/drm/drmP.h| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
From: Ville Syrjälä
drm_vblank_count() returns the software counter. We should not pretend
it's the hw counter since we use the hw counter to figuere out what the
software counter value should be. So instead provide a new function
drm_vblank_no_hw_counter() for drivers that don't have a real hw
> -Original Message-
> From: dri-devel [mailto:dri-devel-bounces at lists.freedesktop.org] On Behalf
> Of Ville Syrjälä
> Sent: mercredi 30 septembre 2015 16:15
> To: Daniel Vetter
> Cc: Thierry Reding; dri-devel at lists.freedesktop.org
> Subject: Re: [PATCH 1/2] drm: Stop using drm_vb
cation/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/18a7f916/attachment-0001.sig>
On Wed, Sep 30, 2015 at 10:46:59AM +0200, Daniel Vetter wrote:
> This was only used for the ums+gem combo, so ripe for removal now that
> we only have kms code left.
>
> v2: Drop fence_reg_start since it's now unused, noticed by Ville.
>
> Cc: Ville Syrjälä
> Signed-off-by: Daniel Vetter
lgt
On 30.09.2015 16:19, Yakir Yang wrote:
> Hi Krzysztof,
>
> On 09/30/2015 01:32 PM, Krzysztof Kozlowski wrote:
>> On 22.09.2015 16:37, Yakir Yang wrote:
>>> Both hsync/vsync polarity and interlace mode can be parsed from
>>> drm display mode, and dynamic_range and ycbcr_coeff can be judge
>>> by th
Shashank,
Please let us know when the next patch series would be ready assuming you
incorporate the feedback from Rob.
I would like to hope we're done with feedback at this point.
Thanks.
Annie Matheson
> On Sep 30, 2015, at 9:25 AM, Sharma, Shashank
> wrote:
>
> Hey Rob,
>
> Thanks f
Hey Rob,
Thanks for the feedback, and the testing efforts.
I will check into your suggestions and get back.
Regards
Shashank
-Original Message-
From: Bradford, Robert
Sent: Wednesday, September 30, 2015 8:02 PM
To: Sharma, Shashank; Roper, Matthew D; Bish, Jim; Smith, Gary K; dri-deve
s_dp {
> ...
> hsync-active-high;
> }
>
> It will return -EOVERFLOW which means it would be broken now...
Whoops, thanks for your remind, after try that, I do see over flow error.
static void *of_find_property_value_of_size(const struct device_node *np,
const char *propname, u32 len)
{
if (len > prop->length)
return ERR_PTR(-EOVERFLOW);
...
}
So I though code should be:
if (of_property_read_bool(dp_node, "hsync-active-high"))
video->h_sync_polarity = true;
And we can't provide full backward compatibility for this property, cause
the previous exynos_dp driver would set this timing value to "false" when
property not defined, but analogix_dp driver keep this timing value
corresponding to "drm_display_mode" when property not found.
Thanks,
- Yakir
> Best regards,
> Krzysztof
>
>
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/1a4256b6/attachment.html>
On Wed, Sep 30, 2015 at 04:46:48PM +0300, ville.syrjala at linux.intel.com
wrote:
> From: Ville Syrjälä
>
> drm_vblank_count() returns the software counter. We should not pretend
> it's the hw counter since we use the hw counter to figuere out what the
> software counter value should be. So in
ize: 4545 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/19a25018/attachment.bin>
On 30 September 2015 at 14:46, Inki Dae wrote:
> Hi Emil,
>
> On 2015ë
09ì 30ì¼ 21:19, Emil Velikov wrote:
>> Hi Inki,
>>
>> On 30 September 2015 at 12:21, Inki Dae wrote:
>>> This patch removes unnecessary pm suspend/resume functions.
>>>
>>> All kms sub drivers will be controlled by top of
Hi Shashank, some feedback below that you would be great to get
addressed before your next version.
On Wed, 2015-09-16 at 23:07 +0530, Shashank Sharma wrote:
> BDW/SKL/BXT platforms support various Gamma correction modes
> which are:
> 1. Legacy 8-bit mode
> 2. 10-bit mode
> 3. 10-bit Split Gamma
Hi Krzysztof,
On 09/30/2015 01:39 PM, Krzysztof Kozlowski wrote:
> On 22.09.2015 16:43, Yakir Yang wrote:
>> After exynos_dp have been split the common IP code into analogix_dp driver,
>> the analogix_dp driver have deprecated some Samsung platform properties which
>> could be dynamically parsed f
nk_train link_train;
>> struct work_struct hotplug_work;
>> struct phy *phy;
>> diff --git a/drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c
>> b/drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c
>> index a388c0a..861097a 100644
>> --- a/drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c
>> +++ b/drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c
>> @@ -1084,15 +1084,15 @@ void analogix_dp_set_video_color_format(struct
>> analogix_dp_device *dp)
>> u32 reg;
>>
>> /* Configure the input color depth, color space, dynamic range */
>> -reg = (dp->video_info->dynamic_range << IN_D_RANGE_SHIFT) |
>> -(dp->video_info->color_depth << IN_BPC_SHIFT) |
>> -(dp->video_info->color_space << IN_COLOR_F_SHIFT);
>> +reg = (dp->video_info.dynamic_range << IN_D_RANGE_SHIFT) |
>> +(dp->video_info.color_depth << IN_BPC_SHIFT) |
>> +(dp->video_info.color_space << IN_COLOR_F_SHIFT);
>> writel(reg, dp->reg_base + ANALOGIX_DP_VIDEO_CTL_2);
>>
>> /* Set Input Color YCbCr Coefficients to ITU601 or ITU709 */
>> reg = readl(dp->reg_base + ANALOGIX_DP_VIDEO_CTL_3);
>> reg &= ~IN_YC_COEFFI_MASK;
>> -if (dp->video_info->ycbcr_coeff)
>> +if (dp->video_info.ycbcr_coeff)
>> reg |= IN_YC_COEFFI_ITU709;
>> else
>> reg |= IN_YC_COEFFI_ITU601;
>> @@ -1229,17 +1229,17 @@ void analogix_dp_config_video_slave_mode(struct
>> analogix_dp_device *dp)
>>
>> reg = readl(dp->reg_base + ANALOGIX_DP_VIDEO_CTL_10);
>> reg &= ~INTERACE_SCAN_CFG;
>> -reg |= (dp->video_info->interlaced << 2);
>> +reg |= (dp->video_info.interlaced << 2);
>> writel(reg, dp->reg_base + ANALOGIX_DP_VIDEO_CTL_10);
>>
>> reg = readl(dp->reg_base + ANALOGIX_DP_VIDEO_CTL_10);
>> reg &= ~VSYNC_POLARITY_CFG;
>> -reg |= (dp->video_info->v_sync_polarity << 1);
>> +reg |= (dp->video_info.v_sync_polarity << 1);
>> writel(reg, dp->reg_base + ANALOGIX_DP_VIDEO_CTL_10);
>>
>> reg = readl(dp->reg_base + ANALOGIX_DP_VIDEO_CTL_10);
>> reg &= ~HSYNC_POLARITY_CFG;
>> -reg |= (dp->video_info->h_sync_polarity << 0);
>> +reg |= (dp->video_info.h_sync_polarity << 0);
>> writel(reg, dp->reg_base + ANALOGIX_DP_VIDEO_CTL_10);
>>
>> reg = AUDIO_MODE_SPDIF_MODE | VIDEO_MODE_SLAVE_MODE;
>>
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/ffa0ff10/attachment-0001.html>
Hi Krzysztof,
On 09/30/2015 01:22 PM, Krzysztof Kozlowski wrote:
> On 22.09.2015 16:34, Yakir Yang wrote:
>> Fix some obvious alignment problems, like alignment and line
>> over 80 characters problems, make this easy to be maintained
>> later.
>>
>> Signed-off-by: Yakir Yang
>> ---
>> Changes in
Hi Krzysztof,
On 09/30/2015 01:17 PM, Krzysztof Kozlowski wrote:
> On 22.09.2015 16:29, Yakir Yang wrote:
>> Split the dp core driver from exynos directory to bridge directory,
>> and rename the core driver to analogix_dp_*, rename the platform
>> code to exynos_dp.
>>
>> Beside the new analogix_d
It was just a wrapper around drm_fb_helper_set_par that
called cursor_set2 in addition. Now that the core handles
this, drop this radeon specific version.
Change-Id: I037664baaf150efbf07074a96be84f6260cf0dc1
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_fb.c | 32 +--
If a driver uses the cursor_set2 crtc callback rather than
cursor_set, use that. This fixes the fbdev helper for drivers
that use cursor_set2.
Change-Id: I127d3f8e72789ba70c3648140f87c6187864e130
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/drm_fb_helper.c | 6 +-
1 file changed, 5 inser
On 09/25/2015 06:15 PM, Inki Dae wrote:
> On 2015ë
09ì 24ì¼ 10:01, Joonyoung Shim wrote:
>> Hi Inki,
>>
>> On 08/17/2015 06:03 PM, Inki Dae wrote:
>>> On 2015ë
08ì 17ì¼ 17:17, Joonyoung Shim wrote:
On 08/17/2015 04:52 PM, Inki Dae wrote:
> On 2015ë
08ì 17ì¼ 14:29, Joonyoung
On Wed, Sep 30, 2015 at 03:45:39PM +0800, Jiang Liu wrote:
> So we need to figure out why we got irq number 0 after enabling
> MSI for AMD IOMMU device. The only hint I got is that iommu driver just
> grabbing the PCI device without providing a PCI device driver for IOMMU
> PCI device, we have solv
On 22.09.2015 16:43, Yakir Yang wrote:
> After exynos_dp have been split the common IP code into analogix_dp driver,
> the analogix_dp driver have deprecated some Samsung platform properties which
> could be dynamically parsed from EDID/MODE/DPCD message, so this is an update
> for Exynos DTS file
Hello Tapani,
this was your patch.
Any comments?
Thanks,
Dieter
Am 29.09.2015 03:56, schrieb bugzilla-daemon at freedesktop.org:
> BUG ID
> 92173 [3]
>
> SUMMARY
> [regression, bisected] commit 266d05a broke WebGL-Water
> Caustics on
> NI/Turks (667
--
> Chris Wilson, Intel Open Source Technology Centre
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/7e23f298/attachment-0001.html>
On Wednesday 30 September 2015, Samuel Pitoiset wrote:
> This patch has been merged by Ben yesterday.
>
> http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=8c713f90a63ffca10d
>122af09d439f3409c933ed
>
> Why do you send a new version ? Is the previous patch wrong?
Oops, sorry. Didn't notice
On 22.09.2015 16:37, Yakir Yang wrote:
> Both hsync/vsync polarity and interlace mode can be parsed from
> drm display mode, and dynamic_range and ycbcr_coeff can be judge
> by the video code.
>
> But presumably Exynos still relies on the DT properties, so take
> good use of mode_fixup() in to ach
Drivers with software vblank counter relies on the on drm core to update
vblank counter and they should not be concern about the warning that
check hardware counter coherency.
Further, the generic message that tracks the current and last counter
values must be counter type (hardware or software) a
On 22.09.2015 16:34, Yakir Yang wrote:
> Fix some obvious alignment problems, like alignment and line
> over 80 characters problems, make this easy to be maintained
> later.
>
> Signed-off-by: Yakir Yang
> ---
> Changes in v5:
> - Resequence this patch after analogix_dp driver have been split
>
On 22.09.2015 16:29, Yakir Yang wrote:
> Split the dp core driver from exynos directory to bridge directory,
> and rename the core driver to analogix_dp_*, rename the platform
> code to exynos_dp.
>
> Beside the new analogix_dp driver would export four hooks.
> "analogix_dp_bind()" and "analogix_d
On Wed, Sep 30, 2015 at 08:26:37PM +0900, Inki Dae wrote:
> Hi,
>
> On 2015ë
09ì 28ì¼ 01:11, Charles Keepax wrote:
> > If binding failed calling exynos_dp_enable in exynos_dp_resume will
> > result in several NULL pointer dereferences. It is much better to
> > simply skip suspend/resume handl
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/9e946c29/attachment-0001.html>
This patch has been merged by Ben yesterday.
http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=8c713f90a63ffca10d122af09d439f3409c933ed
Why do you send a new version ? Is the previous patch wrong?
On 09/30/2015 01:48 PM, Ondrej Zary wrote:
> SiS 761 chipset does not support AGP cards but
SiS 761 chipset does not support AGP cards but has AGP capability (for
the onboard video). At least PC Chips A31G board using this chipset has
an AGP-like AGPro slot that's wired to the PCI bus. Enabling AGP will
fail (GPU lockup and software fbcon, X11 hangs).
Add support for matching just the ho
Hi Inki,
On 30 September 2015 at 12:21, Inki Dae wrote:
> This patch removes unnecessary pm suspend/resume functions.
>
> All kms sub drivers will be controlled by top of Exynos drm driver
> and connector dpms so these sub drivers shouldn't have their own
> pm interfaces.
>
Not sure if you've not
u are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150930/8db7d8df/attachment.html>
Hi all,
On 26 September 2015 at 19:46, Geert Uytterhoeven
wrote:
> Hi David,
>
> On Sat, Sep 26, 2015 at 8:13 PM, David Herrmann
> wrote:
>> On Sat, Sep 26, 2015 at 8:01 PM, Geert Uytterhoeven
>> wrote:
>>> On Sat, Sep 26, 2015 at 7:07 PM, Alex Deucher
>>> wrote:
On Sat, Sep 26, 2015 a
On Mon, Sep 21, 2015 at 3:11 AM, Philipp Zabel
wrote:
> Hi Rob,
>
> thank you for the comments.
>
> Am Freitag, den 18.09.2015, 15:33 -0500 schrieb Rob Herring:
> [...]
>> > +The display-subsystem node binds together all individual device nodes that
>> > +comprise the DISP subsystem.
>> > +
>> >
Hi Andrzej,
2015-09-25 Andrzej Hajda :
> The patch removes unused hdmi_context field.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 1 -
> 1 file changed, 1 deletion(-)
Reviewed-by: Gustavo Padovan
Gustavo
Hi Andrzej,
2015-09-25 Andrzej Hajda :
> Inline function is safer than macro, also the name has been changed to
> be consistent with other inline function encoder_to_hdmi.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 15 +--
> 1 file changed, 9 in
Hi Andrzej,
2015-09-25 Andrzej Hajda :
> Driver always uses the same number of regulators, so there is no point in
> dynamic allocation.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 25 +
> 1 file changed, 9 insertions(+), 16 deletions
Hi Andrzej,
2015-09-25 Andrzej Hajda :
> DRM device should be destroyed before releasing resources.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 8 +---
> 1 file changed, 5 insertions(+), 3 deletions(-)
Reviewed-by: Gustavo Padovan
Gustavo
On Wed, Sep 30, 2015 at 10:30 AM, Philipp Zabel
wrote:
> Am Freitag, den 18.09.2015, 15:33 -0500 schrieb Rob Herring:
>> On Fri, Sep 18, 2015 at 11:11 AM, Philipp Zabel
>> wrote:
>> > From: CK Hu
>> >
>> > Add device tree binding documentation for the display subsystem in
>> > Mediatek MT8173
Hi Andrzej,
2015-09-25 Andrzej Hajda :
> Registers are 32-bit, even if only lower 8-bits are used.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Gustavo Padovan
Gustavo
Hi Andrzej,
2015-09-25 Andrzej Hajda :
> Currently driver tries to set specific HDMI-PHY registers in three situations:
> - before reset,
> - before power off,
> - after applying HDMI-PHY configuration.
>
> First two cases seems to be unnecessary - register contents will be lost
> anyway. The th
Hi all,
I had an issue with the drm driver, when I start the kernel via kexec,
the drm driver freezes the platform. it is caused by the function
vop_initial (when copying registers via ahb). This issue happens with
the chromeos kernel or with the mainline kernel. When I investigated a
bit, I found
Hi Russell,
On 29 September 2015 at 19:10, Russell King
wrote:
> Rather than using a spinlock, use xchg() to atomically update
> dplane->old_fb. This allows us to eliminate dplane->lock.
>
> Signed-off-by: Russell King
> ---
[...]
> @@ -76,13 +75,10 @@ static void armada_ovl_retire_fb(struct a
Hi Andrzej,
2015-09-25 Andrzej Hajda :
> The patch moves PLL stabilization check to separate function, adjust timeout
> parameters and de-duplicates code common for both HW variants.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 68
> ++---
Hi Andrzej,
2015-09-25 Andrzej Hajda :
> Some registers resides at different offsets depending on device version.
> This patch adds infrastructure for mapping such registers to proper address
> based on hdmi_type. It adds also mappings to some registers.
>
> Signed-off-by: Andrzej Hajda
> ---
>
1 - 100 of 141 matches
Mail list logo