From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Peter Rosin <peda@axentia.se>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Jyri Sarha <jsarha@ti.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/4] drm/atmel-hlcdc: bus-width override support
Date: Fri, 24 Aug 2018 09:51:31 +0200 [thread overview]
Message-ID: <20180824095131.5d9cb33f@bbrezillon> (raw)
In-Reply-To: <20180810130359.9882-1-peda@axentia.se>
Hi Peter,
On Fri, 10 Aug 2018 15:03:55 +0200
Peter Rosin <peda@axentia.se> wrote:
> Hi!
>
> The background for these patches is that our PCB interface between
> the SAMA5D3 and the ds90c185 lvds encoder is only using 16 bits, and
> this has to be described somewhere, or the atmel-hlcdc driver have no
> chance of selecting the correct output mode. Since we have similar
> problems with a tda19988 HDMI encoder I added patches to override
> the atmel-hlcdc output format via DT properties compatible with the
> media video-interface binding and things start to play together.
>
> Cheers,
> Peter
>
> Changes since v7 https://lkml.org/lkml/2018/8/4/288
> - The ep device_node was leaked in v7 patch 3/3, so add patch 3/4
> which simplifies fixing this in patch 4/4 (and adds flexibility)
> and adjust patch 4/4 to the changes done in the new 3/4.
> - return -ENOMEM on allocation failure in patch 4/4
I stopped following the discussion at some point. Are there any open
issues or Ack you're waiting for?
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-24 7:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 13:03 [PATCH v8 0/4] drm/atmel-hlcdc: bus-width override support Peter Rosin
2018-08-10 13:03 ` [PATCH v8 1/4] dt-bindings: display: bridge: lvds-transmitter: add ti,ds90c185 Peter Rosin
2018-08-10 13:03 ` [PATCH v8 2/4] dt-bindings: display: atmel: optional video-interface of endpoints Peter Rosin
2018-08-10 13:03 ` [PATCH v8 3/4] drm/atmel-hlcdc: iterate over all output endpoints Peter Rosin
2018-08-13 13:59 ` jacopo mondi
2018-08-13 14:24 ` Peter Rosin
2018-08-13 20:52 ` Rob Herring
2018-08-14 6:35 ` Peter Rosin
2018-08-14 14:33 ` Rob Herring
2018-08-14 15:05 ` Peter Rosin
2018-08-24 7:47 ` Boris Brezillon
2018-08-24 16:33 ` Rob Herring
2018-08-10 13:03 ` [PATCH v8 4/4] drm/atmel-hlcdc: support bus-width (12/16/18/24) in endpoint nodes Peter Rosin
2018-08-24 7:51 ` Boris Brezillon [this message]
2018-08-24 7:59 ` [PATCH v8 0/4] drm/atmel-hlcdc: bus-width override support Peter Rosin
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=20180824095131.5d9cb33f@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacopo+renesas@jmondi.org \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@microchip.com \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
/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).