From: srk@48.io
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>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>, Lubomir Rintel <lkundrak@v3.sk>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Richard Marko <srk@48.io>,
Marek Vasut <marex@denx.de>, Sean Cross <xobs@kosagi.com>
Subject: [PATCH 0/2] Novena laptop: LVDS-to-eDP bridge
Date: Sat, 9 May 2020 13:17:30 +0200 [thread overview]
Message-ID: <20200509111732.26102-1-srk@48.io> (raw)
From: Richard Marko <srk@48.io>
Contains updated patches I've received from Marek with the following
changes:
- yaml docs migration
- extended documentation
Tested on a Kosagi Novena laptop with imx6 display controller.
Based on v5.7-rc2, applies to drm-misc-next 5e6ed29d72d2
CC: Marek Vasut <marex@denx.de>
Cc: Sean Cross <xobs@kosagi.com>
Marek Vasut (2):
dt-bindings: it6251: add bindings for IT6251 LVDS-to-eDP bridge
drm/bridge: Add ITE IT6251 bridge driver
.../bindings/display/bridge/ite,it6251.yaml | 97 +++
drivers/gpu/drm/bridge/Kconfig | 12 +
drivers/gpu/drm/bridge/Makefile | 1 +
drivers/gpu/drm/bridge/ite-it6251.c | 582 ++++++++++++++++++
4 files changed, 692 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml
create mode 100644 drivers/gpu/drm/bridge/ite-it6251.c
base-commit: ae83d0b416db002fe95601e7f97f64b59514d936
--
2.25.1
next reply other threads:[~2020-05-09 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 11:17 srk [this message]
2020-05-09 11:17 ` [PATCH 1/2] dt-bindings: it6251: add bindings for IT6251 " srk
2020-05-09 13:44 ` Laurent Pinchart
2020-05-11 10:15 ` Sam Ravnborg
2020-05-09 11:17 ` [PATCH 2/2] drm/bridge: Add ITE IT6251 bridge driver srk
2020-05-09 13:48 ` Laurent Pinchart
2020-05-11 10:29 ` Sam Ravnborg
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=20200509111732.26102-1-srk@48.io \
--to=srk@48.io \
--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=lkundrak@v3.sk \
--cc=marex@denx.de \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=xobs@kosagi.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®