In previous drm_global_item_ref, there are two times of writing
ref->object if item->refcount is 0. So this patch does a minor update
to put alloc and init ref firstly, and then to modify the item of glob
array. Use "else" to avoid two times of writing ref->object. It can
make the code logic more
On Wed, Sep 07, 2016 at 09:21:05PM +0100, Chris Wilson wrote:
> If the fence context has notifies enabled, each of the fences'
> FENCE_FLAG_SIGNALED_BIT will be updated from the interrupt. We can rely
> on this status for reporting the current fence_is_signaled() and so
> avoid an expensive
bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/9eb89775/attachment.html>
bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/e4c25c0b/attachment.html>
are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/541dc59e/attachment.html>
If the fence context has notifies enabled, each of the fences'
FENCE_FLAG_SIGNALED_BIT will be updated from the interrupt. We can rely
on this status for reporting the current fence_is_signaled() and so
avoid an expensive uncached read.
Signed-off-by: Chris Wilson
Cc: Ben Skeggs
Cc: dri-devel
This fixes the error path for platforms that don't define the new
page_flip_target() hook.
Fixes: c229bfbbd04 ("drm: Add page_flip_target CRTC hook v2")
Testcase: igt/kms_flip/basic-flip-vs-dpms
CC: Michel Dänzer
Signed-off-by: Imre Deak
---
drivers/gpu/drm/drm_crtc.c | 2 +-
1 file changed,
On Wed, Aug 31, 2016 at 4:18 PM, Maxime Ripard
wrote:
> From: Mylène Josserand
>
> The GR8 is an SoC made by Nextthing loosely based on the sun5i family.
>
> Since it's not clear yet what we can factor out and merge with the A10s and
> A13 support, let's keep it out of the sun5i.dtsi include
We get 2 warnings when building kernel with W=1:
drivers/gpu/drm/sti/sti_mixer.c:361:6: warning: no previous prototype for
'sti_mixer_set_matrix' [-Wmissing-prototypes]
drivers/gpu/drm/sti/sti_dvo.c:109:5: warning: no previous prototype for
'dvo_awg_generate_code' [-Wmissing-prototypes]
In
We get 2 warnings when building kernel with W=1:
drivers/gpu/drm/rockchip/rockchip_drm_drv.c:309:6: warning: no previous
prototype for 'rockchip_drm_fb_suspend' [-Wmissing-prototypes]
drivers/gpu/drm/rockchip/rockchip_drm_drv.c:318:6: warning: no previous
prototype for 'rockchip_drm_fb_resume'
We get 2 warnings when building kernel with W=1:
drivers/gpu/drm/msm/mdp/mdp4/mdp4_lcdc_encoder.c:96:23: warning: no previous
prototype for 'get_connector' [-Wmissing-prototypes]
drivers/gpu/drm/msm/mdp/mdp4/mdp4_plane.c:84:5: warning: no previous prototype
for 'mdp4_plane_set_property'
We get 2 warnings when building kernel with W=1:
drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c:130:5: warning: no previous
prototype for 'rockchip_drm_fbdev_init' [-Wmissing-prototypes]
drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c:173:6: warning: no previous
prototype for
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160907/d69a913d/attachment-0001.html>
On an LV-683 (AMD Dual-core G-T56N) Mini-ITX board, I get a Kernel Oops
because Connector 0 (LCD Panel interface) does not have DDC.
Ubuntu 16.04 LTS Kernel (4.4 series):
...
[ 8.262990] [drm] ib test on ring 5 succeeded
[ 8.288897] [drm] Radeon Display Connectors
[ 8.293175] [drm] Connector
On Wed, Sep 7, 2016 at 5:52 PM, Maarten Lankhorst
wrote:
> This reverts commit 77953bd136d2a70bca2dc93b3ccda07a2b37076f.
>
> This causes a kernel panic when trying to assign a blob to a property,
> and has obviously never been tested.
>
> Signed-off-by: Maarten Lankhorst
Tested-by: Liu Ying
>
On Mon, 29 Aug 2016, Meelis Roos wrote:
> Tried 4.8-rc4 on my i5-2400 PC, got this warning:
Fixed in drm-intel-fixes by
commit fc2780b66b15092ac68272644a522c1624c48547
Author: Chris Wilson
Date: Fri Aug 26 11:59:26 2016 +0100
drm/i915: Add GEN7_PCODE_MIN_FREQ_TABLE_GT_RATIO_OUT_OF_RANGE
On Tue, 06 Sep 2016, linux at eikelenboom.it wrote:
> On 2016-09-06 11:25, Jani Nikula wrote:
>> On Tue, 06 Sep 2016, linux at eikelenboom.it wrote:
>>> L.S.,
>>>
>>> Since one of the last 4.8 RC's i'm getting the warning below when
>>> booting on my sandybridge based thinkpad.
>>> From what it
Gamma correction is optional and can be used to adjust the color
output values to match the gamut of a particular TFT LCD panel
Errata:
Gamma_R, Gamma_G and Gamma_B registers are little-endian registers
while the rest of the address-space in 2D-ACE is big-endian.
Workaround:
Split the DCU regs
On Wed, 2016-08-31 at 18:09 +0200, Daniel Vetter wrote:
> Now that there's less stuff in there I noticed that I overlooked
> them.
> Sprinkle some docs over them while at it.
>
> Signed-off-by: Daniel Vetter
> ---
>  include/drm/drm_connector.h   | 24 ++--
> Â
On 06/09/16 21:36, Nicolas Iooss wrote:
> On 06/09/16 12:21, Dave Gordon wrote:
>> On 04/09/16 19:58, Nicolas Iooss wrote:
>>> When building the kernel with clang and some warning flags, the compiler
>>> reports that the return value of dcs_get_backlight() may be
>>> uninitialized:
>>>
>>>
Hi Laurent,
Thanks for your help with this. Good to see that the DU driver is
getting closer to work with the IPMMU hardware! Please see below for
some feedback from me.
On Fri, Aug 19, 2016 at 5:39 PM, Laurent Pinchart
wrote:
> Hello,
>
> This
Hello Maxime,
On Wed, Aug 31, 2016 at 10:18 AM, Maxime Ripard
wrote:
[snip]
> +
> +#include "skeleton.dtsi"
> +
The skeleton.dtsi has been deprecated and shouldn't be used in new DTS files:
http://www.spinics.net/lists/arm-kernel/msg528080.html
Best regards,
Javier
On Wed, Sep 07, 2016 at 04:02:47PM +0800, Koenig, Christian wrote:
> Am 07.09.2016 um 09:54 schrieb Huang Rui:
> > On Wed, Sep 07, 2016 at 09:12:29AM +0200, Christian K?nig wrote:
> >> Am 07.09.2016 um 07:24 schrieb Huang Rui:
snip.
> >>> ++item->refcount;
> >>> - ref->object =
Tagging on to Archit's patchset here.
Add DSI and panel nodes to get graphics up and running
on the Nexus7.
This still depends on the panel driver being present
(currently under review) along with the rpmclk code.
Feedback would be appreciated here!
Cc: Archit Taneja
Cc: vinay simha
Cc:
Sort of tagging on to Archit's patchset here.
Adds the core gpu, and dsi nodes for the apq8064 needed
to get graphics working on the nexus7 and other devices.
Feedback would be greatly appreciated!
Cc: Archit Taneja
Cc: vinay simha
Cc: andy.gross at linaro.org
Cc: robdclark at gmail.com
Cc:
On Wed, Sep 7, 2016 at 2:13 PM, dbasehore . wrote:
> On Tue, Sep 6, 2016 at 10:18 AM, Sean Paul wrote:
>> On Mon, Sep 5, 2016 at 1:06 AM, Lin Huang wrote:
>>> when in ddr frequency scaling process, vop can not do enable or
>>> disable operation, since in dcf we check vop clock to see whether
Hi Dave,
Please pull these collected fixes and cleanups from various sources.
This pull request contains my earlier pull request on with tag
tilcdc-4.9-fixes, so pulling this alone is enough. They both have the
same base and commit ids so it does not matter if you pulled the other
one already
ime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/d7bdff00/attachment.sig>
On Wed, Sep 07, 2016 at 09:12:29AM +0200, Christian König wrote:
> Am 07.09.2016 um 07:24 schrieb Huang Rui:
> >In previous drm_global_item_ref, there are two times of writing
> >ref->object if item->refcount is 0. So this patch does a minor update
> >to put alloc and init ref firstly, and then
On Sun, 04 Sep 2016, Dominik Brodowski wrote:
> Hi!
>
> Since commit 1c80c25fb6 (determined by git bisect, and confirmed by
> reverting this patch on top of 9ca581b50d), the sceen on my DELL XPS 13
> is flickering every once in a while (sometimes multiple times per
> second, sometimes only every
vm_insert_mixed() unlike vm_insert_pfn_prot() and vmf_insert_pfn_pmd(),
fails to check the pgprot_t it uses for the mapping against the one
recorded in the memtype tracking tree. Add the missing call to
track_pfn_insert() to preclude cases where incompatible aliased mappings
are established for a
track_pfn_insert() in vmf_insert_pfn_pmd() is marking dax mappings as
uncacheable rendering them impractical for application usage. DAX-pte
mappings are cached and the goal of establishing DAX-pmd mappings is to
attain more performance, not dramatically less (3 orders of magnitude).
While writing an improved changelog, as prompted by Andrew, for v1 of
"mm: fix cache mode of dax pmd mappings" [1], it struck me that
vmf_insert_pfn_pmd() is implemented correctly. Instead, it is the
memtype tree that is missing a memtype reservation for
devm_memremap_pages() ranges.
On Wed, Sep 7, 2016 at 1:31 PM, Sean Paul wrote:
> On Wed, Sep 7, 2016 at 2:13 PM, dbasehore . wrote:
>> On Tue, Sep 6, 2016 at 10:18 AM, Sean Paul wrote:
>>> On Mon, Sep 5, 2016 at 1:06 AM, Lin Huang wrote:
when in ddr frequency scaling process, vop can not do enable or
disable
On Thu, Sep 1, 2016 at 6:36 AM, Archit Taneja wrote:
> APQ8064 contains a MDP4 based display controller. It contains a HDMI, LVDS
> and 2 DSI outputs.
>
> Add display DT nodes for MDP4, HDMI TX and HDMI PHY. MDP4 based display
> blocks have a flat device hierarchy.
While the nexus7 uses DSI (and
On Thu, Sep 1, 2016 at 6:36 AM, Archit Taneja wrote:
> Make the following changes in the HDMI gpio bindings:
>
> - Use "-gpios" as the suffix for all the gpio names
> - Move all the gpios to optional, since there are platforms that use none
> of them.
> - The HPD gpio is a standard one, remove
On Thu, Sep 1, 2016 at 6:36 AM, Archit Taneja wrote:
> The LVDS port is the first in the list of the output ports in MDP4.
> The driver assumed that if the port and its corresponding endpoint
> is defined, then there should be a panel node too. This isn't
> necessary since boards may not really
> -Original Message-
> From: Masahiro Yamada [mailto:yamada.masahiro at socionext.com]
> Sent: Tuesday, September 06, 2016 7:04 PM
> To: David Airlie; dri-devel at lists.freedesktop.org
> Cc: Masahiro Yamada; Gustavo Padovan; Yakir Yang; Huang, Ray; Deucher,
> Alexander; Liu, Monk; Zhou,
On Wed, Aug 17, 2016 at 01:49:49PM +0300, Mika Kahola wrote:
> Respect max TMDS clock frequency from DPCD for active
> DP to HDMI adapters.
>
> Signed-off-by: Mika Kahola
Reviewed-by: Jim Bride
> ---
> drivers/gpu/drm/i915/intel_drv.h | 3 +++
> drivers/gpu/drm/i915/intel_hdmi.c | 27
On Wed, Aug 17, 2016 at 01:49:48PM +0300, Mika Kahola wrote:
> Read DisplayPort branch device info from through debugfs
> interface.
>
> v2: use drm_dp_helper routines to collect data
> v3: cleanup to match the drm_dp_helper.c patches introduced
> earlier in this series
> v4: move DP branch
On Wed, Sep 7, 2016 at 2:07 PM, dbasehore . wrote:
> On Tue, Sep 6, 2016 at 12:07 PM, Sean Paul wrote:
>> On Tue, Sep 6, 2016 at 3:01 PM, hl wrote:
>>> Hi
>>>
>>>
>>> On 2016å¹´09æ07æ¥ 02:55, Sean Paul wrote:
On Tue, Sep 6, 2016 at 2:15 PM, hl wrote:
>
> Hi Sean,
>
On Wed, Aug 17, 2016 at 01:49:47PM +0300, Mika Kahola wrote:
> DisplayPort branch device may define max supported bits per
> component. Update display info based on this value if bpc
> is defined.
>
> v2: cleanup to match the drm_dp_helper.c patches introduced
> earlier in this series
> v3:
On Wed, 07 Sep 2016, Ying Liu wrote:
> On Wed, Sep 7, 2016 at 5:52 PM, Maarten Lankhorst
> wrote:
>> This reverts commit 77953bd136d2a70bca2dc93b3ccda07a2b37076f.
>>
>> This causes a kernel panic when trying to assign a blob to a property,
>> and has obviously never been tested.
>>
>>
On Wed, Aug 17, 2016 at 01:49:45PM +0300, Mika Kahola wrote:
> Filter out a mode that exceeds the max pixel rate setting
> for DP to VGA dongle. This is defined in DPCD register 0x81
> if detailed cap info i.e. info field is 4 bytes long and
> it is available for DP downstream port.
>
> The
On Wed, Aug 17, 2016 at 01:49:44PM +0300, Mika Kahola wrote:
> SW revision is mandatory field for DisplayPort branch
> devices. This is defined in DPCD register field 0x50A.
To be precise, the revision info is in 0x50A and 0x50B. Since
both the major and minor versions are called out separately
On Wed, Aug 17, 2016 at 01:49:43PM +0300, Mika Kahola wrote:
> HW revision is mandatory field for DisplayPort branch
> devices. This is defined in DPCD register field 0x509.
>
> v2: move drm_dp_ds_revision structure to be part of
> drm_dp_link structure (Daniel)
> v3: remove dependency to
On Wed, Aug 17, 2016 at 01:49:42PM +0300, Mika Kahola wrote:
> Let's remove reference to "struct intel_connector *connector"
> in intel_dp_aux_init() function as it is no longer required.
>
> Signed-off-by: Mika Kahola
Reviewed-by: Jim Bride
> ---
> drivers/gpu/drm/i915/intel_dp.c | 4 ++--
>
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
include/drm/drmP.h
between commit:
c4e68a583202 ("drm: Introduce DRM_DEV_* log messages")
from the drm tree and commit:
30b0da8d556e ("drm: extra printk() wrapper macros")
from the drm-intel tree.
I fixed it up
On 02/08/2016 07:20, Yang, Rong R wrote:
> I sent a new version, could you check this and give comments/ACK?
>
> Thanks,
> Yang Rong
>
>> -Original Message-
>> From: Beignet [mailto:beignet-bounces at lists.freedesktop.org] On Behalf Of
>> Yang Rong
>> Sent: Tuesday, August 2, 2016 15:51
driver. I will update everything to current git and re-test
with amdgpu.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160
Hi, YT:
On Fri, 2016-09-02 at 19:24 +0800, YT Shen wrote:
> This patch add support for the Mediatek MT2701 DISP subsystem.
> There is only one OVL engine in MT2701.
>
> Signed-off-by: YT Shen
[snip...]
> diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c
>
Hi, YT:
On Fri, 2016-09-02 at 19:24 +0800, YT Shen wrote:
> This patch update enable/disable flow of DSI module and MIPI TX module
>
> Signed-off-by: shaoming chen
> Signed-off-by: YT Shen
> ---
I think the description is too simple. Please briefly describe WHY of
this patch. The original
Sorry, please ignore this V2, there is a typo in "goto out" at this patch.
I will send a "update V2" later.
Thanks,
Rui
On Wed, Sep 07, 2016 at 11:26:39AM +0800, Huang Rui wrote:
> In previous drm_global_item_ref, there are two times of writing
> ref->object if item->refcount is 0. So this patch
On Wed, Sep 7, 2016 at 2:54 AM, Maxime Ripard
wrote:
> On Tue, Sep 06, 2016 at 10:50:09AM +0800, Chen-Yu Tsai wrote:
>> >> The implementation might be along the lines of
>> >>
>> >> 1. having multiple output ports, each for a different interface type.
>> >> (Some platforms go this route)
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/65209f2e/attachment.html>
Use drm_accurate_vblank_count so we have the full 32 bit to represent
the frame counter and userspace has a simpler way of knowing when the
counter wraps around.
Signed-off-by: Tomeu Vizoso
---
drivers/gpu/drm/i915/i915_irq.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff
The core provides now an ABI to userspace for generation of frame CRCs,
so implement the ->set_crc_source() callback and reuse as much code as
possible with the previous ABI implementation.
v2:
- Leave the legacy implementation in place as the ABI implementation
in the core is
Adds files and directories to debugfs for controlling and reading frame
CRCs, per CRTC:
dri/0/crtc-0/crc
dri/0/crtc-0/crc/control
dri/0/crtc-0/crc/data
Drivers can implement the set_crc_source callback() in drm_crtc_funcs to
start and stop generating frame CRCs and can add entries to the output
In preparation to using a generic API in the DRM core for continuous CRC
generation, move the related code out of i915_debugfs.c into a new file.
Eventually, only the Intel-specific code will remain in this new file.
v2: Rebased.
v6: Rebased.
Signed-off-by: Tomeu Vizoso
---
Hi,
this series basically takes the facility for continuously capturing CRCs
of frames from the i915 driver and into the DRM core.
The idea is that test suites such as IGT use this information to check
that frames that are exected to be identical, also have identical CRC
values.
Other drivers
/tilcdc_drv.h | 1 -
> 3 files changed, 62 insertions(+), 42 deletions(-)
>
Reviewed-by: Tomi Valkeinen
Tomi
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/f354d9f9/attachment.sig>
thierry,
please review.
On Fri, Aug 26, 2016 at 8:07 AM, Vinay Simha BN wrote:
> Add support for the JDI LT070ME05000 WUXGA DSI panel used in
> Nexus 7 2013 devices.
>
> Programming sequence for the panel is was originally found in the
> android-msm-flo-3.4-lollipop-release branch from:
>
thierry,
please review.
On Fri, Aug 26, 2016 at 8:07 AM, Vinay Simha BN wrote:
> Add documentation for lt070me05000 panel
>
> Cc: Archit Taneja
> Cc: John Stultz
> Cc: Thierry Reding
> Cc: Sumit Semwal
> Signed-off-by: Vinay Simha BN
> Acked-by: Rob Herring
>
> ---
> v2:
> * incorporated
On Wed, Sep 7, 2016 at 3:12 AM, Sean Paul wrote:
> The ->set() callback would always be called when transitioning
> from FLUSH->DISABLE since we assign state to psr->state right
> above the skip condition.
>
> Reported-by: Daniel Kurtz
> Signed-off-by: Sean Paul
Reviewed-by: Daniel Kurtz
>
SI cleanups ...
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/82d6d79a/attachment.html>
and the select from the parent function. I'll
attach a patch momentarily.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/176e6
and the select from the parent function. I'll
attach a patch momentarily.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/99392
WARN if CRTC is touched without CRTC lock. The crtc functions should
not be called simultaneously from multiple threads. Having the DRM
CRTC lock should take care of that.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 8
1 file changed, 8 insertions(+)
diff
Take CRTC lock when calling tilcdc_crtc_disable() in
tilcdc_crtc_destroy().
In theory there could still be some operation ongoing, which should
finish before destroying the CRTC. However, the main reason for
adding this is to be able to add WARNing in tilcdc_crtc_disable() if
CRTC is not locked.
Remove unnecessary tilcdc_crtc_disable() from tilcdc_unload(). The
tilcdc_crtc_disable() called via tilcdc_crtc_destroy() by
drm_mode_config_cleanup() couple of lines later.
The early call to tilcdc_crtc_disable() was a wrong fix (that worked)
for calling drm_flip_work_cleanup() before flushing
Flush flip-work workqueue before drm_flip_work_cleanup(). It causes a
nasty warning if there is unfinished flip-work in the queue when
drm_flip_work_cleanup() is called. The flush_workqueue() has to be
called before drm_crtc_cleanup() for unref_worker() to be able to do
its job.
Signed-off-by:
Clean up LCDC functional clock rate setting code.
The LCDC functional clock is set by two functions: mode_set_nofb() and
cpufreq_transition().
When tilcdc_crtc_mode_set_nofb() is called in atomic commit phase the
drm atomic helpers have taken all the necessary drm locks and turned
off the crtc,
Take crtc modeset lock while updating the crtc clock rate. To avoid a
race in tilcdc_crtc_update_clk(), we do not want crtc mode to change
while we update crtc clock.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
Changes since v2:
- Fix typo from "drm/tilcdc: Clean up LCDC functional clock rate setting code"
description
- Split "drm/tilcdc: Take CRTC lock when calling tilcdc_crtc_disable()" out
of "drm/tilcdc: WARN if CRTC is touched without CRTC lock"
Changes since v1:
- Use
This reverts commit 77953bd136d2a70bca2dc93b3ccda07a2b37076f.
This causes a kernel panic when trying to assign a blob to a property,
and has obviously never been tested.
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/drm_property.c | 23 ++-
1 file changed, 18
Sean,
Thanks for your comments.
On 09/07/2016 03:51 AM, Sean Paul wrote:
> On Fri, Aug 26, 2016 at 6:19 AM, Yakir Yang wrote:
>> Make sure the request PSR state could effect in analogix_dp_send_psr_spd()
>> function, or printing the error Sink PSR state if we failed to effect
>> the request PSR
On Wed, 07 Sep 2016, Masahiro Yamada wrote:
> Remove unneeded variables and assignments.
>
> Signed-off-by: Masahiro Yamada
...
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index 95ddd56..59d029d 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++
In previous drm_global_item_ref, there are two times of writing
ref->object if item->refcount is 0. So this patch does a minor update
to put alloc and init ref firstly, and then to modify the item of glob
array. Use "else" to avoid two times of writing ref->object. It can
make the code logic more
Op 07-09-16 om 10:58 schreef Maarten Lankhorst:
> Property lifetimes are equal to the device lifetime, so the separate
> drm_property_find is not needed. The pointer can be retrieved from
> the properties member, which saves us some locking and a extra lookup.
>
> The lifetime for properties is
On Tue, Sep 6, 2016 at 10:18 AM, Sean Paul wrote:
> On Mon, Sep 5, 2016 at 1:06 AM, Lin Huang wrote:
>> when in ddr frequency scaling process, vop can not do enable or
>> disable operation, since in dcf we check vop clock to see whether
>> vop work. If vop work, dcf do ddr frequency scaling when
o adding locking.
Tomi
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/aa74092c/attachment.sig>
On Tue, Sep 6, 2016 at 12:07 PM, Sean Paul wrote:
> On Tue, Sep 6, 2016 at 3:01 PM, hl wrote:
>> Hi
>>
>>
>> On 2016å¹´09æ07æ¥ 02:55, Sean Paul wrote:
>>>
>>> On Tue, Sep 6, 2016 at 2:15 PM, hl wrote:
Hi Sean,
On 2016å¹´09æ07æ¥ 01:18, Sean Paul wrote:
>
>
Property lifetimes are equal to the device lifetime, so the separate
drm_property_find is not needed. The pointer can be retrieved from
the properties member, which saves us some locking and a extra lookup.
The lifetime for properties is until the device is destroyed, which
happens late in the
On Tue, Sep 06, 2016 at 10:33:18PM +0800, Sean Paul wrote:
> On Mon, Sep 5, 2016 at 3:00 AM, Huang Rui wrote:
> > In previous drm_global_item_ref, there are two times of writing
> > ref->object if item->refcount is 0. So this patch does a minor update
> > to put alloc and init ref firstly, and
Hi, YT:
On Fri, 2016-09-02 at 19:24 +0800, YT Shen wrote:
> From: shaoming chen
>
> add dsi read/write commands for transfer function
>
> Signed-off-by: shaoming chen
> ---
> drivers/gpu/drm/mediatek/mtk_dsi.c | 188
> +
> 1 file changed, 188
This module is allow testing secure calls of SMAF.
Signed-off-by: Benjamin Gaignard
---
drivers/smaf/Kconfig | 6 +++
drivers/smaf/Makefile | 1 +
drivers/smaf/smaf-testsecure.c | 90 ++
3 files changed, 97 insertions(+)
create mode
SMAF CMA allocator implement helpers functions to allow SMAF
to allocate contiguous memory.
match() each if at least one of the attached devices have coherent_dma_mask
set to DMA_BIT_MASK(32).
For allocation it use dma_alloc_attrs() with DMA_ATTR_WRITE_COMBINE and not
dma_alloc_writecombine to
Secure Memory Allocation Framework goal is to be able
to allocate memory that can be securing.
There is so much ways to allocate and securing memory that SMAF
doesn't do it by itself but need help of additional modules.
To be sure to use the correct allocation method SMAF implement
deferred
version 9 changes:
- rebased on 4.8-rc5
- struct dma_attrs doesn't exist anymore so update CMA allocator
to compile with new dma_*_attr functions
- add example SMAF use case in cover letter
version 8 changes:
- rework of the structures used within ioctl
by adding a version field and
On 2016-09-07 02:22, Meng Yi wrote:
> Gamma correction is optional and can be used to adjust the color
> output values to match the gamut of a particular TFT LCD panel
> Errata:
> Gamma_R, Gamma_G and Gamma_B registers are little-endian registers
> while the rest of the address-space in 2D-ACE is
Am 07.09.2016 um 09:54 schrieb Huang Rui:
> On Wed, Sep 07, 2016 at 09:12:29AM +0200, Christian König wrote:
>> Am 07.09.2016 um 07:24 schrieb Huang Rui:
>>> In previous drm_global_item_ref, there are two times of writing
>>> ref->object if item->refcount is 0. So this patch does a minor update
Hi, YT:
On Fri, 2016-09-02 at 19:24 +0800, YT Shen wrote:
> From: shaoming chen
>
> add dsi interrupt control
>
> Signed-off-by: shaoming chen
> ---
> drivers/gpu/drm/mediatek/mtk_dsi.c | 76
> ++
> 1 file changed, 76 insertions(+)
>
[snip...]
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/02374c9d/attachment.html>
Am 07.09.2016 um 01:04 schrieb Masahiro Yamada:
> Remove unneeded variables and assignments.
>
> Signed-off-by: Masahiro Yamada
Tom StDenis was working on a similar patch for amdgpu as well, please
make sure that your work doesn't conflict with his.
Apart from that looks good to me. But I
Am 07.09.2016 um 07:24 schrieb Huang Rui:
> In previous drm_global_item_ref, there are two times of writing
> ref->object if item->refcount is 0. So this patch does a minor update
> to put alloc and init ref firstly, and then to modify the item of glob
> array. Use "else" to avoid two times of
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160907/8f7339bf/attachment.html>
Hi Stefan,
Some comments below
>
> diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c b/drivers/gpu/drm/fsl-
> dcu/fsl_dcu_drm_crtc.c
> index d30b61e..62eb284 100644
> --- a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c
> +++ b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c
> @@ -27,6 +27,9 @@
Hi Stefan,
I had tested the patches on LS1021A-TWR board using drmlib.
Like set three overlays:
root at ls1021atwr:~# ./modetest -P 39:900x100+10+10 at RG24 -P
39:200x200+300+0 at RG24 -P 39:200x200+400+300 at RG24
How did you test the overlays and cursor layer, I mean I see you using x-window
Remove unneeded variables and assignments.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c | 6 +-
drivers/gpu/drm/amd/amdgpu/sdma_v2_4.c| 6 +-
drivers/gpu/drm/amd/amdgpu/sdma_v3_0.c| 6 +-
In order to reduce the time required to turn on the panel, this patch
makes 2 assumptions:
1- In detect(): if there's a panel, we're connected.
2- In get_modes(): if there's a panel, let the panel driver decide if
it should prepare/unprepare in order to get the modes.
The first is
1 - 100 of 117 matches
Mail list logo