From: Inki Dae <inki.dae@samsung.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Kukjin Kim <kgene@kernel.org>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
David Airlie <airlied@linux.ie>,
Joonyoung Shim <jy0922.shim@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] drm/exynos: don't use HW trigger for Exynos5420/5422/5800
Date: Mon, 13 Jun 2016 10:38:17 +0900 [thread overview]
Message-ID: <575E0E89.40400@samsung.com> (raw)
In-Reply-To: <CABxcv=nuw7ZUF0bDC1PZfP0WVQhRY3HSoO5LdwT8_FvNi9N+aQ@mail.gmail.com>
2016년 06월 10일 09:24에 Javier Martinez Canillas 이(가) 쓴 글:
> Hello Inki,
>
> On Thu, Jun 9, 2016 at 6:35 PM, Inki Dae <inki.dae@samsung.com> wrote:
>
> [snip]
>
>>> I know that removing .trg_type is enough but I also removed those lines
>>> because the fields are not used if .trg_type != I80_HW_TRG. So there is
>>> no point to leave a set for unused fields.
>>>
>>> We can latter add those one HW trigger support is fixed for Exynos5420.
>>>
>>
>> As of now, I can merge it but I think it would be not reasonable solution because potential problem still exists even we use SW trigger mode in default - ie., in case of using HW trigger mode at bootloader, same problem would happen as long as we don't support PSR mode support.
>>
>
> Yes, I understand that the problem will show again if the bootloader
> uses HW trigger mode and that we need proper Panel Self Refresh
> support but I think that's a separate issue. That's why I said that
> those can be addressed for v4.8 but revert to SW trigger for v4.7 as a
> short term fix for the regression.
>
> In other words, enabling HW trigger mode breaks the display for the
> Exynos5420 and Exynos5800 Peach Pi Chromebooks with the shipped
> bootloaders (which are probably the most popular Exynos5 devices with
> display and mainline support so is likely to affect users).
I thought to add PSR support somehow but put me other things to trouble.
Anyway, we could support it later so picked it up.
Thanks,
Inki Dae
>
> Best regards,
> Javier
>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: inki.dae@samsung.com (Inki Dae)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/exynos: don't use HW trigger for Exynos5420/5422/5800
Date: Mon, 13 Jun 2016 10:38:17 +0900 [thread overview]
Message-ID: <575E0E89.40400@samsung.com> (raw)
In-Reply-To: <CABxcv=nuw7ZUF0bDC1PZfP0WVQhRY3HSoO5LdwT8_FvNi9N+aQ@mail.gmail.com>
2016? 06? 10? 09:24? Javier Martinez Canillas ?(?) ? ?:
> Hello Inki,
>
> On Thu, Jun 9, 2016 at 6:35 PM, Inki Dae <inki.dae@samsung.com> wrote:
>
> [snip]
>
>>> I know that removing .trg_type is enough but I also removed those lines
>>> because the fields are not used if .trg_type != I80_HW_TRG. So there is
>>> no point to leave a set for unused fields.
>>>
>>> We can latter add those one HW trigger support is fixed for Exynos5420.
>>>
>>
>> As of now, I can merge it but I think it would be not reasonable solution because potential problem still exists even we use SW trigger mode in default - ie., in case of using HW trigger mode at bootloader, same problem would happen as long as we don't support PSR mode support.
>>
>
> Yes, I understand that the problem will show again if the bootloader
> uses HW trigger mode and that we need proper Panel Self Refresh
> support but I think that's a separate issue. That's why I said that
> those can be addressed for v4.8 but revert to SW trigger for v4.7 as a
> short term fix for the regression.
>
> In other words, enabling HW trigger mode breaks the display for the
> Exynos5420 and Exynos5800 Peach Pi Chromebooks with the shipped
> bootloaders (which are probably the most popular Exynos5 devices with
> display and mainline support so is likely to affect users).
I thought to add PSR support somehow but put me other things to trouble.
Anyway, we could support it later so picked it up.
Thanks,
Inki Dae
>
> Best regards,
> Javier
>
>
>
next prev parent reply other threads:[~2016-06-13 1:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20160602142058epcas1p4f26bc6ab2acd0012962f90bb2c6c4141@epcas1p4.samsung.com>
2016-06-02 14:20 ` [PATCH] drm/exynos: don't use HW trigger for Exynos5420/5422/5800 Javier Martinez Canillas
2016-06-02 14:20 ` Javier Martinez Canillas
2016-06-02 14:20 ` Javier Martinez Canillas
2016-06-08 23:09 ` Inki Dae
2016-06-08 23:09 ` Inki Dae
2016-06-09 0:17 ` Javier Martinez Canillas
2016-06-09 0:17 ` Javier Martinez Canillas
2016-06-09 22:35 ` Inki Dae
2016-06-09 22:35 ` Inki Dae
2016-06-09 22:35 ` Inki Dae
2016-06-10 0:24 ` Javier Martinez Canillas
2016-06-10 0:24 ` Javier Martinez Canillas
2016-06-13 1:38 ` Inki Dae [this message]
2016-06-13 1:38 ` 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=575E0E89.40400@samsung.com \
--to=inki.dae@samsung.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=javier@dowhile0.org \
--cc=javier@osg.samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=sw0312.kim@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.