Quoting Brendan Higgins (2019-05-14 15:16:55)
> diff --git a/kunit/test.c b/kunit/test.c
> index 86f65ba2bcf92..a15e6f8c41582 100644
> --- a/kunit/test.c
> +++ b/kunit/test.c
[..]
> +
> +void *kunit_kmalloc(struct kunit *test, size_t size, gfp_t gfp)
> +{
> + struct kunit_kmalloc_params
On Rockchip rk3288-based Chromebooks when you do a suspend/resume
cycle:
1. You lose the ability to detect an HDMI device being plugged in.
2. If you're using the i2c bus built in to dw_hdmi then it stops
working.
Let's call the core dw-hdmi's suspend/resume functions to restore
things.
NOTE:
So a couple of things:
On Thu, 2019-05-16 at 11:17 -0400, sunpeng...@amd.com wrote:
> From: Ville Syrjälä
>
> All available downstream ports - physical and logical - are exposed for
> each MST device. They are listed in /dev/, following the same naming
> scheme as SST devices by appending an
Whoops-one more thing I forgot to mention. This is just personal preference
for me, but if you're ccing me on any of the patches in the series feel free
to just do it for all of them. Makes my inbox a little less confusing to look
at
On Thu, 2019-05-16 at 15:54 -0400, Lyude Paul wrote:
> Hi,
Hi,
On Thu, May 16, 2019 at 2:40 PM Douglas Anderson wrote:
>
> On Rockchip rk3288-based Chromebooks when you do a suspend/resume
> cycle:
>
> 1. You lose the ability to detect an HDMI device being plugged in.
>
> 2. If you're using the i2c bus built in to dw_hdmi then it stops
> working.
>
>
On Rockchip rk3288-based Chromebooks when you do a suspend/resume
cycle:
1. You lose the ability to detect an HDMI device being plugged in.
2. If you're using the i2c bus built in to dw_hdmi then it stops
working.
Let's add a hook to the core dw-hdmi driver so that we can call it in
Reviewed-by: Lyude Paul
On Thu, 2019-05-16 at 11:18 -0400, sunpeng...@amd.com wrote:
> From: Leo Li
>
> Set the connector's kernel device as the parent for the aux kernel
> device. This allows udev rules to access connector attributes when
> creating symlinks to aux devices.
>
> Cc: Ben
Am Mittwoch, 8. Mai 2019, 18:09:05 CEST schrieb Sean Paul:
> From: Sean Paul
>
> Another version of the SR helpers for your consumption.
>
> Pretty minor differences between v4 and v3:
> - lots of documentation changes
> - Use connector to get at crtc state in encoders
> - Use the damage
On Thu, May 16, 2019 at 03:14:45PM +0100, Steven Price wrote:
> drm_gem_dumb_map_offset() is a useful helper for non-dumb clients, so
> rename it to remove the _dumb.
>
> Signed-off-by: Steven Price
Reviewed-by: Daniel Vetter
> ---
> drivers/gpu/drm/drm_dumb_buffers.c | 4 ++--
>
aghsorry, but I need to take back my Reviewed-by. Noticed an issue when
reloading drm and i915. I'll explain it when I respond to patch 2/7 in a
moment
On Thu, 2019-05-16 at 11:17 -0400, sunpeng...@amd.com wrote:
> From: Leo Li
>
> Placing the MST aux device as a child of the connector
Hi, could we (and for future versions of this series and others) get a respin
of this that's actually rebased against drm-tip? That is the defacto standard
branch to do development on, and otherwise anyone trying to test these patches
has to resolve merge conflicts (along with maintainers). The
On Thu, May 16, 2019 at 03:14:46PM +0100, Steven Price wrote:
> Provide a wrapper for drm_gem_map_offset() for clients of shmem. This
> wrapper provides the correct semantics for the drm_gem_shmem_mmap()
> callback.
>
> Signed-off-by: Steven Price
> ---
> drivers/gpu/drm/drm_gem_shmem_helper.c
On Tue, May 14, 2019 at 3:40 AM Xiaqing (A) wrote:
>
>
>
> On 2019/5/14 2:37, John Stultz wrote:
> > This adds a CMA heap, which allows userspace to allocate
> > a dma-buf of contiguous memory out of a CMA region.
> >
> > This code is an evolution of the Android ION implementation, so
> > thanks
On 2019-05-16 3:54 p.m., Lyude Paul wrote:
> [CAUTION: External Email]
>
> Hi, could we (and for future versions of this series and others) get a respin
> of this that's actually rebased against drm-tip? That is the defacto standard
> branch to do development on, and otherwise anyone trying to
On Thu, 2019-05-16 at 11:17 -0400, sunpeng...@amd.com wrote:
> From: Leo Li
>
> Placing the MST aux device as a child of the connector gives udev the
> ability to access the connector device's attributes. This will come in
> handy when writing udev rules to create more descriptive symlinks to
Quoting Brendan Higgins (2019-05-14 15:16:54)
> diff --git a/include/kunit/test.h b/include/kunit/test.h
> new file mode 100644
> index 0..e682ea0e1f9a5
> --- /dev/null
> +++ b/include/kunit/test.h
> @@ -0,0 +1,162 @@
[..]
> +/**
> + * struct kunit - represents a running instance of a
https://bugzilla.kernel.org/show_bug.cgi?id=203627
Aleksandr Mezin (mezin.alexan...@gmail.com) changed:
What|Removed |Added
Regression|No |Yes
--
https://bugzilla.kernel.org/show_bug.cgi?id=203627
Bug ID: 203627
Summary: [Regression] Boot fails with linux-firmware 20190514
Product: Drivers
Version: 2.5
Kernel Version: 4.19.44
Hardware: All
OS: Linux
https://bugs.freedesktop.org/show_bug.cgi?id=110257
67b02...@casix.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110257
--- Comment #2 from Andrew Randrianasulu ---
wasn't this fixed by
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d507bcdcf26b417dea201090165af651253b6b11
--
st/va: reverse qt matrix back to its original order
The quantiser matrix
On Tue, Apr 23, 2019 at 7:26 AM Thierry Reding wrote:
>
> On Tue, Apr 16, 2019 at 12:06:43PM +0200, Marco Felsch wrote:
> > Evervision Electronics is a panel manufacturer from Taipei.
> > http://www.evervisionlcd.com/index.php?lang=en
> >
> > Signed-off-by: Marco Felsch
> > Reviewed-by: Rob
On Wed, May 15, 2019 at 11:24 PM Alex Deucher wrote:
>
> On Wed, May 15, 2019 at 4:52 PM Daniel Vetter wrote:
> >
> > On Wed, May 15, 2019 at 10:08 PM Alex Deucher wrote:
> > >
> > > On Wed, May 15, 2019 at 4:54 AM Daniel Vetter wrote:
> > > >
> > > > On Tue, May 14, 2019 at 04:05:13PM +0200,
Updates HW up-sampling method according to the format type.
Signed-off-by: Lowry Li (Arm Technology China)
---
.../gpu/drm/arm/display/komeda/d71/d71_component.c | 29 ++
1 file changed, 29 insertions(+)
diff --git a/drivers/gpu/drm/arm/display/komeda/d71/d71_component.c
Adds color-encoding properties if layer can support YUV format.
Updates HW YUV-RGB matrix state according to the color-encoding
properties.
Signed-off-by: Lowry Li (Arm Technology China)
---
drivers/gpu/drm/arm/display/komeda/Makefile| 1 +
Hi,
This serie aims at:
- Updating HW up-sampling method according to the format type.
- Adding color-encoding properties if layer can support YUV format,
and updating HW YUV-RGB matrix state according to the color-encoding
properties.
This patch series depends on:
-
On Wed, May 15, 2019 at 11:25 AM Christian König
wrote:
>
> Am 15.05.19 um 10:58 schrieb Daniel Vetter:
> > On Tue, May 14, 2019 at 04:05:14PM +0200, Christian König wrote:
> >> To allow a smooth transition from pinning buffer objects to dynamic
> >> invalidation we first start to cache the
On Thu, May 16, 2019 at 9:49 AM Torsten Duwe wrote:
>
> On Thu, May 16, 2019 at 09:06:41AM -0700, Vasily Khoruzhick wrote:
> >
> > Driver can talk to the panel over AUX channel only after t1+t3, t1 is
> > up to 10ms, t3 is up to 200ms.
>
> This is after power-on. The boot loader needs to deal
On Thu, May 16, 2019 at 09:25:31AM +0200, Christian König wrote:
> Am 16.05.19 um 09:16 schrieb Koenig, Christian:
> > Am 16.05.19 um 04:29 schrieb Kenny Ho:
> > > [CAUTION: External Email]
> > >
> > > On Wed, May 15, 2019 at 5:26 PM Welty, Brian
> > > wrote:
> > > > On 5/9/2019 2:04 PM, Kenny
On Thu, May 16, 2019 at 09:13:27AM +0100, james qian wang (Arm Technology
China) wrote:
> Komeda driver uses a individual component to describe the HW's writeback
> caps, but drivers doesn't define a new structure and still uses the
> existing "struct komeda_layer" to describe this new component.
Oh, please not that problem again :(
Please just try "ssh gitlab.freedesktop.org" if that also times out like
this you need to contact AMD network IT and ask why ssh once more
doesn't work.
Christian.
Am 16.05.19 um 13:43 schrieb Zhou, David(ChunMing):
It mentioned me I cannot push to
Am 16.05.19 um 14:28 schrieb Daniel Vetter:
> [CAUTION: External Email]
>
> On Thu, May 16, 2019 at 09:25:31AM +0200, Christian König wrote:
>> Am 16.05.19 um 09:16 schrieb Koenig, Christian:
>>> Am 16.05.19 um 04:29 schrieb Kenny Ho:
[CAUTION: External Email]
On Wed, May 15, 2019
On Thu, May 16, 2019 at 3:25 AM Christian König
wrote:
> Am 16.05.19 um 09:16 schrieb Koenig, Christian:
> > Am 16.05.19 um 04:29 schrieb Kenny Ho:
> >> On Wed, May 15, 2019 at 5:26 PM Welty, Brian wrote:
> >>> On 5/9/2019 2:04 PM, Kenny Ho wrote:
> Each file is multi-lined with one
Hello,
I haven't gone through the patchset yet but some quick comments.
On Wed, May 15, 2019 at 10:29:21PM -0400, Kenny Ho wrote:
> Given this controller is specific to the drm kernel subsystem which
> uses minor to identify drm device, I don't see a need to complicate
> the interfaces more by
On Thu, May 16, 2019 at 03:00:01PM +0300, Laurent Pinchart wrote:
> Hi Sean,
>
> On Mon, May 13, 2019 at 10:38:58AM -0400, Sean Paul wrote:
> > On Sat, May 11, 2019 at 3:12 PM Laurent Pinchart wrote:
> > > On Thu, May 02, 2019 at 03:49:46PM -0400, Sean Paul wrote:
> > >> From: Sean Paul
> > >>
>
On Thu, May 16, 2019 at 11:22:11AM +0300, Pekka Paalanen wrote:
> On Wed, 15 May 2019 10:24:49 +0200
> Daniel Vetter wrote:
>
> > On Wed, May 15, 2019 at 10:37:31AM +0300, Pekka Paalanen wrote:
> > > On Tue, 14 May 2019 16:34:01 +0200
> > > Daniel Vetter wrote:
> > >
> > > > On Tue, May 14,
On Thu, May 16, 2019 at 2:46 PM Michel Dänzer wrote:
>
> On 2019-05-16 12:09 p.m., Christian König wrote:
> > Am 16.05.19 um 10:16 schrieb zhoucm1:
> >> I was able to push changes to libdrm, but now seems after libdrm is
> >> migrated to gitlab, I cannot yet. What step do I need to get back my
>
On Thu, Apr 04, 2019 at 11:08:04AM +0100, Lowry Li (Arm Technology China) wrote:
> Fixing the DMA mapping sg segment warning, which shows "DMA-API: mapping
> sg segment longer than device claims to support [len=921600] [max=65536]".
> Fixed by setting the max segment size at Komeda driver.
>
>
Hi Noralf.
See few comments in the following.
Sam
On Mon, May 06, 2019 at 08:01:36PM +0200, Noralf Trønnes wrote:
> All drivers add all their connectors so there's no need to keep around an
> array of available connectors.
>
> Rename functions which signature is changed since they will
On Tue, May 14, 2019 at 1:05 PM Laurent Pinchart
wrote:
>
> Hi Sabyasachi,
>
> Thank you for the patch.
>
> On Tue, May 14, 2019 at 01:01:41PM +0530, Sabyasachi Gupta wrote:
> > Remove drm/drm_panel.h which is included more than once
> >
> > Signed-off-by: Sabyasachi Gupta
> > ---
> >
On 16/05/2019 12:19, Robin Murphy wrote:
[...]
> I was expecting to see a similar behaviour to my T620 (which I now
> assume was down to 64-bit job descriptors sort-of-but-not-quite working)
> but this does look a bit more fundamental - the fact that it's a level 1
> fault with VA == head == tail
This patch adds a blob property to get HDR metadata
information from userspace. This will be send as part
of AVI Infoframe to panel.
It also implements get() and set() functions for HDR output
metadata property.The blob data is received from userspace and
saved in connector state, the same is
From: Ville Syrjälä
ADD HLG EOTF to the list of EOTF transfer functions supported.
Hybrid Log-Gamma (HLG) is a high dynamic range (HDR) standard.
HLG defines a nonlinear transfer function in which the lower
half of the signal values use a gamma curve and the upper half
of the signal values use a
Enable Dynamic Range and Mastering Infoframe for HDR
content, which is defined in CEA 861.3 spec.
The metadata will be computed based on blending
policy in userspace compositors and passed as a connector
property blob to driver. The same will be sent as infoframe
to panel which support HDR.
This patch series enables HDR support in drm. It basically defines
HDR metadata structures, property to pass content (after blending)
metadata from user space compositors to driver.
Dynamic Range and Mastering infoframe creation and sending.
ToDo:
1. We need to get the color framework in place
HDR metadata block is introduced in CEA-861.3 spec.
Parsing the same to get the panel's HDR metadata.
v2: Rebase and added Ville's POC changes to the patch.
v3: No Change
v4: Addressed Shashank's review comments
v5: Addressed Shashank's comment and added his RB.
v6: Addressed Jonas Karlman
Added unpack function for DRM infoframe for dynamic
range and mastering infoframe readout.
v2: Addressed Ville's review comments.
Suggested-by: Ville Syrjälä
Signed-off-by: Uma Shankar
---
drivers/video/hdmi.c | 67
1 file changed, 67
Hi Sabyasachi,
On Thu, May 16, 2019 at 06:45:04PM +0530, Sabyasachi Gupta wrote:
> On Tue, May 14, 2019 at 1:05 PM Laurent Pinchart wrote:
> > On Tue, May 14, 2019 at 01:01:41PM +0530, Sabyasachi Gupta wrote:
> > > Remove drm/drm_panel.h which is included more than once
> > >
> > > Signed-off-by:
From: Jonas Karlman
This adds reference count for HDR metadata blob,
handled as part of duplicate and destroy connector
state functions.
v2: Removed the hdr_metadata_changed initialization as
the variable is dropped and not required.
Signed-off-by: Jonas Karlman
Signed-off-by: Uma Shankar
Added state readout for DRM infoframe and enabled
state validation for DRM infoframe.
v2: Addressed Ville's review comments and dropped the
unused drm infoframe read at intel_hdmi_init.
v3: Removed a redundant platform check as per Ville's
comment.
Signed-off-by: Uma Shankar
---
Attach HDR metadata property to connector object.
v2: Rebase
v3: Updated the property name as per updated name
while creating hdr metadata property
Signed-off-by: Uma Shankar
Reviewed-by: Shashank Sharma
---
drivers/gpu/drm/i915/intel_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff
BYT/CHT doesn't support DRM Infoframe. This caused
a WARN_ON due to a missing CASE while executing
intel_hdmi_infoframes_enabled function. This patch
fixes the same.
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Enable writing of HDR metadata infoframe to panel.
The data will be provid by usersapace compositors, based
on blending policies and passsed to driver through a blob
property.
v2: Rebase
v3: Fixed a warning message
v4: Addressed Shashank's review comments
v5: Rebase. Added infoframe
From: Ville Syrjälä
This patch enables infoframes on GLK+ to be
used to send HDR metadata to HDMI sink.
v2: Addressed Shashank's review comment.
v3: Addressed Shashank's review comment.
v4: Added Shashank's RB.
v5: Dropped hdr_metadata_change check while modeset, as per
Ville's suggestion.
This patch enables modeset whenever HDR metadata
needs to be updated to sink.
v2: Addressed Shashank's review comments.
v3: Added Shashank's RB.
v4: Addressed Ville's review comments.
v5: Addressed Ville's review comments.
Signed-off-by: Ville Syrjälä
Signed-off-by: Uma Shankar
Reviewed-by:
Am 16.05.19 um 16:03 schrieb Kenny Ho:
On Thu, May 16, 2019 at 3:25 AM Christian König
wrote:
Am 16.05.19 um 09:16 schrieb Koenig, Christian:
Am 16.05.19 um 04:29 schrieb Kenny Ho:
On Wed, May 15, 2019 at 5:26 PM Welty, Brian wrote:
On 5/9/2019 2:04 PM, Kenny Ho wrote:
Each file is
On Thu, May 16, 2019 at 02:07:34PM +0200, Daniel Vetter wrote:
> On Thu, May 16, 2019 at 2:02 PM Laurent Pinchart
> wrote:
> >
> > Hi Daniel,
> >
> > On Mon, May 13, 2019 at 04:47:47PM +0200, Daniel Vetter wrote:
> > > On Sat, May 11, 2019 at 10:12:02PM +0300, Laurent Pinchart wrote:
> > > > On
Den 16.05.2019 15.07, skrev Sam Ravnborg:
> Hi Noralf.
>
> See few comments in the following.
>
> Sam
>
> On Mon, May 06, 2019 at 08:01:36PM +0200, Noralf Trønnes wrote:
>> All drivers add all their connectors so there's no need to keep around an
>> array of available connectors.
I
Am 16.05.19 um 13:23 schrieb Thomas Hellstrom:
On Thu, 2019-05-16 at 12:05 +0200, Christian König wrote:
Am 16.05.19 um 11:23 schrieb Thomas Hellstrom:
Drivers like vmwgfx may want to test whether the dma page pool is
present
or not. Since it's activated by default by TTM if compiled-in,
Panfrost has a re-implementation of drm_gem_dumb_map_offset() with an
extra bug regarding the handling of imported buffers. However we don't
really want Panfrost calling _dumb functions because it's not a KMS
driver.
This series renames drm_gem_dumb_map_offset() to drop the '_dumb' and
introduces
drm_gem_dumb_map_offset() is a useful helper for non-dumb clients, so
rename it to remove the _dumb.
Signed-off-by: Steven Price
---
drivers/gpu/drm/drm_dumb_buffers.c | 4 ++--
drivers/gpu/drm/drm_gem.c | 6 +++---
drivers/gpu/drm/exynos/exynos_drm_gem.c | 3 +--
https://bugs.freedesktop.org/show_bug.cgi?id=108487
Daniel Stone changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 2019-05-16 12:09 p.m., Christian König wrote:
> Am 16.05.19 um 10:16 schrieb zhoucm1:
>> I was able to push changes to libdrm, but now seems after libdrm is
>> migrated to gitlab, I cannot yet. What step do I need to get back my
>> permission? I already can login into gitlab with old
Hi Allen,
Am Mittwoch, 8. Mai 2019, 09:48:40 CEST schrieb allen:
> From: Allen Chen
>
> Add a DT binding documentation for IT6505.
>
> Signed-off-by: Allen Chen
>
> ---
> .../bindings/display/bridge/ite,it6505.txt | 30
> ++
>
On Thu, May 16, 2019 at 10:54:14AM +, Shankar, Uma wrote:
>
>
> >-Original Message-
> >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf
> >Of Ville
> >Syrjälä
> >Sent: Thursday, May 16, 2019 12:57 AM
> >To: Shankar, Uma
> >Cc: dcasta...@chromium.org;
On Thu, Apr 04, 2019 at 12:06:14PM +0100, james qian wang (Arm Technology
China) wrote:
> For supporting AFBC:
> 1. Check if the user requested modifier can be supported by display HW.
> 2. Check the obj->size with AFBC's requirement.
> 3. Configure HW according to the modifier (afbc features)
Am 16.05.19 um 11:23 schrieb Thomas Hellstrom:
Drivers like vmwgfx may want to test whether the dma page pool is present
or not. Since it's activated by default by TTM if compiled-in, define a
hidden configuration option that the driver can test for.
Cc: Christian König
Signed-off-by: Thomas
Hi Douglas,
Thank you for the patch.
On Thu, May 02, 2019 at 03:38:08PM -0700, Douglas Anderson wrote:
> On Rockchip rk3288-based Chromebooks when you do a suspend/resume
> cycle:
>
> 1. You lose the ability to detect an HDMI device being plugged in.
>
> 2. If you're using the i2c bus built in
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ville
>Syrjälä
>Sent: Thursday, May 16, 2019 12:57 AM
>To: Shankar, Uma
>Cc: dcasta...@chromium.org; jo...@kwiboo.se; intel-...@lists.freedesktop.org;
>emil.l.veli...@gmail.com;
On 16/05/2019 00:22, Rob Herring wrote:
On Wed, May 15, 2019 at 5:06 PM Clément Péron wrote:
Hi Robin,
On Tue, 14 May 2019 at 23:57, Robin Murphy wrote:
On 2019-05-14 10:22 pm, Clément Péron wrote:
Hi,
On Tue, 14 May 2019 at 17:17, Clément Péron wrote:
Hi,
On Tue, 14 May 2019 at
Hi Sean,
On Mon, May 13, 2019 at 10:38:58AM -0400, Sean Paul wrote:
> On Sat, May 11, 2019 at 3:12 PM Laurent Pinchart wrote:
> > On Thu, May 02, 2019 at 03:49:46PM -0400, Sean Paul wrote:
> >> From: Sean Paul
> >>
> >> Everyone who implements connector_helper_funcs->atomic_check reaches
> >>
Hi Douglas,
Thank you for the patch.
On Thu, May 02, 2019 at 03:38:07PM -0700, Douglas Anderson wrote:
> On Rockchip rk3288-based Chromebooks when you do a suspend/resume
> cycle:
>
> 1. You lose the ability to detect an HDMI device being plugged in.
>
> 2. If you're using the i2c bus built in
On Thu, 2019-05-16 at 12:05 +0200, Christian König wrote:
> Am 16.05.19 um 11:23 schrieb Thomas Hellstrom:
> > Drivers like vmwgfx may want to test whether the dma page pool is
> > present
> > or not. Since it's activated by default by TTM if compiled-in,
> > define a
> > hidden configuration
It mentioned me I cannot push to gitlab directly. After that, I added my ssh
pub to gitlab web, and also added gitlab url to git remote.
then push again, it mentions "connection timeout".
-David
Original Message
Subject: Re: [PATCH libdrm 7/7] add syncobj timeline tests v3
On Thu, May 16, 2019 at 2:02 PM Laurent Pinchart
wrote:
>
> Hi Daniel,
>
> On Mon, May 13, 2019 at 04:47:47PM +0200, Daniel Vetter wrote:
> > On Sat, May 11, 2019 at 10:12:02PM +0300, Laurent Pinchart wrote:
> > > On Thu, May 02, 2019 at 03:49:46PM -0400, Sean Paul wrote:
> > >> From: Sean Paul
Am 16.05.19 um 10:16 schrieb zhoucm1:
I was able to push changes to libdrm, but now seems after libdrm is
migrated to gitlab, I cannot yet. What step do I need to get back my
permission? I already can login into gitlab with old freedesktop account.
@Christian, Can you help submit this patch
Den 15.05.2019 15.40, skrev Daniel Vetter:
> On Wed, May 15, 2019 at 03:29:25PM +0200, Noralf Trønnes wrote:
>> drm_fb_helper_hotplug_event() should tolerate the fb_helper argument being
>> NULL. Commit 03a9606e7fee ("drm/fb-helper: Avoid race with DRM userspace")
>> introduced a fb_helper
On 2019年05月16日 18:09, Christian König wrote:
[CAUTION: External Email]
Am 16.05.19 um 10:16 schrieb zhoucm1:
I was able to push changes to libdrm, but now seems after libdrm is
migrated to gitlab, I cannot yet. What step do I need to get back my
permission? I already can login into gitlab
drm_format_horz_chroma_subsampling and drm_format_vert_chroma_subsampling
are basically a lookup in the drm_format_info table plus an access to the
hsub and vsub fields of the appropriate entry.
Most drivers are using this function while having access to the entry
already, which means that we
So far, the drm_format_plane_cpp function was operating on the format's
fourcc and was doing a lookup to retrieve the drm_format_info structure and
return the cpp.
However, this is inefficient since in most cases, we will have the
drm_format_info pointer already available so we shouldn't have to
drm_get_format_info directly calls into drm_format_info, but takes directly
a struct drm_mode_fb_cmd2 pointer, instead of the fourcc directly. It's
shorter to not dereference it, and we can customise the behaviour at the
driver level if we want to, so let's switch to it where it makes sense.
The Rockchip VOP driver has a function, scl_vop_cal_scl_fac, that will
lookup the drm_format_info structure from the fourcc passed to it by its
caller.
However, its only caller already derefences the drm_format_info structure
it has access to to retrieve that fourcc. Change the prototype of that
drm_format_num_planes() is basically a lookup in the drm_format_info table
plus an access to the num_planes field of the appropriate entry.
Most drivers are using this function while having access to the entry
already, which means that we will perform an unnecessary lookup. Removing
the call to
So far, the drm_format_plane_height/width functions were operating on the
format's fourcc and was doing a lookup to retrieve the drm_format_info
structure and return the cpp.
However, this is inefficient since in most cases, we will have the
drm_format_info pointer already available so we
drm_format_info_plane_cpp() basically just returns the cpp array content
found in the drm_format_info structure.
Since it's pretty trivial, let's remove the function and have the users use
the array directly
Suggested-by: Ville Syrjälä
Signed-off-by: Maxime Ripard
---
Changes from v2:
-
On 16/05/2019 10:42, Wen He wrote:
-Original Message-
From: Robin Murphy [mailto:robin.mur...@arm.com]
Sent: 2019年5月16日 1:14
To: Wen He ; dri-devel@lists.freedesktop.org;
linux-ker...@vger.kernel.org; liviu.du...@arm.com
Cc: Leo Li
Subject: [EXT] Re: [v1] drm/arm/mali-dp: Disable
Feature is controlled by DRM_CAP_SYNCOBJ_TIMELINE drm capability.
Signed-off-by: Chunming Zhou
---
include/drm/drm.h| 1 +
tests/amdgpu/syncobj_tests.c | 8
2 files changed, 9 insertions(+)
diff --git a/include/drm/drm.h b/include/drm/drm.h
index c893f3b4..532787bf 100644
Am 16.05.19 um 12:46 schrieb Chunming Zhou:
> Feature is controlled by DRM_CAP_SYNCOBJ_TIMELINE drm capability.
>
> Signed-off-by: Chunming Zhou
Reviewed-by: Christian König
> ---
> include/drm/drm.h| 1 +
> tests/amdgpu/syncobj_tests.c | 8
> 2 files changed, 9
Am 16.05.19 um 12:19 schrieb zhoucm1:
On 2019年05月16日 18:09, Christian König wrote:
[CAUTION: External Email]
Am 16.05.19 um 10:16 schrieb zhoucm1:
I was able to push changes to libdrm, but now seems after libdrm is
migrated to gitlab, I cannot yet. What step do I need to get back my
could you help push this patch as well?
Thanks,
-David
Original Message
Subject: Re: [PATCH libdrm] enable syncobj test depending on capability
From: "Koenig, Christian"
To: "Zhou, David(ChunMing)" ,dri-devel@lists.freedesktop.org
CC:
Am 16.05.19 um 12:46 schrieb Chunming
Drivers like vmwgfx may want to test whether the dma page pool is present
or not. Since it's activated by default by TTM if compiled-in, define a
hidden configuration option that the driver can test for.
Cc: Christian König
Signed-off-by: Thomas Hellstrom
Reviewed-by: Christian König
---
Hi Daniel,
On Mon, May 13, 2019 at 04:47:47PM +0200, Daniel Vetter wrote:
> On Sat, May 11, 2019 at 10:12:02PM +0300, Laurent Pinchart wrote:
> > On Thu, May 02, 2019 at 03:49:46PM -0400, Sean Paul wrote:
> >> From: Sean Paul
> >>
> >> Everyone who implements
On 5/15/2019 2:27 AM, Colin King wrote:
From: Colin Ian King
There is a spelling mistake in a warning message. Fix it.
Signed-off-by: Colin Ian King
Reviewed-by: Mukesh Ojha
Cheers,
-Mukesh
---
drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c | 2 +-
1 file changed, 1 insertion(+), 1
Hi Sam,
Den 15.05.2019 11.04, skrev Sam Ravnborg:
> Hi Noralf.
>
> I have read through the cahnes a copuple of times not and feel confident
> to add my r-b if the comments are considered.
>
> On Mon, May 06, 2019 at 08:01:33PM +0200, Noralf Trønnes wrote:
>> It now only contains the modeset so
On Wed 15 May 13:07 PDT 2019, Sean Paul wrote:
> On Wed, May 15, 2019 at 3:39 PM Jordan Crouse wrote:
> >
> > On Wed, May 15, 2019 at 01:00:52PM -0400, Sean Paul wrote:
> > > From: Sean Paul
> > >
> > > dev_pm_domain_attach_by_name() can return NULL, so we should check for
> > > that case when
>-Original Message-
>From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
>Sent: Thursday, May 16, 2019 1:00 AM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>maarten.lankho...@linux.intel.com; Sharma, Shashank
>;
> -Original Message-
> From: liviu.du...@arm.com [mailto:liviu.du...@arm.com]
> Sent: 2019年5月15日 23:46
> To: Wen He
> Cc: dri-devel@lists.freedesktop.org; linux-ker...@vger.kernel.org; Leo Li
>
> Subject: [EXT] Re: [v1] drm/arm/mali-dp: Disable checking for required pixel
> clock rate
>-Original Message-
>From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
>Sent: Thursday, May 16, 2019 12:40 AM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>maarten.lankho...@linux.intel.com; Sharma, Shashank
>;
>-Original Message-
>From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
>Sent: Thursday, May 16, 2019 12:45 AM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>maarten.lankho...@linux.intel.com; Sharma, Shashank
>;
Hello.
Looks like you're right.
Can you create a patch to fix this?
Thanks.
>Среда, 15 мая 2019, 11:57 +03:00 от Geert Uytterhoeven :
>
>Hi Alexander,
>
>On Thu, Jan 17, 2019 at 2:39 PM Alexander Shiyan < shc_w...@mail.ru > wrote:
>> We have two *_CLASS_DEVICE kernel config options
On Tue, May 14, 2019 at 06:02:25PM +0200, Torsten Duwe wrote:
> From: Icenowy Zheng
>
> Allwinner A64's TCON0 can output RGB666 LCD signal.
>
> Add its pinmux.
>
> Signed-off-by: Icenowy Zheng
> Signed-off-by: Vasily Khoruzhick
> Signed-off-by: Torsten Duwe
> ---
>
> originally:
1 - 100 of 165 matches
Mail list logo
