From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] drm: atmel-hlcdc: various fixes/improvements
Date: Thu, 17 Mar 2016 09:33:43 +0100 [thread overview]
Message-ID: <20160317093343.517ba6f5@bbrezillon> (raw)
In-Reply-To: <CAPM=9tz0rZMwy6JTqzjcSQC+DAPYkjBOiU746C0smyMA0OCGzw@mail.gmail.com>
On Thu, 17 Mar 2016 12:43:11 +1000
Dave Airlie <airlied@gmail.com> wrote:
> On 1 March 2016 at 20:55, Boris Brezillon
> <boris.brezillon@free-electrons.com> wrote:
> > On Wed, 6 Jan 2016 11:19:21 +0100
> > Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> >
> >> Hello,
> >>
> >> This series is a collection of fixes and improvements for the
> >> atmel-hlcdc driver.
> >>
> >> The main feature added here is the support for external RGB -> XXX
> >> bridges (patch 6 and 7).
> >>
> >> The first patch is a fix preventing a potential memory leak.
> >> Patch 2 is adding support for asynchronous mode setting, which was
> >> supported before the migration to atomic mode setting.
> >>
> >> Patch 3 is just a minor fix to expose the real encoder and connector
> >> types (we are currently exposing an LVDS encoder/connector, which is
> >> wrong since the display controller output the pixel stream in raw
> >> RGB).
> >>
> >> Patch 4 is removing useless fields and functions which were left
> >> when moving to atomic modesetting.
> >>
> >> And patch 8 is just a cosmetic patch moving the mode checking code
> >> from ->atomic_check() to ->mode_fixup().
> >
> > Dave, Daniel, any comment on this series (AKA ping)?
>
> On internal driver stuff, I'd usually only look on a git pull :-)
Yep, Daniel told me that both of you usually don't review internal
driver changes. I'll send a PR soon (after the merge window of course).
Thanks,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-17 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 10:19 [PATCH 0/8] drm: atmel-hlcdc: various fixes/improvements Boris Brezillon
2016-01-06 10:19 ` [PATCH 1/8] drm: atmel-hlcdc: add a ->cleanup_fb() operation Boris Brezillon
2016-03-08 15:03 ` Nicolas Ferre
2016-01-06 10:19 ` [PATCH 2/8] drm: atmel-hlcdc: support asynchronous atomic commit operations Boris Brezillon
2016-01-06 10:19 ` [PATCH 3/8] drm: atmel-hlcdc: fix connector and encoder types Boris Brezillon
2016-03-08 15:03 ` Nicolas Ferre
2016-01-06 10:19 ` [PATCH 4/8] drm: atmel-hlcdc: remove leftovers from atomic mode setting migration Boris Brezillon
2016-03-08 15:04 ` Nicolas Ferre
2016-01-06 10:19 ` [PATCH 5/8] drm: atmel-hlcdc: support extended timing ranges on sama5d4 and sama5d2 Boris Brezillon
2016-03-08 15:08 ` Nicolas Ferre
2016-01-06 10:19 ` [PATCH 6/8] drm: atmel-hlcdc: move output mode selection in CRTC implementation Boris Brezillon
2016-01-06 10:19 ` [PATCH 7/8] drm: atmel-hlcdc: rework the output code to support drm bridges Boris Brezillon
2016-01-06 10:19 ` [PATCH 8/8] drm: atmel-hlcdc: check display mode validity in crtc->mode_fixup() Boris Brezillon
2016-03-08 15:44 ` Nicolas Ferre
2016-03-01 10:55 ` [PATCH 0/8] drm: atmel-hlcdc: various fixes/improvements Boris Brezillon
2016-03-17 2:43 ` Dave Airlie
2016-03-17 8:33 ` Boris Brezillon [this message]
2016-03-16 13:06 ` Nicolas Ferre
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=20160317093343.517ba6f5@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).