From: Peter Senna Tschudin <peter.senna@collabora.com>
To: Archit Taneja <architt@codeaurora.org>
Cc: airlied@linux.ie, akpm@linux-foundation.org,
daniel.vetter@ffwll.ch, davem@davemloft.net,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
enric.balletbo@collabora.com, eballetbo@gmail.com,
galak@codeaurora.org, gregkh@linuxfoundation.org,
heiko@sntech.de, ijc+devicetree@hellion.org.uk,
javier@dowhile0.org, jslaby@suse.cz, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
mark.rutland@arm.com, martin.donnelly@ge.com,
martyn.welch@collabora.co.uk, mchehab@osg.samsung.com,
pawel.moll@arm.com, peter.senna@gmail.com,
p.zabel@pengutronix.de, thierry.reding@gmail.com,
rmk+kernel@armlinux.org.uk, robh@kernel.org, robh+dt@kernel.org,
shawnguo@kernel.org, tiwai@suse.com, treding@nvidia.com
Subject: Re: [PATCH V3 0/4] megachips-stdpxxxx-ge-b850v3-fw
Date: Wed, 8 Mar 2017 10:42:23 +0100 [thread overview]
Message-ID: <20170308094223.GA25268@collabora.com> (raw)
In-Reply-To: <3583de63-eda5-5d9c-741e-040db1ccee69@codeaurora.org>
On Mon, Mar 06, 2017 at 03:27:16PM +0530, Archit Taneja wrote:
Hi Archit,
> Hi,
>
> On 3/3/2017 9:27 PM, Peter Senna Tschudin wrote:
> > The video processing pipeline on the second output on the GE B850v3:
> >
> > Host -> LVDS|--(STDP4028)--|DP -> DP|--(STDP2690)--|DP++ -> Video output
> >
> > Each bridge has a dedicated flash containing firmware for supporting the
> > custom design. The result is that in this design neither the STDP4028
> > nor the STDP2690 behave as the stock bridges would. The compatible
> > strings include the suffix "-ge-b850v3-fw" to make it clear that the
> > driver is for the bridges with the firmware which is specific for the GE
> > B850v3.
> >
> > The driver is powerless to control the video processing pipeline, as the
> > two bridges behaves as a single one. The driver is only needed for
> > telling the host about EDID / HPD, and for giving the host powers to ack
> > interrupts.
>
> queued Patches 1,2 and 3 to drm-misc-next. Made stdp2690_get_edid static
> in Patch #3 to fix a sparse warning.
What about 4/4, aka the dt change? Do I need an ack from Rob Herring?
Thanks a lot!
[...]
next prev parent reply other threads:[~2017-03-08 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 15:57 [PATCH V3 0/4] megachips-stdpxxxx-ge-b850v3-fw Peter Senna Tschudin
2017-03-03 15:57 ` [PATCH V3 1/4] dt-bindings: display: megachips-stdpxxxx-ge-b850v3-fw Peter Senna Tschudin
2017-03-03 15:57 ` [PATCH V3 2/4] MAINTAINERS: Add entry for megachips-stdpxxxx-ge-b850v3-fw Peter Senna Tschudin
2017-03-03 15:57 ` [PATCH V3 3/4] drm/bridge: Drivers for megachips-stdpxxxx-ge-b850v3-fw (LVDS-DP++) Peter Senna Tschudin
2017-03-03 15:57 ` [PATCH V3 4/4] dts/imx6q-b850v3: Use megachips-stdpxxxx-ge-b850v3-fw bridges (LVDS-DP++) Peter Senna Tschudin
2017-03-08 10:10 ` Peter Senna Tschudin
2017-03-13 12:41 ` Shawn Guo
2017-03-06 9:57 ` [PATCH V3 0/4] megachips-stdpxxxx-ge-b850v3-fw Archit Taneja
2017-03-08 9:42 ` Peter Senna Tschudin [this message]
2017-03-08 9:47 ` Lucas Stach
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=20170308094223.GA25268@collabora.com \
--to=peter.senna@collabora.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=architt@codeaurora.org \
--cc=daniel.vetter@ffwll.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eballetbo@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier@dowhile0.org \
--cc=jslaby@suse.cz \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=martin.donnelly@ge.com \
--cc=martyn.welch@collabora.co.uk \
--cc=mchehab@osg.samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=peter.senna@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.com \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).