From: Thierry Reding <thierry.reding@gmail.com>
To: Ajay Kumar <ajaykumar.rs@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, daniel.vetter@ffwll.ch,
joshi@samsung.com, dri-devel@lists.freedesktop.org,
a.hajda@samsung.com, ajaynumb@gmail.com, prashanth.g@samsung.com
Subject: Re: [RFC V3 2/3] drm/bridge: add a dummy panel driver to support lvds bridges
Date: Tue, 13 May 2014 10:05:03 +0200 [thread overview]
Message-ID: <20140513080501.GH6754@ulmo> (raw)
In-Reply-To: <1399647182-20951-3-git-send-email-ajaykumar.rs@samsung.com>
[-- Attachment #1.1: Type: text/plain, Size: 2076 bytes --]
On Fri, May 09, 2014 at 08:23:01PM +0530, Ajay Kumar wrote:
> implement basic panel controls as a drm_bridge so that
> the existing bridges can make use of it.
>
> The driver assumes that it is the last entity in the bridge chain.
>
> Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
> ---
> .../bindings/drm/bridge/bridge_panel.txt | 45 ++++
Can we please stop adding files to this directory? Device tree bindings
are supposed to be OS agnostic, but DRM is specific to Linux and should
not be used when describing hardware.
> diff --git a/Documentation/devicetree/bindings/drm/bridge/bridge_panel.txt b/Documentation/devicetree/bindings/drm/bridge/bridge_panel.txt
[...]
> + -led-en-gpio:
> + eDP panel LED enable GPIO.
> + Indicates which GPIO needs to be powered up as output
> + to enable the backlight.
Since this is used to control a backlight, then this should really be a
separate node to describe the backlight device (and use the
corresponding backlight driver) rather than duplicating a subset of that
functionality.
> + -panel-pre-enable-delay:
> + delay value in ms required for panel_pre_enable process
> + Delay in ms needed for the eDP panel LCD unit to
> + powerup, and delay needed between panel_VCC and
> + video_enable.
What are panel_VCC or video_enable?
> + -panel-enable-delay:
> + delay value in ms required for panel_enable process
> + Delay in ms needed for the eDP panel backlight/LED unit
> + to powerup, and delay needed between video_enable and
> + BL_EN.
Similarily, what does BL_EN stand for?
> + bridge-panel {
> + compatible = "drm-bridge,panel";
Again, drm- doesn't mean anything outside of Linux (and maybe BSD),
therefore shouldn't be used to describe hardware in device tree.
> diff --git a/drivers/gpu/drm/bridge/bridge_panel.c b/drivers/gpu/drm/bridge/bridge_panel.c
[...]
This duplicates much of the functionality that panels should provide. I
think a better solution would be to properly integrate panels with
bridges.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-13 8:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 14:52 [RFC V3 0/3] drm/bridge: panel and chaining Ajay Kumar
2014-05-09 14:53 ` [RFC V3 1/3] drm/bridge: add helper functions to support bridge chain Ajay Kumar
2014-05-09 14:53 ` [RFC V3 2/3] drm/bridge: add a dummy panel driver to support lvds bridges Ajay Kumar
2014-05-13 8:05 ` Thierry Reding [this message]
2014-05-13 16:49 ` Ajay kumar
2014-05-14 14:54 ` Thierry Reding
2014-05-14 18:09 ` Ajay kumar
2014-05-15 8:13 ` Thierry Reding
2014-05-15 11:40 ` Ajay kumar
2014-05-17 20:33 ` Ajay kumar
2014-05-17 21:14 ` Thierry Reding
2014-05-18 8:20 ` Ajay kumar
2014-05-19 15:30 ` Thierry Reding
2014-05-19 19:07 ` Ajay kumar
2014-05-19 20:10 ` Thierry Reding
2014-06-03 9:58 ` Ajay kumar
2014-06-03 12:52 ` Andrzej Hajda
2014-05-09 14:53 ` [RFC V3 3/3] drm: create and demonstrate bridge chaining using exynos_dp Ajay Kumar
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=20140513080501.GH6754@ulmo \
--to=thierry.reding@gmail.com \
--cc=a.hajda@samsung.com \
--cc=ajaykumar.rs@samsung.com \
--cc=ajaynumb@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=joshi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prashanth.g@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.