From: Thierry Reding <treding@nvidia.com>
To: Chris Zhong <zyw@rock-chips.com>
Cc: <heiko@sntech.de>, <linux-rockchip@lists.infradead.org>,
<mark.yao@rock-chips.com>, <emil.l.velikov@gmail.com>,
<airlied@linux.ie>, <ajaykumar.rs@samsung.com>,
<rmk+kernel@arm.linux.org.uk>, <dri-devel@lists.freedesktop.org>,
Inki Dae <inki.dae@samsung.com>, "Takashi Iwai" <tiwai@suse.de>,
Vincent Palatin <vpalatin@chromium.org>,
Andy Yan <andy.yan@rock-chips.com>,
Rahul Sharma <rahul.sharma@samsung.com>,
Sean Paul <seanpaul@chromium.org>,
Andrew Bresticker <abrestic@chromium.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 06/13] drm/bridge: Add Synopsys DesignWare MIPI DSI host controller driver
Date: Thu, 26 Nov 2015 09:04:49 +0100 [thread overview]
Message-ID: <20151126080447.GA28064@ulmo.nvidia.com> (raw)
In-Reply-To: <5656AEDA.4080607@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]
On Thu, Nov 26, 2015 at 03:03:54PM +0800, Chris Zhong wrote:
> Hi Thierry
>
> Thanks for your feedback.
>
>
> On 11/21/2015 12:07 AM, Thierry Reding wrote:
> >On Fri, Nov 20, 2015 at 04:15:32PM +0800, Chris Zhong wrote:
> >>add Synopsys DesignWare MIPI DSI host controller driver support.
> >>
> >>Signed-off-by: Chris Zhong <zyw@rock-chips.com>
> >>---
> >>
> >>Changes in v4:
> >>eliminate some warnning
> >>
> >>Changes in v3: None
> >>Changes in v2: None
> >>
> >> drivers/gpu/drm/bridge/Kconfig | 11 +
> >> drivers/gpu/drm/bridge/Makefile | 1 +
> >> drivers/gpu/drm/bridge/dw_mipi_dsi.c | 1056 ++++++++++++++++++++++++++++++++++
> >> include/drm/bridge/dw_mipi_dsi.h | 27 +
> >> 4 files changed, 1095 insertions(+)
> >> create mode 100644 drivers/gpu/drm/bridge/dw_mipi_dsi.c
> >> create mode 100644 include/drm/bridge/dw_mipi_dsi.h
> >>
> >>
> >>+struct dw_mipi_dsi {
> >>+ struct mipi_dsi_host dsi_host;
> >>+ struct drm_connector connector;
> >>+ struct drm_encoder *encoder;
> >struct drm_bridge already has a pointer to an encoder, can't you reuse
> >that instead?
> >
> >>+ struct drm_bridge *bridge;
> >Typically you'd embed the bridge into the driver structure.
> I'm almost done with all the modifications according to your comments.
> Remaining this point I can not understand, the dsi is a pointer of
> drm_bridge,
> hence I can not get the bridge by container_of.
> Although, the "bridge->driver_private = dsi" have done in
> dw_mipi_dsi_register.
I don't understand. If you don't make bridge a pointer, but rather embed
it within the structure, then you can use container_of(), can't you? You
get it allocated automatically as part of allocating the dw_mipi_dsi
structure. See for example the ps8622 and ptn3460 bridge drivers.
On a slightly unrelated note, I'm not sure if we discussed this already
or if it was in another thread, but why is this even a bridge driver? A
bridge is typically some IC outside of the SoC, whereas this clearly is
IP designed into the SoC. So it's really more of an encoder rather than
a bridge.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-26 8:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 8:15 [PATCH v4 0/13] Add mipi dsi support for rk3288 Chris Zhong
2015-11-20 8:15 ` [PATCH v4 01/13] clk: rockchip: add id for mipidsi sclk on rk3288 Chris Zhong
2015-11-23 17:29 ` Heiko Stübner
2015-11-20 8:15 ` [PATCH v4 02/13] clk: rockchip: add mipidsi clocks " Chris Zhong
2015-11-20 8:15 ` [PATCH v4 03/13] drm/rockchip: return a true clock rate to adjusted_mode Chris Zhong
2015-11-20 8:57 ` Mark yao
2015-11-20 8:15 ` [PATCH v4 04/13] drm/dsi: Add a helper to get bits per pixel of MIPI DSI pixel format Chris Zhong
2015-11-20 8:15 ` [PATCH v4 05/13] Documentation: dt-bindings: Add bindings for Synopsys DW MIPI DSI DRM bridge driver Chris Zhong
2015-11-20 14:32 ` Rob Herring
2015-11-20 8:15 ` [PATCH v4 06/13] drm/bridge: Add Synopsys DesignWare MIPI DSI host controller driver Chris Zhong
2015-11-20 16:07 ` Thierry Reding
2015-11-26 7:03 ` Chris Zhong
2015-11-26 8:04 ` Thierry Reding [this message]
2015-11-26 10:05 ` Chris Zhong
2015-11-20 8:15 ` [PATCH v4 07/13] drm: rockchip: Support Synopsys DesignWare MIPI DSI host controller Chris Zhong
2015-11-20 8:15 ` [PATCH v4 08/13] Documentation: dt-bindings: Add bindings for rk3288 DW MIPI DSI driver Chris Zhong
2015-11-20 8:15 ` [PATCH v4 09/13] ARM: dts: rockchip: add rk3288 mipi_dsi nodes Chris Zhong
2015-11-20 8:15 ` [PATCH v4 10/13] of: add vendor prefix for boe Chris Zhong
2015-11-23 8:08 ` Thierry Reding
2015-11-20 8:15 ` [PATCH v4 11/13] drm/panel: simple: Add support for BOE TV080WUM-NL0 Chris Zhong
2015-11-23 8:09 ` Thierry Reding
2015-11-20 8:15 ` [PATCH v4 12/13] drm/panel: simple: Add boe,tv080wum-nl0 simple panel device tree binding Chris Zhong
2015-11-23 8:10 ` Thierry Reding
2015-11-20 8:15 ` [PATCH v4 13/13] ARM: dts: rockchip: add support mipi panel tv080wum-nl0 for rk3288-evb Chris Zhong
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=20151126080447.GA28064@ulmo.nvidia.com \
--to=treding@nvidia.com \
--cc=abrestic@chromium.org \
--cc=airlied@linux.ie \
--cc=ajaykumar.rs@samsung.com \
--cc=andy.yan@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=heiko@sntech.de \
--cc=inki.dae@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.com \
--cc=rahul.sharma@samsung.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=seanpaul@chromium.org \
--cc=tiwai@suse.de \
--cc=vpalatin@chromium.org \
--cc=zyw@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