linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lubomir Rintel <lkundrak@v3.sk>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@siol.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Add support for Chrontel CH7033 VGA/DVI Encoder
Date: Fri, 21 Feb 2020 17:27:40 +0100	[thread overview]
Message-ID: <20200221162743.14141-1-lkundrak@v3.sk> (raw)

Hi,

chained to this message is a driver for CH7033 along with device tree
binding docs.

Since the initial submission, issues pointed out in Laurent Pinchart's
review [1] were addressed. Details in individual patches' change log.
At his suggestion, the driver has been made to use bridge/display-connector.
This allowed removing some fat, but for the time being it means that the 
patches apply against Laurent's branch [2] instead of master or drm-next.

[1] https://lore.kernel.org/lkml/20191220074914.249281-1-lkundrak@v3.sk/
[2] omapdrm/bridge/devel branch (at d27b7b2098de5) of
    git://linuxtv.org/pinchartl/media.git

Tested to work well on MMP3-based Dell Wyse 3020. There's no datasheet or
programming manual available.

Thanks,
Lubo



             reply	other threads:[~2020-02-21 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 16:27 Lubomir Rintel [this message]
2020-02-21 16:27 ` [PATCH v2 1/3] dt-bindings: Add vendor prefix for Chrontel, Inc Lubomir Rintel
2020-02-21 16:27 ` [PATCH v2 2/3] dt-bindings: display: Add Chrontel CH7033 Video Encoder binding Lubomir Rintel
2020-02-21 16:27 ` [PATCH v2 3/3] drm/bridge: chrontel-ch7033: Add a new driver Lubomir Rintel

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=20200221162743.14141-1-lkundrak@v3.sk \
    --to=lkundrak@v3.sk \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@siol.net \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=narmstrong@baylibre.com \
    --cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).