From: Archit Taneja <architt@codeaurora.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: airlied@linux.ie, a.hajda@samsung.com, Jose.Abreu@synopsys.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: bridge: dw-hdmi: Fix overflow workaround for Amlogic Meson GX SoCs
Date: Tue, 6 Mar 2018 15:54:57 +0530 [thread overview]
Message-ID: <be7cad05-ab4a-572b-1535-fbd85ea7c386@codeaurora.org> (raw)
In-Reply-To: <d0ecb49f-f2bd-0a0d-fa18-c7cb178ca17a@baylibre.com>
Hi,
On Tuesday 06 March 2018 03:23 PM, Neil Armstrong wrote:
> Hi Architt,
>
> On 23/02/2018 12:44, Neil Armstrong wrote:
>> The Amlogic Meson GX SoCs, embedded the v2.01a controller, has been also
>> identified needing this workaround.
>> This patch adds the corresponding version to enable a single iteration for
>> this specific version.
>>
>> Fixes: be41fc55f1aa ("drm: bridge: dw-hdmi: Handle overflow workaround based on device version")
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> ---
>> drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
>> index a38db40..f5018f9 100644
>> --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
>> +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
>> @@ -1637,6 +1637,8 @@ static void dw_hdmi_clear_overflow(struct dw_hdmi *hdmi)
>> * (and possibly on the platform). So far only i.MX6Q (v1.30a) and
>> * i.MX6DL (v1.31a) have been identified as needing the workaround, with
>> * 4 and 1 iterations respectively.
>> + * The Amlogic Meson GX SoCs (v2.01a) have been identifies as needing
>> + * the workaround with a single iteration.
s/identifies/identified
>> */
>>
>> switch (hdmi->version) {
>> @@ -1644,6 +1646,7 @@ static void dw_hdmi_clear_overflow(struct dw_hdmi *hdmi)
>> count = 4;
>> break;
>> case 0x131a:
>> + case 0x201a:
>> count = 1;
>> break;
>> default:
>>
>
> This fixes a long time issue on Amlogic SoCs, is it ok for you ?
Looks good to me. Feel free to queue it to drm-misc-next.
Thanks,
Archit
>
> Thanks,
> Neil
>
next prev parent reply other threads:[~2018-03-06 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 11:44 Neil Armstrong
2018-03-06 9:53 ` Neil Armstrong
2018-03-06 10:24 ` Archit Taneja [this message]
2018-04-19 8:18 ` Neil Armstrong
2018-04-19 8:27 ` Greg KH
2018-04-26 8:38 ` Neil Armstrong
2018-04-26 8:59 ` Greg KH
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=be7cad05-ab4a-572b-1535-fbd85ea7c386@codeaurora.org \
--to=architt@codeaurora.org \
--cc=Jose.Abreu@synopsys.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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
all inboxes | Powered by JetHome®