On Mon, Feb 12, 2018 at 12:46:11PM -0500, Lyude Paul wrote:
> On Sun, 2018-02-11 at 10:38 +0100, Lukas Wunner wrote:
> > Introduce a helper to determine if the current task is an output poll
> > worker.
> >
> > This allows us to fix a long-standing deadlock in several DRM drivers
> > wherein the
Hi,
On 13/02/18 14:00, Laurent Pinchart wrote:
> The dss_device is the top-level component in the omapdss driver. Give
> the omapdrm driver access to the dss_device pointer in order to obtain
> pointers to all other components from it. This requires a new global
> variable in the omapdss driver
Hi Rob,
On 13 February 2018 at 20:00, Rob Clark wrote:
> On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote:
>> Qualcomm has been working for the past few weeks on forward porting their
>> downstream drm driver from 4.14 to mainline. Please consider
Dear drm-misc maintainers,
On Sun, Feb 11, 2018 at 10:38:28AM +0100, Lukas Wunner wrote:
> Fix a deadlock on hybrid graphics laptops that's been present since 2013:
This series has been reviewed, consent has been expressed by the most
interested parties, patch [1/5] which touches files outside
https://bugs.freedesktop.org/show_bug.cgi?id=105083
Michel Dänzer changed:
What|Removed |Added
CC|
On Tuesday, 2018-02-13 16:31:20 -0800, Keith Packard wrote:
> This extension adds the ability to borrow an X RandR output for
> temporary use directly by a Vulkan application. For DRM, we use the
> Linux resource leasing mechanism.
>
> Signed-off-by: Keith Packard
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=105021
--- Comment #16 from Alex Deucher ---
Does disabling MSIs help? Append amdgpu.msi=0 to the kernel command line in
grub?
--
You are receiving this mail because:
You are the assignee for the
I added all three patches to my next tree
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/log/?h=next
This will hoepfully reveal any fallout.
Would be good to have an ACK from the score, tile and um maintainers in case
they verified that this change did not break anything.
On
https://bugs.freedesktop.org/show_bug.cgi?id=105089
--- Comment #2 from galym ---
Created attachment 137351
--> https://bugs.freedesktop.org/attachment.cgi?id=137351=edit
Game stops working when I start the fight with the king of the wolves in quest
dedicated to Ciri
On Tue, Feb 13, 2018 at 8:34 AM, Qiang Yu wrote:
> Hi guys,
>
> I'm working on the Lima project for ARM mali400/450 GPU. Now lima
> kernel driver uses CMA for all buffers, but mali400/450 GPU has MMU
> for each vertex/fragment shader processor, so I want to refine the lima
>
On 14/02/18 14:44, Sean Paul wrote:
> On Wed, Feb 14, 2018 at 3:33 AM, Hans Verkuil wrote:
>> Hi Sean,
>>
>> On 13/02/18 21:18, Sean Paul wrote:
>>>
>>> Hi Dave,
>>> Here's the pull request for HDCP. Hopefully no surprises since it's been
>>> baking
>>> in drm-tip for a while
On Tue, 13 Feb 2018, Anusha Srivatsa wrote:
> Forward Error Correction is supported on DP 1.4.
> This patch adds corresponding DPCD register definitions.
>
> v2: Add dri-devel mailing list to the CC list(Jani)
>
> v3: Change names, add missing masks (Manasi)
>
> v4: Add
Exynos5, Exynos4 and S5PV210 platforms have been converted to
use Device Tree and Exynos DRM driver long time ago. Remove
dead platform code for these platforms and update Kconfig
s3c-fb entry accordingly.
Cc: Jingoo Han
Signed-off-by: Bartlomiej Zolnierkiewicz
On 06/02/18 23:23, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 6 Feb 2018 21:51:15 +0100
>
> Omit an extra message for a memory allocation failure in these functions.
>
> This issue was detected by using the Coccinelle software.
>
>
On 06/02/18 23:24, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 6 Feb 2018 22:10:11 +0100
>
> Add a jump target so that a bit of exception handling can be better reused
> at the end of this function.
>
> Signed-off-by: Markus Elfring
The following happens when connection a DVI output driven
from the SiI9022 using a DVI-to-VGA adapter plug:
i2c i2c-0: sendbytes: NAK bailout.
i2c i2c-0: sendbytes: NAK bailout.
Then no picture. Apparently the I2C engine inside the SiI9022
is not smart enough to try to fall back to DDC I2C. Or
On Wed, Feb 14, 2018 at 3:30 AM, Daniel Stone wrote:
> Hi Rob,
>
> On 13 February 2018 at 20:00, Rob Clark wrote:
>> On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote:
>>> Qualcomm has been working for the past few weeks on
Hi,
On 13/02/18 14:00, Laurent Pinchart wrote:
> Hello,
>
> Most of this series has previously been posted as part of "[PATCH 00/48]
> omapdrm: Merge omapdrm and omapdss". With "[PATCH v2 00/15] omapdrm:
> Miscellaneous fixes and cleanups" posted and merged a few days ago, it
> completes the
Hey Rob,
This looks good to me, feel free to add my r-b.
Reviewed-by: Robert Foss
Rob.
On 02/13/2018 11:11 PM, Rob Herring wrote:
The check for a valid fence fd is inverted, so we're failing to pass
IN_FENCE_FD's to the kernel when we have a valid fence.
Op 14-02-18 om 09:46 schreef Lukas Wunner:
> Dear drm-misc maintainers,
>
> On Sun, Feb 11, 2018 at 10:38:28AM +0100, Lukas Wunner wrote:
>> Fix a deadlock on hybrid graphics laptops that's been present since 2013:
> This series has been reviewed, consent has been expressed by the most
>
https://bugs.freedesktop.org/show_bug.cgi?id=105089
Bug ID: 105089
Summary: radeonsi GPU lockup / crash with wine [The Witcher 3]
Product: Mesa
Version: 17.3
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=105021
--- Comment #14 from arne_woer...@yahoo.com ---
i forgot to mention:
both kernels (4.15.2-2-MANJARO (60Hz vert freq) and 4.14.16-1-MANJARO (40Hz
vert freq)) work fine,
_but_ they both need at least one of these kernel parameters in the grub.cfg:
https://bugs.freedesktop.org/show_bug.cgi?id=105083
--- Comment #2 from Vavooon ---
(In reply to denisgolovan from comment #0)
> Hi
>
> Upgrading to 4.15.2 with amdgpu dc results in blinking of color temperature
> when redshift application started. Kernel 4.13.13 worked fine.
On Tue, Feb 13, 2018 at 1:05 PM, Bartlomiej Zolnierkiewicz
wrote:
> On Saturday, February 10, 2018 01:48:55 PM Mathieu Malaterre wrote:
>> Hi,
>>
>> On Thu, Feb 8, 2018 at 2:28 PM, Bartlomiej Zolnierkiewicz
>> wrote:
>> > On Wednesday, January
Hi guys,
I'm working on the Lima project for ARM mali400/450 GPU. Now lima
kernel driver uses CMA for all buffers, but mali400/450 GPU has MMU
for each vertex/fragment shader processor, so I want to refine the lima
kernel driver for non-contiguous memory support.
After some investigation on
Quoting Ben Skeggs :
On Wed, Feb 14, 2018 at 1:40 AM, Gustavo A. R. Silva
wrote:
Hi all,
While doing some static analysis I ran into the following piece of code at
drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c:957:
957#define node(root, dir)
Add an intel_bios_cleanup() function to act as counterpart of
intel_bios_init() and move the cleanup of vbt related resources there,
putting it in the same file as the allocation.
Changed in v2:
-While touching the code anyways, remove the unnecessary:
if (dev_priv->vbt.child_dev) done before
Hi all,
While doing some static analysis I ran into the following piece of
code at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c:957:
957#define node(root, dir) ((root)->head.dir == >list) ? NULL :
\
958list_entry((root)->head.dir, struct nvkm_vma, head)
959
On Tue, Feb 13, 2018 at 7:22 PM, Tomasz Figa wrote:
> On Tue, Feb 13, 2018 at 9:57 PM, Robin Murphy wrote:
>> On 13/02/18 08:24, Tomasz Figa wrote:
>>>
>>> Hi Vivek,
>>>
>>> Thanks for the patch. Please see my comments inline.
>>>
>>> On Wed, Feb 7, 2018
Hi Tomasz,
Please find my response inline below.
On Tue, Feb 13, 2018 at 1:33 PM, Tomasz Figa wrote:
> Hi Vivek,
>
> Thanks for the patch. Please see some comments inline.
>
> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
> wrote:
>> From:
The function offb_destroy did not deallocate the color map leaving some
memory around after destruction. Call the color map deallocate function to
remove the memory leak.
Handle another case where color map should have been deallocated during an
error code path.
Fix memory leaks reported by
Hi Dave,
CI has been really effective in catching problems before users have reported
them to us. All Bugzillas closed from this tag are from our CI reports!
Due to FOSDEM prep and travel, there's quite a hunk of patches, I've tried
to highlight the ones with most impact on the top.
Regards,
Hi,
On 12-02-18 20:45, Ville Syrjälä wrote:
On Tue, Feb 06, 2018 at 03:12:37PM +0100, Hans de Goede wrote:
Add an intel_bios_cleanup() function to act as counterpart of
intel_bios_init() and move the cleanup of vbt related resources there,
putting it in the same file as the allocation.
Hi Sean,
On 13/02/18 21:18, Sean Paul wrote:
>
> Hi Dave,
> Here's the pull request for HDCP. Hopefully no surprises since it's been
> baking
> in drm-tip for a while now.
>
> topic/hdcp-2018-02-13:
> Add HDCP support to i915 drm driver.
>
> Cheers, Sean
>
>
> The following changes since
https://bugs.freedesktop.org/show_bug.cgi?id=105089
--- Comment #1 from galym ---
Created attachment 137350
--> https://bugs.freedesktop.org/attachment.cgi?id=137350=edit
dmesg log
--
You are receiving this mail because:
You are the assignee for the
Forward Error Correction is supported on DP 1.4.
This patch adds corresponding DPCD register definitions.
v2: Add dri-devel mailing list to the CC list(Jani)
v3: Change names, add missing masks (Manasi)
v4: Add missing shifts to mask (Manasi)
v5: Arrange the definitions in ascending order
of
Hi Tomasz,
On Tue, Feb 13, 2018 at 1:54 PM, Tomasz Figa wrote:
> Hi Vivek,
>
> Thanks for the patch. Please see my comments inline.
>
> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
> wrote:
>> From: Sricharan R
>>
>>
The FB_I810_I2C symbol previously had a blank help text, which was
removed in e9829ac4e5fd ("video: fbdev: kconfig: Remove blank help
text").
Give it a proper help text, derived from commit 74f6ae84b23 ("[PATCH]
i810fb: Add > i2c/DDC support").
Signed-off-by: Ulf Magnusson
So far models of the Dell Venue 8 Pro, with a panel with MIPI panel
index = 3, one of which has been kindly provided to me by Jan Brummer,
where not working with the i915 driver, giving a black screen on the
first modeset.
The problem with at least these Dells is that their VBT defines a MIPI
Make intel_bios_cleanup function free the DSI VBT data structures which
are memdup-ed by parse_mipi_config() and parse_mipi_sequence().
Reviewed-by: Ville Syrjälä
Signed-off-by: Hans de Goede
---
drivers/gpu/drm/i915/intel_bios.c | 6 ++
Hi Tomasz,
On Tue, Feb 13, 2018 at 2:01 PM, Tomasz Figa wrote:
> Hi Vivek,
>
> Thanks for the patch. Please see my comments inline.
Thanks for reviewing the patch series.
>
> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
> wrote:
>> From:
Interrupt commands causes the CP to trigger an interrupt as the command
is processed, regardless of the GPU being done processing previous
commands. This is seen by the interrupt being delivered before the
fence is written on 8974 and is likely the cause of the additional
CP_WAIT_FOR_IDLE
Hi Tomasz,
On Wed, Feb 14, 2018 at 8:31 AM, Tomasz Figa wrote:
> On Wed, Feb 14, 2018 at 11:13 AM, Rob Clark wrote:
>> On Tue, Feb 13, 2018 at 8:59 PM, Tomasz Figa wrote:
>>> On Wed, Feb 14, 2018 at 3:03 AM, Rob Clark
When the linux kernel is build with (typical kernel ship with Debian
installer):
CONFIG_FB=y
CONFIG_FB_OF=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_FB_RADEON=m
The offb driver takes precedence over module radeonfb. It is then
impossible to load the module, error reported is:
[ 96.551486]
On Wed, Feb 14, 2018 at 6:13 PM, Vivek Gautam
wrote:
> Hi Tomasz,
>
> On Wed, Feb 14, 2018 at 11:08 AM, Tomasz Figa wrote:
>> On Wed, Feb 14, 2018 at 1:17 PM, Vivek Gautam
>> wrote:
>>> Hi Tomasz,
>>>
>>> On Wed, Feb
On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos wrote:
>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15:
>
> NV5 in another PC (secondary card in x86-64) made the systrem crash on
> boot, in nvkm_therm_clkgate_fini.
Mind booting with nouveau.debug=trace?
Hi Tomasz,
On Wed, Feb 14, 2018 at 11:08 AM, Tomasz Figa wrote:
> On Wed, Feb 14, 2018 at 1:17 PM, Vivek Gautam
> wrote:
>> Hi Tomasz,
>>
>> On Wed, Feb 14, 2018 at 8:31 AM, Tomasz Figa wrote:
>>> On Wed, Feb 14, 2018 at
On Wed, Feb 14, 2018 at 2:46 PM, Tomasz Figa wrote:
Adding Jordan to this thread as well.
> On Wed, Feb 14, 2018 at 6:13 PM, Vivek Gautam
> wrote:
>> Hi Tomasz,
>>
>> On Wed, Feb 14, 2018 at 11:08 AM, Tomasz Figa wrote:
>>>
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../drm/amd/include/asic_reg/uvd/uvd_4_0_sh_mask.h | 795 -
.../drm/amd/include/asic_reg/uvd/uvd_5_0_enum.h| 1211
Hi Laurent,
Thankyou for the patch.
On 12/01/18 03:20, Laurent Pinchart wrote:
> On Gen3 hardware the VSP compositor is required for display. Enable it
> by default in the kernel configuration. The option is kept
> user-configurable for testing purpose on Gen2 platforms.
>
> Signed-off-by:
On Wed, Feb 14, 2018 at 9:35 AM, Ilia Mirkin wrote:
> On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos wrote:
>>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15:
>>
>> NV5 in another PC (secondary card in x86-64) made the systrem crash
Hi,
On 14 February 2018 at 13:50, Sean Paul wrote:
> On Wed, Feb 14, 2018 at 07:22:53AM -0500, Rob Clark wrote:
>> On Wed, Feb 14, 2018 at 3:30 AM, Daniel Stone wrote:
>> > This one I guess you can't get around though. Can they still run from
>> >
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../gpu/drm/amd/powerplay/inc/polaris10_ppsmc.h| 412 -
drivers/gpu/drm/amd/powerplay/inc/pp_feature.h | 67
2 files changed, 479
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../gpu/drm/amd/include/asic_reg/vce/vce_1_0_d.h | 64 --
.../drm/amd/include/asic_reg/vce/vce_1_0_sh_mask.h | 99 --
2 files
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../amd/include/asic_reg/sdma0/sdma0_4_0_default.h | 286 -
.../amd/include/asic_reg/sdma1/sdma1_4_0_default.h | 282
2
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../drm/amd/include/asic_reg/dce/dce_11_2_enum.h | 6813
.../drm/amd/include/asic_reg/dce/dce_8_0_enum.h| 1117
2 files changed,
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../gpu/drm/amd/include/asic_reg/gca/gfx_8_1_d.h | 2791 ---
.../drm/amd/include/asic_reg/gca/gfx_8_1_enum.h| 6808 --
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../amd/include/asic_reg/nbif/nbif_6_1_sh_mask.h | 10281 ---
1 file changed, 10281 deletions(-)
delete mode 100644
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../drm/amd/include/asic_reg/oss/oss_2_4_enum.h| 1340 --
.../drm/amd/include/asic_reg/oss/oss_3_0_1_enum.h | 1464 ---
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../drm/amd/include/asic_reg/umc/umc_6_0_default.h | 31 -
.../drm/amd/include/asic_reg/umc/umc_6_0_offset.h | 52 --
2 files
displayobject.h is not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
drivers/gpu/drm/amd/include/displayobject.h | 249
1 file changed, 249 deletions(-)
delete mode 100644
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../drm/amd/include/asic_reg/bif/bif_5_0_enum.h| 1198
.../drm/amd/include/asic_reg/bif/bif_5_1_enum.h| 1068 -
2 files
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../gpu/drm/amd/include/asic_reg/smu/smu_6_0_d.h | 148 -
.../drm/amd/include/asic_reg/smu/smu_6_0_sh_mask.h | 715 ---
Hi Tomi,
On Wednesday, 14 February 2018 15:24:53 EET Tomi Valkeinen wrote:
> Hi,
>
> On 13/02/18 14:00, Laurent Pinchart wrote:
> > Hello,
> >
> > Most of this series has previously been posted as part of "[PATCH 00/48]
> > omapdrm: Merge omapdrm and omapdss". With "[PATCH v2 00/15] omapdrm:
>
On 14/02/18 17:39, Laurent Pinchart wrote:
>> I have to admit I didn't go through every line of the patches, but
>> overall I think this looks good. The only problem is the support for
>> DSS6, which I mentioned in the other mail.
>>
>> We don't have DSS6 support in mainline, but it's a critical
On Tue, Feb 13, 2018 at 10:46:58PM -0800, Bjorn Andersson wrote:
> Interrupt commands causes the CP to trigger an interrupt as the command
> is processed, regardless of the GPU being done processing previous
> commands. This is seen by the interrupt being delivered before the
> fence is written on
On Wed, 14 Feb 2018, Sean Paul wrote:
> On Wed, Feb 14, 2018 at 02:48:29PM +0100, Hans Verkuil wrote:
>> Yes, your patches I've seen, but the 12 from Ramalingam I haven't seen.
>> At least not on dri-devel. It's a bit weird.
>
> Ahh, I'm sorry I misunderstood. I think Ram
On Wed, Feb 14, 2018 at 03:43:56PM +0100, Michel Dänzer wrote:
> On 2018-02-14 03:08 PM, Sean Paul wrote:
> > On Wed, Feb 14, 2018 at 10:26:35AM +0100, Maarten Lankhorst wrote:
> >> Op 14-02-18 om 09:46 schreef Lukas Wunner:
> >>> Dear drm-misc maintainers,
> >>>
> >>> On Sun, Feb 11, 2018 at
On Tue, Feb 13, 2018 at 3:00 PM, Rob Clark wrote:
> On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote:
>> Hi dri-devel,
>> Qualcomm has been working for the past few weeks on forward porting their
>> downstream drm driver from 4.14 to mainline. Please
https://bugs.freedesktop.org/show_bug.cgi?id=105095
Bug ID: 105095
Summary: piglit arb_vertex_type_2_10_10_10_rev-array_types
failed for BARTS
Product: Mesa
Version: 17.3
Hardware: Other
OS: All
> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15:
NV5 in another PC (secondary card in x86-64) made the systrem crash on
boot, in nvkm_therm_clkgate_fini.
--
Meelis Roos (mr...@linux.ee)
___
dri-devel mailing list
On 2018-02-14 03:08 PM, Sean Paul wrote:
> On Wed, Feb 14, 2018 at 10:26:35AM +0100, Maarten Lankhorst wrote:
>> Op 14-02-18 om 09:46 schreef Lukas Wunner:
>>> Dear drm-misc maintainers,
>>>
>>> On Sun, Feb 11, 2018 at 10:38:28AM +0100, Lukas Wunner wrote:
Fix a deadlock on hybrid graphics
All thoses headers are not used by any source files.
Lets just remove them.
Signed-off-by: Corentin Labbe
---
.../drm/amd/include/asic_reg/gmc/gmc_8_1_enum.h| 1198
.../drm/amd/include/asic_reg/gmc/gmc_8_2_enum.h| 1068 -
2 files
Hello
This patchset remove several headers which are not used by any source
file.
Regards
Change since v1:
- splited in multiple patchs
Change since v2
- Use --irreversible-delete for format-patch
Corentin Labbe (13):
drm/amd/include: remove unused asic_reg/oss headers
drm/amd/include:
Hi Tomi,
On Wednesday, 14 February 2018 10:31:17 EET Tomi Valkeinen wrote:
> Hi,
>
> On 13/02/18 14:00, Laurent Pinchart wrote:
> > The dss_device is the top-level component in the omapdss driver. Give
> > the omapdrm driver access to the dss_device pointer in order to obtain
> > pointers to all
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #18 from Ainola ---
I applied the patch to 4.15.3 on archlinux and have tested with xset dpms force
{standby,suspend} with success.
--
You are receiving this mail because:
You are the assignee for the
On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote:
> Hi Jordan,
>
> On Wed, Feb 14, 2018 at 1:42 AM, Jordan Crouse wrote:
> > On Tue, Feb 13, 2018 at 06:10:38PM +0900, Tomasz Figa wrote:
> >> Hi Vivek,
> >>
> >> Thanks for the patch. Please see my comments
On 14/02/18 10:33, Vivek Gautam wrote:
On Wed, Feb 14, 2018 at 2:46 PM, Tomasz Figa wrote:
Adding Jordan to this thread as well.
On Wed, Feb 14, 2018 at 6:13 PM, Vivek Gautam
wrote:
Hi Tomasz,
On Wed, Feb 14, 2018 at 11:08 AM, Tomasz Figa
On Wed, Feb 14, 2018 at 10:48 AM, Jordan Crouse wrote:
> On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote:
>>
>> - When submitting commands to the GPU, the GPU driver will
>> pm_runtime_get_sync() on the GPU device, which will automatically do
>> the same on all
Hi Sergei,
Thank you for the patch.
On Friday, 19 January 2018 20:29:20 EET Sergei Shtylyov wrote:
> Document the R-Car V3M (R8A77970) SoC in the R-Car LVDS bindings.
>
> Signed-off-by: Sergei Shtylyov
Reviewed-by: Laurent Pinchart
https://bugs.freedesktop.org/show_bug.cgi?id=105021
--- Comment #18 from Alex Deucher ---
(In reply to arne_woerner from comment #17)
> yup:
> i mean: i did not test, which one is necessary...
> so i cannot say, if all three r necessary, or if just one/two of them
>
Hello,
This patch series fixes the LVDS startup sequence for Gen2 and Gen3
SoCs, and then proceeds to refactoring the code to merge the Gen2 and
Gen3 implementations in preparation for V3M support.
The patches have been previously posted as part of the following series.
[PATCH 0/2] Fix LVDS
From: Sergei Shtylyov
According to the latest revision 2.00 of the R-Car Gen2 manual, the LVDS
and the bias circuit must be enabled after the LVDS I/O pins are
enabled, not before. Fix the Gen2 LVDS startup sequence accordingly.
While at it, also fix the
On 01/13/2018 12:40 AM, Laurent Pinchart wrote:
> According to the latest versions of both the Gen2 and Gen3 datasheets,
> the operating range for the LVDS clock is 31 MHz to 148.5 MHz on all
Not quite so with R-Car D3/E3 (which have the low boundary of 5 MHz) But we
don't
support them yet
Hi Sergei,
Thank you for the patch.
On Friday, 19 January 2018 20:29:21 EET Sergei Shtylyov wrote:
> Add support for the R-Car V3M (R8A77970) SoC to the LVDS encoder driver.
> Note that there are some differences with the other R-Car gen3 SoCs, e.g.
> LVDPLLCR has the same layout as in the R-Car
Hi Inki,
On 02/14/2018 06:57 AM, Inki Dae wrote:
>> diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c
>> b/drivers/gpu/drm/exynos/exynos_hdmi.c
>> index a4b75a46f946..abd84cbcf1c2 100644
>> --- a/drivers/gpu/drm/exynos/exynos_hdmi.c
>> +++ b/drivers/gpu/drm/exynos/exynos_hdmi.c
>> @@ -1068,10
Bit field [2:0] of HDMI_I2S_PIN_SEL_1 corresponds to SDATA_0,
not SDATA_2. This patch removes redefinition of HDMI_I2S_SEL_DATA2
constant and adds missing HDMI_I2S_SEL_DATA0.
The value of bit field selecting SDATA_1 (pin_sel_3) is also changed,
so it is 3 as suggested in the Exynos TRMs.
On 2/13/2018 12:00 PM, Rob Clark wrote:
On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote:
Hi dri-devel,
Qualcomm has been working for the past few weeks on forward porting their
downstream drm driver from 4.14 to mainline. Please consider this PR as a
request for
On Wed, Feb 14, 2018 at 1:46 AM, Bjorn Andersson
wrote:
> Interrupt commands causes the CP to trigger an interrupt as the command
> is processed, regardless of the GPU being done processing previous
> commands. This is seen by the interrupt being delivered before the
>
From: Sergei Shtylyov
According to the latest revisions of the R-Car Gen3 manual, the LVDS mode
must be set before the LVDS I/O pins are enabled, not after -- fix the
Gen3 LVDS startup sequence accordingly.
Fixes: e947eccbeba4 ("drm: rcar-du: Add support for
From: Sergei Shtylyov
After the recent corrections to the R-Car gen2/3 LVDS startup code, already
similar enough at their ends rcar_lvds_enable_gen{2|3}() started asking for
a merge and it's becoming actually necessary with the addition of the R-Car
V3M
On Wed, Feb 14, 2018 at 02:48:29PM +0100, Hans Verkuil wrote:
> On 14/02/18 14:44, Sean Paul wrote:
> > On Wed, Feb 14, 2018 at 3:33 AM, Hans Verkuil wrote:
> >> Hi Sean,
> >>
> >> On 13/02/18 21:18, Sean Paul wrote:
> >>>
> >>> Hi Dave,
> >>> Here's the pull request for HDCP.
https://bugs.freedesktop.org/show_bug.cgi?id=104439
--- Comment #5 from Francesco Turco ---
I just finished trying kernel 4.15.3 with the QupZilla web browser (instead of
Qutebrowser). Unfortunately it still crashes.
--
You are receiving this mail because:
You are the
> Actually this was brought up to me already, there's a fix on the mailing list
> for this I reviewed a little while ago from nvidia that we should pull in:
>
> https://patchwork.freedesktop.org/patch/203205/
>
> Would you guys mind confirming that this patch fixes your issues?
It works on my
Hi Sergei,
On Tuesday, 16 January 2018 17:42:41 EET Laurent Pinchart wrote:
> On Saturday, 13 January 2018 11:25:31 EET Sergei Shtylyov wrote:
> > On 1/13/2018 1:15 AM, Laurent Pinchart wrote:
> According to the latest revisions of the R-Car gen3 manual, the LVDS
> mode must be set
On Thu, Feb 01, 2018 at 11:32:25AM +0100, Lucas Stach wrote:
> Hi Jordan,
>
> just some drive-by comments:
Drive by comments are the best.
> Am Mittwoch, den 31.01.2018, 11:25 -0700 schrieb Jordan Crouse:
> > Add support for the A6XX family of Adreno GPUs. The biggest addition
> > is the GMU
https://bugs.freedesktop.org/show_bug.cgi?id=105021
--- Comment #17 from arne_woer...@yahoo.com ---
(In reply to Alex Deucher from comment #15)
> (In reply to arne_woerner from comment #14)
> > _but_ they both need at least one of these kernel parameters in the
> > grub.cfg:
> >
Add support for the A6XX family of Adreno GPUs. The biggest addition
is the GMU (Graphics Management Unit) which takes over most of the
power management of the GPU itself but in a ironic twist of fate
needs a goodly amount of management itself. Add support for the
A6XX core code, the GMU and the
From: Sharat Masetty
Add initial register headers for A6XX targets.
Signed-off-by: Sharat Masetty
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/adreno/a6xx.xml.h | 1600 +
Brief refresh of the a6xx GPU support for drm/msm
(v1 found here https://patchwork.freedesktop.org/series/37428/)
Thanks to Lucas for his comments, more comments gladly welcomed. I know it is
hard when you are reviewing code that won't be immediately coming to a device
near you but any feedback
1 - 100 of 151 matches
Mail list logo