Hi Tomi,
On Wednesday 19 September 2012 14:45:29 Tomi Valkeinen wrote:
On Fri, 2012-08-17 at 02:49 +0200, Laurent Pinchart wrote:
Hi everybody,
While working on DT bindings for the Renesas Mobile SoC display controller
(a.k.a. LCDC) I quickly realized that display panel implementation
Hi Inki,
On Saturday 20 October 2012 22:10:17 Inki Dae wrote:
Hi Laurent. sorry for being late.
No worries.
2012/8/17 Laurent Pinchart laurent.pinch...@ideasonboard.com:
Hi everybody,
While working on DT bindings for the Renesas Mobile SoC display controller
(a.k.a. LCDC) I quickly
On 2012-10-31 15:13, Laurent Pinchart wrote:
OMAP SoC
So here's first the SoC specific display nodes. OMAP has a DSS (display
subsystem) block, which contains the following elements:
- DISPC (display controller) reads the pixels from memory and outputs
them using specified video
Hi Jun,
I've finally been able to resume my work on the panel framework (I hope to
post a v2 at the end of the week).
On Thursday 23 August 2012 14:23:01 Jun Nie wrote:
Hi Laurent,
Do you plan to add an API to get and parse EDID to mode list?
An API to get the raw EDID data is likely
Hi Zhou,
On Tuesday 04 September 2012 16:20:38 Zhou Zhu wrote:
Hi Laurent,
Basically I agree that we need a common panel framework. I just have
some questions:
1. I think we should add color format in videomode - if we use such
common video mode structure shared across subsystems.
In
Hi Laurent. sorry for being late.
2012/8/17 Laurent Pinchart laurent.pinch...@ideasonboard.com:
Hi everybody,
While working on DT bindings for the Renesas Mobile SoC display controller
(a.k.a. LCDC) I quickly realized that display panel implementation based on
board code callbacks would need
Hi Tomi,
2012/8/17 Tomi Valkeinen tomi.valkei...@ti.com:
Hi,
On Fri, 2012-08-17 at 02:49 +0200, Laurent Pinchart wrote:
I will appreciate all reviews, comments, criticisms, ideas, remarks, ... If
Oookay, where to start... ;)
A few cosmetic/general comments first.
I find the file naming
correct some typo. Sorry for this.
2012/10/20 Inki Dae inki@samsung.com:
Hi Laurent. sorry for being late.
2012/8/17 Laurent Pinchart laurent.pinch...@ideasonboard.com:
Hi everybody,
While working on DT bindings for the Renesas Mobile SoC display controller
(a.k.a. LCDC) I quickly
Hi,
On Fri, 2012-08-17 at 02:49 +0200, Laurent Pinchart wrote:
Hi everybody,
While working on DT bindings for the Renesas Mobile SoC display controller
(a.k.a. LCDC) I quickly realized that display panel implementation based on
board code callbacks would need to be replaced by a
Hi Laurent,
Basically I agree that we need a common panel framework. I just have
some questions:
1. I think we should add color format in videomode - if we use such
common video mode structure shared across subsystems.
In HDMI, colors are bind with timings tightly. We need a combined
videomode
Hi Laurent,
Do you plan to add an API to get and parse EDID to mode list?
video mode is tightly coupled with panel that is capable of hot-plug.
Or you are busy on modifying EDID parsing code for sharing it amoung
DRM/FB/etc? I see you mentioned this in Mar. It is great if you are
considering
Hi Tomi,
On Tuesday 21 August 2012 08:49:57 Tomi Valkeinen wrote:
On Tue, 2012-08-21 at 01:29 +0200, Laurent Pinchart wrote:
On Monday 20 August 2012 14:39:30 Tomi Valkeinen wrote:
On Sat, 2012-08-18 at 03:16 +0200, Laurent Pinchart wrote:
Hi Tomi,
mipi-dbi-bus might not belong
On Sat, 2012-08-18 at 03:16 +0200, Laurent Pinchart wrote:
Hi Tomi,
mipi-dbi-bus might not belong to include/video/panel/ though, as it can be
used for non-panel devices (at least in theory). The future mipi-dsi-bus
certainly will.
They are both display busses. So while they could be used
Hi Tomi,
On Monday 20 August 2012 14:39:30 Tomi Valkeinen wrote:
On Sat, 2012-08-18 at 03:16 +0200, Laurent Pinchart wrote:
Hi Tomi,
mipi-dbi-bus might not belong to include/video/panel/ though, as it can be
used for non-panel devices (at least in theory). The future mipi-dsi-bus
On Tue, 2012-08-21 at 01:29 +0200, Laurent Pinchart wrote:
Hi Tomi,
On Monday 20 August 2012 14:39:30 Tomi Valkeinen wrote:
On Sat, 2012-08-18 at 03:16 +0200, Laurent Pinchart wrote:
Hi Tomi,
mipi-dbi-bus might not belong to include/video/panel/ though, as it can be
used for
Hi,
On Fri, 2012-08-17 at 02:49 +0200, Laurent Pinchart wrote:
I will appreciate all reviews, comments, criticisms, ideas, remarks, ... If
Oookay, where to start... ;)
A few cosmetic/general comments first.
I find the file naming a bit strange. You have panel.c, which is the
core framework,
Hi Tomi,
Thanks a lot for the review.
On Friday 17 August 2012 11:38:14 Tomi Valkeinen wrote:
On Fri, 2012-08-17 at 02:49 +0200, Laurent Pinchart wrote:
I will appreciate all reviews, comments, criticisms, ideas, remarks, ...
If
Oookay, where to start... ;)
A few cosmetic/general
On Fri, 2012-08-17 at 13:10 +0200, Laurent Pinchart wrote:
What kind of directory structure do you have in mind ? Panels are already
isolated in drivers/video/panel/ so we could already ditch the panel- prefix
in drivers.
The same directory also contains files for the framework and buses.
Hi Tomi,
On Friday 17 August 2012 14:42:31 Tomi Valkeinen wrote:
On Fri, 2012-08-17 at 13:10 +0200, Laurent Pinchart wrote:
What kind of directory structure do you have in mind ? Panels are already
isolated in drivers/video/panel/ so we could already ditch the panel-
prefix in drivers.
Hi everybody,
While working on DT bindings for the Renesas Mobile SoC display controller
(a.k.a. LCDC) I quickly realized that display panel implementation based on
board code callbacks would need to be replaced by a driver-based panel
framework.
Several driver-based panel support solution
On Friday, August 17, 2012 9:50 AM Laurent Pinchart wrote:
Hi everybody,
While working on DT bindings for the Renesas Mobile SoC display controller
(a.k.a. LCDC) I quickly realized that display panel implementation based on
board code callbacks would need to be replaced by a driver-based
21 matches
Mail list logo
