From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Mans Rullgard <mans@mansr.com>
Cc: David Airlie <airlied@linux.ie>, Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/sun4i: hdmi: add support for ddc-i2c-bus property
Date: Mon, 1 Apr 2019 13:58:29 +0200 [thread overview]
Message-ID: <20190401115829.n52yna5c43i6w7yy@flea> (raw)
In-Reply-To: <20190328130249.19356-1-mans@mansr.com>
[-- Attachment #1.1: Type: text/plain, Size: 442 bytes --]
On Thu, Mar 28, 2019 at 01:02:49PM +0000, Mans Rullgard wrote:
> Sometimes it is desirabled to use a separate i2c controller for ddc
> access. This adds support for the ddc-i2c-bus property of the
> hdmi-connector node, using the specified controller if provided.
>
> Signed-off-by: Mans Rullgard <mans@mansr.com>
Applied to drm-misc-next, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-04-01 11:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 13:47 [PATCH] drm/sun4i: hdmi: add support for ddc-i2c-bus property Mans Rullgard
2019-03-11 15:47 ` Maxime Ripard
2019-03-11 16:11 ` Måns Rullgård
2019-03-14 15:41 ` Maxime Ripard
2019-03-14 16:09 ` Måns Rullgård
2019-03-18 15:50 ` Maxime Ripard
2019-03-18 16:23 ` Måns Rullgård
2019-03-19 12:34 ` Maxime Ripard
2019-03-19 12:48 ` Måns Rullgård
2019-03-21 15:44 ` Maxime Ripard
2019-03-21 18:00 ` Måns Rullgård
2019-03-26 19:49 ` Maxime Ripard
2019-03-28 13:02 ` Mans Rullgard
2019-04-01 11:58 ` 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=20190401115829.n52yna5c43i6w7yy@flea \
--to=maxime.ripard@bootlin.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.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;
as well as URLs for NNTP newsgroup(s).