On 03.08.2016 11:24, Marek Szyprowski wrote:
Hi,
> I'm working now on something similar, but more generic. There is
> already a framework for picture processing (converting, scaling,
> blitting, rotating) in Exynos DRM.
In DRM, not v4l ? Hmm, interesting.
On mx5/mx6 we've got an IPU, which is a
On 03.08.2016 13:47, Daniel Vetter wrote:
> Because for optimal performance you _must_ supply the commands to the
> kernel in an as close to the format/layout used by the hardware as
> possible. That means no shared command submission of any kind. And the
> other reason is that cache transfers and
#x27;t get this command
to work.
--
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/20160804/1a48d71f/attachment.html>
Hi Lin,
On 2016ë
08ì 03ì¼ 16:38, hl wrote:
>
> Hi Chanwoo Choi,
> On 2016å¹´08æ02æ¥ 12:21, Chanwoo Choi wrote:
>> Hi Lin,
>>
>> On the next version, I'd like you to add the 'linux-pm at vger.kernel.org'
>> because devfreq is a subsystem of power management.
> Sure, will do it next version
-
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/20160804/a9083cb7/attachment-0001.html>
HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160804/dbf46619/attachment.html>
Hi Yakir
After apply your patch, I got following warning messge:
drivers/gpu/drm/rockchip/inno_hdmi.c:818:2: warning: initialization from
incompatible pointer type [enabled by default]
drivers/gpu/drm/rockchip/inno_hdmi.c:818:2: warning: (near
initialization for 'audio_codec_ops.hw_params') [en
Mark,
Got it, would rebase soonest :-)
Thanks,
- Yakir
On 08/04/2016 10:01 AM, Mark yao wrote:
> Hi Yakir
>
> After apply your patch, I got following warning messge:
>
> drivers/gpu/drm/rockchip/inno_hdmi.c:818:2: warning: initialization
> from incompatible pointer type [enabled by default]
>
[1.162571] Unable to handle kernel NULL pointer dereference at virtual
address 0200
[1.165656] Modules linked in:
[1.165941] CPU: 5 PID: 143 Comm: kworker/5:2 Not tainted 4.4.15 #237
[1.166506] Hardware name: Rockchip RK3399 Evaluation Board v1 (Android) (DT)
[1.167153] Wor
From: Junzhi Zhao
The mtk_hdmi_send_infoframe have to
be run after PLL and PIXEL clock of HDMI enable.
Make sure that HDMI inforframes can be sent
successfully.
Signed-off-by: Junzhi Zhao
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_hdmi.c | 17 +++--
1 file chang
From: Junzhi Zhao
Pixel clock should be 297MHz when resolution is 4K.
Signed-off-by: Junzhi Zhao
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_dpi.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_dpi.c
b/drivers/gpu/d
From: Junzhi Zhao
In order to improve 4K resolution performance,
we have to enhance the HDMI driving current
when clock rate is greater than 165MHz.
Signed-off-by: Junzhi Zhao
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_mt8173_hdmi_phy.c | 42 +---
1 file
This is MT8173 HDMI 4K support PATCH v3, based on 4.7-rc1.
In order to support HDMI 4K on MT8173,
we have to make some modifications.
1) Make sure that mtk_hdmi_send_infoframe is sent successfully.
2) Enhance the HDMI driving current to improve performance.
3) Make sure that pixel clock is 297MHz
On 04.08.2016 06:33, Rodrigo Vivi wrote:
> For now DC is only helping on screen off scenarios since PSR is disabled.
>
> But if we want to enable PSR first we need to make DC reliable with screen on.
> Biggest challenge is to deal with vblank counters since frame counter register
> is read only an
Use the core destroy_state helpers to destroy core state to ensure we don't
leak if/when more fields get added later.
Signed-off-by: Daniel Kurtz
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c |3 +--
drivers/gpu/drm/mediatek/mtk_drm_plane.c |3 +--
2 files chan
From: Daniel Kurtz
This function no longer exists.
Signed-off-by: Daniel Kurtz
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.h |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_crtc.h
b/drivers/gpu/drm/mediatek/mtk_drm_crtc.h
index
These patches based on 4.7-rc1 to clean up unused function
& variable and use drm core function instead.
The following patches are needed to cleanly apply on top of v4.7-rc1:
- https://patchwork.kernel.org/patch/8044001/
(drm: Deal with rotation in drm_plane_helper_check_update())
- https://p
From: Daniel Kurtz
The mtk_plane_enable is just called once by mtk_plane_atomic_update.
So, merge mtk_plane_enable into mtk_plane_atomic_update.
While we are here, also clean up the function a bit by using an fb local
variables.
Signed-off-by: Bibby Hsieh
Signed-off-by: Daniel Kurtz
---
driv
From: Daniel Kurtz
Use the framebuffer's format to compute its cpp, and use it when
calculating the address shift value.
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_plane.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_d
From: Daniel Kurtz
Now that mtk_drm_plane just contains its base struct drm_plane, we can
just remove it and use struct drm_plane everywhere.
Signed-off-by: Daniel Kurtz
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 16
drivers/gpu/drm/mediatek/m
From: Daniel Kurtz
It is not actually useful to a mtk plane to know its zpos/index, so just
remove this field.
This let's completely remove struct mtk_drm_plane in a follow up patch.
Signed-off-by: Daniel Kurtz
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c |2 +-
To properly implement atomic w/ runtime pm, we move
drm_atomic_helper_commit_modeset_enables() above
drm_atomic_helper_commit_planes() to ensure CRTCs are enabled before
modifying plane registers, and set active_only to true to filter out
plane update notifications when the CRTC is disabled.
Accor
On Wed, Aug 03, 2016 at 08:07:38PM -0700, Dhinakaran Pandiyan wrote:
> @@ -2588,7 +2592,7 @@ _intel_dp_set_link_train(struct intel_dp *intel_dp,
> *DP |= DP_LINK_TRAIN_PAT_2_CPT;
> break;
> case DP_TRAINING_PATTERN_3:
> -
On Wed, Aug 03, 2016 at 08:07:39PM -0700, Dhinakaran Pandiyan wrote:
> Since a DRM function that reads link DP link status is available, let's
> use that instead of the i915 clone.
>
> Signed-off-by: Dhinakaran Pandiyan
> ---
> drivers/gpu/drm/i915/intel_dp.c | 15 +++
>
On Wed, Aug 03, 2016 at 08:07:40PM -0700, Dhinakaran Pandiyan wrote:
> The causes of clock recovery and channel equalization failures are not
> explicitly printed in debug messages. Help debugging link training
> failures by printing why it failed.
>
> Doing this in the driver would mean re-implem
was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160804/4cb473fe/attachment.html>
From: Michel Dänzer
With the previous change, it's safe to let page flips take effect
anytime during a vertical blank period.
This can avoid delaying a flip by a frame in some cases where we get to
amdgpu_flip_work_func -> adev->mode_info.funcs->page_flip during a
vertical blank period.
Signed
From: Michel Dänzer
Mostly the same as the existing page_flip hook, but takes an additional
parameter specifying the target vertical blank period when the flip
should take effect.
Signed-off-by: Michel Dänzer
---
drivers/gpu/drm/drm_crtc.c | 23 +++
include/drm/drm_crtc.h
From: Michel Dänzer
These flags allow userspace to explicitly specify the target vertical
blank period when a flip should take effect.
Signed-off-by: Michel Dänzer
---
Note that the previous patches in this series can avoid delaying page
flips in some cases even without this patch or any cor
From: Michel Dänzer
With the previous change, it's safe to let page flips take effect
anytime during a vertical blank period.
This can avoid delaying a flip by a frame in some cases where we get to
radeon_flip_work_func -> adev->mode_info.funcs->page_flip during a
vertical blank period.
Signed
The purpose of this series is to allow drivers to avoid unnecessarily
delaying page flips, by explicitly telling the driver which vblank seqno
a flip is supposed to take effect in.
Patch 1 sets the target to the vblank seqno after the current one when
the DRM_IOCTL_MODE_PAGE_FLIP ioctl is called,
From: Michel Dänzer
Now we can program a flip during a vertical blank period, if it's the
one targeted by the flip (or a later one). This allows simplifying
amdgpu_flip_work_func considerably.
Signed-off-by: Michel Dänzer
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 3 +-
drivers/gpu/d
From: Michel Dänzer
Now we can program a flip during a vertical blank period, if it's the
one targeted by the flip (or a later one). This allows simplifying
radeon_flip_work_func considerably.
Signed-off-by: Michel Dänzer
---
drivers/gpu/drm/radeon/radeon.h | 1 +
drivers/gpu/drm/ra
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160804/0e6f19cf/attachment-0001.html>
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160804/06f76dac/attachment.html>
On Thu, Aug 04, 2016 at 04:11:06AM +0100, Chris Wilson wrote:
> On Wed, Aug 03, 2016 at 08:07:39PM -0700, Dhinakaran Pandiyan wrote:
> > Since a DRM function that reads link DP link status is available, let's
> > use that instead of the i915 clone.
> >
> > Signed-off-by: Dhinakaran Pandiyan
> > -
ives/dri-devel/attachments/20160804/7ef848a1/attachment.html>
Remove code for reading the EDID and DPCD fields and use the helpers
instead.
Besides the obvious code reduction, other helpers are being added to the
core that could be used in this driver and will be good to be able to
use them instead of duplicating them.
Signed-off-by: Tomeu Vizoso
Cc: Javie
On 2 August 2016 at 08:49, Jon Hunter wrote:
>
> On 02/08/16 07:26, Tomeu Vizoso wrote:
>> On 23 June 2016 at 17:59, Jon Hunter wrote:
>>> If the 'i2c-bus' device-tree node is present for an I2C adapter then
>>> parse this subnode for I2C slaves.
>>>
>>> Signed-off-by: Jon Hunter
>>> ---
>>> dr
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/20160804/67a2500a/attachment.html>
On Wed, Aug 03, 2016 at 03:19:28PM -0700, Matt Roper wrote:
> On Wed, Aug 03, 2016 at 06:00:42PM +0300, Ville Syrjälä wrote:
> > On Tue, Aug 02, 2016 at 06:37:37PM -0400, Lyude wrote:
> > > Now that we can hook into update_crtcs and control the order in which we
> > > update CRTCs at each modeset
On Wed, 03 Aug 2016, Noralf Trønnes wrote:
> Hi,
>
> I have changed simpledrm to use drm_simple_kms_helper and now I'm
> facing this:
>
> drivers/video/fbdev/Kconfig:5:error: recursive dependency detected!
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
>
> drivers/video/fbd
Hey
On Thu, Aug 4, 2016 at 9:04 AM, Jani Nikula
wrote:
> On Wed, 03 Aug 2016, Noralf Trønnes wrote:
>> Hi,
>>
>> I have changed simpledrm to use drm_simple_kms_helper and now I'm
>> facing this:
>>
>> drivers/video/fbdev/Kconfig:5:error: recursive dependency detected!
>> For a resolution refer
On 03/08/16 20:11, Daniel Vetter wrote:
> It's super confusing that new drivers need to be marked with
> DRIVER_MODESET when really it means DRIVER_MODERN. Much better to
> invert the meaning and rename it to something that's suitably
> off-putting.
>
> Since there's over 100 places using DRIVER_MO
Hi
On Wed, Aug 3, 2016 at 9:11 PM, Daniel Vetter wrote:
> It's super confusing that new drivers need to be marked with
> DRIVER_MODESET when really it means DRIVER_MODERN. Much better to
> invert the meaning and rename it to something that's suitably
> off-putting.
>
> Since there's over 100 plac
Hi
On Wed, Aug 3, 2016 at 9:11 PM, Daniel Vetter wrote:
> Except for nouveau, only legacy drivers need this really. And nouveau
> is already marked up with DRIVER_KMS_LEGACY_CONTEXT as the special
> case.
>
> I've tried to be careful to leave everything related to modeset still
> using the DRIVER
On Thu, Aug 04, 2016 at 09:32:01AM +0200, David Herrmann wrote:
> Hi
>
> On Wed, Aug 3, 2016 at 9:11 PM, Daniel Vetter
> wrote:
> > It's super confusing that new drivers need to be marked with
> > DRIVER_MODESET when really it means DRIVER_MODERN. Much better to
> > invert the meaning and rename
On 03/08/16 20:11, Daniel Vetter wrote:
> Except for nouveau, only legacy drivers need this really. And nouveau
> is already marked up with DRIVER_KMS_LEGACY_CONTEXT as the special
> case.
>
> I've tried to be careful to leave everything related to modeset still
> using the DRIVER_MODESET flag. Oth
On Thu, 04 Aug 2016, Rodrigo Vivi wrote:
> No functional change.
>
> This is the last user of legacy function so we will be able
> to clean up drm_irq.c a bit.
>
> Signed-off-by: Rodrigo Vivi
> ---
> drivers/gpu/drm/i915/intel_drv.h | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
>
Nice, looking forward to this for quite a while now.
I'm rather busy and not so deep into the display stuff anyway, so the
whole set is Acked-by: Christian König .
Let me know if I should take a deeper look as well.
Regards,
Christian.
Am 04.08.2016 um 05:39 schrieb Michel Dänzer:
> The purp
On Thu, Aug 04, 2016 at 12:39:41PM +0900, Michel Dänzer wrote:
> From: Michel Dänzer
>
> These flags allow userspace to explicitly specify the target vertical
> blank period when a flip should take effect.
I like the idea. Atomic could use this too, although there we'd need to
potentially pass
On 03/08/16 19:04, David Herrmann wrote:
> The minor referred to by "DRM_MINOR_LEGACY" is called 'dev->primary' and
> gets 'cardX' as name assigned. Lets reduce this magnificent number of
> names for the same concept by one and rename DRM_MINOR_LEGACY to
> DRM_MINOR_PRIMARY (to match the actual str
On Thu, 04 Aug 2016, Dhinakaran Pandiyan
wrote:
> A full dump of link status can be handy in debugging link training
> failures. Let's add that to the debug messages when link training fails.
>
> Signed-off-by: Dhinakaran Pandiyan
> ---
> drivers/gpu/drm/i915/intel_dp_link_training.c | 11 +
On Thu, 04 Aug 2016, David Herrmann wrote:
> Hey
>
> On Thu, Aug 4, 2016 at 9:04 AM, Jani Nikula
> wrote:
>> On Wed, 03 Aug 2016, Noralf Trønnes wrote:
>>> Hi,
>>>
>>> I have changed simpledrm to use drm_simple_kms_helper and now I'm
>>> facing this:
>>>
>>> drivers/video/fbdev/Kconfig:5:error
On Thu, Aug 04, 2016 at 01:32:57AM +0200, Enrico Weigelt, metux IT consult
wrote:
> On 03.08.2016 13:47, Daniel Vetter wrote:
>
> > Because for optimal performance you _must_ supply the commands to the
> > kernel in an as close to the format/layout used by the hardware as
> > possible. That means
On Thu, Aug 04, 2016 at 10:38:02AM +0300, Jani Nikula wrote:
> On Thu, 04 Aug 2016, Rodrigo Vivi wrote:
> > No functional change.
> >
> > This is the last user of legacy function so we will be able
> > to clean up drm_irq.c a bit.
> >
> > Signed-off-by: Rodrigo Vivi
> > ---
> > drivers/gpu/drm/i
Am 03.08.2016 um 11:16 schrieb Nicolai Hähnle:
> On 03.08.2016 11:09, Dan Carpenter wrote:
>> Hello Nicolai Hähnle,
>>
>> The patch 324c614a819a: "drm/amdgpu/gfx7: set
>> USER_SHADER_ARRAY_CONFIG based on disable_cu parameter" from Jun 17,
>> 2016, leads to the following static checker warning:
>
On 3 August 2016 at 10:01, Daniel Vetter wrote:
> On Fri, Jul 22, 2016 at 04:10:45PM +0200, Tomeu Vizoso wrote:
>> 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 imp
Lets move forward and hide the remaining DRI1 drivers behind a config
option, so we have a central place to disable them all. Furthermore, we
can provide a clear warning to anyone enabling them.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/Kconfig | 135 -
The legacy DRI1 drivers expose highly broken interfaces to user-space. No
modern system should enable them, or you will effectively allow user-space
to circumvent most of your kernel security measures. The DRI1 kernel APIs
are simply broken.
User-space can always use vesafb/efifb/simplefb and frie
On Thu, Aug 04, 2016 at 10:21:58AM +0800, Mark Yao wrote:
> [1.162571] Unable to handle kernel NULL pointer dereference at virtual
> address 0200
> [1.165656] Modules linked in:
> [1.165941] CPU: 5 PID: 143 Comm: kworker/5:2 Not tainted 4.4.15 #237
> [1.166506] Hardware name: R
On Wed, Aug 03, 2016 at 10:04:36PM +0300, Ville Syrjälä wrote:
> On Wed, Aug 03, 2016 at 09:53:46AM -0700, Rodrigo Vivi wrote:
> > It was really strange to see negative vblank seqs on debug
> > messages. It is rare to have that big number, but when it
> > happens it is confusing and misleading.
>
On Thu, Aug 04, 2016 at 10:06:56AM +0200, David Herrmann wrote:
> Lets move forward and hide the remaining DRI1 drivers behind a config
> option, so we have a central place to disable them all. Furthermore, we
> can provide a clear warning to anyone enabling them.
>
> Signed-off-by: David Herrmann
On Wed, Aug 3, 2016 at 8:26 PM, Chris Wilson
wrote:
> At a higher level, all objects are created with definite size i.e. 0 is
> illegal. In forthcoming patches, this assumption is dependent upon in
> the drm_mm range manager, i.e. trying to create a drm_mm node with size
> 0 will have undefined b
On Wed, Aug 03, 2016 at 07:26:28PM +0100, Chris Wilson wrote:
> At a higher level, all objects are created with definite size i.e. 0 is
> illegal. In forthcoming patches, this assumption is dependent upon in
> the drm_mm range manager, i.e. trying to create a drm_mm node with size
> 0 will have und
On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
> The legacy DRI1 drivers expose highly broken interfaces to user-space. No
> modern system should enable them, or you will effectively allow user-space
> to circumvent most of your kernel security measures. The DRI1 kernel APIs
> are
On Wed, Aug 03, 2016 at 08:08:19PM +0100, Chris Wilson wrote:
> On Wed, Aug 03, 2016 at 08:04:29PM +0200, David Herrmann wrote:
> > Rather than using "struct file*", use "struct drm_file*" as tag VM tag for
> > BOs. This will pave the way for "struct drm_file*" without any "struct
> > file*" back-p
On Thu, Aug 04, 2016 at 08:45:25AM +0100, Frank Binns wrote:
> On 03/08/16 19:04, David Herrmann wrote:
> > The minor referred to by "DRM_MINOR_LEGACY" is called 'dev->primary' and
> > gets 'cardX' as name assigned. Lets reduce this magnificent number of
> > names for the same concept by one and re
On Thu, Aug 04, 2016 at 08:37:49AM +0100, Frank Binns wrote:
> On 03/08/16 20:11, Daniel Vetter wrote:
> > Except for nouveau, only legacy drivers need this really. And nouveau
> > is already marked up with DRIVER_KMS_LEGACY_CONTEXT as the special
> > case.
> >
> > I've tried to be careful to leav
On Wed, Aug 03, 2016 at 02:33:39PM -0700, Rodrigo Vivi wrote:
> DC state reset the frame counter that is a read-only register.
>
> So, besides blocking DC state on vblank let's restore the
> drm crtc vblank counter to a place we know it is reliable.
>
> Signed-off-by: Rodrigo Vivi
> ---
> drive
Hey
On Wed, Aug 3, 2016 at 9:01 PM, Chris Wilson
wrote:
> On Wed, Aug 03, 2016 at 08:04:26PM +0200, David Herrmann wrote:
>> @@ -98,13 +99,14 @@ int drm_clients_info(struct seq_file *m, void *data)
>>
>> rcu_read_lock(); /* locks pid_task()->comm */
>> task = pid_task
Hey
On Thu, Aug 4, 2016 at 10:16 AM, Daniel Vetter wrote:
> On Wed, Aug 03, 2016 at 08:08:19PM +0100, Chris Wilson wrote:
>> On Wed, Aug 03, 2016 at 08:04:29PM +0200, David Herrmann wrote:
>> > Rather than using "struct file*", use "struct drm_file*" as tag VM tag for
>> > BOs. This will pave the
On Wed, Aug 03, 2016 at 02:33:38PM -0700, Rodrigo Vivi wrote:
> In modern systems there are situations that you can let the screen
> enabled and sleep or shut off a most of the display controler.
>
> In situations like this the vblank hw counter can be reset.
> When this happens everything in the
On 04/08/16 09:20, Daniel Vetter wrote:
> On Thu, Aug 04, 2016 at 08:37:49AM +0100, Frank Binns wrote:
>> On 03/08/16 20:11, Daniel Vetter wrote:
>>> Except for nouveau, only legacy drivers need this really. And nouveau
>>> is already marked up with DRIVER_KMS_LEGACY_CONTEXT as the special
>>> case
On Wed, Aug 03, 2016 at 02:33:34PM -0700, Rodrigo Vivi wrote:
> This will allow drivers to control specific power saving
> feature and power domains when dealing with vblanks.
>
> Vblanks code are protected by spin_locks where we can't
> have anything that can sleep. While power saving features
>
On Wed, Aug 03, 2016 at 02:33:35PM -0700, Rodrigo Vivi wrote:
> drm_crtc_vblank_get call the drm_vblank_prepare that will be used soon
> to control power saving states or anything else that needs a mutex
> before the vblank happens.
>
> local_irq_disable disables kernel preemption so we won't be a
On Thu, Aug 04, 2016 at 09:36:36AM +0100, Frank Binns wrote:
> On 04/08/16 09:20, Daniel Vetter wrote:
> > On Thu, Aug 04, 2016 at 08:37:49AM +0100, Frank Binns wrote:
> > > On 03/08/16 20:11, Daniel Vetter wrote:
> > > > Except for nouveau, only legacy drivers need this really. And nouveau
> > > >
Thanks for the review, Sean.
My comments, inline.
Regards
Shashank
On 8/3/2016 11:10 PM, Sean Paul wrote:
> On Wed, Aug 3, 2016 at 6:56 AM, Shashank Sharma
> wrote:
>> This patch adds drm flag bits for aspect ratio information
>>
>> Currently drm flag bits don't have field for mode's picture
>>
Regards
Shashank
On 8/3/2016 11:14 PM, Sean Paul wrote:
> On Wed, Aug 3, 2016 at 6:56 AM, Shashank Sharma
> wrote:
>> Current DRM layer functions dont parse aspect ratio information
> s/dont/don't/
Got it.
>
>> while converting a user mode->kernel mode or viceversa. This
> s/viceversa/vice vers
On 3 August 2016 at 19:04, David Herrmann wrote:
> @@ -277,9 +276,9 @@ EXPORT_SYMBOL(drm_vma_offset_remove);
> /**
> * drm_vma_node_allow - Add open-file to list of allowed users
> * @node: Node to modify
> - * @filp: Open file to add
> + * @tag: Tag of file to remove
s/to remove/to add/
-E
On 3 August 2016 at 11:56, Shashank Sharma wrote:
> --- a/include/uapi/drm/drm_mode.h
> +++ b/include/uapi/drm/drm_mode.h
> +
> +/* Aspect ratio flag bitmask (4 bits 22:19) */
> +#define DRM_MODE_FLAG_PARMASK (0x0F<<19)
> +#define DRM_MODE_FLAG_PARNONE \
> +
Hi,
On 4 August 2016 at 04:39, Michel Dänzer wrote:
> Patch 6 extends the ioctl with new flags, which allow userspace to
> explicitly specify the target vblank seqno. This can also avoid delaying
> flips in some cases where we are already in the target vertical blank
> period when the ioctl is c
On 04.08.2016 18:51, Daniel Stone wrote:
> On 4 August 2016 at 04:39, Michel Dänzer wrote:
>> Patch 6 extends the ioctl with new flags, which allow userspace to
>> explicitly specify the target vblank seqno. This can also avoid delaying
>> flips in some cases where we are already in the target ve
Hi,
On 4 August 2016 at 08:50, Daniel Vetter wrote:
> One problem with 2d blitters is that there's no common userspace
> interface, but many: Xrender, hwc, old X drawing api, various attempts by
> khronos to standardize something, cairo, ... It's probably worse than
> video decoding even, and def
On 4 August 2016 at 11:01, Michel Dänzer wrote:
> On 04.08.2016 18:51, Daniel Stone wrote:
>> On 4 August 2016 at 04:39, Michel Dänzer wrote:
>>> Patch 6 extends the ioctl with new flags, which allow userspace to
>>> explicitly specify the target vblank seqno. This can also avoid delaying
>>> f
drm_connector_register_all requires a few too many locks because our
connector_list locking is busted. Add another FIXME+hack to work
around this. This should address the below lockdep splat:
==
[ INFO: possible circular locking dependency detect
Hello Emil,
Thanks for your time.
I have got mixed opinion on this.
IMHO we should expose them to userspace too, as UI agents like Hardware
composer/X/Wayland must know what does these
flags means, so that they can display them on the end user screen (like
settings menu)
But few people even
On Thu, 04 Aug 2016, Daniel Vetter wrote:
> drm_connector_register_all requires a few too many locks because our
> connector_list locking is busted. Add another FIXME+hack to work
> around this. This should address the below lockdep splat:
>
> ==
2016-07-12 12:13 GMT+02:00 Daniel Vetter :
> On Wed, Jun 29, 2016 at 6:31 AM, Daniel Kurtz wrote:
>> On Fri, Jun 17, 2016 at 3:14 AM, Emil Velikov
>> wrote:
+static ssize_t ps8640_update_fw_store(struct device *dev,
+ struct device_attribute *attr,
>
On Thu, Aug 04, 2016 at 03:46:09PM +0530, Sharma, Shashank wrote:
> Hello Emil,
>
> Thanks for your time.
>
> I have got mixed opinion on this.
>
> IMHO we should expose them to userspace too, as UI agents like Hardware
> composer/X/Wayland must know what does these
>
> flags means, so that the
On Thu, Aug 04, 2016 at 10:59:57AM +0800, Bibby Hsieh wrote:
> To properly implement atomic w/ runtime pm, we move
> drm_atomic_helper_commit_modeset_enables() above
> drm_atomic_helper_commit_planes() to ensure CRTCs are enabled before
> modifying plane registers, and set active_only to true to fi
On Thu, Aug 04, 2016 at 12:39:36PM +0900, Michel Dänzer wrote:
> From: Michel Dänzer
>
> Mostly the same as the existing page_flip hook, but takes an additional
> parameter specifying the target vertical blank period when the flip
> should take effect.
>
> Signed-off-by: Michel Dänzer
> ---
On Thu, Aug 04, 2016 at 12:39:41PM +0900, Michel Dänzer wrote:
> From: Michel Dänzer
>
> These flags allow userspace to explicitly specify the target vertical
> blank period when a flip should take effect.
>
> Signed-off-by: Michel Dänzer
> ---
>
> Note that the previous patches in this ser
On Thu, Aug 04, 2016 at 12:35:59PM +0200, Enric Balletbo Serra wrote:
> 2016-07-12 12:13 GMT+02:00 Daniel Vetter :
> > On Wed, Jun 29, 2016 at 6:31 AM, Daniel Kurtz
> > wrote:
> >> On Fri, Jun 17, 2016 at 3:14 AM, Emil Velikov >> gmail.com> wrote:
> +static ssize_t ps8640_update_fw_store(st
the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160804/2e4c8373/attachment.html>
On Thu, Aug 04, 2016 at 12:47:38PM +0200, Daniel Vetter wrote:
> On Thu, Aug 04, 2016 at 12:39:36PM +0900, Michel Dänzer wrote:
> > From: Michel Dänzer
> >
> > Mostly the same as the existing page_flip hook, but takes an additional
> > parameter specifying the target vertical blank period when
This is MT2701 DRM support PATCH v6, based on 4.7-rc1.
We add DSI interrupt control, transfer function for MIPI DSI panel support.
Most codes are the same, except some register changed.
For example:
- DISP_OVL address offset changed, color format definition changed.
- DISP_RDMA fifo size changed
Add MT8173 prefix for hardware related macros.
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 60
1 file changed, 30 insertions(+), 30 deletions(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c
b/drivers/gpu/drm/mediatek/mtk_drm_ddp
There are some hardware settings changed, between MT8173 & MT2701:
DISP_OVL address offset changed, color format definition changed.
DISP_RDMA fifo size changed.
DISP_COLOR offset changed.
And add prefix for mtk_ddp_main & mtk_ddp_ext & mutex_mod.
Signed-off-by: YT Shen
---
drivers/gpu/drm/media
We need to acquire mutex before using the resources,
and need to release it after finished.
So we don't need to write registers in the blanking period.
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 75 +++
drivers/gpu/drm/mediatek/mtk_drm_ddp.
1 - 100 of 192 matches
Mail list logo
