get display timings from device tree
Use videomode helpers to get display timings and configurations from
device tree
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
so we can use have list gpio as example (probe via DT)
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
to simplify the check on the presence of the callback
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Today we mix pdata and drivers data in the struct atmel_lcdfb_info
Fix it and introduce a new struct atmel_lcdfb_pdata for platform data only
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
In preparation to switching the jz4740 clk driver to the common clk framework
update the clk enable/disable calls to clk_prepare_enable/clk_disable_unprepare.
Signed-off-by: Lars-Peter Clausen <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
'xoffset' and 'yoffset' are unsigned and hence cannot be less than 0.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
'xoffset' and 'yoffset' are unsigned and hence cannot be less than 0.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
'yoffset' is unsigned and hence cannot be less than 0.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
'break' after return statement is redundant. Remove it.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Convert 0 to false and 1 to true when assigning values to bool
variables. Inspired by commit 3db1cd5c05.
The simplified semantic patch that find this problem is as
follows (http://coccinelle.lip6.fr/):
@@
bool b;
@@
(
-b = 0
+b = false
|
-b = 1
+b = true
)
Signed-off-by: Peter Senna Tschudin <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Add pitch length info of graphics/video layer, pitch is used
to represent line length in byte, the usage depends on pix_fmt.
If the fmt is YUV, the pitch[0] will be Y length,pitch[1]
will be U length, pitch[2] will be V lenth.
If the fmt is RGB, the picth[0] will be line lenth, and
pitch[1]/pitch[2] will be 0 and not be used.
Signed-off-by: Jing Xiang <[email protected]>
Signed-off-by: Jett.Zhou <[email protected]>
Signed-off-by: Zhou Zhu <[email protected]>
Reviewed-by: Daniel Drake <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Add new func mmpfb_set_win to make code clean, it will do resolution
and fmt setting of win in mmpfb_set_win.
Signed-off-by: Jing Xiang <[email protected]>
Signed-off-by: Jett.Zhou <[email protected]>
Signed-off-by: Zhou Zhu <[email protected]>
Reviewed-by: Daniel Drake <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
According to new rbswap scheme of mmp_display, it support appropriate
rbswap setting based on specific pix_fmt, then we can remove the legacy
rbswap setting for ttc_dkb platform.
Signed-off-by: Jett.Zhou <[email protected]>
Signed-off-by: Zhou Zhu <[email protected]>
Reviewed-by: Daniel Drake <[email protected]>
Acked-by: Haojian Zhuang <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
We could set rb swap in two modules: DMA controler input part and
dsi interface output part.
DMA input part is based on pix_fmt to set rbswap, dsi output interface
part will set rbswap based on platform dsi_rbswap configuration.
This patch include below change and enhancement:
1) The input format which support rbswap is based on RGB format,
eg. RGB565 indicates the source data in memory is that Red is [15~11],
Green is [10~5], Blue is [4:0], Red is MSB, Blue is LSB, but for the
display dma input default setting(rbswap = 0), it only support Blue
is [15~11], Green is [10~5], Red is [4:0], Red is LSB, Blue is MSB,
so for this format(RGB565), display controller need to set rbswap
= 1 and it can support the MSB/LSB correctly.
BGR/YUV format will not set it in mmp display driver.
2) The dsi output part of rbswap is depend on dsi_rbswap which is
defined in specific platfrom. For output dsi interface, it has this
feature to do rbswap again if it needs specifc byte sequence of RGB
byte for DSI panel.
eg. If display content is set RGB565 in memory and DMA input part set
rbswap in driver to support Red as MSB , Blue LSB, but dsi panel only
support Red as LSB, Blue as MSB, then it can use this feature.
If there is no this requirement of panel, this dsi output part is not
needed.
Signed-off-by: Guoqing Li <[email protected]>
Signed-off-by: Jett.Zhou <[email protected]>
Signed-off-by: Zhou Zhu <[email protected]>
Reviewed-by: Daniel Drake <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Acked-by: Kristoffer Ericson <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han <[email protected]>
Signed-off-by: Tomi Valkeinen <[email protected]>
