From: "Peter Senna Tschudin" <peter.senna@collabora.co.uk>
To: "Archit Taneja" <architt@codeaurora.org>
Cc: galak@codeaurora.org, thierry.reding@gmail.com,
kernel@pengutronix.de, "Rob Herring" <robh@kernel.org>,
ykk@rock-chips.com, jslaby@suse.cz, tiwai@suse.com,
eballetbo@gmail.com, devicetree@vger.kernel.org,
shawnguo@kernel.org, linux@roeck-us.net, davem@davemloft.net,
p.zabel@pengutronix.de, peter.senna@gmail.com,
daniel.vetter@ffwll.ch, enric.balletbo@collabora.com,
"Peter Senna Tschudin" <peter.senna@collabora.com>,
javier@dowhile0.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, martin.donnelly@ge.com,
linux@armlinux.org.uk, heiko@sntech.de, mark.rutland@arm.com,
akpm@linux-foundation.org, airlied@linux.ie,
"Fabio Estevam" <fabio.estevam@nxp.com>,
mchehab@osg.samsung.com, linux-arm-kernel@lists.infradead.org,
robh+dt@kernel.org, martyn.welch@collabora.co.uk,
gregkh@linuxfoundation.org, treding@nvidia.com,
rmk+kernel@armlinux.org.uk
Subject: Re: [PATCH V5 3/4] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge
Date: Mon, 26 Sep 2016 09:58:26 +0100 [thread overview]
Message-ID: <3a56-57e8e300-3-10c8a340@87357206> (raw)
In-Reply-To: <c157d4a6-2d63-07d6-4274-883d79c8ab9e@codeaurora.org>
Hi Archit,
On Monday, September 26, 2016 10:31 CEST, Archit Taneja <architt@codeaurora.org> wrote:
> Hi Peter,
>
> On 09/26/2016 01:57 PM, Peter Senna Tschudin wrote:
> > Patch 1/4 is already on linux-next, but what about this one? Ping?
>
> I'd posted some queries a couple of times which you didn't answer to.
> Could you please respond to them before we try to get this merged?
Your queries were already answered by similar questions. The commit messages and cover letter also addresses the design decisions of the code. But basically the driver usefulness to other scenarios is severely limited by the firmware used by both chips. And when using the firmware that goes with this specific hardware, then yes, the two chips are always expected to work together. But the main point is that with the custom firmware each chip do not behave as independent bridges anymore.
On the other side, I was careful to use meaningful names for the registers, so a future implementation based on same chips can take the basics from this work, at least as a starting point.
Thanks,
Peter
next prev parent reply other threads:[~2016-09-26 8:58 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 16:39 [PATCH 0/5] Add driver for GE B850v3 LVDS/DP++ Bridge Peter Senna Tschudin
2016-05-30 16:39 ` [PATCH 1/5] drm/imx-ldb: Add support to drm-bridge Peter Senna Tschudin
2016-06-02 13:09 ` Philipp Zabel
2016-05-30 16:39 ` [PATCH 2/5] arm/dts/imx6q-b850v3: Configure IPU assignment order Peter Senna Tschudin
2016-05-30 16:49 ` Fabio Estevam
2016-06-02 12:55 ` Philipp Zabel
2016-05-30 16:39 ` [PATCH 3/5] Documentation/devicetree/bindings: Add b850v3_lvds_dp Peter Senna Tschudin
2016-06-02 12:49 ` Philipp Zabel
2016-06-02 23:19 ` Peter Senna Tschudin
2016-06-02 22:57 ` Rob Herring
2016-05-30 16:39 ` [PATCH 4/5] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge Peter Senna Tschudin
2016-05-31 7:48 ` Enric Balletbo Serra
2016-05-30 16:39 ` [PATCH 5/5] arm/dts/imx6q-b850v3: Use " Peter Senna Tschudin
2016-05-30 16:54 ` Fabio Estevam
2016-06-09 16:25 ` [PATCH V2 0/5] Add driver for " Peter Senna Tschudin
2016-06-09 16:25 ` [PATCH V2 1/5] drm/imx-ldb: Add support to drm-bridge Peter Senna Tschudin
2016-06-09 16:25 ` [PATCH V2 2/5] dts/imx6q-b850v3: Configure IPU assignment order Peter Senna Tschudin
2016-06-09 16:25 ` [PATCH V2 3/5] Documentation/devicetree/bindings: b850v3_lvds_dp Peter Senna Tschudin
2016-06-10 17:42 ` Rob Herring
2016-06-10 18:54 ` Javier Martinez Canillas
2016-06-09 16:25 ` [PATCH V2 4/5] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge Peter Senna Tschudin
2016-06-10 7:39 ` Enric Balletbo Serra
2016-06-10 9:44 ` Peter Senna Tschudin
2016-06-10 14:13 ` Daniel Vetter
2016-06-22 8:34 ` Archit Taneja
2016-06-09 16:25 ` [PATCH V2 5/5] dts/imx6q-b850v3: Use " Peter Senna Tschudin
2016-07-31 19:55 ` [PATCH V3 0/5] Add driver for " Peter Senna Tschudin
2016-07-31 19:55 ` [PATCH V3 1/5] drm/imx-ldb: Add support to drm-bridge Peter Senna Tschudin
2016-08-01 10:21 ` Philipp Zabel
2016-08-02 18:46 ` Peter Senna Tschudin
2016-07-31 19:55 ` [PATCH V3 2/5] dts/imx6q-b850v3: Configure IPU assignment order Peter Senna Tschudin
2016-08-01 8:54 ` Lucas Stach
2016-08-01 12:30 ` Peter Senna Tschudin
2016-08-02 13:13 ` Daniel Vetter
2016-07-31 19:55 ` [PATCH V3 3/5] Documentation/devicetree/bindings: b850v3_lvds_dp Peter Senna Tschudin
2016-08-01 16:59 ` Rob Herring
2016-07-31 19:55 ` [PATCH V3 4/5] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge Peter Senna Tschudin
2016-07-31 19:55 ` [PATCH V3 5/5] dts/imx6q-b850v3: Use " Peter Senna Tschudin
2016-08-04 22:36 ` [PATCH V4 0/4] Add driver for " Peter Senna Tschudin
2016-08-04 22:36 ` [PATCH V4 1/4] drm/imx-ldb: Add support to drm-bridge Peter Senna Tschudin
2016-08-16 15:40 ` Martyn Welch
2016-08-04 22:36 ` [PATCH V4 2/4] Documentation/devicetree/bindings: b850v3_lvds_dp Peter Senna Tschudin
2016-08-05 7:28 ` Enric Balletbo Serra
2016-08-16 15:59 ` Martyn Welch
2016-08-04 22:37 ` [PATCH V4 3/4] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge Peter Senna Tschudin
2016-08-05 7:38 ` Enric Balletbo Serra
2016-08-04 22:37 ` [PATCH V4 4/4] dts/imx6q-b850v3: Use " Peter Senna Tschudin
2016-08-09 16:41 ` [PATCH V5 0/4] Add driver for " Peter Senna Tschudin
2016-08-09 16:41 ` [PATCH V5 1/4] drm/imx-ldb: Add support to drm-bridge Peter Senna Tschudin
2016-08-11 9:38 ` Philipp Zabel
2016-08-09 16:41 ` [PATCH V5 2/4] Documentation/devicetree/bindings: b850v3_lvds_dp Peter Senna Tschudin
2016-09-26 8:26 ` Peter Senna Tschudin
2016-08-09 16:41 ` [PATCH V5 3/4] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge Peter Senna Tschudin
2016-08-16 4:15 ` Archit Taneja
2016-09-26 8:27 ` Peter Senna Tschudin
2016-09-26 8:31 ` Archit Taneja
2016-09-26 8:58 ` Peter Senna Tschudin [this message]
2016-09-26 10:28 ` Archit Taneja
2016-09-26 10:29 ` Archit Taneja
2016-09-26 11:54 ` Peter Senna Tschudin
2016-09-26 12:54 ` Archit Taneja
2016-08-09 16:41 ` [PATCH V5 4/4] dts/imx6q-b850v3: Use " Peter Senna Tschudin
2016-09-26 8:27 ` Peter Senna Tschudin
2016-09-29 10:39 ` Shawn Guo
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=3a56-57e8e300-3-10c8a340@87357206 \
--to=peter.senna@collabora.co.uk \
--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=fabio.estevam@nxp.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@collabora.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 \
--cc=ykk@rock-chips.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).