dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org
Cc: Jyri Sarha <jsarha@ti.com>
Subject: Re: [PATCH 0/5] drm: ti-tfp410 improvements
Date: Mon, 10 Dec 2018 15:39:36 +0200	[thread overview]
Message-ID: <03f6f666-1fbf-7cbf-ec1b-649a5d228a1e@ti.com> (raw)
In-Reply-To: <20181206202610.18167-1-laurent.pinchart@ideasonboard.com>

On 06/12/18 22:26, Laurent Pinchart wrote:
> Hello,
> 
> This small patch series improves the ti-tfp410 driver with three new features,
> in patch 2/5 to 5/5. Patch 1/5 has been previously posted by Stefan, and I've
> included it here to support patch 5/5 that needs to store other polarity
> information in the bridge timings than the sampling edges.
> 
> These changes are meant to support the missing tfp410 features currently
> implemented in the omapdrm custom tfp410 driver, in order to move to
> drm_bridge.
> 
> The series is based on top of the "[PATCH v2 0/2] Clarify display info PIXDATA
> bus flags" series [1] previously posted on the mailing list.
> 
> [1] https://lists.freedesktop.org/archives/dri-devel/2018-December/199204.html
> 
> Laurent Pinchart (4):
>   dt-bindings: display: tfp410: Add bus parameters properties
>   drm/bridge: ti-tfp410: Set connector type based on DT connector node
>   drm/bridge: ti-tfp410: Add support for the powerdown GPIO
>   drm/bridge: ti-tfp410: Report input bus config through bridge timings
> 
> Stefan Agner (1):
>   drm/bridge: use bus flags in bridge timings
> 
>  .../bindings/display/bridge/ti,tfp410.txt     |  24 +++-
>  drivers/gpu/drm/bridge/dumb-vga-dac.c         |   6 +-
>  drivers/gpu/drm/bridge/ti-tfp410.c            | 109 +++++++++++++++++-
>  include/drm/drm_bridge.h                      |  12 +-
>  4 files changed, 131 insertions(+), 20 deletions(-)

For the series:

Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>

 Tomi

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2018-12-10 13:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 20:26 [PATCH 0/5] drm: ti-tfp410 improvements Laurent Pinchart
2018-12-06 20:26 ` [PATCH 1/5] drm/bridge: use bus flags in bridge timings Laurent Pinchart
2018-12-06 20:26 ` [PATCH 2/5] dt-bindings: display: tfp410: Add bus parameters properties Laurent Pinchart
2018-12-06 20:26 ` [PATCH 3/5] drm/bridge: ti-tfp410: Set connector type based on DT connector node Laurent Pinchart
2018-12-11 13:00   ` Jyri Sarha
2018-12-06 20:26 ` [PATCH 4/5] drm/bridge: ti-tfp410: Add support for the powerdown GPIO Laurent Pinchart
2018-12-11 13:01   ` Jyri Sarha
2018-12-11 14:26     ` Laurent Pinchart
2018-12-06 20:26 ` [PATCH 5/5] drm/bridge: ti-tfp410: Report input bus config through bridge timings Laurent Pinchart
2018-12-11 14:48   ` Jyri Sarha
2018-12-11 15:19     ` Tomi Valkeinen
2018-12-11 15:35       ` Jyri Sarha
2018-12-11 15:43     ` Laurent Pinchart
2018-12-10 13:39 ` Tomi Valkeinen [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=03f6f666-1fbf-7cbf-ec1b-649a5d228a1e@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=laurent.pinchart@ideasonboard.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