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 v9 0/4] drm/atmel-hlcdc: bus-width override support
Date: Mon, 27 Aug 2018 22:40:55 +0200 [thread overview]
Message-ID: <20180827224055.3ab63c43@bbrezillon> (raw)
In-Reply-To: <20180827223505.7e2fe6f6@bbrezillon>
On Mon, 27 Aug 2018 22:35:05 +0200
Boris Brezillon <boris.brezillon@bootlin.com> wrote:
> On Mon, 27 Aug 2018 22:31:22 +0200
> Peter Rosin <peda@axentia.se> wrote:
>
> > On 2018-08-27 21:24, Boris Brezillon wrote:
> > > On Sat, 25 Aug 2018 10:56:16 +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.
> > >
> > > Queued to drm-misc-next.
> >
> > Thanks!
> >
> > Minute issue, you seem to have some spell-check going on or something,
> > because the subject of patch 1/4 has been "corrected" from
> > "...add ti,ds90c185" to "...add ti, ds90c185"
> >
> > You might want to evaluate if that auto-correction "feature" should be
> > disabled/tweaked/whatever...
>
> Hm, weird. I just downloaded the mbox from dri-devel's patchwork and
> passed it to dim apply. dim tends to do a lot of things behind the
> scene, so maybe it's also trying to fix typos :-).
Nope, looks like it was already wrong on patchwork [1], don't know what
happened, because the version I have in my mailbox is correct.
[1]https://patchwork.freedesktop.org/patch/246039/
_______________________________________________
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-27 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 8:56 [PATCH v9 0/4] drm/atmel-hlcdc: bus-width override support Peter Rosin
2018-08-25 8:56 ` [PATCH v9 1/4] dt-bindings: display: bridge: lvds-transmitter: add ti,ds90c185 Peter Rosin
2018-08-25 8:56 ` [PATCH v9 2/4] dt-bindings: display: atmel: optional video-interface of endpoints Peter Rosin
2018-08-25 8:56 ` [PATCH v9 3/4] drm/atmel-hlcdc: always iterate over the first 4 output endpoints Peter Rosin
2018-08-25 8:56 ` [PATCH v9 4/4] drm/atmel-hlcdc: support bus-width (12/16/18/24) in endpoint nodes Peter Rosin
2018-08-27 19:24 ` [PATCH v9 0/4] drm/atmel-hlcdc: bus-width override support Boris Brezillon
2018-08-27 20:31 ` Peter Rosin
2018-08-27 20:35 ` Boris Brezillon
2018-08-27 20:40 ` Boris Brezillon [this message]
2018-08-27 20:48 ` 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=20180827224055.3ab63c43@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).