tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: bc29281af131ae8c02e05322e7fc72829ec555f0
commit: ed238ee1ef30254146a5811270d37ed1cc9826d1 [324/336] drm/amdgpu: add some
VM PD/PT iterators v2
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
sed -i "${line}s/^/drm_public /" $f
fi
done < /tmp/a.txt
In which /tmp/a.txt contains the public symbols from
exynos-symbol-check. The idea here will be to switch the
Now that symbols that should be exported are annotated accordingly, make
all the rest hidden by default.
Signed-off-by: Lucas De Marchi
---
amdgpu/meson.build | 2 +-
etnaviv/meson.build | 2 +-
exynos/meson.build | 2 +-
freedreno/meson.build | 2 +-
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
sed -i "${line}s/^/drm_public /" $f
fi
done < /tmp/a.txt
In which /tmp/a.txt contains the public symbols from
omap-symbol-check. The idea here will be to switch the
This was done with:
nm --dynamic --defined-only build/amdgpu/libdrm_amdgpu.so | \
grep amdgpu_ | \
cut -d' ' -f3 > /tmp/a.txt
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
line=$((line-1))
Now that symbols that should be exported are annotated accordingly, make
all the rest hidden by default.
Signed-off-by: Lucas De Marchi
---
Makefile.am | 1 +
amdgpu/Makefile.am | 1 +
etnaviv/Makefile.am | 1 +
exynos/Makefile.am | 1 +
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
sed -i "${line}s/^/drm_public /" $f
fi
done < /tmp/a.txt
In which /tmp/a.txt contains the public symbols from
freedreno-symbol-check. The idea here will be to switch the
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
sed -i "${line}s/^/drm_public /" $f
fi
done < /tmp/a.txt
In which /tmp/a.txt contains the public symbols from
etnaviv-symbol-check. The idea here will be to switch the
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
sed -i "${line}s/^/drm_public /" $f
fi
done < /tmp/a.txt
In which /tmp/a.txt contains the public symbols from
tegra-symbol-check. The idea here will be to switch the
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
sed -i "${line}s/^/drm_public /" $f
fi
done < /tmp/a.txt
In which /tmp/a.txt contains the public symbols from
radeon-symbol-check. The idea here will be to switch the
This was done with:
nm --dynamic --defined-only build/nouveau/libdrm_nouveau.so | \
grep nouveau_ | \
cut -d ' ' -f3 > /tmp/a.txt
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
line=$((line-1))
Rely on -fvisibility=hidden to hide the symbols. Previous version of
this series applying only to drm_intel.so is
Reviewed-by: Eric Engestrom
but it's not included here since I changed the approach for the build
system change.
drm_private can also be removed from other symbols but it
This was done with:
nm --dynamic --defined-only build/libdrm.so | \
grep " T " | \
grep -v _fini | grep -v _init | \
cut -d' ' -f3 > /tmp/a.txt
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
sed -i
This was done with:
nm --dynamic --defined-only build/libkms/libkms.so | \
grep kms_ | \
cut -d' ' -f3 > /tmp/a.txt
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
sed -i "${line}s/^/drm_public /" $f
This was done with:
while read sym; do
read f func line _ <<<$(cscope -d -L -1 $sym)
if [ ! -z "$f" ]; then
line=$((line-1))
sed -i "${line}s/^/drm_public /" $f
fi
done < /tmp/a.txt
Then some corner cases were manually fixed. "a.txt" above
On 2018-09-13 09:46, Jordan Crouse wrote:
enum dpu_ad isn't used and can be safely removed.
Signed-off-by: Jordan Crouse
---
Reviewed-by: Jeykumar Sankaran
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_mdss.h | 6 --
1 file changed, 6 deletions(-)
diff --git
All DRM_CLIENT capabilities are tied to KMS support, so returning
-ENOTSUPP when KMS is not supported.
Cc: Chris Wilson
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/drm_ioctl.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/drm_ioctl.c
Hi Jacopo,
Thank you for the patch.
On Tuesday, 11 September 2018 18:46:53 EEST jacopo mondi wrote:
> On Tue, Sep 04, 2018 at 03:10:19PM +0300, Laurent Pinchart wrote:
> > All Gen3 SoCs supported so far have a fixed association between DPAD0
> > and DU channels, which led to hardcoding that
Hi Jacopo,
On Tuesday, 11 September 2018 17:59:02 EEST jacopo mondi wrote:
> On Tue, Sep 04, 2018 at 03:10:18PM +0300, Laurent Pinchart wrote:
> > On selected SoCs, the DU can use the clock output by the LVDS encoder
> > PLL as its input dot clock. This feature is optional, but on the D3 and
> >
Hi Jacopo,
On Tuesday, 11 September 2018 16:23:23 EEST jacopo mondi wrote:
> On Tue, Sep 04, 2018 at 03:10:16PM +0300, Laurent Pinchart wrote:
> > The LVDS encoders in the D3 and E3 SoCs differ significantly from those
> > in the other R-Car Gen3 family members:
> >
> > - The LVDS PLL
Hi Jacopo,
On Tuesday, 11 September 2018 16:31:55 EEST jacopo mondi wrote:
> Hi Laurent,
>sorry, I might be confused but,
>
> On Tue, Sep 04, 2018 at 03:10:15PM +0300, Laurent Pinchart wrote:
> > The THC63LVD1024 is restricted to a pixel clock frequency in the range
> > of 8 to 135 MHz.
Hm, one nitpick here. Since /sys/kernel/debug/dri/*/state creation depends on
the driver supporting atomic, maybe it would be good to make it so that we set
DRIVER_ATOMIC in the driver_stub structure, then disable it per-device depending
on the nouveau_atomic setting + hw support. That way we can
On Thursday, 2018-09-13 21:11:18 +0100, Eric Engestrom wrote:
> On Thursday, 2018-09-13 12:43:53 -0700, Lucas De Marchi wrote:
> > On 9/13/18 1:03 AM, Eric Engestrom wrote:
> > > On Wednesday, 2018-09-12 14:05:34 -0700, Lucas De Marchi wrote:
> > > > Rely on -fvisibility=hidden to hide the
On Thursday, 2018-09-13 12:43:53 -0700, Lucas De Marchi wrote:
> On 9/13/18 1:03 AM, Eric Engestrom wrote:
> > On Wednesday, 2018-09-12 14:05:34 -0700, Lucas De Marchi wrote:
> > > Rely on -fvisibility=hidden to hide the symbols. This only applies to
> > > drm_intel.so sice there's no point in
https://bugs.freedesktop.org/show_bug.cgi?id=107898
--- Comment #7 from Felix Kuehling ---
Good timing. We were just given a laptop that has similar problems and found a
partial workaround: Try adding "iommu=pt" to your kernel command line. This may
at least get you through the KFD
https://bugs.freedesktop.org/show_bug.cgi?id=105333
--- Comment #13 from Axel Davy ---
I inserted a printf inside the if condition that calls driQueryOptionb on this
option in si_pipe.c and ran a nine app, and it did print, so the env var is not
ignored.
--
You are receiving this mail because:
If the ioctl is not supported on a particular piece of HW/driver
combination, report ENOTSUP (aka EOPNOTSUPP) so that it can be easily
distinguished from both the lack of the ioctl and from a regular invalid
parameter.
v2: Across all the kms ioctls we had a mixture of reporting EINVAL,
ENODEV and
https://bugs.freedesktop.org/show_bug.cgi?id=105333
--- Comment #12 from Marek Olšák ---
It's possible that nine ignores the env var.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Thu, Sep 13, 2018 at 12:40:20PM -0400, Alex Deucher wrote:
> On Thu, Sep 13, 2018 at 12:39 PM Michel Dänzer wrote:
> >
> > On 2018-09-13 6:31 p.m., Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > Disable atomic on a per-device basis instead of for all devices.
> > > Made possible
Quoting Lucas De Marchi (2018-09-13 19:23:49)
> +Chris
>
> On 9/13/18 12:19 AM, Chih-Wei Huang wrote:
> > Note this patch breaks drm_gralloc:
> >
> > FAILED:
> > out/target/product/x86_64/obj_x86/SHARED_LIBRARIES/libgralloc_drm_intermediates/LINKED/libgralloc_drm.so
> > /bin/bash -c
On Thursday, 2018-09-13 10:43:04 -0700, Rodrigo Vivi wrote:
> On Thu, Sep 13, 2018 at 09:45:47AM +0100, Eric Engestrom wrote:
> > On Thursday, 2018-09-13 15:19:00 +0800, Chih-Wei Huang wrote:
> > > Note this patch breaks drm_gralloc:
> > >
> > > FAILED:
> > >
https://bugs.freedesktop.org/show_bug.cgi?id=105333
--- Comment #11 from Axel Davy ---
(In reply to Marek Olšák from comment #9)
> You can try to set glsl_correct_derivatives_after_discard=true, but I don't
> know if that works with nine.
Setting glsl_correct_derivatives_after_discard should
+Chris
On 9/13/18 12:19 AM, Chih-Wei Huang wrote:
Note this patch breaks drm_gralloc:
FAILED:
out/target/product/x86_64/obj_x86/SHARED_LIBRARIES/libgralloc_drm_intermediates/LINKED/libgralloc_drm.so
/bin/bash -c "prebuilts/clang/host/linux-x86/clang-4053586/bin/clang++
-nostdlib
On 09/13/2018 07:38 PM, Matthew Wilcox wrote:
On Thu, Sep 13, 2018 at 06:52:43PM +0200, Thomas Hellstrom wrote:
On 09/13/2018 05:28 PM, Matthew Wilcox wrote:
On Thu, Sep 13, 2018 at 04:56:53PM +0200, Thomas Hellstrom wrote:
On 09/13/2018 04:10 PM, Matthew Wilcox wrote:
I think this could be
On Thu, Sep 13, 2018 at 09:45:47AM +0100, Eric Engestrom wrote:
> On Thursday, 2018-09-13 15:19:00 +0800, Chih-Wei Huang wrote:
> > Note this patch breaks drm_gralloc:
> >
> > FAILED:
> > out/target/product/x86_64/obj_x86/SHARED_LIBRARIES/libgralloc_drm_intermediates/LINKED/libgralloc_drm.so
> >
On 13.09.2018 01:38, Philipp Zabel wrote:
> On Wed, 2018-09-12 at 11:32 -0700, Stefan Agner wrote:
>> A bridge might require specific settings for the pixel data on
>> the bus.
>
> On which bus? The bridge has input and output.
>
>> Copy the bus flags from the bridge timings if a bridge
>> is in
On 09/12/2018 05:58 PM, Christophe Leroy wrote:
> _PAGE_NO_CACHE is a platform specific flag. In addition, this flag
> is misleading because one would think it requests a noncached page
> whereas a noncached page is _PAGE_NO_CACHE | _PAGE_GUARDED
>
> _PAGE_NO_CACHE alone means write combined
On 09/13/2018 05:28 PM, Matthew Wilcox wrote:
On Thu, Sep 13, 2018 at 04:56:53PM +0200, Thomas Hellstrom wrote:
Hi,
On 09/13/2018 04:10 PM, Matthew Wilcox wrote:
On Thu, Sep 13, 2018 at 01:58:37PM +0200, Thomas Hellstrom wrote:
Commit 4eb085e42fde ("drm/vmwgfx: Convert to new IDA API")
Hi Philipp,
On 13.09.2018 01:36, Philipp Zabel wrote:
> Hi Stefan,
>
> thank you for the report. I think what happens is the following:
Thanks for looking into it!
>
> On Wed, 2018-09-12 at 15:26 -0700, Stefan Agner wrote:
>> Hi,
>>
>> While working on Apalis iMX6 with four displays, I
https://bugs.freedesktop.org/show_bug.cgi?id=105333
--- Comment #10 from had...@gmx.de ---
(In reply to Marek Olšák from comment #9)
> You can try to set glsl_correct_derivatives_after_discard=true, but I don't
> know if that works with nine.
I tried with the env variable set with latest git
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #19 from Richard Smith (smit...@gmx.co.uk) ---
Additional: I should probably have mentioned that I am running Debian testing.
--
You are receiving this mail because:
You are watching the assignee of the bug.
enum dpu_ad isn't used and can be safely removed.
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_mdss.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_mdss.h
b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_mdss.h
index
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #18 from Richard Smith (smit...@gmx.co.uk) ---
Created attachment 278497
--> https://bugzilla.kernel.org/attachment.cgi?id=278497=edit
dmesg
The dmesg output for the last time it happened.
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=200621
Richard Smith (smit...@gmx.co.uk) changed:
What|Removed |Added
CC||smit...@gmx.co.uk
On Thu, Sep 13, 2018 at 12:39 PM Michel Dänzer wrote:
>
> On 2018-09-13 6:31 p.m., Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Disable atomic on a per-device basis instead of for all devices.
> > Made possible by the new device.driver_features thing.
> >
> > Cc: Alex Deucher
> > Cc:
On 2018-09-13 6:31 p.m., Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Disable atomic on a per-device basis instead of for all devices.
> Made possible by the new device.driver_features thing.
>
> Cc: Alex Deucher
> Cc: "Christian König"
> Cc: "David (ChunMing) Zhou"
> Cc: Harry Wentland
>
From: Ville Syrjälä
Disable atomic on a per-device basis instead of for all devices.
Made possible by the new device.driver_features thing.
Cc: Alex Deucher
Cc: "Christian König"
Cc: "David (ChunMing) Zhou"
Cc: Harry Wentland
Cc: Michel Dänzer
Suggested-by: Michel Dänzer
Signed-off-by:
From: Ville Syrjälä
We now have per-device driver_features, so let's use that
to disable atomic only for pre-nv50.
Cc: Ben Skeggs
Cc: Lyude Paul
Cc: nouv...@lists.freedesktop.org
Cc: Daniel Vetter
Reviewed-by: Daniel Vetter
Suggested-by: Daniel Vetter
Signed-off-by: Ville Syrjälä
---
On Thu, Sep 13, 2018 at 06:06:01PM +0300, Ville Syrjälä wrote:
> On Thu, Sep 13, 2018 at 04:52:34PM +0200, Michel Dänzer wrote:
> > On 2018-09-13 4:29 p.m., Ville Syrjälä wrote:
> > > On Thu, Sep 13, 2018 at 03:50:01PM +0200, Daniel Vetter wrote:
> > >> On Thu, Sep 13, 2018 at 04:16:21PM +0300,
On Thu, 13 Sep 2018 09:25:37 +0200,
Bruno Prémont wrote:
>
> On Wed, 12 Sep 2018 20:06:43 +0200 Takashi Iwai wrote:
> > On Wed, 12 Sep 2018 19:46:58 +0200,
> > Ville Syrjälä wrote:
> > >
> > > On Tue, Sep 11, 2018 at 03:50:13PM +0200, Bruno Prémont wrote:
> > > > Hi,
> > > >
> > > > I have a
Hi
This fixes a boot issue I had on Raven (
https://bugs.freedesktop.org/show_bug.cgi?id=107922)
Feel free to add to both patches:
Tested-by: Mike Lothian
Cheers
Mike
On Thu, 13 Sep 2018 at 12:22 Christian König <
ckoenig.leichtzumer...@gmail.com> wrote:
> While cutting the lists we
https://bugs.freedesktop.org/show_bug.cgi?id=107922
--- Comment #5 from Mike Lothian ---
Created attachment 141553
--> https://bugs.freedesktop.org/attachment.cgi?id=141553=edit
newest dmesg
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107922
--- Comment #4 from Mike Lothian ---
So that gets the machine booting however there's still this back trace
[0.370419] WARNING: CPU: 2 PID: 1 at
drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1379
On Thu, Sep 13, 2018 at 04:52:34PM +0200, Michel Dänzer wrote:
> On 2018-09-13 4:29 p.m., Ville Syrjälä wrote:
> > On Thu, Sep 13, 2018 at 03:50:01PM +0200, Daniel Vetter wrote:
> >> On Thu, Sep 13, 2018 at 04:16:21PM +0300, Ville Syrjala wrote:
> >>> From: Ville Syrjälä
> >>>
> >>> We wish to
Hi,
On 09/13/2018 04:10 PM, Matthew Wilcox wrote:
On Thu, Sep 13, 2018 at 01:58:37PM +0200, Thomas Hellstrom wrote:
Commit 4eb085e42fde ("drm/vmwgfx: Convert to new IDA API") indroduced
an incorrect return value from the function vmw_gmrid_man_get_node(),
when we run out if integer ids.
https://bugs.freedesktop.org/show_bug.cgi?id=107922
--- Comment #3 from Michel Dänzer ---
Does https://patchwork.freedesktop.org/patch/249122/ help, by any chance?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.20-wip
head: 8901a65f080ad6f4d7c3ef9f23c6f3a0e3e194aa
commit: f4eac80add11572fe36800c045a1ed1fd9132ec0 [89/317] drm/amd/powerplay:
add the smu manager for vega20 (v2)
config: i386-randconfig-s1-201836 (attached as .config)
On Thu, Sep 13, 2018 at 04:26:53PM +0200, Neil Armstrong wrote:
> Hi Daniel,
>
> On 13/09/2018 15:21, Daniel Vetter wrote:
> > On Wed, Sep 12, 2018 at 01:06:07PM +0200, Noralf Trønnes wrote:
> >>
> >> Den 12.09.2018 12.57, skrev Noralf Trønnes:
> >>> (Cc: Daniel Vetter)
> >>>
> >>
> >> Somehow
On 2018-09-13 4:29 p.m., Ville Syrjälä wrote:
> On Thu, Sep 13, 2018 at 03:50:01PM +0200, Daniel Vetter wrote:
>> On Thu, Sep 13, 2018 at 04:16:21PM +0300, Ville Syrjala wrote:
>>> From: Ville Syrjälä
>>>
>>> We wish to control certain driver_features flags on a per-device basis
>>> while still
https://bugs.freedesktop.org/show_bug.cgi?id=107922
--- Comment #2 from Mike Lothian ---
Created attachment 141552
--> https://bugs.freedesktop.org/attachment.cgi?id=141552=edit
journalctl kernel output
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107922
Mike Lothian changed:
What|Removed |Added
CC||m...@fireburn.co.uk
--- Comment #1 from
https://bugs.freedesktop.org/show_bug.cgi?id=107922
Bug ID: 107922
Summary: System Freezes on Raven with agd5f 4.20-wip kernel
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity:
On 09/13/18 16:29, Mauro Carvalho Chehab wrote:
> Em Thu, 13 Sep 2018 13:47:27 +0200
> Hans Verkuil escreveu:
>
>> From: Hans Verkuil
>>
>> The CTA-861 standards have been updated to refer to opRGB instead
>> of AdobeRGB. The official standard is in fact named opRGB, so
>> switch to that.
>>
>>
On Thu, Sep 13, 2018 at 03:50:01PM +0200, Daniel Vetter wrote:
> On Thu, Sep 13, 2018 at 04:16:21PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > We wish to control certain driver_features flags on a per-device basis
> > while still sharing a single drm_driver instance across all
Em Thu, 13 Sep 2018 13:47:27 +0200
Hans Verkuil escreveu:
> From: Hans Verkuil
>
> The CTA-861 standards have been updated to refer to opRGB instead
> of AdobeRGB. The official standard is in fact named opRGB, so
> switch to that.
>
> The two old defines referring to ADOBERGB in the public
Hi Daniel,
On 13/09/2018 15:21, Daniel Vetter wrote:
> On Wed, Sep 12, 2018 at 01:06:07PM +0200, Noralf Trønnes wrote:
>>
>> Den 12.09.2018 12.57, skrev Noralf Trønnes:
>>> (Cc: Daniel Vetter)
>>>
>>
>> Somehow that CC was dropped somewhere after leaving email client.
>> Trying once more.
>
>
On 13.09.2018 09:53, Archit Taneja wrote:
> I have moved on to other stuff for now. Haven't been able to make time
> to review bridge related work. Andrzej has been doing it by himself
> for a while now.
>
> Cc: Andrzej Hajda
> Cc: Laurent Pinchart
> Cc: Gustavo Padovan
> Cc: Maarten Lankhorst
On Thu, Sep 13, 2018 at 03:35:36PM +0200, Takashi Iwai wrote:
> On Thu, 13 Sep 2018 15:27:16 +0200, Jian-Hong Pan wrote:
> > 2018-09-13 14:56 GMT+08:00 Takashi Iwai :
> > > The recent change of vga_switcheroo allowed the runtime PM for
> > > HD-audio on AMD GPUs, but this also resulted in a
On Thu, 13 Sep 2018 15:58:13 +0200,
Lukas Wunner wrote:
>
> On Thu, Sep 13, 2018 at 03:35:36PM +0200, Takashi Iwai wrote:
> > On Thu, 13 Sep 2018 15:27:16 +0200, Jian-Hong Pan wrote:
> > > 2018-09-13 14:56 GMT+08:00 Takashi Iwai :
> > > > The recent change of vga_switcheroo allowed the runtime PM
On 09/13/18 15:48, Russell King - ARM Linux wrote:
> On Thu, Sep 13, 2018 at 03:33:20PM +0200, Hans Verkuil wrote:
>> On 09/13/18 15:16, Daniel Vetter wrote:
>>> On Thu, Sep 13, 2018 at 10:33:35AM +0100, Russell King - ARM Linux wrote:
Hi Hans,
I'll pick it up in due course.
On Thu, Sep 13, 2018 at 04:16:21PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> We wish to control certain driver_features flags on a per-device basis
> while still sharing a single drm_driver instance across all the
> devices. To that end introduce device.driver_features. By default
>
On Thu, Sep 13, 2018 at 03:33:20PM +0200, Hans Verkuil wrote:
> On 09/13/18 15:16, Daniel Vetter wrote:
> > On Thu, Sep 13, 2018 at 10:33:35AM +0100, Russell King - ARM Linux wrote:
> >> Hi Hans,
> >>
> >> I'll pick it up in due course.
> >>
> >> Thanks.
> >>
> >> On Tue, Sep 11, 2018 at
On Thu, Sep 13, 2018 at 01:47:26PM +0200, Hans Verkuil wrote:
> From: Hans Verkuil
>
> This patch series replaces all AdobeRGB references by opRGB references.
>
> In November last year all references to the AdobeRGB colorspace were removed
> from the CTA-861 standards (all versions) and
On Thu, Sep 13, 2018 at 01:23:00PM +0530, Archit Taneja wrote:
> I have moved on to other stuff for now. Haven't been able to make time
> to review bridge related work. Andrzej has been doing it by himself
> for a while now.
>
> Cc: Andrzej Hajda
> Cc: Laurent Pinchart
> Cc: Gustavo Padovan
>
On Thu, Sep 13, 2018 at 03:33:20PM +0200, Hans Verkuil wrote:
> On 09/13/18 15:16, Daniel Vetter wrote:
> > On Thu, Sep 13, 2018 at 10:33:35AM +0100, Russell King - ARM Linux wrote:
> >> Hi Hans,
> >>
> >> I'll pick it up in due course.
> >>
> >> Thanks.
> >>
> >> On Tue, Sep 11, 2018 at
On Wed, Sep 12, 2018 at 03:58:17PM +, Christophe Leroy wrote:
> _PAGE_NO_CACHE is a platform specific flag. In addition, this flag
> is misleading because one would think it requests a noncached page
> whereas a noncached page is _PAGE_NO_CACHE | _PAGE_GUARDED
>
> _PAGE_NO_CACHE alone means
On 09/13/18 15:16, Daniel Vetter wrote:
> On Thu, Sep 13, 2018 at 10:33:35AM +0100, Russell King - ARM Linux wrote:
>> Hi Hans,
>>
>> I'll pick it up in due course.
>>
>> Thanks.
>>
>> On Tue, Sep 11, 2018 at 08:41:59AM +0200, Hans Verkuil wrote:
>>> Russell (or someone else), can you Ack this
On Wed, Sep 12, 2018 at 10:29:42AM +0100, Chris Wilson wrote:
> If the ioctl is not supported on a particular piece of HW/driver
> combination, report ENOTSUPP so that it can be easily distinguished from
> both the lack of the ioctl and from a regular invalid parameter.
>
> v2: Across all the kms
Quoting Ville Syrjala (2018-09-13 14:16:22)
> From: Ville Syrjälä
>
> Currently we're clearing DRIVER_ATOMIC in driver.driver_features
> for older platforms. This will not work correctly should we ever
> have a system with and old and new GPU in it. While that is not
> possible currently let's
Quoting Ville Syrjala (2018-09-13 14:16:21)
> From: Ville Syrjälä
>
> We wish to control certain driver_features flags on a per-device basis
> while still sharing a single drm_driver instance across all the
> devices. To that end introduce device.driver_features. By default
> it will be set to
On Wed, Sep 12, 2018 at 01:06:07PM +0200, Noralf Trønnes wrote:
>
> Den 12.09.2018 12.57, skrev Noralf Trønnes:
> > (Cc: Daniel Vetter)
> >
>
> Somehow that CC was dropped somewhere after leaving email client.
> Trying once more.
Yeah I just made myself unpopular. If you want SMEM_START, then
Hi Sakari,
On Thu, Sep 13, 2018 at 01:19:12PM +0300, Sakari Ailus wrote:
> On Thu, Sep 13, 2018 at 12:55:33PM +0300, Sakari Ailus wrote:
> > Hi Jacopo,
> >
> > On Thu, Sep 13, 2018 at 11:46:14AM +0200, jacopo mondi wrote:
> > > Hi Sakari,
> > >
> > > On Thu, Sep 13, 2018 at 12:29:35AM +0300,
From: Ville Syrjälä
Currently we're clearing DRIVER_ATOMIC in driver.driver_features
for older platforms. This will not work correctly should we ever
have a system with and old and new GPU in it. While that is not
possible currently let's make the code more correct and use
the per-device
On Thu, Sep 13, 2018 at 10:33:35AM +0100, Russell King - ARM Linux wrote:
> Hi Hans,
>
> I'll pick it up in due course.
>
> Thanks.
>
> On Tue, Sep 11, 2018 at 08:41:59AM +0200, Hans Verkuil wrote:
> > Russell (or someone else), can you Ack this patch? I'd like to get this
> > for 4.20.
> >
>
From: Ville Syrjälä
We wish to control certain driver_features flags on a per-device basis
while still sharing a single drm_driver instance across all the
devices. To that end introduce device.driver_features. By default
it will be set to ~0 to not impose any limits beyond
Hi Dave,
Coming to you from stormy North Carolina! It looks like Florence will wrap
right around us, so hopefully no drm-misc service interruptions will occur in
the next week :-)
Quite a lot of activity this week, both in volume and UAPI. Two of the line
items in UAPI section are functionality
On 04.09.2018 14:10, Laurent Pinchart wrote:
> The THC63LVD1024 is restricted to a pixel clock frequency in the range
> of 8 to 135 MHz. Implement the bridge .mode_valid() operation
> accordingly.
>
> Signed-off-by: Laurent Pinchart
Reviewed-by: Andrzej Hajda
--
Regards
Andrzej
Am Dienstag, 28. August 2018, 12:24:43 CEST schrieb Damian Kos:
> Hello!
>
> This is the series of patches that will add support for the Cadence's DPI/DP
> bridge. Please note that this is a preliminary version of the driver and there
> will be more patches in the future with updates, fixes and
Am Dienstag, 28. August 2018, 12:24:48 CEST schrieb Damian Kos:
> From: Quentin Schulz
>
> This patch finally adds the preliminary driver for Cadence MHDP DPI/DP bridge.
>
> Changes made in the low level driver (cdn-dp-reg.*):
> - moved it to from drivers/gpu/drm/rockchip to
>
Commit 4eb085e42fde ("drm/vmwgfx: Convert to new IDA API") indroduced
an incorrect return value from the function vmw_gmrid_man_get_node(),
when we run out if integer ids. Instead of returning 0 (meaning
non-fatal error) we forward the ida_simple_get error code -ENOSPC.
This causes TTM not to
From: Deepak Rawat
If framebuffers are larger, we create bounce surfaces that are within
STDU limits.
Signed-off-by: Deepak Rawat
Reviewed-by: Thomas Hellstrom
Signed-off-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c| 25 -
From: Deepak Rawat
For all display units, limit mode size exposed to texture_max_width/
height as this is the maximum framebuffer size that virtual device can
create.
Signed-off-by: Deepak Rawat
Reviewed-by: Sinclair Yeh
Reviewed-by: Thomas Hellstrom
Signed-off-by: Thomas Hellstrom
---
From: Deepak Rawat
During atomic check to prepare the new topology no need to check if
old_crtc_state was enabled or not. This will cause atomic_check to fail
because due to connector routing a crtc can be in atomic_state even if
there was no change to enable status.
Detected this issue with
From: Deepak Rawat
For STDU individual screen target size is limited by
SVGA_REG_SCREENTARGET_MAX_WIDTH/HEIGHT registers so add that limit
during atomic check_modeset.
An additional limit is placed in the update_layout ioctl to avoid
requesting layouts that current user-space typically can't
From: Hans Verkuil
These names have been renamed in the CTA-861 standard due to trademark
issues. Replace them here as well so they are in sync with the standard.
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/adv7511.c | 4 ++--
drivers/media/v4l2-core/v4l2-dv-timings.c | 4
From: Hans Verkuil
Drop all Adobe references and use the official opRGB standard
instead.
Signed-off-by: Hans Verkuil
---
Documentation/media/uapi/v4l/biblio.rst | 10 --
Documentation/media/uapi/v4l/colorspaces-defs.rst | 8
From: Hans Verkuil
The CTA-861 standards have been updated to refer to opRGB instead
of AdobeRGB. The official standard is in fact named opRGB, so
switch to that.
The two old defines referring to ADOBERGB in the public API are
put under #ifndef __KERNEL__ and a comment mentions that they are
From: Hans Verkuil
The CTA-861 standard renamed ADOBE to OP, so do the same to remain
in sync with the standard.
Signed-off-by: Hans Verkuil
Cc: amd-...@lists.freedesktop.org
---
drivers/gpu/drm/amd/display/dc/core/dc_hw_sequencer.c | 4 ++--
From: Hans Verkuil
This patch series replaces all AdobeRGB references by opRGB references.
In November last year all references to the AdobeRGB colorspace were removed
from the CTA-861 standards (all versions) and replaced with the corresponding
international opRGB standard (IEC 61966-2-5) due
From: Hans Verkuil
The CTA-861 standard renamed this from ADOBE to OP. Make the
same change to sync with the standard.
Signed-off-by: Hans Verkuil
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
1 - 100 of 186 matches
Mail list logo
