2014? 1? 8? Inki Dae?? ??:
> 2014? 1? 7? Jakob Bornecrantz?? ??:
>> On Tue, Jan 7, 2014 at 7:40 AM, Hyungwon Hwang
wrote:
>>> tests/kmstest: support exynos
>>>
>
>>> Add exynos to list of kmstest supported modules.
>>>
>>> Sign
ibkms/internal.h|2 ++
>> libkms/linux.c |4
>> tests/kmstest/main.c |1 +
>> 3 files changed, 7 insertions(+)
>
> Reviewed-by: Jakob Bornecrantz
>
Hi Rob,
Could you merge this patch?
Signed-off-by: Inki dae
Thank
ted by Seung-Woo link below, and I
merged already them to exynos-drm-next.
http://www.spinics.net/lists/dri-devel/msg50921.html
Thanks,
Inki Dae
> Reviewed-by: Daniel Vetter
>> ---
>> drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 +-
>> 1 file changed, 1 insertion(+), 1
problem.
Thanks,
Inki Dae
The following changes since commit fe3c703c3d80bd4c2da0d47a7d56930926af7cbc:
drm/dp: Clarify automated test constant and add constant for FAUX test
pattern (2013-12-18 11:47:43 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git
Kill DRM_WAKUP and DRM_INIT_WAITQUEUE
Less yelling ftw!
Signed-off-by: Daniel Vetter
Signed-off-by: Dave Airlie
It seems that Daniel missed it. So could you merge this patch to
drm-next directly?
Thanks and Happy New Year!
Inki Dae
2013/12/30 Seung-Woo Kim :
> DRM_HZ and DR
ead of existing one.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 21 +
drivers/gpu/drm/exynos/exynos_drm_drv.h |1 +
drivers/gpu/drm/exynos/exynos_drm_gem.c | 74 ++-
drivers/gpu/drm/exynos/exynos_drm
Hi,
Below is my comments.
Thanks for your contributions,
Inki Dae
2013/10/30 Sean Paul :
> This patch removes all of the suspend/resume logic from the individual
> drivers and consolidates it in drm_drv. This consolidation reduces the
> number of functions which enable/disable the ha
Sorry, there was my missing point. Ignore the below my comments.
Thanks,
Inki Dae
2013/12/3 Inki Dae :
> 2013/10/30 Sean Paul :
>> This patch implements drm_connector directly in the vidi
>> driver, this will allow us to move away from the exynos_drm_connector
>> layer
2013/12/3 Inki Dae :
> Hi Sean,
>
>
> 2013/10/30 Sean Paul :
>> This patch implements drm_connector directly in the dp driver, this will
>> allow us to move away from the exynos_drm_connector layer.
>>
>> Signed-off-by: Sean Paul
>> ---
>>
>
2013/10/30 Sean Paul :
> This creates a new display hook called create_connector. The purpose is
> to allow the display driver to create its own drm_connector instead of
> using the exynos_drm_connector. This moves things closer to completely
> removing the exynos_drm_connector abstraction.
>
> Sig
2013/10/30 Sean Paul :
> This patch implements drm_connector directly in the vidi
> driver, this will allow us to move away from the exynos_drm_connector
> layer.
>
> Signed-off-by: Sean Paul
> ---
>
> Changes in v3:
> - Added to the patchset
>
> drivers/gpu/drm/exynos/exynos_drm_vidi.c |
Hi Sean,
2013/10/30 Sean Paul :
> This patch implements drm_connector directly in the dp driver, this will
> allow us to move away from the exynos_drm_connector layer.
>
> Signed-off-by: Sean Paul
> ---
>
> Changes in v3:
> - Added to the patchset
>
> drivers/gpu/drm/exynos/exynos_dp_co
Hi Dave,
This pull request includes two fixup patches pended for long time.
Please kindly let me know if there is any problem.
Thanks,
Inki Dae
The following changes since commit 1b28c3e628315ac0d9ef2d3fac0403f05ae692db:
drm/qxl: fix memory leak in release list handling (2013-11-29 08:36
out actual codes.
Thanks,
Inki Dae
2013/11/30 Rob Clark :
> On Fri, Nov 29, 2013 at 12:05 PM, Tomasz Figa wrote:
>> On Friday 29 of November 2013 09:13:19 Rob Clark wrote:
>>> On Fri, Nov 29, 2013 at 4:10 AM, Tomasz Figa
>>> wrote:
>>> > I would mostly
gree to this way. :(
Anyway, we can say the use of lvds bridge is dependent on board but
actually, the use of lvds bridge would be more dependent on bus device
or lcd panel attached to the board. So my opinion is to bind dt in the
bus or lcd panel drivers that need lvds bridge. If dt binding of lvd
CCing Kukjin, Sylwester, and Tomasz.
Hi Kukjin, Sylwester, and Tomasz,
Shirish has investigated hdmiphy configuration in more detail, and updated
it since we gave comments to him. Shouldn't this patch series be reviewed
again? Plz, give him your feedback if necessary.
Thanks,
Ink
Hi Shirish,
2013/11/25 Shirish S :
> This patch adds dt support to hdmiphy config settings
> as it is board specific and depends on the signal pattern
> of board.
>
> Signed-off-by: Shirish S
> ---
> .../devicetree/bindings/video/exynos_hdmi.txt | 31
> drivers/gpu/drm/exynos/exy
f469 100644
--- a/arch/arm/lib/getuser.S
+++ b/arch/arm/lib/getuser.S
@@ -66,7 +66,7 @@ ENTRY(__get_user_4)
mov pc, lr
ENDPROC(__get_user_4)
-__get_user_bad:
+ENTRY(__get_user_bad)
mov r2, #0
mov r0, #-EFAULT
mov pc, lr
I guess __get_user_bad is not global but drm_mode_atomic_ioctl
function tries to refer this function as extern.
Is it build error only I can see?
Thanks,
Inki Dae
Hi Dave,
This pull request includes two fixup patches.
Please kindly let me know if there is any problem.
Thanks,
Inki Dae
The following changes since commit 760c960bd6880cf22a57c0af9ff60c96250aad39:
drm/sysfs: fix hotplug regression since lifetime changes (2013-11-21 21:10:00
+1000
This patch releases a vma object when cleaning up userptr resources.
A new vma object was allocated and copied when getting userptr pages
so the new vma object should be freed properly if the userptr pages
aren't used anymore.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
dr
> -Original Message-
> From: Tomasz Figa [mailto:tomasz.figa at gmail.com]
> Sent: Monday, November 11, 2013 11:09 AM
> To: Inki Dae
> Cc: 'Sean Paul'; dri-devel at lists.freedesktop.org; airlied at linux.ie;
> marcheu at chromium.org
> Subject: Re: [PATCH
Hi Sean,
When are you going to post your next version? Need more time? Other
DRM drivers have been merged to drm-next except Exynos. So plz hurry
up if you want to merge this re-factoring patch series during merge
window.
Thanks,
Inki Dae
2013/10/30 Sean Paul :
> This patchset refactors pa
> -Original Message-
> From: Sean Paul [mailto:seanpaul at chromium.org]
> Sent: Tuesday, November 05, 2013 12:44 AM
> To: Inki Dae
> Cc: Thierry Reding; Laurent Pinchart; dri-devel; Sylwester Nawrocki;
> St?phane Marchesin
> Subject: Re: [PATCH v2 12/26] drm/
st
>> > > >> use required-elements and leave the pipe nodes out.
>> > > >
>> > > > Just to put my two cents in, as one of the people involved into "the
>> > > > device tree movement", I'd say that instead of creating artifical
er today), as it is quite a lot of changes, so stay
> tuned for further comments. ;)
>
Hi Tomasz,
Are you reviewing yet? I have looked into this patch series but I
couldn't find any big issues excepting bridge and eDP related patches
so I
n be
done at probe of separated encoder/connector driver. Of course, for
avoiding power ordering issue, each encoder/connector drivers
shouldn't have their resume/suspend interfaces, and their pm should be
handled by dpms callback at top level of drm driver.
This way I think we could simplify to compose the display pipeline
node as device tree,and also we could have a separated device driver
as driver model.
Thanks,
Inki Dae
> Dave.
> ___
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
2013/11/1 Sean Paul :
> On Thu, Oct 31, 2013 at 6:30 AM, Inki Dae wrote:
>>
>>
>>> -Original Message-
>>> From: Sean Paul [mailto:seanpaul at chromium.org]
>>> Sent: Wednesday, October 30, 2013 1:13 AM
>>> To: dri-devel at lists.freedesk
As I mentioned already, I'll not merge eDP related codes yet. So can you
rebase patche 25 through 26 to top of patch 20?
Thanks,
Inki Dae
> -Original Message-
> From: Sean Paul [mailto:seanpaul at chromium.org]
> Sent: Wednesday, October 30, 2013 1:13 AM
>
oving this driver into drm side. Let's watch new rules for device tree
bindings of DRM world. So I'd not like to merge this driver yet.
Thanks,
Inki Dae
> -Original Message-
> From: Sean Paul [mailto:seanpaul at chromium.org]
> Sent: Wednesday, October 30, 20
t;
> - if (subdrv->manager->display_ops->type == EXYNOS_DISPLAY_TYPE_LCD)
> {
> + if (display->type == EXYNOS_DISPLAY_TYPE_LCD) {
> ret = exynos_drm_attach_lcd_bridge(dev, encoder);
The lvds bridge related codes need more reviews so I&
CCing Jingoo,
> -Original Message-
> From: Sean Paul [mailto:seanpaul at chromium.org]
> Sent: Wednesday, October 30, 2013 1:13 AM
> To: dri-devel at lists.freedesktop.org; inki.dae at samsung.com
> Cc: airlied at linux.ie; tomasz.figa at gmail.com; marcheu at chromium.org;
> Sean
> Paul
ready commented about that, and my patch has already be
removed from exynos-drm-next. Please re-post that fixup. :)
Thanks,
Inki Dae
>
> Sean
> ___
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi Dave,
2013/10/29 Dave Airlie :
> On Tue, Oct 29, 2013 at 12:56 PM, Inki Dae wrote:
>> Hi,
>>
>> 2013/10/29 Olof Johansson :
>>> On Mon, Oct 28, 2013 at 6:35 AM, Inki Dae wrote:
>>>> This patch makes callback funtions of each sub driver to be called
2013/10/28 Sean Paul :
> On Mon, Oct 28, 2013 at 9:35 AM, Inki Dae wrote:
>> This patch fixes build error incurred by the re-factoring patch applying.
>>
>> The re-factoring patch set from Sean missed to apply the update to vidi
>> module so this patch applies the up
Hi,
2013/10/29 Olof Johansson :
> On Mon, Oct 28, 2013 at 6:35 AM, Inki Dae wrote:
>> This patch makes callback funtions of each sub driver to be called
>> with device object instead of display and manager.
>>
>> Exynos drm framework doesn't need to pass a mana
2013/10/28 Sean Paul :
> On Mon, Oct 28, 2013 at 9:35 AM, Inki Dae wrote:
>> This patch makes callback funtions of each sub driver to be called
>> with device object instead of display and manager.
>>
>> Exynos drm framework doesn't need to pass a manager or a
2013/10/29 Kukjin Kim :
> On 10/28/13 06:42, Inki Dae wrote:
>>
>> Hi Tomasz,
>>
>> I have merged the re-factoring patch set from Sean Paul. Can you
>> re-base your patch set at top of exynos-drm-next?
>>
> Basically, RFC is not patch for merge. So To
Hi Shirish,
I have merged the re-factoring patch set from Sean Paul to exynos-drm-next.
Can you re-base your patch set at top of exynos-drm-next?
Thanks,
Inki Dae
> -Original Message-
> From: Shirish S [mailto:s.shirish at samsung.com]
> Sent: Monday, October 28, 2013 7:39 PM
Hi Tomasz,
I have merged the re-factoring patch set from Sean Paul. Can you
re-base your patch set at top of exynos-drm-next?
Thanks,
Inki Dae
2013/10/21 Tomasz Stanislawski :
> This patchset adds support for HDMI at SoCs from Exynos4 family. The patches
> are rebased on kisho
Hi Rahul,
I have merged the re-factoring patch set from Sean Paul to
exynos-drm-next except eDP related patch set that these need more
reviews. Can you re-base at top of exynos-drm-next?
Thanks,
Inki Dae
2013/10/22 Rahul Sharma :
> Currently, exynos hdmiphy operations and configs are k
This patch fixes build error incurred by the re-factoring patch applying.
The re-factoring patch set from Sean missed to apply the update to vidi
module so this patch applies the update so that vidi module is also built
correctly.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
bject. So this patch
hides sub driver's context from framework.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_drm_connector.c | 10 +--
drivers/gpu/drm/exynos/exynos_drm_core.c |8 +-
drivers/gpu/drm/exynos/exynos_drm_crtc.c
Sorry for some typos.
2013/10/24 Inki Dae :
> 2013/10/23 Rob Clark :
>> On Wed, Oct 23, 2013 at 9:18 AM, Inki Dae wrote:
>>> Look at omapdrm, nouveau, and radeon drm drivers.
>>
>>
>> btw, please don't look at omapdrm as a "good" example in thi
2013/10/23 Rob Clark :
> On Wed, Oct 23, 2013 at 9:18 AM, Inki Dae wrote:
>> Look at omapdrm, nouveau, and radeon drm drivers.
>
>
> btw, please don't look at omapdrm as a "good" example in this regard.
> The layering is really not a good idea and for a long ti
2013/10/23 Sean Paul :
> On Wed, Oct 23, 2013 at 10:29 AM, Dave Airlie wrote:
>>> As I mentioned earlier, display_ops is needed to have no any
>>> dependency of drm framework directly like below,
>>>
>>> DRM Framework
>>>
2013/10/23 Sean Paul :
> On Wed, Oct 23, 2013 at 1:42 AM, Inki Dae wrote:
>> 2013/10/23 Sean Paul :
>>> On Wed, Oct 23, 2013 at 12:48 AM, Inki Dae wrote:
>>>> 2013/10/23 St?phane Marchesin :
>>>>>
>>>>>
>>>>>
>>
2013/10/23 Sean Paul :
> On Wed, Oct 23, 2013 at 12:48 AM, Inki Dae wrote:
>> 2013/10/23 St?phane Marchesin :
>>>
>>>
>>>
>>> On Tue, Oct 22, 2013 at 9:15 PM, Inki Dae wrote:
>>>>
>>>> 2013/10/23 St?phane Marchesin :
2013/10/22 Inki Dae :
> 2013/10/17 Sean Paul :
>> This patch splits display and manager from subdrv. The result is that
>> crtc functions can directly call into manager callbacks and encoder
>> functions can directly call into display callbacks. This will allow
>> us to
2013/10/23 St?phane Marchesin :
>
>
>
> On Tue, Oct 22, 2013 at 9:15 PM, Inki Dae wrote:
>>
>> 2013/10/23 St?phane Marchesin :
>> >
>> >
>> >
>> > On Tue, Oct 22, 2013 at 8:38 PM, Inki Dae wrote:
>> >>
>> >> 201
2013/10/23 St?phane Marchesin :
>
>
>
> On Tue, Oct 22, 2013 at 8:38 PM, Inki Dae wrote:
>>
>> 2013/10/23 St?phane Marchesin :
>> >
>> >
>> >
>> > On Tue, Oct 22, 2013 at 7:28 PM, Inki Dae wrote:
>> >>
>> >> 201
2013/10/23 St?phane Marchesin :
>
>
>
> On Tue, Oct 22, 2013 at 7:28 PM, Inki Dae wrote:
>>
>> 2013/10/22 Sean Paul :
>> > On Tue, Oct 22, 2013 at 1:30 AM, Inki Dae wrote:
>> >>
>> >>
>> >>> -Original Message-
>&
2013/10/22 Sean Paul :
> On Tue, Oct 22, 2013 at 1:30 AM, Inki Dae wrote:
>>
>>
>>> -Original Message-
>>> From: Sean Paul [mailto:seanpaul at chromium.org]
>>> Sent: Tuesday, October 22, 2013 6:18 AM
>>> To: Inki Dae
>>>
> --
Build error. it seems that you missed vidi module. Can you consider
vidi module also?
Thanks,
Inki Dae
> drivers/gpu/drm/exynos/exynos_drm_hdmi.h | 2 +
> drivers/gpu/drm/exynos/exynos_drm_plane.c | 15 +-
> 13 files changed, 466 insertions(+), 942 deletions(-)
> delete mode 100644 drivers/gpu/drm/exynos/exynos_drm_hdmi.c
>
> -Original Message-
> From: Sean Paul [mailto:seanpaul at chromium.org]
> Sent: Tuesday, October 22, 2013 6:18 AM
> To: Inki Dae
> Cc: dri-devel; Dave Airlie; Tomasz Figa; St?phane Marchesin
> Subject: Re: [PATCH v2 12/26] drm/exynos: Split manager/display/subdrv
&
> -Original Message-
> From: Sean Paul [mailto:seanpaul at chromium.org]
> Sent: Monday, October 21, 2013 11:47 PM
> To: Inki Dae
> Cc: dri-devel; Dave Airlie; Tomasz Figa; St?phane Marchesin
> Subject: Re: [PATCH v2 12/26] drm/exynos: Split manager/display/subdrv
&
> -Original Message-
> From: Sean Paul [mailto:seanpaul at chromium.org]
> Sent: Thursday, October 17, 2013 11:37 PM
> To: Inki Dae
> Cc: dri-devel; Dave Airlie; Tomasz Figa; St?phane Marchesin
> Subject: Re: [PATCH v2 12/26] drm/exynos: Split manager/display/subdrv
&
e specific exynos drm header.
And another one, the patch 6 passes manager object to manager_ops, and for
this, you made the manager object to be set to driver data;
platform_set_drvdata(pdev, &manager). That isn't reasonable. Generally,
driver_data would point to device driver's context object.
Thanks,
Inki Dae
> -Original Message-
> From: Sean Paul [mailto:seanpaul at chromium.org]
> Sent: Thursday, October 17, 2013 5:40 AM
> To: dri-devel; InKi Dae
> Cc: Dave Airlie; Tomasz Figa; St?phane Marchesin; Sean Paul
> Subject: Re: [PATCH v2 26/26] drm/exynos: Consolidate suspend/r
2013/10/16 Sean Paul :
> On Tue, Oct 15, 2013 at 12:09 AM, Inki Dae wrote:
>> 2013/10/15 Inki Dae :
>>>> diff --git a/drivers/gpu/drm/exynos/exynos_drm_encoder.c
>>>> b/drivers/gpu/drm/exynos/exynos_drm_encoder.c
>>>> index c417c90..ba6
2013/10/15 Inki Dae :
>> diff --git a/drivers/gpu/drm/exynos/exynos_drm_encoder.c
>> b/drivers/gpu/drm/exynos/exynos_drm_encoder.c
>> index c417c90..ba63c72 100644
>> --- a/drivers/gpu/drm/exynos/exynos_drm_encoder.c
>> +++ b/drivers/gpu/drm/exynos/exynos_drm
This patch removes unnecessary runtime pm related function calls
from fimd_suspend and fimd_resume functions.
Changelog v2:
- use UNIVERSAL_DEV_PM_OPS macro instead.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 59
> diff --git a/drivers/gpu/drm/exynos/exynos_drm_encoder.c
> b/drivers/gpu/drm/exynos/exynos_drm_encoder.c
> index c417c90..ba63c72 100644
> --- a/drivers/gpu/drm/exynos/exynos_drm_encoder.c
> +++ b/drivers/gpu/drm/exynos/exynos_drm_encoder.c
> @@ -26,24 +26,23 @@
> * exynos specific encoder str
2013/10/14 Sean Paul :
> On Mon, Oct 14, 2013 at 8:42 AM, Inki Dae wrote:
>> Hi, Sean.
>>
>>
>> It's a great patch set.:) That's exactly what we want. So I'd like to merge
>> all patch set to exynos-drm-next if there is no design issue about ne
1. Do not rebase them at top of lvds-bridge patch set.
2. Change all patch set for callbacks to be called
_with_device_object instead of ctx.
The below is my comments.
Thanks for your contributions,
Inki Dae
> -Original Message-
> From: Sean Paul [mailto:seanp...
> void exynos_drm_encoder_plane_enable(struct drm_encoder *encoder, void
> *data)
> @@ -495,7 +495,7 @@ void exynos_drm_encoder_plane_enable(struct
> drm_encoder *encoder, void *data)
> zpos = *(int *)data;
>
> if (manager_ops && manager_ops->win_enable)
> - manage
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Saturday, October 12, 2013 1:20 PM
> To: Inki Dae
> Cc: DRI mailing list; Stéphane Marchesin; Dave Airlie; Tomasz Figa
> Subject: Re: [PATCH 12/23] drm/exynos: Split manager/display/subdrv
&
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Saturday, October 12, 2013 11:07 AM
> To: Inki Dae
> Cc: DRI mailing list; Stéphane Marchesin; Dave Airlie; Tomasz Figa
> Subject: Re: [PATCH 12/23] drm/exynos: Split manager/display/subdrv
&
> static int exynos_drm_create_enc_conn(struct drm_device *dev,
> - struct exynos_drm_subdrv *subdrv)
> + struct exynos_drm_display *display)
> {
> struct drm_encoder *encoder;
> struct drm_connector *conn
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Thursday, October 10, 2013 6:37 PM
> To: Inki Dae
> Cc: 'Olof Johansson'; 'Sean Paul'; devicet...@vger.kernel.org; linux-
> samsung-...@vger.kernel.org; linux-...@vger.kerne
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Thursday, October 10, 2013 3:29 AM
> To: Inki Dae
> Cc: Olof Johansson; Sean Paul; devicet...@vger.kernel.org; linux-samsung-
> s...@vger.kernel.org; linux-...@vger.kernel.org; linux-
> k
This patch removes unnecessary runtime pm related function calls
from fimd_suspend and fimd_resume functions.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 38 +-
1 file changed, 11 insertions(+), 27 deletions
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Saturday, October 05, 2013 12:05 AM
> To: Inki Dae
> Cc: Kukjin Kim; DRI mailing list; linux-samsung-soc; Linux ARM Kernel;
> Linux Kernel Mailing List; linux-...@vger.kernel.org;
> devic
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Friday, October 04, 2013 11:17 PM
> To: Inki Dae
> Cc: Kukjin Kim; DRI mailing list; linux-samsung-...@vger.kernel.org;
> linux-arm-ker...@lists.infradead.org; linux-ker...@vger.kern
2013/10/4 Sean Paul :
> On Thu, Oct 3, 2013 at 10:29 PM, Inki Dae wrote:
>> 2013/10/4 Sean Paul :
>>> This patch adds code to look for the ptn3460 in the device tree file on
>>> exynos initialization. If ptn node is found, the driver will initialize
>>> the p
2013/10/4 Sean Paul :
> This patch adds code to look for the ptn3460 in the device tree file on
> exynos initialization. If ptn node is found, the driver will initialize
> the ptn3460 driver and skip creating a DP connector (since the bridge
> driver will register its own connector).
>
> Signed-off
2013/10/4 Olof Johansson :
> On Thu, Oct 3, 2013 at 10:39 AM, Inki Dae wrote:
>> 2013/10/3 Sean Paul :
>>> On Thu, Oct 3, 2013 at 9:55 AM, Inki Dae wrote:
>>>> Can a regulator be used instead of gpio in other board case?
>>>>
>>>
>>> No
2013/10/4 Sean Paul :
> On Thu, Oct 3, 2013 at 2:23 PM, Inki Dae wrote:
>> 2013/10/4 Sean Paul :
>>> On Thu, Oct 3, 2013 at 1:39 PM, Inki Dae wrote:
>>>> 2013/10/3 Sean Paul :
>>>>> On Thu, Oct 3, 2013 at 9:55 AM, Inki Dae wrote:
>>>>&
2013/10/4 Sean Paul :
> On Thu, Oct 3, 2013 at 1:39 PM, Inki Dae wrote:
>> 2013/10/3 Sean Paul :
>>> On Thu, Oct 3, 2013 at 9:55 AM, Inki Dae wrote:
>>>> Hi, thank you for your contribution and the below is my short comments,
>>>>
>>>> 20
2013/10/4 Sean Paul :
> On Thu, Oct 3, 2013 at 1:18 PM, Inki Dae wrote:
>> 2013/10/4 Sean Paul :
>>> On Thu, Oct 3, 2013 at 10:43 AM, Inki Dae wrote:
>>>> 2013/10/2 Sean Paul :
>>>>> This patch adds code to look for the ptn3460 in the device tree fil
2013/10/3 Sean Paul :
> On Thu, Oct 3, 2013 at 9:55 AM, Inki Dae wrote:
>> Hi, thank you for your contribution and the below is my short comments,
>>
>> 2013/10/2 Sean Paul :
>>> This patch adds a drm_bridge driver for the PTN3460 DisplayPort to LVDS
>>> b
2013/10/4 Sean Paul :
> On Thu, Oct 3, 2013 at 10:43 AM, Inki Dae wrote:
>> 2013/10/2 Sean Paul :
>>> This patch adds code to look for the ptn3460 in the device tree file on
>>> exynos initialization. If ptn node is found, the driver will initialize
>>> the p
ree I recommend,
In board dts,
i2c@I2CD000 {
ptn3460_bridge: prn3460-bridge@20 {
...
}
}
fimd@11c0 {
...
output_dev = <&ptn3460_bridge>;
}
With this, I believe that you
Hi, thank you for your contribution and the below is my short comments,
2013/10/2 Sean Paul :
> This patch adds a drm_bridge driver for the PTN3460 DisplayPort to LVDS
> bridge chip.
>
> Signed-off-by: Sean Paul
> ---
> .../devicetree/bindings/drm/bridge/ptn3460.txt | 27 ++
> drivers/gpu/d
the drm_pending_event at postclose().
And it calls drm_vblank_put() for pair if there is any unhandled page
flip event.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 35 +++
1 file changed, 22 insertions
> -Original Message-
> From: linux-samsung-soc-ow...@vger.kernel.org [mailto:linux-samsung-soc-
> ow...@vger.kernel.org] On Behalf Of Tomasz Figa
> Sent: Monday, September 30, 2013 8:13 AM
> To: Sylwester Nawrocki
> Cc: Inki Dae; Rahul Sharma; devicet...@vger.kernel.
> -Original Message-
> From: Sylwester Nawrocki [mailto:sylvester.nawro...@gmail.com]
> Sent: Monday, September 30, 2013 7:09 AM
> To: Inki Dae
> Cc: Rahul Sharma; devicet...@vger.kernel.org; linux-samsung-soc;
> sw0312.kim; sunil joshi; dri-devel; kgene.kim; Sh
be waked up.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c
b/drivers/gpu/drm/exynos/exynos_drm_drv.c
index f727f98
2013/9/29 Inki Dae
>
>
> 2013/9/26 Al Viro
>
>> On Wed, Sep 25, 2013 at 01:34:30PM +0900, Inki Dae wrote:
>>
>> > It seems that we can use a new anon file instead of using drm file to
>> > resolve the issue.
>>
>> Could you describe what a
2013/9/26 Al Viro
> On Wed, Sep 25, 2013 at 01:34:30PM +0900, Inki Dae wrote:
>
> > It seems that we can use a new anon file instead of using drm file to
> > resolve the issue.
>
> Could you describe what are you trying to achieve with that ioctl() and
> what semant
Thanks for your comments.
Thank,
Inki Dae
2013/9/26 Al Viro
> On Tue, Sep 24, 2013 at 01:41:00PM +0900, Inki Dae wrote:
>
> > I can't see to hold ->mmap_sem when it calls find_vma() anywhere else.
>
> Er... What, in your opinion, would protect the result of find_vma(
2013/9/27 Rahul Sharma
> On 16 September 2013 18:10, Inki Dae wrote:
> > CCing devicetree,
> >
> >> -Original Message-
> >> From: Rahul Sharma [mailto:r.sh.o...@gmail.com]
> >> Sent: Tuesday, September 10, 2013 5:28 PM
> >> To: Sean
> -Original Message-
> From: Inki Dae [mailto:inki@samsung.com]
> Sent: Tuesday, September 24, 2013 1:41 PM
> To: 'Al Viro'
> Cc: 'YoungJun Cho'; 'dri-devel@lists.freedesktop.org'
> Subject: RE: [RFC] deadlock in "drm/exynos: fi
Please, ignore this patch. This patch has still some problems. I will post
it later.
Thanks,
Inki Dae
> -Original Message-
> From: Inki Dae [mailto:inki@samsung.com]
> Sent: Monday, September 23, 2013 7:43 PM
> To: airl...@linux.ie; dri-devel@lists.freedesktop.org
&g
Thanks for your comment.
> -Original Message-
> From: Al Viro [mailto:v...@ftp.linux.org.uk] On Behalf Of Al Viro
> Sent: Monday, September 23, 2013 10:07 PM
> To: Inki Dae
> Cc: 'YoungJun Cho'; dri-devel@lists.freedesktop.org
> Subject: Re: [RFC] deadlo
mmap_pgoff
call and then up_write(&mm->mmap_sem) after do_mmap_pg_off call
so that when another process called mmap system call, the process
can wait for up_write() call until the ->f_op pointer is restored.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exy
Hi,
> -Original Message-
> From: Al Viro [mailto:v...@ftp.linux.org.uk] On Behalf Of Al Viro
> Sent: Monday, September 23, 2013 6:29 AM
> To: YoungJun Cho
> Cc: dri-devel@lists.freedesktop.org; Inki Dae
> Subject: [RFC] deadlock in "drm/exynos: fix wrong point
CPU access to a shared buffer if there
is someone accessing the shared buffer. If no anyone then select
system call will be returned at once.
References:
[1] http://lwn.net/Articles/470339/
[2] https://patchwork.kernel.org/patch/2625361/
[3] http://linux.die.net/man/2/fcntl
Signed-o
ler doesn't use intefaces for
the DMA device driver.
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/base/dma-buf.c | 81
1 file changed, 81 insertions(+)
diff --git a/drivers/base/dma-buf.c b/drivers/base/dma-buf.c
in
<-- Request gpu rendering
time |
|
|<-- Request page flip (deferred)
| <- vsync signal
|<-- Displayed on screen
|
|
|
| <- vsy
Hi Dave,
Just small fixes, and code cleanups.
Please kindly let me know if there is any problem.
Thanks,
Inki Dae
The following changes since commit d2aebe338ac745f1934d01618f97a30f6bba5fec:
drm/udl: rip out set_need_resched (2013-09-16 08:35:04 +1000)
are available in the git repository
1301 - 1400 of 3059 matches
Mail list logo
