mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] drm: bridge: dw-hdmi: Fix overflow workaround for Amlogic Meson GX SoCs
Date: Thu, 26 Apr 2018 10:38:08 +0200	[thread overview]
Message-ID: <8766c753-bc2c-0e54-0ac0-73acaa0e11d8@baylibre.com> (raw)
In-Reply-To: <20180419082751.GA23187@kroah.com>

Hi Greg,

On 19/04/2018 10:27, Greg KH wrote:
> On Thu, Apr 19, 2018 at 10:18:35AM +0200, Neil Armstrong wrote:
>> Hi Greg,
>>
>> 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>
>>
>> This patch is now present in linux master as commit 9c305eb442f3b371fc722ade827bbf673514123e
>> Could it be selected for 4.14 ?
>> The patch has been reworked to apply for 4.17 as indicated in the commit log, but the original patch will apply over 4.14.
> 
> I don't have any "original" patch here, I just tried applying it to
> 4.16.y and 4.14.y and it did not work.  Can you please provide a working
> backport?

I sent a backported version last week, any news of it ?

Message-Id: <1524128048-11086-1-git-send-email-narmstrong@baylibre.com>

Thanks,
Neil

> 
> thanks,
> 
> greg k-h
> 

  reply	other threads:[~2018-04-26  8:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1519386277-25902-1-git-send-email-narmstrong@baylibre.com>
2018-04-19  8:18 ` Neil Armstrong
2018-04-19  8:27   ` Greg KH
2018-04-26  8:38     ` Neil Armstrong [this message]
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=8766c753-bc2c-0e54-0ac0-73acaa0e11d8@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=linus-amlogic@lists.infradead.org \
    /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®