On Tue 2016-08-09 08:04:54, Daniel Vetter wrote:
> On Sun, Jul 24, 2016 at 05:00:31PM +0200, Pavel Machek wrote:
> > On Mon 2016-08-08 16:08:12, Gustavo Padovan wrote:
> > > 2016-08-07 Pavel Machek :
> > >
> > > > On Sun 2016-07-24 15:21:11, Greg Kroah-Hartman wrote:
> > > > > On Mon, Jul 18,
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/aef49f28/attachment.html>
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/ff56b1d7/attachment.html>
e bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/dec53766/attachment.html>
- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/f7616a67/attachment.html>
see eight
Tuxes and and a couple lines output but it won't go further. :/
--
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
because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/d3a794f4/attachment-0001.html>
On Wed, Aug 10, 2016 at 06:57:02PM +0200, Daniel Vetter wrote:
> On Wed, Aug 10, 2016 at 5:26 PM, Fabien DESSENNE
> wrote:
> > On 08/10/2016 04:12 PM, Daniel Vetter wrote:
> >> On Wed, Aug 10, 2016 at 01:04:54PM +0200, Fabien DESSENNE wrote:
> >>> On 08/10/2016 12:35 PM, Daniel Vetter wrote:
>
.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/217e18c0/attachment.html>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160810/fdbf8d08/attachment.html>
attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/3753d7be/attachment.html>
;https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/aac43116/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #17 from Stas Sergeev ---
> Not necessarily. Less fans means less power usage means money saved
You can set up fancontrol or put 0 into pwm1 manually
to stop the fan. But putting 0 into pwm1_min is IMHO
quite useless, it can as well
On Wed, Aug 10, 2016 at 5:26 PM, Fabien DESSENNE
wrote:
> On 08/10/2016 04:12 PM, Daniel Vetter wrote:
>> On Wed, Aug 10, 2016 at 01:04:54PM +0200, Fabien DESSENNE wrote:
>>> On 08/10/2016 12:35 PM, Daniel Vetter wrote:
On Wed, Aug 10, 2016 at 11:21:56AM +0200, Fabien Dessenne wrote:
>
For reasons that entirely elude me fb.h exposes all the structures,
even when it is not enabled. Except for special stuff like fb_defio.
Which means all the drivers which haven't yet switched over to the
defio support in the helpers and still roll their own, will fail
to compile when fbdev
Seems to at least compile fine, only change needed was to use
the fb_set_suspend helper.
Cc: alexander.deucher at amd.com
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/Kconfig| 8
drivers/gpu/drm/radeon/radeon_fb.c | 2 +-
2 files changed, 1 insertion(+), 9 deletions(-)
vmwgfx doesn't actually build without that.
It would be great if vmwgfx could switch over to the fbdev emulation
helpers, since those will take care of all this already. I guess one
reason to not do that was lack of defio support in the helpers, but
that's fixed now. If there's any other hold-up,
Everyone who uses the fbdev emulation helpers doesn't need to include
fb.h directly. Remove it.
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c | 1 -
drivers/gpu/drm/amd/powerplay/hwmgr/fiji_hwmgr.c| 1 -
Lots of drivers don't properly compile without this when CONFIG_FB=n.
It's kinda a hack, but since CONFIG_FB doesn't stub any fucntions when
it's disabled I think it makes sense to add it to drm_fb_helper.h.
Long term we probably need to rethink all the logic to unload firmware
framebuffer
0-day has been annoying me lately with a constant trickle of build failures with
a few drivers when DRM_FBDEV_EMULATION is not set. This series here should fix
them all I hope.
-Daniel
Daniel Vetter (5):
drm/fb-helper: Add a dummy remove_conflicting_framebuffers
drm: Remove superflous
s 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/20160810/d40971b8/attachment.html>
On Wed, 10 Aug 2016 16:04:37 +0200
Daniel Vetter wrote:
> On Wed, Aug 10, 2016 at 01:52:45PM +0200, Boris Brezillon wrote:
> > On Wed, 10 Aug 2016 14:41:52 +0300
> > Ville Syrjälä wrote:
> >
> > > On Wed, Aug 10, 2016 at 11:25:03AM +0200, Boris Brezillon wrote:
> > > > On Wed, 10 Aug
On Tue, Aug 09, 2016 at 03:41:23PM +0200, Daniel Vetter wrote:
> - Move the intro section into a DOC comment, and update it slightly.
> - kernel-doc for struct drm_framebuffer!
>
> Signed-off-by: Daniel Vetter
> ---
> Documentation/gpu/drm-kms.rst | 26 +--
>
ent was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160810/68bd6cbf/attachment.html>
On 08/10/2016 04:12 PM, Daniel Vetter wrote:
> On Wed, Aug 10, 2016 at 01:04:54PM +0200, Fabien DESSENNE wrote:
>> On 08/10/2016 12:35 PM, Daniel Vetter wrote:
>>> On Wed, Aug 10, 2016 at 11:21:56AM +0200, Fabien Dessenne wrote:
These pixel formats are supported by format_check() from
vblank should be enabled regardless of whether an event
is expected back. This is especially important for a cursor
plane.
Signed-off-by: Sean Paul
---
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git
Remove the delayed worker, opting instead for the non-delayed
variety. Also introduce a lock to ensure we don't have races
with the worker and psr_state. Finally, cancel and wait for
the worker to finish when disabling the bridge.
Signed-off-by: Sean Paul
---
There's no need for this to be in a worker, much less a
delayed worker.
Signed-off-by: Sean Paul
---
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 28
1 file changed, 4 insertions(+), 24 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
So we can change the state while holding another spinlock
(such as vblank_lock). Also add some locking around the
flush function to ensure there are no races.
Signed-off-by: Sean Paul
---
drivers/gpu/drm/rockchip/rockchip_drm_psr.c | 54 +
1 file changed, 39
Since it needs to be taken in the vblank_enable/disable stack,
which is protected by another spinlock. This lock should be
completely uncontested, since it's only taken in find_psr and
register, which is only called on init.
Signed-off-by: Sean Paul
---
This is a follow-on set to Yakir's original PSR set here:
https://lkml.org/lkml/2016/7/24/34
There are a few issues with the code that needed to be
shored up.
(1) The use of mutexes instead of spinlocks caused issues calling the
psr functions from vblank_enable/disable.
(2) The
/commits/Lin-Huang/rk3399-support-ddr-frequency-scaling/20160810-114433
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed
/commits/Lin-Huang/rk3399-support-ddr-frequency-scaling/20160810-114433
config: i386-allyesconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed
On 08/10/2016 04:59 PM, Inki Dae wrote:
> Hi Shuah,
>
> 2016ë
08ì 11ì¼ 02:30ì Shuah Khan ì´(ê°) ì´ ê¸:
>> Fix exynos_drm_gem_create_ioctl() attempts to allocate non-contiguous GEM
>> memory without IOMMU. In this case, there is no point in attempting to
>
> DRM gem can be used for
Daniel Vetter wrote on 2016/08/10 16:35:29:
> Daniel Vetter
> From: Daniel Vetter
>
> 2016/08/10 16:35
>
>
> jiang.biao2 at zte.com.cn,
>
>
> Re: [RESEND PATCH] drm/gma500: Fix comments in gtt.c
>
> On Wed, Aug 10, 2016 at 11:35:14AM +0800, jiang.biao2 at zte.com.cn wrote:
> >
> > Fix some
On Wed, Aug 10, 2016 at 4:23 PM, Sean Paul wrote:
> Is there a reason we create drm_kms_helper.c/h in patch 2 and then
> rename it in patch 3? Could you squash this?
My own incompetence ;-) It's already squashed here in my tree.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41
On Wed, Aug 10, 2016 at 4:27 PM, Noralf Trønnes wrote:
> Den 10.08.2016 10:43, skrev Daniel Vetter:
>>
>> On Tue, Aug 09, 2016 at 07:45:40PM +0200, Noralf Trønnes wrote:
>>>
>>> This adds a way for in-kernel users to iterate over the available
>>> DRM minors. The implementation is oops safe so
Add support for cdn DP controller which is embedded in the rk3399
SoCs. The DP is compliant with DisplayPort Specification,
Version 1.3, This IP is compatible with the rockchip type-c PHY IP.
There is a uCPU in DP controller, it need a firmware to work,
please put the firmware file to
Adds parsing for HDMI 2.0 'HDMI Forum Vendor
Specific Data Block'. This block is present in
some HDMI 2.0 EDID's and gives information about
scrambling support, SCDC, 3D Views, and others.
Parsed parameters are stored in drm_connector
structure.
Signed-off-by: Jose Abreu
Cc: Carlos Palminha
Den 10.08.2016 10:43, skrev Daniel Vetter:
> On Tue, Aug 09, 2016 at 07:45:40PM +0200, Noralf Trønnes wrote:
>> This adds a way for in-kernel users to iterate over the available
>> DRM minors. The implementation is oops safe so the panic code
>> can safely use it.
>>
>> Signed-off-by: Noralf
On Wed, Aug 10, 2016 at 12:46:23PM +0200, Maarten Lankhorst wrote:
> When doing a atomic commit affecting multiple crtc's, multiple events
> are generated. The user_data member does not allow you to distinguish,
> because they all have the same pointer.
>
> I've chosen to use crtc_id, because
We had only DRM_INFO() and DRM_ERROR(), whereas the underlying printk()
provides several other useful intermediate levels such as NOTICE and
WARNING. So this patch fills out the set by providing both regular and
once-only macros for each of the levels INFO, NOTICE, and WARNING, using
a common
On Wed, Aug 10, 2016 at 01:04:54PM +0200, Fabien DESSENNE wrote:
>
> On 08/10/2016 12:35 PM, Daniel Vetter wrote:
> > On Wed, Aug 10, 2016 at 11:21:56AM +0200, Fabien Dessenne wrote:
> >> These pixel formats are supported by format_check() from drm_crtc.c, so
> >> provide there depth and bpp.
>
On Wed, Aug 10, 2016 at 01:52:45PM +0200, Boris Brezillon wrote:
> On Wed, 10 Aug 2016 14:41:52 +0300
> Ville Syrjälä wrote:
>
> > On Wed, Aug 10, 2016 at 11:25:03AM +0200, Boris Brezillon wrote:
> > > On Wed, 10 Aug 2016 12:09:41 +0300
> > > Ville Syrjälä wrote:
> > >
> > > > On Wed,
Hi CK,
On Fri, 2016-08-05 at 14:18 +0800, CK Hu wrote:
> Hi, YT:
>
> On Thu, 2016-08-04 at 19:07 +0800, YT Shen wrote:
> > This patch adds the device nodes for the DISP function blocks for MT2701
> >
> > Signed-off-by: YT Shen
> > ---
> > arch/arm/boot/dts/mt2701.dtsi | 86
> >
Hi CK,
On Fri, 2016-08-05 at 14:36 +0800, CK Hu wrote:
> Hi, YT:
>
> On Thu, 2016-08-04 at 19:07 +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
> > ---
> >
Hi CK,
On Fri, 2016-08-05 at 18:08 +0800, CK Hu wrote:
> Hi, YT:
>
> On Thu, 2016-08-04 at 19:07 +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 | 261
Hi CK,
On Fri, 2016-08-05 at 18:24 +0800, CK Hu wrote:
> Hi, YT:
>
> On Thu, 2016-08-04 at 19:07 +0800, YT Shen wrote:
> > From: shaoming chen
> >
> > add dsi interrupt control
> >
> > Signed-off-by: shaoming chen
> > ---
> > drivers/gpu/drm/mediatek/mtk_dsi.c | 76
> >
On Wed, Aug 10, 2016 at 11:25:03AM +0200, Boris Brezillon wrote:
> On Wed, 10 Aug 2016 12:09:41 +0300
> Ville Syrjälä wrote:
>
> > On Wed, Aug 10, 2016 at 10:35:22AM +0200, Boris Brezillon wrote:
> > > Hi Ville,
> > >
> > > On Fri, 22 Jul 2016 18:47:01 +0300
> > > ville.syrjala at
On Wed, Aug 10, 2016 at 12:52 PM, Daniel Vetter
wrote:
> 0-day has been annoying me lately with a constant trickle of build failures
> with
> a few drivers when DRM_FBDEV_EMULATION is not set. This series here should fix
> them all I hope.
> -Daniel
>
> Daniel Vetter (5):
> drm/fb-helper: Add
By request forwarded patch
This is also
Reviewed-by: Thomas Hellstrom
/Thomas
Forwarded Message
Subject:[PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless
Date: Sat, 10 Oct 2015 12:56:34 +0200
From: Jason A. Donenfeld
To: Dave
On Tue, Aug 9, 2016 at 7:30 AM, Wolfram Sang
wrote:
> The core will do this for us now.
>
> Signed-off-by: Wolfram Sang
Applied patches 1, 5.
Thanks,
Alex
> ---
> drivers/gpu/drm/radeon/radeon_i2c.c | 8 ++--
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git
Hi Lin,
Looks good to me about the devfreq/devfreq-event usage.
[Usage of the devfreq/devfreq-event APIs]
Reviewed-by: Chanwoo Choi
Regards,
Chanwoo Choi
On 2016ë
08ì 10ì¼ 12:26, Lin Huang wrote:
> when in ddr frequency scaling process, vop can not do
> enable or disable operation, since
On 08/09/2016 04:08 PM, Daniel Vetter wrote:
> On Tue, Aug 9, 2016 at 3:59 PM, Thomas Hellstrom
> wrote:
>> Hmm.
>>
>> I don't have a strong opinion on this, but IMO the original idea of
>> allowing a user-space driver to optimize away the dirty calls isn't a
>> bad one.
>> Since the
Call strcpytoupper() rather than copying the string explicitly and then
walking it to convert it to uppercase.
Signed-off-by: Markus Mayer
---
drivers/gpu/drm/nouveau/nvkm/engine/fifo/gk104.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
Call strlcpytolower() rather than copying the string explicitly and
then walking it to convert it to lowercase.
Signed-off-by: Markus Mayer
---
drivers/gpu/drm/nouveau/nvkm/core/firmware.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git
Add a collection of generic functions to convert strings to lowercase
or uppercase.
Changing the case of a string (with or without copying it first) seems
to be a recurring requirement in the kernel that is currently being
solved by several duplicated implementations doing the same thing. This
This series introduces a family of generic string case conversion
functions. This kind of functionality is needed in several places in
the kernel. Right now, everybody seems to be implementing their own
copy of this functionality.
Based on the discussion of the previous version of this series[1]
On Wed, 10 Aug 2016 13:52:45 +0200
Boris Brezillon wrote:
> On Wed, 10 Aug 2016 14:41:52 +0300
> Ville Syrjälä wrote:
>
> > On Wed, Aug 10, 2016 at 11:25:03AM +0200, Boris Brezillon wrote:
> > > On Wed, 10 Aug 2016 12:09:41 +0300
> > > Ville Syrjälä wrote:
> > >
> > > > On Wed, Aug
Hi Lin,
I add the some comment on below.
If you modify them, feel free to add the my reviewed tag on next version:
Reviewed-by: Chanwoo Choi
On 2016ë
08ì 10ì¼ 12:26, Lin Huang wrote:
> base on dfi result, we do ddr frequency scaling, register
> dmc driver to devfreq framework, and use
Hi Dave,
A few fixes for 4.8:
- revert temporary workarounds for PX now that the d3cold stuff as landed
- fix bugs in a couple of error paths
The following changes since commit 36e9d08b58f44c3a02974c405ccaaa6ecfaf05b8:
drm/cirrus: Fix NULL pointer dereference when registering the fbdev
On Wed, 10 Aug 2016 14:41:52 +0300
Ville Syrjälä wrote:
> On Wed, Aug 10, 2016 at 11:25:03AM +0200, Boris Brezillon wrote:
> > On Wed, 10 Aug 2016 12:09:41 +0300
> > Ville Syrjälä wrote:
> >
> > > On Wed, Aug 10, 2016 at 10:35:22AM +0200, Boris Brezillon wrote:
> > > > Hi Ville,
> > >
Hello Shuah,
On Wed, Aug 10, 2016 at 1:30 PM, Shuah Khan wrote:
> Fix exynos_drm_gem_create_ioctl() attempts to allocate non-contiguous GEM
> memory without IOMMU. In this case, there is no point in attempting to
> allocate non-contiguous memory, only to return error during the next step
> from
Hello Shuah,
On Wed, Aug 10, 2016 at 1:30 PM, Shuah Khan wrote:
> Fix exynos_drm_gem_create() error messages to include flags and size when
> flags and size are invalid.
>
> Signed-off-by: Shuah Khan
> ---
Reviewed-by: Javier Martinez Canillas
Best regards,
Javier
Hi Lin,
On 2016ë
08ì 10ì¼ 12:26, Lin Huang wrote:
> This patch adds the documentation for rockchip rk3399 dmc driver.
>
> Signed-off-by: Lin Huang
> ---
> Changes in v5:
> -None
>
> Changes in v4:
> -None
>
> Changes in v3:
> -None
>
> Changes in v2:
> -None
>
> Changes in v1:
> -None
Hello Shuah,
On 08/08/2016 07:48 PM, Shuah Khan wrote:
> Fix unsupported GEM memory type error message to include the memory type
> information.
>
> Signed-off-by: Shuah Khan
> ---
> Changes since v1:
> -- Comment changed to read clearly
>
> drivers/gpu/drm/exynos/exynos_drm_fb.c | 6 +++---
>
Hi Lin,
On 2016ë
08ì 10ì¼ 12:26, Lin Huang wrote:
> This patch adds the documentation for rockchip dfi devfreq-event driver.
>
> Signed-off-by: Lin Huang
> ---
> Changes in v5:
> -None
>
> Changes in v4:
> -None
>
> Changes in v3:
> -None
>
> Changes in v2:
> -None
>
> Changes in v1:
/commits/Lin-Huang/rk3399-support-ddr-frequency-scaling/20160810-114433
config: arm-multi_v7_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 5.4.0-6) 5.4.0 20160609
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #6 from Alex Deucher ---
Bisecting is a process for determining which specific commit in a project
caused a regression. Google for "linux kernel git bisect howto".
--
You are receiving this mail because:
You are watching the
On 08/10/2016 12:35 PM, Daniel Vetter wrote:
> On Wed, Aug 10, 2016 at 11:21:56AM +0200, Fabien Dessenne wrote:
>> These pixel formats are supported by format_check() from drm_crtc.c, so
>> provide there depth and bpp.
>>
>> Signed-off-by: Fabien Dessenne
> Why?
At least for consistency between
Add a page_flip_handler2 member to drmEventContext and bump
DRM_EVENT_CONTEXT.
To make sure that the new api works as intended, modetest is
changed to use it.
Signed-off-by: Maarten Lankhorst
Cc: David Airlie
Cc: Daniel Stone
---
include/drm/drm.h | 2 +-
tests/modetest/modetest.c |
When doing a atomic commit affecting multiple crtc's, multiple events
are generated. The user_data member does not allow you to distinguish,
because they all have the same pointer.
I've chosen to use crtc_id, because using pipe would create ambiguity
when pipe = 0. A test for != 0 is easier to
When generating events for a atomic commit involving multiple crtc's
it's not possible to distinguish which crtc belongs to which page flip event.
Solve this by putting crtc_id in the reserved member of page_flip_event.
I've checked weston, and the following ddx: modesetting (xserver), i915,
drivers/devfreq/rk3399_dmc.c:393:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Lin Huang
Signed-off-by: Fengguang Wu
---
rk3399_dmc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/devfreq/rk3399_dmc.c
/linux/commits/Lin-Huang/rk3399-support-ddr-frequency-scaling/20160810-114433
coccinelle warnings: (new ones prefixed by >>)
>> drivers/devfreq/rk3399_dmc.c:393:2-3: Unneeded semicolon
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure
On Wed, Aug 10, 2016 at 11:21:56AM +0200, Fabien Dessenne wrote:
> These pixel formats are supported by format_check() from drm_crtc.c, so
> provide there depth and bpp.
>
> Signed-off-by: Fabien Dessenne
Why? Who's going to use this?
-Daniel
> ---
> drivers/gpu/drm/drm_fourcc.c | 11
On Wed, Aug 10, 2016 at 10:35:22AM +0200, Boris Brezillon wrote:
> Hi Ville,
>
> On Fri, 22 Jul 2016 18:47:01 +0300
> ville.syrjala at linux.intel.com wrote:
>
> > From: Ville Syrjälä
> >
> > The global mode_config.rotation_property is going away, switch over to
> > per-plane
Fix some comment faults in gtt.c.
Signed-off-by: Jiang Biao
---
drivers/gpu/drm/gma500/gtt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/gtt.c b/drivers/gpu/drm/gma500/gtt.c
index 8f69225..9f9f588 100644
--- a/drivers/gpu/drm/gma500/gtt.c
+++
Fix exynos_drm_gem_create_ioctl() attempts to allocate non-contiguous GEM
memory without IOMMU. In this case, there is no point in attempting to
allocate non-contiguous memory, only to return error during the next step
from exynos_drm_framebuffer_init() which leads to display manager failing
to
Fix exynos_drm_gem_create() error messages to include flags and size when
flags and size are invalid.
Signed-off-by: Shuah Khan
---
drivers/gpu/drm/exynos/exynos_drm_gem.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_gem.c
On Tue, Aug 9, 2016 at 9:41 AM, Daniel Vetter wrote:
> First part is just a bit of rst fallout to make drm doc builds warning free.
> But
> then I started to split out parts of drm_crtc into their own files.
> framebuffers
> and connectors are done, next up on my plans are encoders, and then
On Tue, Aug 9, 2016 at 9:50 AM, Daniel Vetter wrote:
> Move the documentation into Documentation/gpu, link it up and pull in
> the kernel doc.
>
> No actual text changes except that I did polish the kerneldoc a bit,
> especially for vga_client_register().
>
> v2: Remove some rst from
when in ddr frequency scaling process, vop can not do
enable or disable operation, since dcf will base on vop vblank
time to do frequency scaling and need to get vop irq if there
have vop enabled. So need register to devfreq notifier, and we can
get the dmc status. Also, when there have two vop
base on dfi result, we do ddr frequency scaling, register
dmc driver to devfreq framework, and use simple-ondemand
policy.
Signed-off-by: Lin Huang
---
Changes in v5:
- improve dmc driver suggest by Chanwoo Choi
Changes in v4:
- use arm_smccc_smc() function talk to bl31
- delete rockchip_dmc.c
This patch adds the documentation for rockchip rk3399 dmc driver.
Signed-off-by: Lin Huang
---
Changes in v5:
-None
Changes in v4:
-None
Changes in v3:
-None
Changes in v2:
-None
Changes in v1:
-None
.../devicetree/bindings/devfreq/rk3399_dmc.txt | 35 ++
1 file
on rk3399 platform, there is dfi conroller can monitor
ddr load, base on this result, we can do ddr freqency
scaling.
Signed-off-by: Lin Huang
Acked-by: Chanwoo Choi
---
Changes in v5:
-None
Changes in v4:
-None
Changes in v3:
-None
Changes in v2:
-None
Changes in v1:
-None
This patch adds the documentation for rockchip dfi devfreq-event driver.
Signed-off-by: Lin Huang
---
Changes in v5:
-None
Changes in v4:
-None
Changes in v3:
-None
Changes in v2:
-None
Changes in v1:
-None
.../bindings/devfreq/event/rockchip-dfi.txt | 20
1
add ddrc clock setting, so we can do ddr frequency
scaling on rk3399 platform in future.
Signed-off-by: Lin Huang
---
Changes in v5:
- fit for the ddr type
Changes in v4:
- None
Changes in v3:
- None
Changes in v2:
- remove clk_ddrc_dpll_src from critical clock list
Changes in v1:
- remove
Signed-off-by: Lin Huang
---
Changes in v5:
-None
Changes in v4:
-None
Changes in v3:
-None
Changes in v2:
-None
Changes in v1:
-None
include/dt-bindings/clock/rk3399-cru.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/clock/rk3399-cru.h
On new rockchip platform(rk3399 etc), there have dcf controller to
do ddr frequency scaling, and this controller will implement in
arm-trust-firmware. We add a special clock-type to handle that.
Signed-off-by: Lin Huang
---
Changes in v5:
- delete unuse mux_flag
- use div_flag to distinguish sip
rk3399 platform have dfi controller can monitor ddr load,
and dcf controller to handle ddr register so we can get the
right ddr frequency and make ddr controller happy work(which
will implement in bl31). So we do ddr frequency scaling with
following flow:
kernel
On Wed, 10 Aug 2016 12:09:41 +0300
Ville Syrjälä wrote:
> On Wed, Aug 10, 2016 at 10:35:22AM +0200, Boris Brezillon wrote:
> > Hi Ville,
> >
> > On Fri, 22 Jul 2016 18:47:01 +0300
> > ville.syrjala at linux.intel.com wrote:
> >
> > > From: Ville Syrjälä
> > >
> > > The global
On Wed, Aug 10, 2016 at 04:52:53PM +0800, jiang.biao2 at zte.com.cn wrote:
>
>
> Daniel Vetter wrote on 2016/08/10 16:35:29:
>
> > Daniel Vetter
> > From: Daniel Vetter
> >
> > 2016/08/10 16:35
> >
> >
> > jiang.biao2 at zte.com.cn,
> >
> >
> > Re: [RESEND PATCH] drm/gma500: Fix comments in
These pixel formats are supported by format_check() from drm_crtc.c, so
provide there depth and bpp.
Signed-off-by: Fabien Dessenne
---
drivers/gpu/drm/drm_fourcc.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/drm_fourcc.c b/drivers/gpu/drm/drm_fourcc.c
index
On Wed, Aug 10, 2016 at 11:15:29AM +0200, Daniel Vetter wrote:
> On Tue, Aug 09, 2016 at 07:45:41PM +0200, Noralf Trønnes wrote:
> > This adds support for outputting kernel messages on panic().
> > The drivers that supports it, provides a framebuffer that the
> > messages can be rendered on.
> >
On Tue, Aug 9, 2016 at 9:41 AM, Daniel Vetter wrote:
> We seem to have a bit a mess in how to describe the bus formats, with
> a multitude of competing ways. Might be best to consolidate it all and
> use MEDIA_BUS_FMT_ also for the hdmi color formats and high color
> modes.
>
> Also move all the
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160810/7331416e/attachment.html>
On Tue, Aug 09, 2016 at 07:45:41PM +0200, Noralf Trønnes wrote:
> This adds support for outputting kernel messages on panic().
> The drivers that supports it, provides a framebuffer that the
> messages can be rendered on.
>
> Signed-off-by: Noralf Trønnes
Thinking about how we should
On Tue, Aug 9, 2016 at 9:41 AM, Daniel Vetter wrote:
> - Shuffle docs from drm-kms.rst into the structure docs where it makes
> sense.
> - Put the remaining bits into a new overview section.
>
> One thing I've changed is around probing: Old docs says that you
> _must_ use the probe helpers,
On Tue, Aug 9, 2016 at 9:41 AM, Daniel Vetter wrote:
> They're only used internally within the dp helpers. Also nuke the
> kerneldoc (we only document the driver interface in the drm shared
> functions). And move the header file from the public include/
> directory to the source files into
1 - 100 of 135 matches
Mail list logo