linux-samsung-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrzej Hajda <a.hajda@samsung.com>
To: Inki Dae <inki.dae@samsung.com>,
	dri-devel@lists.freedesktop.org,
	linux-samsung-soc@vger.kernel.org
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] drm/exynos/dsi: make te-gpios optional
Date: Wed, 15 Mar 2017 08:58:57 +0100	[thread overview]
Message-ID: <2573ff3c-f04f-0270-329b-4ed626748300@samsung.com> (raw)
In-Reply-To: <58C8B98B.3070505@samsung.com>

On 15.03.2017 04:48, Inki Dae wrote:
>
> 2017년 03월 14일 00:30에 Andrzej Hajda 이(가) 쓴 글:
>> In case of HW-TRIGGER te-gpios interrupt is not necessary. With this
>> patch we can get rid of 60 interrupt callbacks per second.
> Andrzej,
>
> Sorry but above description is not clear.

I agree, it could be improved.

>
> If panel device node of command mode panel device doesn't provide te-gpios property then now the panel driver will fail to probe.
> Seems this patch makes it to allow the panel driver probing is always ok even if gpio is invalid.

I guess you mean DSI driver.

>
> So how about handling this at top of this function like below?
>
> if (!of_property_read_bool(node, "te-gpios"))
> 	return 0;

Looks OK, it can be also done without additional call:
dsi->te_gpio = of_get_named_gpio(dsi->panel_node, "te-gpios", 0);
if (dsi->te_gpio == -ENOENT)
        return 0;

>
> And I think the description should be modified properly including subject of this patch. 

OK, I will post v2.

BTW, I though little bit about it and:
1. te-gpios property is in panel node, but panel driver do not use it at
all.
2. it is parsed by DSI driver, but DSI driver does not need it at all,
it just forwards it to DECON.
3. DECON driver uses it, but it does not control it at all: parsing,
switching on/off, life time.

So maybe it would better to move whole te-gpios property to DECON node,
maybe even make it interrupt property instead of gpio, as it servers
only to irq.
After move DECON driver would know when this property is required and
probe should fail (SW mode), it could control enable/disable of
associated irq - currently the code is racy,
and finally there will not be parsing of panel node by DSI driver - it
violates DT principles.

What do you think about it?

Regards
Andrzej

>
> Thanks,
> Inki Dae
>
>> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
>> ---
>>  drivers/gpu/drm/exynos/exynos_drm_dsi.c | 5 ++---
>>  1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/exynos/exynos_drm_dsi.c b/drivers/gpu/drm/exynos/exynos_drm_dsi.c
>> index 812e2ec..f95fac5 100644
>> --- a/drivers/gpu/drm/exynos/exynos_drm_dsi.c
>> +++ b/drivers/gpu/drm/exynos/exynos_drm_dsi.c
>> @@ -1349,9 +1349,8 @@ static int exynos_dsi_register_te_irq(struct exynos_dsi *dsi)
>>  
>>  	dsi->te_gpio = of_get_named_gpio(dsi->panel_node, "te-gpios", 0);
>>  	if (!gpio_is_valid(dsi->te_gpio)) {
>> -		dev_err(dsi->dev, "no te-gpios specified\n");
>> -		ret = dsi->te_gpio;
>> -		goto out;
>> +		dev_info(dsi->dev, "no te-gpios specified\n");
>> +		return 0;
>>  	}
>>  
>>  	ret = gpio_request(dsi->te_gpio, "te_gpio");
>>
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-03-15  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170313153029eucas1p114f034a5dea7374f6d14d4d1636d0b68@eucas1p1.samsung.com>
2017-03-13 15:30 ` [PATCH] drm/exynos/dsi: make te-gpios optional Andrzej Hajda
2017-03-15  3:48   ` Inki Dae
2017-03-15  7:58     ` Andrzej Hajda [this message]
2017-03-15  9:07       ` Inki Dae

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2573ff3c-f04f-0270-329b-4ed626748300@samsung.com \
    --to=a.hajda@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).