mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: megous@megous.com
Cc: dev@linux-sunxi.org, David Airlie <airlied@linux.ie>,
	Chen-Yu Tsai <wens@csie.org>,
	"open list:DRM DRIVERS FOR ALLWINNER A10"
	<dri-devel@lists.freedesktop.org>,
	"moderated list:ARM/Allwinner sunXi SoC support"
	<linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] drm/sun4i: Enable the output on the pins (tcon0)
Date: Mon, 26 Feb 2018 10:13:21 +0100	[thread overview]
Message-ID: <20180226091321.b5dqdlsiq2eyix7c@flea.lan> (raw)
In-Reply-To: <20180222161217.23904-1-megous@megous.com>

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

On Thu, Feb 22, 2018 at 05:12:17PM +0100, megous@megous.com wrote:
> From: Ondrej Jirman <megous@megous.com>
> 
> I noticed that with 4.16-rc1 LVDS output on A83T based TBS A711 tablet doesn't
> work (there's output but it's garbled). I compared some older patches for LVDS
> support with the mainlined ones and this change is missing from mainline Linux.
> 
> I don't know what the register does exactly and the harcoded register value
> doesn't inspire much confidence that it will work in a general case, so I'm
> sending this RFC.
> 
> This patch fixes the issue on A83T.
> 
> Signed-off-by: Ondrej Jirman <megous@megous.com>

Applied, thanks!
Maxime

-- 
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-02-26  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 16:12 megous
2018-02-26  9:13 ` Maxime Ripard [this message]

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=20180226091321.b5dqdlsiq2eyix7c@flea.lan \
    --to=maxime.ripard@bootlin.com \
    --cc=airlied@linux.ie \
    --cc=dev@linux-sunxi.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=megous@megous.com \
    --cc=wens@csie.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®