)]}' { "log": [ { "commit": "804ce9866d56130032c9c8afc90a1297b7deed56", "tree": "6dd70984f411d2a3624d3f8db7facc3d6396b9ad", "parents": [ "f5e7e844a571124ffc117d4696787d6afc4fc5ae", "c895305e806b4346006d3cfba2b432d52268ecd3" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Jun 01 16:57:51 2012 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Jun 01 16:57:51 2012 -0700" }, "message": "Merge tag \u0027fbdev-updates-for-3.5\u0027 of git://github.com/schandinat/linux-2.6\n\nPull fbdev updates from Florian Tobias Schandinat:\n - driver for AUO-K1900 and AUO-K1901 epaper controller\n - large updates for OMAP (e.g. decouple HDMI audio and video)\n - some updates for Exynos and SH Mobile\n - various other small fixes and cleanups\n\n* tag \u0027fbdev-updates-for-3.5\u0027 of git://github.com/schandinat/linux-2.6: (130 commits)\n video: bfin_adv7393fb: Fix cleanup code\n video: exynos_dp: reduce delay time when configuring video setting\n video: exynos_dp: move sw reset prioir to enabling sw defined function\n video: exynos_dp: use devm_ functions\n fb: handle NULL pointers in framebuffer release\n OMAPDSS: HDMI: OMAP4: Update IRQ flags for the HPD IRQ request\n OMAPDSS: Apply VENC timings even if panel is disabled\n OMAPDSS: VENC/DISPC: Delay dividing Y resolution for managers connected to VENC\n OMAPDSS: DISPC: Support rotation through TILER\n OMAPDSS: VRFB: remove compiler warnings when CONFIG_BUG\u003dn\n OMAPFB: remove compiler warnings when CONFIG_BUG\u003dn\n OMAPDSS: remove compiler warnings when CONFIG_BUG\u003dn\n OMAPDSS: DISPC: fix usage of dispc_ovl_set_accu_uv\n OMAPDSS: use DSI_FIFO_BUG workaround only for manual update displays\n OMAPDSS: DSI: Support command mode interleaving during video mode blanking periods\n OMAPDSS: DISPC: Update Accumulator configuration for chroma plane\n drivers/video: fsl-diu-fb: don\u0027t initialize the THRESHOLDS registers\n video: exynos mipi dsi: support reverse panel type\n video: exynos mipi dsi: Properly interpret the interrupt source flags\n video: exynos mipi dsi: Avoid races in probe()\n ...\n" }, { "commit": "f5f4fd451634e5295cc807684a0eabd264b9db4d", "tree": "ba8901bf5d8e89eb0247cd315b7573bc4dd99de6", "parents": [ "6677110b748aa1fe92d039b09d34ac7f35391fb0" ], "author": { "name": "Corentin Chary", "email": "corentin.chary@gmail.com", "time": "Tue May 29 15:07:20 2012 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue May 29 16:22:30 2012 -0700" }, "message": "backlight: initialize struct backlight_properties properly\n\nIn all these files, the .power field was never correctly initialized.\n\nSigned-off-by: Corentin Chary \u003ccorentin.chary@gmail.com\u003e\nCc: Jingoo Han \u003cjg1.han@samsung.com\u003e\nCc: Dave Airlie \u003cairlied@gmail.com\u003e\nCc: Richard Purdie \u003crpurdie@rpsys.net\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "e92a5b28f71aea01b281f9c89d97a4bc5b24748f", "tree": "908694252565b02713732987733046692bbe5175", "parents": [ "c808ab9c82b20227a8b7659c5c8b75290047523c" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Mon May 21 21:47:21 2012 -0500" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 11:00:09 2012 +0300" }, "message": "OMAPDSS: HDMI: OMAP4: Update IRQ flags for the HPD IRQ request\n\ngenirq requires that the IRQ requests that do not provided a handler to\nuse the IRQF_ONESHOT flag. This is to prevent situations in which the irq line\nis reenabled while the interrupt is still asserted. While this situation may\nnot happen in edge type interrupts, genirq still requires to use IRQF_ONESHOT.\n\nAlso, remove the IRQF_DISABLED as the flag is now a NOOP and has been\ndeprecated.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "c808ab9c82b20227a8b7659c5c8b75290047523c", "tree": "a1cd624c6a2890aa355f1265d436207d68a320ee", "parents": [ "2aefad49d8e3a898cf629d4c5264ffd061113531" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon May 21 09:47:12 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 11:00:08 2012 +0300" }, "message": "OMAPDSS: Apply VENC timings even if panel is disabled\n\nThe VENC interfaces uses it\u0027s venc_set_timing() function to take in a new set\nof timings. If the panel is disabled, it does not disable and re-enable the\ninterface. Currently, the manager timings are applied in venc_power_on(), these\nare not called by set_timings if the panel is disabled. When checking overlay\nand manager data, the DSS driver uses the last applied manager timings, and not\nthe timings held by omap_dss_device struct. Hence, there is a need to apply the\nnew manager timings even if the panel is disabled.\n\nApply the manager timings if the VENC panel is disabled.\n\nThis is similar to the commit below which fixed the same issue for HDMI/DPI\ninterfaces:\n\nfcc36619901064a76e15a545ea36d38ba0e54192\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "2aefad49d8e3a898cf629d4c5264ffd061113531", "tree": "0fb4f039679cfcb544d795b21eb3c148fe9c1287", "parents": [ "65e006ff4bb06d42b532f866a846db6e4e637723" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Fri May 18 14:36:54 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 11:00:01 2012 +0300" }, "message": "OMAPDSS: VENC/DISPC: Delay dividing Y resolution for managers connected to VENC\n\nDSS2 driver uses the timings in manager\u0027s private data to check the validity of\noverlay and manager infos written by the user. For VENC interface, we divide the\nY resolution by half when writing to the DISPC_DIGIT_SIZE register as the\ncontent is interlaced. However, the height of the manager/display with respect\nto the content shown through VENC still remains the same.\n\nThe VENC driver divides the y_res parameter in omap_video_timings by half, and\nthen applies the configuration. This leads to manager\u0027s private data storing\nthe wrong Y resolution. Hence, overlay related checks fail.\n\nEnsure that manager\u0027s private data stores the original timings, and the Y\nresolution is halved only when we write to the DISPC register. This is a hack,\nthe proper solution would be to pass some sort of interlace parameter which\nmakes the call whether we should divide y_res or not.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "65e006ff4bb06d42b532f866a846db6e4e637723", "tree": "8b791304b33ea7888d7e43504865d899b5d1a096", "parents": [ "3cb6a1b9672a2e0937a1475e3d68e6c236133156" ], "author": { "name": "Chandrabhanu Mahapatra", "email": "cmahapatra@ti.com", "time": "Fri May 11 19:19:55 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 10:59:15 2012 +0300" }, "message": "OMAPDSS: DISPC: Support rotation through TILER\n\nTILER is a block in OMAP4\u0027s DMM which lets DSS fetch frames in a rotated manner.\nPhysical memory can be mapped to a portion of OMAP\u0027s system address space called\nTILER address space. The TILER address space is split into 8 views. Each view\nrepresents a rotated or mirrored form of the mapped physical memory. When a\nDISPC overlay\u0027s base address is programmed to one of these views, the TILER\nfetches the pixels according to the orientation of the view. A view is further\nsplit into 4 containers, each container holds elements of a particular size.\nRotation can be achieved at the granularity of elements in the container. For\nmore information on TILER, refer to the Memory Subsytem section in OMAP4 TRM.\nRotation type TILER has been added which is used to exploit the capabilities of\nthese 8 views for performing various rotations.\n\nWhen fetching from addresses mapped to TILER space, the DISPC DMA can fetch\npixels in either 1D or 2D bursts. The fetch depends on which TILER container we\nare accessing. Accessing 8, 16 and 32 bit sized containers requires 2D bursts,\nand page mode sized containers require 1D bursts.\n\nThe DSS2 user is expected to provide the Tiler address of the view that it is\ninterested in. This is passed to the paddr and p_uv_addr parameters in\nomap_overlay_info. It is also expected to provide the stride value based on the\nview\u0027s orientation and container type, this should be passed to the screen_width\nparameter of omap_overlay_info. In calc_tiler_rotation_offset screen_width is\nused to calculate the required row_inc for DISPC. x_predecim and y_predecim are\nalso used to calculate row_inc and pix_inc thereby adding predecimation support\nfor TILER.\n\nSigned-off-by: Chandrabhanu Mahapatra \u003ccmahapatra@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "3cb6a1b9672a2e0937a1475e3d68e6c236133156", "tree": "be69080b3a27b0221c0a30aa1871ba24bf2be3fb", "parents": [ "4a75cb857d2ec5f8f40f23a817ec162b93661bae" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 18 11:49:53 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 10:59:15 2012 +0300" }, "message": "OMAPDSS: VRFB: remove compiler warnings when CONFIG_BUG\u003dn\n\nIf CONFIG_BUG is not enabled, BUG() does not stop the execution. Many\nplaces in code expect the execution to stop, and this causes compiler\nwarnings about uninitialized variables and returning from a non-void\nfunction without a return value.\n\nThis patch fixes the warnings by initializing the variables and\nreturning properly after BUG() lines. However, the behaviour is still\nundefined after the BUG, but this is the choice the user makes when\nusing CONFIG_BUG\u003dn.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "4a75cb857d2ec5f8f40f23a817ec162b93661bae", "tree": "da91b912bbaf9cbc567f8e0883a8f626d484d16d", "parents": [ "c6eee968d40d319f0ac7a8a63dcbc633d9e6a2ea" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 18 11:48:28 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 10:59:15 2012 +0300" }, "message": "OMAPFB: remove compiler warnings when CONFIG_BUG\u003dn\n\nIf CONFIG_BUG is not enabled, BUG() does not stop the execution. Many\nplaces in code expect the execution to stop, and this causes compiler\nwarnings about uninitialized variables and returning from a non-void\nfunction without a return value.\n\nThis patch fixes the warnings by initializing the variables and\nreturning properly after BUG() lines. However, the behaviour is still\nundefined after the BUG, but this is the choice the user makes when\nusing CONFIG_BUG\u003dn.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "c6eee968d40d319f0ac7a8a63dcbc633d9e6a2ea", "tree": "69c37f169f25f8fad858b032508d2a1c2cd5c8ea", "parents": [ "36377357db00f8660039578ba57a2a19bfc9ad3d" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 18 11:47:02 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 10:59:14 2012 +0300" }, "message": "OMAPDSS: remove compiler warnings when CONFIG_BUG\u003dn\n\nIf CONFIG_BUG is not enabled, BUG() does not stop the execution. Many\nplaces in code expect the execution to stop, and this causes compiler\nwarnings about uninitialized variables and returning from a non-void\nfunction without a return value.\n\nThis patch fixes the warnings by initializing the variables and\nreturning properly after BUG() lines. However, the behaviour is still\nundefined after the BUG, but this is the choice the user makes when\nusing CONFIG_BUG\u003dn.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "36377357db00f8660039578ba57a2a19bfc9ad3d", "tree": "8965ddaa268af056f28922b4224a1225fd404574", "parents": [ "3568f2a46f2a73bab18c914df06afd98a97e0e0e" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 15 15:54:15 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 10:59:14 2012 +0300" }, "message": "OMAPDSS: DISPC: fix usage of dispc_ovl_set_accu_uv\n\nCommit 05dd0f5308213e169b02458a7f3a61362e581e14 (\"OMAPDSS: DISPC: Update\nAccumulator configuration for chroma plane\") adds\ndispc_ovl_set_accu_uv() function that sets the accu, but the function\nonly handles YUV and NV12 modes, and BUGs otherwise.\n\nThe patch also adds a call to the function, but unfortunately the place\nof call was such that the mode could be other than YUV or NV12, thus\ncrashing the driver.\n\nThis patchs moves the call to a slightly later spot, at which point only\nYUV and NV12 modes are handled.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nCc: Chandrabhanu Mahapatra \u003ccmahapatra@ti.com\u003e\n" }, { "commit": "3568f2a46f2a73bab18c914df06afd98a97e0e0e", "tree": "ff90a459d943101693a74e4ccf44112d1e9d3423", "parents": [ "6f28c2964b535f9439d52c437aa2fbfef7ed149c" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 15 15:31:01 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 22 10:59:13 2012 +0300" }, "message": "OMAPDSS: use DSI_FIFO_BUG workaround only for manual update displays\n\nThere is a problem related to DSS FIFO thresholds and power management\non OMAP3. It seems that when the full PM hits in, we get underflows. The\ncore reason is unknown, but after experiments it looks like only\nparticular FIFO thresholds work correctly.\n\nThis bug is related to an earlier patch, which added special FIFO\nthreshold configuration for OMAP3, because DSI command mode output\ndidn\u0027t work with the normal threshold configuration.\n\nHowever, as the above work-around worked fine for other output types\nalso, we currently always configure thresholds in this special way on\nOMAP3. In theory there should be negligible difference with this special\nway and the standard way. The first paragraph explains what happens in\npractice.\n\nThis patch changes the driver to use the special threshold configuration\nonly when the output is a manual update display on OMAP3. This does\ninclude RFBI displays also, and although it hasn\u0027t been tested (no\nboards using RFBI) I suspect the similar behaviour is present there\nalso, as the DISPC side should work similarly for DSI command mode and\nRFBI.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nCc: Joe Woodward \u003cjw@terrafix.co.uk\u003e\n" }, { "commit": "6f28c2964b535f9439d52c437aa2fbfef7ed149c", "tree": "d46ed3e233b954425ec9a74e0c33a6fd62cb0eb6", "parents": [ "05dd0f5308213e169b02458a7f3a61362e581e14" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Tue May 15 11:32:18 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon May 21 12:21:18 2012 +0300" }, "message": "OMAPDSS: DSI: Support command mode interleaving during video mode blanking periods\n\nDSI supports interleaving of command mode packets during the HSA, HFP, HBP and\nBLLP blanking intervals in a video mode stream. This is useful as a user may\nwant to read or change the configuration of a panel without stopping the video\nstream.\n\nOn OMAP DSI, we can queue HS or LP command mode packets in the TX FIFO, and\nthe DSI HW takes care of interleaving this data during the one of the blanking\nintervals. The DSI HW needs to be programmed with the maximum amount of data\nthat can be interleaved in a particular blanking period. A blanking period\ncannot be used to send command mode data for it\u0027s complete duration, there is\nsome amount of time required for the DSI data and clock lanes to transition\nto the desired LP or HS state.\n\nBased on the state of the lanes at the beginning and end of the blanking period,\nwe have different scenarios, with each scenario having a different value of time\nrequired to transition to HS or LP. Refer to the section \u0027Interleaving Mode\u0027 in\nOMAP TRM for more info on the scenarios and the equations to calculate the time\nrequired for HS or LP transitions.\n\nWe use the scenarios which takes the maximum time for HS or LP transition, this\ngives us the minimum amount of time that can be used to interleave command mode\ndata. The amount of data that can be sent during this minimum time is calculated\nfor command mode packets both in LP and HS. These are written to the registers\nDSI_VM_TIMING4 to DSI_VM_TIMING6.\n\nThe calculations don\u0027t take into account the time required of transmitting BTA\nwhen doing a DSI read, or verifying if a DSI write went through correctly. Until\nthese latencies aren\u0027t considered, the behaviour of DSI is unpredictable when\na BTA is interleaved during a blanking period. Enhancement of these calculations\nis a TODO item.\n\nThe calculations are derived from DSI parameter calculation tools written by\nSebastien Fagard \u003cs-fagard@ti.com\u003e\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "05dd0f5308213e169b02458a7f3a61362e581e14", "tree": "1f7248a3ea593ff33ea96dec723e5565e776c85a", "parents": [ "037983e61b61e82fa28fea38d02e354d74c66bab" ], "author": { "name": "Chandrabhanu Mahapatra", "email": "cmahapatra@ti.com", "time": "Tue May 15 12:22:34 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue May 15 13:51:56 2012 +0300" }, "message": "OMAPDSS: DISPC: Update Accumulator configuration for chroma plane\n\nDISPC has two accumulator registers DISPC_VIDp_ACCU_0 and DISPC_VIDp_ACCU_1 each\nwith horizontal and vertical bit fields. The bit fields can take values in the\nrange of -1024 to 1023. Based on bit field values DISPC decides on which one out\nof 8 phases the filtering starts. DISPC_VIDp_ACCU_0 is used for progressive\noutput and for interlaced output both DISPC_VIDp_ACCU_0 and DISPC_VIDp_ACCU_1\nare used.\n\nThe current accumulator values in DISPC scaling logic for chroma plane takes\ndefault values for all color modes and rotation types. So, the horizontal and\nvertical up and downsampling accumulator bit field values have been updated for\nbetter performance.\n\nSigned-off-by: Chandrabhanu Mahapatra \u003ccmahapatra@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "f3a97491f2c54e5239663f8f147b34c280cf7db5", "tree": "8d502829f3b27b5d8b587fb965919260d832497a", "parents": [ "b7dea05aec8b6421500929d5003866655d6d9dab" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Wed May 09 21:09:50 2012 -0500" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:17:10 2012 +0300" }, "message": "OMAPDSS: HDMI: Implement DSS driver interface for audio\n\nImplement the DSS device driver audio support interface in the HDMI\npanel driver and generic driver. The implementation relies on the\nIP-specific functions that are defined at DSS probe time.\n\nA mixed locking strategy is used. The panel\u0027s mutex is used when\nthe state of the panel is queried as required by the audio functions.\nThe audio state is protected using a spinlock as users of DSS HDMI\naudio functionality might start/stop audio while holding a spinlock.\nThe mutex and the spinlock are held and released as needed by each\nindividual function to protect the panel state and the audio state.\n\nAlthough the panel\u0027s audio_start functions does not check whether\nthe panel is active, the audio _ENABLED state can be reached only\nfrom audio_enable, which does check the state of the panel. Also,\nif the panel is ever disabled, the audio state will transition\nto _DISABLED. Transitions are always protected by the audio lock.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "b7dea05aec8b6421500929d5003866655d6d9dab", "tree": "d042965ba9e46ff850f388bdf099146e66e7d90e", "parents": [ "24ccfc5541b11f1e6ffcf10f5ce94370440d6c75" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Wed Apr 25 19:29:06 2012 -0500" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:17:09 2012 +0300" }, "message": "OMAPDSS: HDMI: Panel: Simplify the name of the HDMI mutex\n\nAs the hdmi_lock mutex is inside the hdmi struct, rename to simply\n\"lock\". This is only a change in the name. There are not changes\nin functionality.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "24ccfc5541b11f1e6ffcf10f5ce94370440d6c75", "tree": "6657224dc42aa28ad885ca5ae9c399579bda669e", "parents": [ "6ec355d6c79e811a3b7f85ca6b22fa4bd7b1bbfc" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Thu May 03 12:27:12 2012 -0500" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:17:09 2012 +0300" }, "message": "OMAPDSS: HDMI: OMAP4: Remap speaker order to match ALSA order\n\nAs of today, the only know user of the DSS HDMI audio support is\nASoC. Hence, it makes sense to remap the speaker order to match\nthe ALSA speaker order. In the future, a dynamic mapping mechanism\nmay be implemented.\n\nRemapping is needed as the HDMI speaker order is FL/FR/LFE/C/RL/RR/\nRLC-FLC/RRC-FLC while the ALSA order is FL/FR/RL/RR/C/LFE/SL/SR.\nRefer to CEA-861 Section 6.6.2 for further details.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "6ec355d6c79e811a3b7f85ca6b22fa4bd7b1bbfc", "tree": "316df760312fd6833c0bcc609e5dd46930cc196f", "parents": [ "25a653597ee63119a477e9bdeb6b41bd7cd56140" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Wed Mar 21 12:38:15 2012 -0600" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:17:08 2012 +0300" }, "message": "OMAPDSS: HDMI: Add an audio configuration function\n\nThe generic HDMI driver does not need to know about the specific\nsettings of a given IP. Hence, it just passes the audio configuration\nand the IP library parses such configuration and sets the IP\naccordingly. This patch introduces an IP-specific audio configuration\nfunction.\n\nAlso, this patch implements the audio config function for OMAP4. The\nDMA, format and core config functions are no longer exposed to the\ngeneric HDMI driver as they are IP-specific.\n\nThe audio configuration function caters for 16-bit through 24-bit\naudio samples with sample rates from 32kHz and up to 192kHz as well\nas up to 8 audio channels.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "25a653597ee63119a477e9bdeb6b41bd7cd56140", "tree": "def05373310514afb1ce680ed741c52c54baf134", "parents": [ "35547626f3cc527d5e899bbfbac6b9e373f47aa0" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Fri Mar 23 15:49:02 2012 -0600" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:17:08 2012 +0300" }, "message": "OMAPDSS: HDMI: Add support for more audio sample rates in N/CTS calculation\n\nAdd support for more sample rates when calculating N and CTS. This\ncovers all the audio sample rates that an HDMI source is allowed\nto transmit according to the HDMI 1.4a specification.\n\nAlso, reorganize the logic for the calculation when using deep color.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "35547626f3cc527d5e899bbfbac6b9e373f47aa0", "tree": "8b80136667c91e48c601fab95fb24b12361478b4", "parents": [ "c1164ed87ea592c2001a0040ffbf9a75cf501d1c" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Tue Mar 20 21:02:01 2012 -0600" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:17:06 2012 +0300" }, "message": "OMAPDSS: HDMI: Relocate N/CTS calculation\n\nThe N and CTS parameters are relevant to all HDMI implementations and\nnot specific to a given IP. Hence, the calculation is relocated\ninto the generic HDMI driver.\n\nAlso, deep color is not queried but it is still considered in the\ncalculation of N. This is to be changed when deep color functionality is\nimplemented in the driver.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "c1164ed87ea592c2001a0040ffbf9a75cf501d1c", "tree": "9a64206f353c349323d225dd88a7cf1ff7985742", "parents": [ "7e151f7f6abdd75831797ae45ec2aa3d0a648416" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Mon Mar 19 12:27:41 2012 -0600" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:15:23 2012 +0300" }, "message": "OMAPDSS: HDMI: OMAP4: Expand configuration for IEC-60958 audio\n\nUtilize a snd_aes_iec958 struct to write the parameters of the IEC-60958\nchannel status word into the HDMI IP registers. Hence, the user of the\ndriver has full control of what parameters are written in the word.\n\nAlso, some of the parameters of the I2S structure have been removed\nas they are actually IEC-60958 parameters.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "7e151f7f6abdd75831797ae45ec2aa3d0a648416", "tree": "b74dea57e63e80735732b812aa29e835c532a3ad", "parents": [ "3df9fb5c51ca617e410da890f631100ea9f10652" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Thu Mar 15 14:08:03 2012 -0600" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:15:22 2012 +0300" }, "message": "OMAPDSS: HDMI: Decouple HDMI audio from ASoC\n\nInstead of having OMAPDSS HDMI audio functionality depending on the\nASoC HDMI audio driver, use a new config option so that\npotential users, including ASoC, may select if needed.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "3df9fb5c51ca617e410da890f631100ea9f10652", "tree": "0f705465db5e66149a14061df988d776f47fe802", "parents": [ "7c92af16780c614b493c4e8a9f495f9dc8008de4" ], "author": { "name": "Axel Castaneda Gonzalez", "email": "x0055901@ti.com", "time": "Thu May 03 09:00:21 2012 -0500" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:15:22 2012 +0300" }, "message": "OMAPDSS: HDMI: Decouple wrapper enable/disable and audio start/stop\n\nDecouple the enable/disable operation of the HDMI audio wrapper from\naudio start/stop. Otherwise, an audio FIFO underflow may occur. The\naudio wrapper enablement must be done after configuration and\nbefore audio playback is started.\n\nSigned-off-by: Axel Castaneda Gonzalez \u003cx0055901@ti.com\u003e\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "7c92af16780c614b493c4e8a9f495f9dc8008de4", "tree": "78bf084a14a362aa7253b3d6d3e273c5977e2b6b", "parents": [ "199e7fd6219cac2065a0e7e09d9d505e1f03f29e" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Mon Mar 19 09:30:21 2012 -0600" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:15:21 2012 +0300" }, "message": "OMAPDSS: HDMI: OMAP4: Remove invalid I2S settings\n\nAccording to the most up-to-date documentation from Texas Instruments,\nthe configuration of High Bitrate Audio is not possible. Also, it is\nnot possible to set polarity of the I2S Word Select signal. This patch\nremoves the invalid settings.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "199e7fd6219cac2065a0e7e09d9d505e1f03f29e", "tree": "51a342a17921556f6951184197553c7fa4c0263a", "parents": [ "7c3291f06b4e025c4bd373adbb3f6354080f5097" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Thu Mar 15 10:39:00 2012 -0600" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:15:21 2012 +0300" }, "message": "OMAPDSS: HDMI: OMAP4: Remove CEA-861 audio infoframe and IEC-60958 enums\n\nInstead of having its own definitions for CEA-861 and IEC-60958, the HDMI\ndriver should use those provided by ALSA. This patch removes the definitions\nthat are already provided by ALSA.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "7c3291f06b4e025c4bd373adbb3f6354080f5097", "tree": "b4f825147f46ddc8aaf83d57b5168072adb99ce1", "parents": [ "c0456be38fef2866b1dbeceb756485b001fa23b9" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Thu Mar 15 12:58:51 2012 -0600" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:15:18 2012 +0300" }, "message": "OMAPDSS: HDMI: Remove ASoC codec\n\nRemove the ASoC OMAP HDMI audio codec. The goal of removing the codec\nis to, in subsequent patches, give way to the implementation of the HDMI\naudio support using the DSS device driver audio interface. This\napproach will expose the HDMI audio functionality to any interested entity.\n\nIn a separate patch, ASoC will use this new approach to expose HDMI audio\nto ALSA.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "c0456be38fef2866b1dbeceb756485b001fa23b9", "tree": "ff48172b118125d8f598d967c76561e02d89c497", "parents": [ "027bdc85ee74f8f456a47dc53154252ef7d1792f" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Fri Apr 27 13:48:45 2012 -0500" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:13:51 2012 +0300" }, "message": "OMAPDSS: HDMI: Split video_enable into video_enable/disable\n\nTo improve readability, split the video_enable HDMI IP operation\ninto two separate functions for enabling and disabling video.\nThe video_enable function is also modified to return an error value.\n\nWhile there, update these operations for the OMAP4 IP accordingly.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "027bdc85ee74f8f456a47dc53154252ef7d1792f", "tree": "99d55912caa0f4b3c43552b89160d22faf9d3584", "parents": [ "9c0b8420369cb5d7fd2fea51d4705cbd0ea52743" ], "author": { "name": "Ricardo Neri", "email": "ricardo.neri@ti.com", "time": "Fri Apr 20 17:17:46 2012 -0500" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:13:50 2012 +0300" }, "message": "OMAPDSS: HDMI: Split audio_enable into audio_enable/disable\n\nTo improve readability, split the audio_enable HDMI IP operation\ninto two separate functions for enabling and disabling audio.\nThe audio_enable function is also modified to return an error value.\n\nWhile there, update these operations for the OMAP4 IP accordingly.\n\nSigned-off-by: Ricardo Neri \u003cricardo.neri@ti.com\u003e\n" }, { "commit": "af461d64e11f81db4a7619dd574fe779ae3a0884", "tree": "4985e69beb92a6f9ed9e280dc1e6d5d6c3efb645", "parents": [ "38f3daf678d909e8ee5638f21a34f35c01343420" ], "author": { "name": "Russ Dill", "email": "Russ.Dill@ti.com", "time": "Wed May 09 15:08:08 2012 -0700" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:09:29 2012 +0300" }, "message": "OMAPDSS: TFP410: use gpio_set_value_cansleep\n\nThe Beagleboard xM gpio used for TFP410 powerdown is connected through\nan I2C attached chip which means setting the GPIO can sleep. Code that\ncalls tfp410_power_on/off holds a mutex, so sleeping should be fine.\n\nSigned-off-by: Russ Dill \u003cRuss.Dill@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "38f3daf678d909e8ee5638f21a34f35c01343420", "tree": "0e0ea8fa43e038980632906186f1e9d0021f82a7", "parents": [ "11ee9606407031827d43ecde8e62a418ac3b4f83" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 02 14:55:12 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 15:09:24 2012 +0300" }, "message": "OMAPDSS: separate pdata based initialization\n\nMove the platform-data based display device initialization into a\nseparate function, so that we may later add of-based initialization.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "11ee9606407031827d43ecde8e62a418ac3b4f83", "tree": "ca384f9c195ff7a124b9c0c587231389c98e2f1f", "parents": [ "9d8232a77fd55e00f0c519518c0ac5bbff1e477c" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri Mar 09 16:07:39 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:54:41 2012 +0300" }, "message": "OMAPDSS: DSI: improve DSI module id handling\n\nWe currently use the id of the dsi platform device (dsidev-\u003eid) as the\nDSI hardware module ID. This works because we assign the ID manually in\narch/arm/mach-omap2/display.c at boot time.\n\nHowever, with device tree the platform device IDs are automatically\nassigned to an arbitrary number, and we can\u0027t use it.\n\nInstead of using dsidev-\u003eid during operation, this patch stores the\nvalue of dsidev-\u003eid to a private field of the dsi driver at probe(). The\nfuture device tree code can thus set the private field with some other\nway.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "9d8232a77fd55e00f0c519518c0ac5bbff1e477c", "tree": "3d66ccadf59dd122577e2fb2f44f2b27a6c3bf89", "parents": [ "35deca3de6190b6bc03e34ed45de079047f834ab" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Mar 01 16:58:39 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:54:38 2012 +0300" }, "message": "OMAPDSS: init omap_dss_devices internally\n\nNow that each output driver creates their own display devices, the\noutput drivers can also initialize those devices.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "35deca3de6190b6bc03e34ed45de079047f834ab", "tree": "6e778144d508dc5550cb105b39d06a522459069a", "parents": [ "c018c6738bdae8c9f49766fd3d8b3770be2572f9" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Mar 01 15:45:53 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:52:23 2012 +0300" }, "message": "OMAPDSS: interface drivers register their panel devices\n\nCurrently the higher level omapdss platform driver gets the list of\ndisplays in its platform data, and uses that list to create the\nomap_dss_device for each display.\n\nWith DT, the logical way to do the above is to list the displays under\neach individual output, i.e. we\u0027d have \"dpi\" node, under which we would\nhave the display that uses DPI. In other words, each output driver\nhandles the displays that use that particular output.\n\nTo make the current code ready for DT, this patch modifies the output\ndrivers so that each of them creates the display devices which use that\noutput. However, instead of changing the platform data to suit this\nmethod, each output driver is passed the full list of displays, and the\ndrivers pick the displays that are meant for them. This allows us to\nkeep the old platform data, and thus we avoid the need to change the\nboard files.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "c018c6738bdae8c9f49766fd3d8b3770be2572f9", "tree": "cca221bd0afb92d5acaffad11bcad984cef90c1d", "parents": [ "d64f14e191310570264454998201a84d211f30aa" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Feb 23 13:00:51 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:52 2012 +0300" }, "message": "OMAPDSS: change default_device handling\n\nWe currently have a two ways to set a \"default panel device\" for dss, to\nwhich the overlays are connected when the omapdss driver is loaded:\n\n- in textual format (name of the display) as cmdline parameter\n- as a pointer to the panel device from board file via pdata\n\nThe current code handles this in a bit too complex way by using both of\nthe above methods during runtime. However, with DT we don\u0027t have pdata\nanymore, so the code handling the second case won\u0027t work anymore. The\ncurrent code has also the problem that it modifies the platform_data.\n\nThis patch simplifies the code a bit by using the pointer method only\ninside the probe function, and stores the name of the panel device. This\nway we only need to handle the textual format during operation and also\navoid modifying the platform_data.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "d64f14e191310570264454998201a84d211f30aa", "tree": "9205a28e51c882382decfe5034912145c7314416", "parents": [ "6e7e8f06b2c77dbb5d28062a174e4d67aec4b924" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri Feb 17 17:43:03 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:52 2012 +0300" }, "message": "OMAPFB: add __init \u0026 __exit\n\nChange omapfb to use platform_driver_probe and add __init \u0026 __exit.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "6e7e8f06b2c77dbb5d28062a174e4d67aec4b924", "tree": "7d04633073c62d6ef4bb25ddbdfb0f7c09cd2666", "parents": [ "61055d4b2eb164cb81af1e5940a31c7f2e53757e" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri Feb 17 17:41:13 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:52 2012 +0300" }, "message": "OMAPDSS: add __init \u0026 __exit\n\nNow that we are using platform_driver_probe() we can add __inits and\n__exits all around.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "61055d4b2eb164cb81af1e5940a31c7f2e53757e", "tree": "e79580e110c1a73b8a917d3ee50f478026069722", "parents": [ "e40402cf182e798fd71824f4ad02fb51ce599bb2" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed Mar 07 12:53:38 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:52 2012 +0300" }, "message": "OMAPDSS: use platform_driver_probe for dsi/hdmi/rfbi/venc/dpi/sdi\n\nNow that the core.c doesn\u0027t fail if output driver\u0027s init fails, we can\nchange the uses of platform_driver_register to platform_driver_probe.\nThis will allow us to use __init in the following patches.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "e40402cf182e798fd71824f4ad02fb51ce599bb2", "tree": "2b3c87838f5f53a4eb7e74738f6d792ab64d1c8d", "parents": [ "461395c464e559a01cbc66d97ed4b8585b437cf9" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri Mar 02 18:01:07 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:52 2012 +0300" }, "message": "OMAPDSS: move the creation of debugfs files\n\nInstead of having an ugly #ifdef mess in the core.c for creating debugfs\nfiles, add a dss_debugfs_create_file() function that the dss drivers\ncan use to create the debugfs files.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "461395c464e559a01cbc66d97ed4b8585b437cf9", "tree": "5e0f97a1d61fdcb8c59c7f6f3674508c16aab767", "parents": [ "852f083843af618eaa8997f7803c9aed8293fdf9" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri Mar 02 17:37:53 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:52 2012 +0300" }, "message": "OMAPDSS: handle output-driver reg/unreg more dynamically\n\nInitialize and uninitialize the output drivers by using arrays of\npointers to the init/uninit functions. This simplifies the code\nslightly.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "852f083843af618eaa8997f7803c9aed8293fdf9", "tree": "45d823a928788f772e30a13ae8b2b9b4dfd109f7", "parents": [ "a57dd4fe7bef557afaa1a6cdb77cd95b2cba094e" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri Feb 17 17:58:04 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:51 2012 +0300" }, "message": "OMAPDSS: remove uses of dss_runtime_get/put\n\nNow that the omapdss_core device is the parent for all other dss\ndevices, we don\u0027t need to use the dss_runtime_get/put anymore. Instead,\nenabling omapdss_core will happen automatically when a child device is\nenabled.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "a57dd4fe7bef557afaa1a6cdb77cd95b2cba094e", "tree": "50cae3f775bc743299dc7285c758df599d2874cc", "parents": [ "53f576a8dc5729e719c862aba2ed3430867bd5cb" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Feb 20 16:57:37 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:51 2012 +0300" }, "message": "OMAPDSS: create DPI \u0026 SDI drivers\n\nWe currently have separate device/driver for each DSS HW module. The DPI\nand SDI outputs are more or less parts of the DSS or DISPC hardware\nmodules, but in SW it makes sense to represent them as device/driver\npairs similarly to all the other outputs. This also makes sense for\ndevice tree, as each node under dss will be a platform device, and\nhandling DPI \u0026 SDI somehow differently than the rest would just make the\ncode more complex.\n\nThis patch modifies the dpi.c and sdi.c to create drivers for the\nplatform devices.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "11436e1dd2aab1a33f81a3737ec8641788ec8543", "tree": "79d698da00da5dc465769dfab9f78656134714f8", "parents": [ "04c742c3dccac296fdc52b464bd0491ffe88de23" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed Mar 07 12:53:18 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:51 2012 +0300" }, "message": "OMAPDSS: use platform_driver_probe for core/dispc/dss\n\nThe platform devices for omapdss, dss and dispc drivers are always\npresent, so we can use platform_driver_probe instead of\nplatform_driver_register.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "04c742c3dccac296fdc52b464bd0491ffe88de23", "tree": "8e2cfc3dbb4965118c4d67639d1910db86286d73", "parents": [ "00928eaf52007ee4e1fb7dc860bc02a56c125bb4" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Feb 23 15:32:37 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:51 2012 +0300" }, "message": "OMAPDSS: remove return from platform_driver_unreg\n\nFor unknown reasons we seem to have a return in each of the omapdss\u0027s\nuninit functions, which is a void function.\n\nRemove the returns.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "00928eaf52007ee4e1fb7dc860bc02a56c125bb4", "tree": "f5e4b086bf57243d1d5b1ae7f38891c26b473263", "parents": [ "e23d83b0c92bbe30d1fe9d5c0b972e50c6593946" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Feb 20 11:50:06 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:51 2012 +0300" }, "message": "OMAPDSS: clean up the omapdss platform data mess\n\nThe omapdss pdata handling is a mess. This is more evident when trying\nto use device tree for DSS, as we don\u0027t have platform data anymore in\nthat case. This patch cleans the pdata handling by:\n\n- Remove struct omap_display_platform_data. It was used just as a\n wrapper for struct omap_dss_board_info.\n- Pass the platform data only to omapdss device. The drivers for omap\n dss hwmods do not need the platform data. This should also work better\n for DT, as we can create omapdss device programmatically in generic omap\n boot code, and thus we can pass the pdata to it.\n- Create dss functions for get_ctx_loss_count and dsi_enable/disable_pads\n that the dss hwmod drivers can call.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "e23d83b0c92bbe30d1fe9d5c0b972e50c6593946", "tree": "9f0890f9896ed7e2c0391f67c5a56d22c5b011b1", "parents": [ "958f2717b84e88bf833d996997fda8f73276f2af" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Jan 10 11:26:52 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:50 2012 +0300" }, "message": "OMAPDSS: DSI: use dsi_get_dsidev_id(dsidev) instead of dsidev-\u003eid\n\nThe DSI driver uses dsi_get_dsidev_id() to get the ID number for the DSI\ninstance. However, there were a few places where dsidev-\u003eid was used\ninstead of the function. Fix those places to use the function.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "958f2717b84e88bf833d996997fda8f73276f2af", "tree": "6a6a6af4d4c323530024aa5e6e4f38e7425da05c", "parents": [ "3a028bb99d1f1e5c444060a176cbd4bf93530df3" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri Feb 17 12:19:48 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:50 2012 +0300" }, "message": "OMAPDSS: TFP410: pdata rewrite\n\nTo ease device tree adaptation in the future, rewrite TFP410 platform\ndata handling to be done inside probe(), so that probe() is the only\nplace where we need to handle the DT/pdata choice.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "3a028bb99d1f1e5c444060a176cbd4bf93530df3", "tree": "198ca5954a9dd59e005c871374fffac355f7e6ab", "parents": [ "b3e68d306519cc96ff5ad2957d133997f91bb53e" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu May 10 11:15:14 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:27 2012 +0300" }, "message": "OMAPFB: fix parsing of vram parameter\n\nomapfb_parse_vram_param()\u0027s check for end pointer returned from\nsimple_strtoul() is wrong, causing the code to bug if the second or\nlater vram parameters are non-parseable, for example\n\"omapfb.vram\u003d0:2M,:5M\".\n\nHowever, even in that case the code will most likely bail out with\n-EINVAL in the following checks, so the bug is probably not a fatal one.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nReported-by: Hein Tibosch \u003chein_tibosch@yahoo.es\u003e\n" }, { "commit": "b3e68d306519cc96ff5ad2957d133997f91bb53e", "tree": "d3bc04745f82e682fda0096ed300ad9725fc4458", "parents": [ "0aca3c63e068e47616bdd54b9d19e4771db86e8e" ], "author": { "name": "Grazvydas Ignotas", "email": "notasas@gmail.com", "time": "Thu May 10 14:19:56 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:21 2012 +0300" }, "message": "OMAPDSS: OMAPFB: always allow to configure overlay\n\nCurrently when multiple overlays are active, OMAPFB_SETUP_PLANE fails.\nInstead of failing, allow it to configure the first overlay as if there\nwas only one overlay, the remaining ones will have to be configured in\nother ways (sysfs).\n\nThis allows overlay-controlling programs (like video players) to function\nproperly when framebuffer is cloned to another display (like TV).\n\nSigned-off-by: Grazvydas Ignotas \u003cnotasas@gmail.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "0aca3c63e068e47616bdd54b9d19e4771db86e8e", "tree": "9d73c3bb318180b6c80cc4446f03983f2b698bf4", "parents": [ "9b71fb5cbcdd83c65e5fe6db9cd12246f7ea0262" ], "author": { "name": "Grazvydas Ignotas", "email": "notasas@gmail.com", "time": "Tue Apr 24 00:08:54 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri May 11 14:44:13 2012 +0300" }, "message": "OMAPDSS: VENC: allow switching venc output type at runtime\n\nVENC output type (composite/svideo) doesn\u0027t have to be fixed by board\nwiring, it is possible to also provide composite signal through svideo\nluminance connector (software enabled), which is what pandora does.\n\nHaving to recompile the kernel for users who have TV connector types\nthat don\u0027t match default board setting is very inconvenient, especially\nfor users of a consumer device, so add support for switching VENC output\ntype at runtime over a new sysfs file output_type.\n\nSigned-off-by: Grazvydas Ignotas \u003cnotasas@gmail.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "9b71fb5cbcdd83c65e5fe6db9cd12246f7ea0262", "tree": "d034047d7cd562700c59a0b1b3ba707367939fe7", "parents": [ "1dfafbc655b3723e37120d4b30e82d1c87767dd1", "e4a9e94cc58ed6e4efb02b80be3a9bf57f448d07" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu May 10 19:55:44 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu May 10 20:24:14 2012 +0300" }, "message": "Merge branch \u0027for-l-o-3.5\u0027\n\nConflicts:\n\tdrivers/video/omap2/displays/panel-taal.c\n\nMerge OMAP DSS related board file changes. The branch will also be\nmerged through linux-omap tree to solve conflicts.\n" }, { "commit": "81ab95b7ec91e47c81e5e6ef4aac7b08c1ae90aa", "tree": "f20c901613fa622b2e05d0d20c0aa001925d5dd2", "parents": [ "3fa03ba8542c40b90c95facfecd9b2789f71c0b6" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Tue May 08 15:53:20 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:09 2012 +0300" }, "message": "OMAPDSS: DISPC: Remove usage of dispc_mgr_get_device()\n\nThe functions calc_fclk_five_taps() and check_horiz_timing_omap3() use the\nfunction dispc_mgr_get_device() to get the omap_dss_device pointer to which\nthe manager is connected, the width of the panel is derived from that.\n\nThe manager\u0027s timing is stored in it\u0027s private data in APPLY. This contains\nthe latest timings applied to the manager. Pass these timings to\ndispc_ovl_setup() and use them in the above functions. Remove the function\ndispc_mgr_get_device() as it isn\u0027t used any more.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "3fa03ba8542c40b90c95facfecd9b2789f71c0b6", "tree": "df910c413818cbbb1c03e36abe561f19ae941d65", "parents": [ "b3d795abb253c7605f8b6257f2e25e7ebaaf4b57" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon Apr 09 15:06:41 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:09 2012 +0300" }, "message": "OMAPDSS: DISPC: Remove omap_dss_device pointer usage from dispc_mgr_pclk_rate()\n\nThe pixel clock rate for the TV manager is calculated by checking the device\ntype connected to the manager, and then requesting the VENC/HDMI interface for\nthe pixel clock rate.\n\nRemove the use of omap_dss_device pointer from here by checking which interface\ngenerates the pixel clock by reading the DSS_CTRL.VENC_HDMI_SWITCH bit.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "b3d795abb253c7605f8b6257f2e25e7ebaaf4b57", "tree": "903ddd5ed9598fd80f710d5832deba6ae4d08474", "parents": [ "fcc36619901064a76e15a545ea36d38ba0e54192" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon Apr 09 14:36:08 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:08 2012 +0300" }, "message": "OMAPDSS: APPLY: Remove an unnecessary omap_dss_device pointer\n\nThe omap_dss_device pointer declared in dss_ovl_setup_fifo() isn\u0027t used. Remove\nthe pointer variable declaration and it\u0027s assignment.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "fcc36619901064a76e15a545ea36d38ba0e54192", "tree": "efd1ecca35ccd40b56e8c0cad06bda824904acf1", "parents": [ "228b21349db4ca5636ec1efdb3b3d54fe18092de" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Thu May 03 20:03:11 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:08 2012 +0300" }, "message": "OMAPDSS: DPI/HDMI: Apply manager timings even if panel is disabled\n\nThe DPI and HDMI interfaces use their \u0027set_timing\u0027 functions to take in a new\nset of timings. If the panel is disabled, they do not disable and re-enable\nthe interface. Currently, the manager timings are applied in hdmi_power_on()\nand dpi_set_mode() respectively, these are not called by set_timings if the\npanel is disabled.\n\nWhen checking overlay and manager data, the DSS driver uses the last applied\nmanager timings, and not the timings held by omap_dss_device struct. Hence,\nthere is a need to apply the new manager timings even if the panel is disabled.\n\nApply the manager timings if the panel is disabled. Eventually, there should be\none common place where the timings are applied independent of the state of the\npanel.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "228b21349db4ca5636ec1efdb3b3d54fe18092de", "tree": "61e933b8f50ec5225e91fe2bf6bbfbb11a26c1af", "parents": [ "5dd747e8892a63a5d4cc1d2765c0f533a5d74cfd" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Fri Apr 27 01:22:28 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:07 2012 +0300" }, "message": "OMAPDSS: APPLY: Remove display dependency from overlay and manager checks\n\nIn order to check the validity of overlay and manager info, there was a need to\nuse the omap_dss_device struct to get the panel resolution. The manager\u0027s\nprivate data in APPLY now contains the manager timings. Hence, we don\u0027t need to\nrely on the display resolution any more.\n\nPass the manager\u0027s timings in private data to dss_mgr_check(). Remove the need\nto pass omap_dss_device structs in the functions which check for the validity\nof overlay and manager parameters.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "5dd747e8892a63a5d4cc1d2765c0f533a5d74cfd", "tree": "2b58d6d31773dfee3c69c755baa07e158ddb540a", "parents": [ "b917fa3961448903f4ee823917194bdf20709fbd" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Tue May 08 18:19:15 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:07 2012 +0300" }, "message": "OMAPDSS: APPLY: Don\u0027t check manager settings if it is disabled\n\nIf a manager is disabled, there is no guarantee at any point in time that all\nit\u0027s parameters are configured. There is always a chance that some more\nparameters are yet to be configured by a user of DSS, or by DSS itself.\n\nHowever, when the manager is enabled, we can be certain that all the parameters\nhave been configured, as we can\u0027t enable a manager with an incomplete\nconfiguration. Therefore, if a manager is disabled, don\u0027t check for the validity\nof it\u0027s parameters or the parameters of the overlays connected to it. Only check\nonce it is enabled. Add a check in dss_check_settings_low() to achieve the same.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "b917fa3961448903f4ee823917194bdf20709fbd", "tree": "f243fc3c8b20b1ea50071e96081e437a99890098", "parents": [ "4172116385ede7abcfbbcc6eb6b7133385695001" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Fri Apr 27 01:07:28 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:07 2012 +0300" }, "message": "OMAPDSS: MANAGER: Create a function to check manager timings\n\nCreate a function dss_mgr_check_timings() which wraps around the function\ndispc_mgr_timings_ok(). This is mainly a clean up to hide dispc functions\nfrom interface drivers.\n\ndss_mgr_check_timings() is added in the function dss_mgr_check(), it currently\ntakes the timings maintained in the omap_dss_device struct. This would be later\nreplaced by the timings stored in the manager\u0027s private data.\n\nMake dss_mgr_check_timings() and dispc_mgr_timings_ok() take a const\nomap_video_timings pointer since these functions just check the timings.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "4172116385ede7abcfbbcc6eb6b7133385695001", "tree": "5b1102aea3d951a057d4a8420761b78dd0fd8758", "parents": [ "45324a2648bcfa96adeae71ae992da931eed79f6" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Thu Apr 26 20:10:46 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:06 2012 +0300" }, "message": "OMAPDSS: Apply manager timings instead of direct DISPC writes\n\nReplace the function dispc_mgr_set_timings() with dss_mgr_set_timings() in the\ninterface drivers. The latter function ensures that the timing related DISPC\nregisters are configured according to the shadow register programming model.\n\nRemove the call to dispc_mgr_go() in dpi_set_timings() as the manager\u0027s go bit\nis set by dss_mgr_set_timings().\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "45324a2648bcfa96adeae71ae992da931eed79f6", "tree": "267fbbeb378426dede1dad5b5e64cdd58996d2ed", "parents": [ "408d9dbbc4eebd8c4f2cd5d487f1b9c3c12c2c59" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Thu Apr 26 19:31:22 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:44:06 2012 +0300" }, "message": "OMAPDSS: APPLY: Add manager timings as extra_info in private data\n\nDISPC manager size and DISPC manager blanking parameters(for LCD managers)\nfollow the shadow register programming model. Currently, they are programmed\ndirectly by the interface drivers.\n\nTo configure manager timings using APPLY, there is a need to introduce extra\ninfo flags for managers, similar to what is done for overlays. This is needed\nbecause timings aren\u0027t a part of overlay_manager_info struct configured by a\nuser of DSS, they are configured internally by the interface or panel drivers.\n\nAdd dirty and shadow_dirty extra_info flags for managers, update these flags\nat the appropriate places. Rewrite the function extra_info_update_ongoing()\nslightly as checking for manager\u0027s extra_info flags can simplify the code a bit.\n\nCreate function dss_mgr_set_timings() which applies the new manager timings to\nextra_info.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\n" }, { "commit": "408d9dbbc4eebd8c4f2cd5d487f1b9c3c12c2c59", "tree": "7f640d074dd5df13fc366cb1f49b36f301bb5c84", "parents": [ "a2e5d82758a82b4848f00b1f28f8f71920e1b076" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon May 07 16:51:36 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:43:17 2012 +0300" }, "message": "OMAPDSS: DISPC: Remove Fake VSYNC support\n\nFake VSYNC support is a hack and has some bugs in it. It isn\u0027t used by any user\nof DSS. Remove Fake VSYNC support. For DSI command mode and RFBI panels, a user\nof DSS should wait for the completion of a frame by using the panel driver\u0027s\nsync op.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "a2e5d82758a82b4848f00b1f28f8f71920e1b076", "tree": "0b89a775f46fdf89bbc10d48e36f7e06e6106b0e", "parents": [ "9b9c457b43a0bfe227c5016606a2543e2ac4424e" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon May 07 16:51:35 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:43:11 2012 +0300" }, "message": "OMAPDSS: Fix DSI_FCLK clock source selection\n\nThe wrong bit field was being updated in DSS_CTRL when trying to configure the\nclock source of DSI2 functional clock. Use the correct bit field based on the\ndsi module number.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "9b9c457b43a0bfe227c5016606a2543e2ac4424e", "tree": "52dc3977a8c6f7dc3625e4f3025df6cd85a2bf3f", "parents": [ "3c7de24771cbc4546728875dc77016bbfc0195df" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon May 07 18:50:28 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:43:05 2012 +0300" }, "message": "OMAPDSS: HDMI: define and dump CORE registers in correct order\n\nThe HDMI core register offset macros aren\u0027t defined in ascending order of their\nvalues, some of the offset macros are also redefined. The same issues occur when\nthese core registers are dumped.\n\nClean up the ordering of HDMI core registers and remove repeated registers in\nthe definition in ti_hdmi_4xxx_ip.h and in ti_hdmi_4xxx_core_dump().\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "3c7de24771cbc4546728875dc77016bbfc0195df", "tree": "6584fa596bdf2fc6e481ac53ee579357407f438d", "parents": [ "8b53d9911982794b3f6d5513741495c3f70962cd" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon May 07 18:50:27 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 13:42:58 2012 +0300" }, "message": "OMAPDSS: HDMI: Fix ti_hdmi_4xxx_core_dump\n\nThe function ti_hdmi_4xxx_core_dump has some bugs, the following mention the\nbugs and the solutions:\n\n- The macros DUMPCORE and DUMPCOREAV in ti_hdmi_4xxx_core_dump() use\n hdmi_pll_base() for the offsets needed to calculate register addresses, use\n functions hdmi_core_sys_base() amd hdmi_av_base() to calculate the correct\n offsets for CORE_SYS and CORE_AV registers.\n\n- Many of the CORE_AV registers use the DUMPCORE macro, and hence the register\n addresses are calculated incorrectly. Rename the current DUMPCOREAV macro as\n DUMPCOREAV2 as it takes 2 arguments to dump indexed CORE_AV registers, create\n a new macro called DUMPCOREAV which is now used for dumping non-indexed\n CORE_AV registers.\n\nThanks to Ancy Tom \u003cancytom@gmail.com\u003e for pointing out the issues.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "e4a9e94cc58ed6e4efb02b80be3a9bf57f448d07", "tree": "c4b33461be5176e7c5ae7cc1590501b889f13ad1", "parents": [ "3acc797c1db2eb873b13a07f21fe9572af4b78ee" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed Mar 28 15:58:56 2012 +0300" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 10:53:05 2012 +0300" }, "message": "OMAPDSS: DSI: implement generic DSI pin config\n\nIn preparation for device tree, this patch changes how the DSI pins are\nconfigured. The current configuration method is only doable with board\nfiles and the configuration data is OMAP specific.\n\nThis patch moves the configuration data to the panel\u0027s platform data,\nand the data can easily be given via DT in the future. The configuration\ndata format is also changed to a generic one which should be suitable\nfor all platforms.\n\nThe new format is an array of pin numbers, where the array items start\nfrom clock + and -, then data1 + and -, and so on. For example:\n\n{\n\t0,\t// pin num for clock lane +\n\t1,\t// pin num for clock lane -\n\t2,\t// pin num for data1 lane +\n\t3,\t// pin num for data1 lane -\n\t...\n}\n\nThe pin numbers are translated by the DSI driver and used to configure\nthe hardware appropriately.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nAcked-by: Tony Lindgren \u003ctony@atomide.com\u003e\n" }, { "commit": "3acc797c1db2eb873b13a07f21fe9572af4b78ee", "tree": "6b28c959da58c5ac7a0da4080688d9b1220fa2cb", "parents": [ "dac8eb5f1d29eb4cf44305239da7e7a477e48a90" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Feb 20 12:18:52 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 10:53:05 2012 +0300" }, "message": "OMAPDSS: Taal: move reset gpio handling to taal driver\n\nThe reset GPIO for Taal panel driver is currently requested in the\n4430sdp board file. This patch moves the gpio request/free into the Taal\ndriver, where it should be.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nAcked-by: Tony Lindgren \u003ctony@atomide.com\u003e\n" }, { "commit": "dac8eb5f1d29eb4cf44305239da7e7a477e48a90", "tree": "96f5e5e5bf832d68b71e5343aece056f466d69a2", "parents": [ "2e6f2ee7ace43d7c8d0e9abf9b0767ab99d3f2aa" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Dec 22 11:12:13 2011 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 10:51:05 2012 +0300" }, "message": "OMAPDSS: TFP410: rename dvi files to tfp410\n\nNow that the tfp410 driver has been renamed in the code, this patch\nfinishes the renaming by renaming the files.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nAcked-by: Tony Lindgren \u003ctony@atomide.com\u003e\n" }, { "commit": "2e6f2ee7ace43d7c8d0e9abf9b0767ab99d3f2aa", "tree": "e3a3b3a56f0adb45e9e4e0f40c69245386622275", "parents": [ "e813a55eb9c9bc6c8039fb16332cf43402125b30" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Mar 05 14:29:28 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 10:51:05 2012 +0300" }, "message": "OMAPDSS: TFP410: rename dvi -\u003e tfp410\n\nThe driver for the TFP410 DPI-to-DVI chip was named quite badly as \"DVI\npanel driver\". This patch renames the code to use tfp410 name for the\ndriver.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nAcked-by: Tony Lindgren \u003ctony@atomide.com\u003e\n" }, { "commit": "e813a55eb9c9bc6c8039fb16332cf43402125b30", "tree": "18b4450d21ba7755587d442865142f641fee3f14", "parents": [ "2da35193dc81b574001a47347f41c4922b1266d3" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Fri Feb 17 13:30:27 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 10:51:04 2012 +0300" }, "message": "OMAP: board-files: remove custom PD GPIO handling for DVI output\n\nNow that the panel-dvi driver handles the PD (power-down) GPIO, we can\nremove the custom PD handling from the board files.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nAcked-by: Tony Lindgren \u003ctony@atomide.com\u003e\n" }, { "commit": "2da35193dc81b574001a47347f41c4922b1266d3", "tree": "b9816c8b8fba317eae9bfdb6ff9fb31387a4e052", "parents": [ "66f75a5d028beaf67c931435fdc3e7823125730c" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Dec 22 10:37:33 2011 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed May 09 10:51:04 2012 +0300" }, "message": "OMAPDSS: panel-dvi: add PD gpio handling\n\nThe driver for the TFP410 chip should handle the power-down signal of\nthe chip, instead of the current way of handling it in the board files.\n\nThis patch adds power_down_gpio into the device\u0027s platform data, and\nadds the necessary code in the driver to request and handle the GPIO.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "8b53d9911982794b3f6d5513741495c3f70962cd", "tree": "2932bf95e14f4d890704983918d19e4a482593f7", "parents": [ "7faa92339bbb1e6b9a80983b206642517327eb75" ], "author": { "name": "Chandrabhanu Mahapatra", "email": "cmahapatra@ti.com", "time": "Mon Apr 23 12:16:50 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu May 03 16:13:01 2012 +0300" }, "message": "OMAPDSS: DISPC: Correct DISPC functional clock usage\n\nDISPC_FCLK is incorrectly used as functional clock of DISPC in scaling\ncalculations. So, DISPC_CORE_CLK replaces as functional clock of DISPC.\nDISPC_CORE_CLK is derived from DISPC_FCLK divided by an independent DISPC\ndivisor LCD.\n\nSigned-off-by: Chandrabhanu Mahapatra \u003ccmahapatra@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "7faa92339bbb1e6b9a80983b206642517327eb75", "tree": "90c07ee4961a574606d0e1b86201546c6220ea1f", "parents": [ "aed74b55004e1d6c7d445543ceed1d2f110969a1" ], "author": { "name": "Chandrabhanu Mahapatra", "email": "cmahapatra@ti.com", "time": "Mon Apr 02 20:43:17 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu May 03 16:12:57 2012 +0300" }, "message": "OMAPDSS: DISPC: Handle synclost errors in OMAP3\n\nIn OMAP3 DISPC video overlays suffer from some undocumented horizontal position\nand timing related limitations leading to SYNCLOST errors. Whenever the image\nwindow is moved towards the right of the screen SYNCLOST errors become\nfrequent. Checks have been implemented to see that DISPC driver rejects\nconfiguration exceeding above limitations.\n\nThis code was successfully tested on OMAP3. This code is written based on code\nwritten by Ville Syrjälä \u003cville.syrjala@nokia.com\u003e in Linux OMAP kernel. Ville\nSyrjälä \u003cville.syrjala@nokia.com\u003e had added checks for video overlay horizontal\ntiming and DISPC horizontal blanking length limitations.\n\nSigned-off-by: Chandrabhanu Mahapatra \u003ccmahapatra@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "aed74b55004e1d6c7d445543ceed1d2f110969a1", "tree": "3fca3598efc38cf825505011f55ee0b791d84f14", "parents": [ "3dd606e435b36f8461d4c89227a41ac6976969c3" ], "author": { "name": "Chandrabhanu Mahapatra", "email": "cmahapatra@ti.com", "time": "Mon Apr 02 20:43:16 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu May 03 16:12:48 2012 +0300" }, "message": "OMAPDSS: DISPC: Enable predecimation\n\nIn OMAP3 and OMAP4, the DISPC Scaler can downscale an image up to 4 times, and\nup to 2 times in OMAP2. However, with predecimation, the image can be reduced\nto 16 times by fetching only the necessary pixels in memory. Then this\npredecimated image can be downscaled further by the DISPC scaler.\n\nThe pipeline is configured to use a burst of size 8 * 128 bits which consists\nof 8 mini bursts of 16 bytes each. So, horizontal predecimation more than 16\ncan lead to complete discarding of such mini bursts. L3 interconnect may\nhandover the bus to some other initiator and inturn delay the fetching of\npixels leading to underflows. So, maximum predecimation limit is fixed at 16.\n\nBased on the downscaling required, a prior calculation of predecimation values\nfor width and height of an image is done. Since, Predecimation reduces quality\nof an image higher priorty is given to DISPC Scaler for downscaling.\n\nThis code was successfully tested on OMAP2, OMAP3 and OMAP4. Horizontal and\nvertical predecimation worked fine except for some synclost errors due to\nundocumented errata in OMAP3 which are fixed later and skewed images were seen\non OMAP2 and OMAP3 during horizontal predecimation which will be addressed in\nthe future patches.\n\nThis code is based on code written by Lajos Molnar \u003clajos@ti.com\u003e who had added\npredecimation support for NV12/YUV/rotated/SDMA buffers.\n\nSigned-off-by: Chandrabhanu Mahapatra \u003ccmahapatra@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "3dd606e435b36f8461d4c89227a41ac6976969c3", "tree": "97b7d182c1df8aa91e8d67f6bb57a55443d1137f", "parents": [ "8f366162d213f21d9d77560429085033278830c5" ], "author": { "name": "Jan Weitzel", "email": "j.weitzel@phytec.de", "time": "Fri Apr 20 11:41:22 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:11 2012 +0300" }, "message": "ARM: OMAP2+ Add Primview displays to panel-generic\n\nAdd displays to panel-generic-dpi.c\nPrime View PD050VL1 (640 x 480)\nPrime View PD104SLF (800 x 600)\nPrime View PM070WL4 (800 x 480)\n\nSigned-off-by: Jan Weitzel \u003cj.weitzel@phytec.de\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "8f366162d213f21d9d77560429085033278830c5", "tree": "e45918b90ba174e58f3ea609e35e7aa34ec67e31", "parents": [ "c51d921a0cd83ecc768de7176bc7b7c2d76db278" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon Apr 16 12:53:44 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:10 2012 +0300" }, "message": "OMAPDSS: DISPC: Clean up manager timing/size functions\n\nClean up the DISPC manager timings related function by:\n\n- Create a common function to set size for LCD and TV.\n- Create a common function to check timings for LCD and TV.\n- Add dss params to get the range of manager size.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "c51d921a0cd83ecc768de7176bc7b7c2d76db278", "tree": "e2d121eb789e626c56e5f4502e0f094ec289ace7", "parents": [ "e5c09e06a9ef882e770aa1fa1bcfd5e5c90c6519" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon Apr 16 12:53:43 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:10 2012 +0300" }, "message": "OMAPDSS: DISPC: Use a common function to set manager timings\n\nCurrently, a LCD manager\u0027s timings is set by dispc_mgr_set_lcd_timings() and TV\nmanager\u0027s timings is set by dispc_set_digit_size(). Use a common function called\ndispc_mgr_set_timings() which sets timings for both type of managers.\n\nWe finally want the interface drivers to use an overlay manager function to\nconfigure it\u0027s timings, having a common DISPC function would make things\ncleaner.\n\nFor LCD managers, dispc_mgr_set_timings() sets LCD size and blanking values, for\nTV manager, it sets only the TV size since blanking values don\u0027t exist for TV.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "e5c09e06a9ef882e770aa1fa1bcfd5e5c90c6519", "tree": "46d6f24789846ebd6ae9cb07a00bd8b4335148c4", "parents": [ "693cc078dc8b89d20a0d7d32f1a32d03a4fc1e7f" ], "author": { "name": "Archit Taneja", "email": "archit@ti.com", "time": "Mon Apr 16 12:53:42 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:09 2012 +0300" }, "message": "OMAPDSS: DISPC/RFBI: Use dispc_mgr_set_lcd_timings() for setting lcd size\n\nThe RFBI driver uses dispc_mgr_set_lcd_size() to set the width and height of\nthe LCD manager. Replace this to use dispc_mgr_set_lcd_timings(), pass dummy\nblanking parameters like done in the DSI driver.\n\nThis prevents the need to export dispc_mgr_set_lcd_size(), and use a common\nfunction to set lcd timings.\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "e97374c0fe770ea9fde0a3061c552dc674ad3c5a", "tree": "e4f438eda281ed416961767a18592e8f37797487", "parents": [ "697bacbaea2aab955b4afa6f6c0c799e44f426fa" ], "author": { "name": "Thomas Weber", "email": "weber@corscience.de", "time": "Fri Feb 17 13:41:59 2012 +0100" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:08 2012 +0300" }, "message": "OMAPDSS: Add EDT ET0500G0DH6 display support\n\nThe EDT ET0500G0DH6 is a 5 inch display. It is\ntested on an OMAP3 board.\n\nSigned-off-by: Thomas Weber \u003cweber@corscience.de\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "697bacbaea2aab955b4afa6f6c0c799e44f426fa", "tree": "b735ae1764238652e6b28bd53c745de3c90868c5", "parents": [ "31e8dfe14871f08d335e6884cb2b96f2679c1ebe" ], "author": { "name": "Thomas Weber", "email": "weber@corscience.de", "time": "Fri Feb 17 13:41:58 2012 +0100" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:08 2012 +0300" }, "message": "OMAPDSS: Add Mitsubishi AA084SB01 display support\n\nThis patch adds support for the Mitsubishi display\nAA084SB01. This is a 7 inch LVDS display. It is tested with\nan OMAP3 board.\n\nSigned-off-by: Thomas Weber \u003cweber@corscience.de\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "31e8dfe14871f08d335e6884cb2b96f2679c1ebe", "tree": "6debaf9dcb5f8897593f0f18b0deff4fe1aaca7d", "parents": [ "4b6430fc98cfe051eab69f4696a608bba14ebd6c" ], "author": { "name": "Grazvydas Ignotas", "email": "notasas@gmail.com", "time": "Thu Mar 15 20:00:24 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:07 2012 +0300" }, "message": "OMAPDSS: TPO-TD03MTEA1: add set/check timing functions\n\nOn pandora we use .set_timings to alter refresh rate,\nso add .check_timings/.set_timings functions.\n\nSigned-off-by: Grazvydas Ignotas \u003cnotasas@gmail.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "4b6430fc98cfe051eab69f4696a608bba14ebd6c", "tree": "3af96f2ef29fba9c7942228f6b29971044edfa7a", "parents": [ "f3fb3bbc7f71d573be40213af4a90751a81b2379" ], "author": { "name": "Grazvydas Ignotas", "email": "notasas@gmail.com", "time": "Thu Mar 15 20:00:23 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:07 2012 +0300" }, "message": "OMAPDSS: provide default get_timings function for panels\n\nWith this we can eliminate some duplicate code in panel drivers.\nAlso lgphilips-lb035q02, nec-nl8048hl11-01b, picodlp and\ntpo-td043mtea1 gain support of reading timings over sysfs.\n\nSigned-off-by: Grazvydas Ignotas \u003cnotasas@gmail.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "f3fb3bbc7f71d573be40213af4a90751a81b2379", "tree": "da7047c8d3490f86dc20a6efac2d97e0cd22788e", "parents": [ "2c83af49ca83ebf521f9360baaca3718bb5d303e" ], "author": { "name": "Grazvydas Ignotas", "email": "notasas@gmail.com", "time": "Fri Mar 09 02:42:49 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:06 2012 +0300" }, "message": "OMAPDSS: OMAPFB: check for matching memory size early\n\nIf the size of memory region that is being set up is the same as before,\nwe don\u0027t have to do memory and layer busy checks.\n\nSigned-off-by: Grazvydas Ignotas \u003cnotasas@gmail.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "2c83af49ca83ebf521f9360baaca3718bb5d303e", "tree": "11e1d36e5a76a8b1dc26a3d312b36266808eec82", "parents": [ "956107eadc27ffbcdf80357e16138f9595f0f4fd" ], "author": { "name": "Mark Brown", "email": "broonie@opensource.wolfsonmicro.com", "time": "Mon Mar 19 15:02:32 2012 +0000" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:06 2012 +0300" }, "message": "OMAPDSS: TPO-TD03MTEA1: Correct comment for power on delay\n\nSince any power on stabilisation delay for the supply itself should be\ntaken care of transparently by the regulator API when the regulator is\nenabled the additional delay that the TPO-TD03MTEA1 driver adds after\nthat returned should be due to the requirements of the device itself\nrather than the supply (the delay is also suspicously long for one for\na regulator to ramp). Correct the comment to avoid misleading people\ntaking this code as a reference.\n\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nAcked-by: Grazvydas Ignotas \u003cnotasas@gmail.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "956107eadc27ffbcdf80357e16138f9595f0f4fd", "tree": "538f8791d014419cee70c8a6489215970374d2ff", "parents": [ "ec8741078d0a644d68827c8a347ac6be153622b5" ], "author": { "name": "Mark Brown", "email": "broonie@opensource.wolfsonmicro.com", "time": "Mon Mar 19 15:02:31 2012 +0000" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:05 2012 +0300" }, "message": "OMAPDSS: TPO-TD03MTEA1: Check for errors from regulator_enable()\n\nIt is possible for regulator_enable() to fail and if it does fail that\u0027s\ngenerally a bad sign for anything we try to do with the hardware afterwards\nso check for and immediately return an error if regulator_enable() fails.\n\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nAcked-by: Grazvydas Ignotas \u003cnotasas@gmail.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "ec8741078d0a644d68827c8a347ac6be153622b5", "tree": "ecc4429b24c977502a319a7e89214c97dc14e87a", "parents": [ "9c3d5eb71b1fdcdef434a46444d931ada6938446" ], "author": { "name": "Mark Brown", "email": "broonie@opensource.wolfsonmicro.com", "time": "Mon Mar 19 14:56:39 2012 +0000" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:05 2012 +0300" }, "message": "OMAPDSS: VENC: Check for errors from regulator_enable()\n\nIt is possible for regulator_enable() to fail and if it does fail that\u0027s\ngenerally a bad sign for anything we try to do with the hardware afterwards\nso check for and immediately return an error if regulator_enable() fails.\n\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "9c3d5eb71b1fdcdef434a46444d931ada6938446", "tree": "4ed6c46f7e1902383ddb3637b018aaa2e4d01d4a", "parents": [ "b6e695abe710ee1ae248463d325169efac487e17" ], "author": { "name": "Mark Brown", "email": "broonie@opensource.wolfsonmicro.com", "time": "Mon Mar 19 14:50:46 2012 +0000" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:04 2012 +0300" }, "message": "OMAP: DSS2: Remove suspicous and unused TAAL regulator API usage\n\nThe TAAL driver contains some regulator support which is currently unused\n(the code is there but the one panel supported by the driver doesn\u0027t have\nany regulators provided). This code mostly looks like an open coded\nversion of the regulator core bulk API.\n\nThe only additional feature is that a voltage range can be set once when\nthe device is opened, though this is never varied at runtime. The general\nexpectation is that if the device is not actively managing the voltage of\nthe device (eg, doing DVFS) then any configuration will be done using the\nconstraints rather than by drivers, saving them code and ensuring that\nthey work well with systems where the voltage is not configurable.\n\nIf systems are added needing regulator support this can be added back in,\nthough it should be based on core features rather than open coding things.\n\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "b6e695abe710ee1ae248463d325169efac487e17", "tree": "9baf03162d4832be0bb73581844d69939397300c", "parents": [ "a8081d317978416197295df22fc2ea71e4812f50" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Mar 15 15:22:58 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:04 2012 +0300" }, "message": "OMAPDSS: DSI: remove option to use pck for DSI PLL clkin\n\nFor some OMAP versions the TRM says that the pixel clock from DISPC can\nbe used as an input clock for DSI PLL, instead of the default, which is\nsysclk. For some OMAP versions the bits affecting this are marked as\nreserved. This feature has never been tested, so it\u0027s unknown if the HW\neven works, and has never been used.\n\nTo clean things up, this patch removes the functionality. This should\nnot affect any board.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "a8081d317978416197295df22fc2ea71e4812f50", "tree": "c4156f1a48fd63f6abc6209cc98d80523e36a843", "parents": [ "62c1dcfc7451a8e42104776705a317e06a8e24a3" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Mar 08 12:52:38 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Apr 23 10:48:03 2012 +0300" }, "message": "OMAPDSS: Ensure OPP100 when DSS is operational\n\nMost of the DSS clocks have restrictions on their frequency based on the\nOPP in use. For example, maximum frequency for a clock may be 180MHz in\nOPP100, but 90MHz in OPP50. This means that when a high enough pixel\nclock or function clock is required, we need to use OPP100.\n\nHowever, there\u0027s currently no way in the PM framework to make that kind\nof request. The closest we get is to ask for very high bus throughput\nfrom the PM framework, which should effectively force OPP100.\n\nThis patch is a simple version for handling the problem. Instead of\nasking for OPP100 only when needed, this patch asks for OPP100 whenever\nDSS is active. This obviously is not an optimal solution for cases with\nsmall displays where OPP50 would work just fine. However, a proper\nsolution is a complex one, and this patch is a short term solution for\nthe problem.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nCc: Paul Walmsley \u003cpaul@pwsan.com\u003e\nAcked-by: Kevin Hilman \u003ckhilman@ti.com\u003e\n" }, { "commit": "820d41cf0cd0e94a5661e093821e2e5c6b36a9d8", "tree": "4d03046048dc52a8fa539c7e7b846e02738d8ca5", "parents": [ "6268b325c3066234e7bddb99d2b98bcedb0c0033", "88b48684fe2d4f6207223423227c80d5408bccaf" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Mar 29 18:02:10 2012 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Mar 29 18:02:10 2012 -0700" }, "message": "Merge tag \u0027cleanup2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc\n\nPull \"ARM: cleanups of io includes\" from Olof Johansson:\n \"Rob Herring has done a sweeping change cleaning up all of the\n mach/io.h includes, moving some of the oft-repeated macros to a common\n location and removing a bunch of boiler plate. This is another step\n closer to a common zImage for multiple platforms.\"\n\nFix up various fairly trivial conflicts (\u003cmach/io.h\u003e removal vs changes\naround it, tegra localtimer.o is *still* gone, yadda-yadda).\n\n* tag \u0027cleanup2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (29 commits)\n ARM: tegra: Include assembler.h in sleep.S to fix build break\n ARM: pxa: use common IOMEM definition\n ARM: dma-mapping: convert ARCH_HAS_DMA_SET_COHERENT_MASK to kconfig symbol\n ARM: __io abuse cleanup\n ARM: create a common IOMEM definition\n ARM: iop13xx: fix missing declaration of iop13xx_init_early\n ARM: fix ioremap/iounmap for !CONFIG_MMU\n ARM: kill off __mem_pci\n ARM: remove bunch of now unused mach/io.h files\n ARM: make mach/io.h include optional\n ARM: clps711x: remove unneeded include of mach/io.h\n ARM: dove: add explicit include of dove.h to addr-map.c\n ARM: at91: add explicit include of hardware.h to uncompressor\n ARM: ep93xx: clean-up mach/io.h\n ARM: tegra: clean-up mach/io.h\n ARM: orion5x: clean-up mach/io.h\n ARM: davinci: remove unneeded mach/io.h include\n [media] davinci: remove includes of mach/io.h\n ARM: OMAP: Remove remaining includes for mach/io.h\n ARM: msm: clean-up mach/io.h\n ...\n" }, { "commit": "d61b7a572b292e2be409e13b4b3adf475f18fb29", "tree": "e9d30390860147136c05e66abf1edda1bc5b0562", "parents": [ "18d9946bc7e2252fe3c0f2f609ac383c627edefd", "f4e2467bad53023589cbff18dd1ab6e0aa3f004c" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Mar 27 16:03:32 2012 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Mar 27 16:03:32 2012 -0700" }, "message": "Merge tag \u0027cleanup\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc\n\nPull \"ARM: global cleanups\" from Arnd Bergmann:\n \"Quite a bit of code gets removed, and some stuff moved around, mostly\n the old samsung s3c24xx stuff. There should be no functional changes\n in this series otherwise. Some cleanups have dependencies on other\n arm-soc branches and will be sent in the second round.\n\n Signed-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\"\n\nFixed up trivial conflicts mainly due to #include\u0027s being changes on\nboth sides.\n\n* tag \u0027cleanup\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (121 commits)\n ep93xx: Remove unnecessary includes of ep93xx-regs.h\n ep93xx: Move EP93XX_SYSCON defines to SoC private header\n ep93xx: Move crunch code to mach-ep93xx directory\n ep93xx: Make syscon access functions private to SoC\n ep93xx: Configure GPIO ports in core code\n ep93xx: Move peripheral defines to local SoC header\n ep93xx: Convert the watchdog driver into a platform device.\n ep93xx: Use ioremap for backlight driver\n ep93xx: Move GPIO defines to gpio-ep93xx.h\n ep93xx: Don\u0027t use system controller defines in audio drivers\n ep93xx: Move PHYS_BASE defines to local SoC header file\n ARM: EXYNOS: Add clock register addresses for EXYNOS4X12 bus devfreq driver\n ARM: EXYNOS: add clock registers for exynos4x12-cpufreq\n PM / devfreq: update the name of EXYNOS clock registers that were omitted\n PM / devfreq: update the name of EXYNOS clock register\n ARM: EXYNOS: change the prefix S5P_ to EXYNOS4_ for clock\n ARM: EXYNOS: use static declaration on regarding clock\n ARM: EXYNOS: replace clock.c for other new EXYNOS SoCs\n ARM: OMAP2+: Fix build error after merge\n ARM: S3C24XX: remove call to s3c24xx_setup_clocks\n ...\n" }, { "commit": "dc7e57fa80ec5231e33ee2f51f6211c9fb84b9e3", "tree": "e9c67d2de2177685281f3e09a075bca0d6ef223d", "parents": [ "b622f1b538f91ab320838656fc0b31d11a67c5fc" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Mon Mar 19 15:05:02 2012 +0200" }, "committer": { "name": "Florian Tobias Schandinat", "email": "FlorianSchandinat@gmx.de", "time": "Wed Mar 21 12:55:15 2012 +0000" }, "message": "OMAPDSS: register dss drivers in module init\n\nWe do the dss driver registration in a rather strange way: we have the\nhigher level omapdss driver, and we use that driver\u0027s probe function to\nregister the drivers for the rest of the dss devices.\n\nThere doesn\u0027t seem to be any reason for that, and additionally the\nsoon-to-be-merged patch \"ARM: OMAP: omap_device: remove\nomap_device_parent\" will break omapdss initialization with the current\nregistration model.\n\nThis patch changes the registration for all drivers to happen at the\nsame place, in the init of the module.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nSigned-off-by: Florian Tobias Schandinat \u003cFlorianSchandinat@gmx.de\u003e\n" }, { "commit": "e9fe8a714e450b26f76eaf8832f5b9fe24d00e79", "tree": "78d0045cfdede7ad7e42181bde96978fdc792e06", "parents": [ "f413070e3f0bccb40ca939b90699347daf815607", "df01d53068bdf31609aafd9a857901a1f16dfa52" ], "author": { "name": "Florian Tobias Schandinat", "email": "FlorianSchandinat@gmx.de", "time": "Tue Mar 20 08:49:51 2012 +0000" }, "committer": { "name": "Florian Tobias Schandinat", "email": "FlorianSchandinat@gmx.de", "time": "Tue Mar 20 08:49:51 2012 +0000" }, "message": "Merge branch \u0027for-3.4\u0027 of git://gitorious.org/linux-omap-dss2/linux into fbdev-next\n" }, { "commit": "e3643b77de143c5548ec93abd8aa68f4123295ea", "tree": "41981957bc93e8211fe55cd04b7cac47e74bc770", "parents": [ "86ca5b6fef2bf1aa77a62f29d844400e4fed8dde", "44b2cef5ae6da48523fa634230ca66107110a7dd" ], "author": { "name": "Olof Johansson", "email": "olof@lixom.net", "time": "Tue Mar 13 16:08:06 2012 -0700" }, "committer": { "name": "Olof Johansson", "email": "olof@lixom.net", "time": "Tue Mar 13 16:08:06 2012 -0700" }, "message": "Merge branch \u0027next/cleanup-exynos-clock\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung into next/cleanup\n\n* \u0027next/cleanup-exynos-clock\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung:\n ARM: EXYNOS: Add clock register addresses for EXYNOS4X12 bus devfreq driver\n ARM: EXYNOS: add clock registers for exynos4x12-cpufreq\n PM / devfreq: update the name of EXYNOS clock registers that were omitted\n PM / devfreq: update the name of EXYNOS clock register\n ARM: EXYNOS: change the prefix S5P_ to EXYNOS4_ for clock\n ARM: EXYNOS: use static declaration on regarding clock\n ARM: EXYNOS: replace clock.c for other new EXYNOS SoCs\n (includes an update to v3.3-rc6)\n" }, { "commit": "df01d53068bdf31609aafd9a857901a1f16dfa52", "tree": "abd6e418faf42e0c83c4e95b2e40121578a6f22d", "parents": [ "001b7f3ecd164ba748e45f698714b3a574a11438" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Wed Mar 07 10:28:48 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Mar 13 15:46:21 2012 +0200" }, "message": "OMAPDSS: APPLY: fix clearing shadow dirty flag with manual update\n\nCurrently the shadow-dirty flags for manual update displays is cleared\nin the apply_irq_handler when an update has finished. This is not\ncorrect, as the shadow registers are taken into use (i.e. after that\nthey are not dirty) when the update is started.\n\nMove the mgr_clear_shadow_dirty() call from apply_irq_handler to\ndss_mgr_start_update() to fix this.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "6076c644126e5424f32aec6c8f2bdc19bbcc8859", "tree": "014d9da4c98f7b3d81cc2d6e669a2a5e4c8d1709", "parents": [ "68a7f1f79f004e7a2a53352c82319d567ebb1da1" ], "author": { "name": "Tony Lindgren", "email": "tony@atomide.com", "time": "Thu Mar 01 08:35:01 2012 -0600" }, "committer": { "name": "Rob Herring", "email": "rob.herring@calxeda.com", "time": "Tue Mar 06 21:34:38 2012 -0600" }, "message": "ARM: OMAP: Remove remaining includes for mach/io.h\n\nThese are no longer needed with the recent iomap.h\nchanges.\n\nReported-by: Rob Herring \u003crobherring2@gmail.com\u003e\nSigned-off-by: Tony Lindgren \u003ctony@atomide.com\u003e\nCc: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\nCc: Florian Tobias Schandinat \u003cFlorianSchandinat@gmx.de\u003e\n" }, { "commit": "4614679c9d3b77e87b390b6afe8a8dfc980f4387", "tree": "4d329525727de808f6b4dbe25d83451acd9aff5a", "parents": [ "21e56f79abad987555351c73569fc8358636b0fa" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Thu Feb 23 12:21:09 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Mar 06 14:08:39 2012 +0200" }, "message": "OMAPDSS: APPLY: print warning if wait_pending_extra_info_updates fails\n\nwait_pending_extra_info_updates() currently does a hacky second check\nfor extra_info_update_ongoing() at the end of the function to show a\nwarning if extra_info update is still ongoing. The call to\nextra_info_update_ongoing() should really be inside spinlock, but that\u0027s\na bit heavy just for verification.\n\nRather than that, check the return value of the\nwait_for_completion_timeout() and print an error if it has timeouted or\nreturned an error.\n\nEven better would be to return the error value and act on it in the\ncallers of wait_pending_extra_info_updates. However, it\u0027s not clear what\nthe callers should do in case of an error, as the error should only\nhappen if there\u0027s a bug in the driver or the HW. So we\u0027ll just print the\nwarning for now.\n\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "21e56f79abad987555351c73569fc8358636b0fa", "tree": "f96b97e7903c994b776182f4a3ab6eabc3a59208", "parents": [ "c0c1cfcb577d61ec55e209bc5f869d3d80a8f371" ], "author": { "name": "Lajos Molnar", "email": "lajos@ti.com", "time": "Wed Feb 22 12:23:16 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Mar 06 14:08:30 2012 +0200" }, "message": "OMAPDSS: MANAGER/APPLY: Add runtime_pm protection around wait_for_go/vsync functions\n\nIf DSS suspends within the functions dss_mgr_wait_for_go(),\ndss_mgr_wait_for_go_ovl() or dss_mgr_wait_for_vsync(). It may lose it\u0027s clock\nand lead to a register access failure.\n\nRequest runtime_pm around these functions.\n\n[archit@ti.com: Moved runtime_pm calls to wait_for_go/vsync functions rather\nthen calling them from omap_dispc_wait_for_irq_interruptible_timeout()]\n\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "c0c1cfcb577d61ec55e209bc5f869d3d80a8f371", "tree": "ae9fd192d44637645723430c777a12d21c6252f7", "parents": [ "08f3267e264e3cf05f0e79cf0f63a2162fd4bd1c" ], "author": { "name": "Lajos Molnar", "email": "lajos@ti.com", "time": "Tue Feb 21 19:36:31 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Mar 06 14:08:23 2012 +0200" }, "message": "OMAPDSS: DISPC: Fix FIR coefficients\n\ncoef3_M8 had an incorrect phase with 50% more intensity. This resulted in\nbanding on slightly down/upscaled images. Fixed a rounding error in coef5_M9.\n\nAlso removed ARRAY_LEN macro as ARRAY_SIZE is the standard linux one.\n\nSigned-off-by: Lajos Molnar \u003clajos@ti.com\u003e\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "08f3267e264e3cf05f0e79cf0f63a2162fd4bd1c", "tree": "0d3187627bc4eec5e5bc8375843678e9a72eedd4", "parents": [ "dd2116a35aa9a5a7b71e1d21f30aec8927434d19" ], "author": { "name": "Lajos Molnar", "email": "lajos@ti.com", "time": "Tue Feb 21 19:36:30 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Mar 06 14:08:16 2012 +0200" }, "message": "OMAPDSS: DISPC: Fix OMAP4 supported color formats\n\nAdd missing but supported color formats for GFX pipeline in dss features:\nRGBX16-4444, RGBA16-4444 and XRGB16-1555.\n\nIn dispc_ovl_set_color_mode():\n\n- Remove unsupported modes on GFX pipeline: YUV2 and UYVY. Replace these by\n missing modes supported by GFX pipelines: RGBX16-4444 and RGBA16-4444.\n\n- Fix swapped modes on VID pipelines: RGBX16-4444 and XRGB16-4444.\n\nSigned-off-by: Lajos Molnar \u003clajos@ti.com\u003e\nSigned-off-by: Archit Taneja \u003carchit@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "dd2116a35aa9a5a7b71e1d21f30aec8927434d19", "tree": "8ef49664dfd6eb538264abec6df545abd8d4738e", "parents": [ "0ba86d7edea1f9f2d9497c31200910263e8b4128" ], "author": { "name": "Mythri P K", "email": "mythripk@ti.com", "time": "Tue Feb 21 12:10:58 2012 +0530" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Mar 06 14:08:10 2012 +0200" }, "message": "OMAPDSS: HDMI: Add M2 divider while calculating clkout\n\nWhile calculating regm and regmf value add using M2 divider in\nthe equation.\nFormula for calculating:\nOutput clock on digital core domain:\n\tCLKOUT \u003d (M / (N+1))*CLKINP*(1/M2)\nInternal oscillator output clock on internal LDO domain:\n\tCLKDCOLDO \u003d (M / (N+1))*CLKINP\nThe current code when allows variable M2 values as input\nignores using M2 divider values in calculation of regm and regmf.\nso fix it by using M2 in calculation although the default value for\nM2 is 1.\n\nSigned-off-by: Mythri P K \u003cmythripk@ti.com\u003e\nSigned-off-by: Tomi Valkeinen \u003ctomi.valkeinen@ti.com\u003e\n" }, { "commit": "0ba86d7edea1f9f2d9497c31200910263e8b4128", "tree": "387f713e1afdd181e92699dcaa5fa3d45b30c75b", "parents": [ "973b659cbf2604b0b52829c224f6064d64118818", "192cfd58774b4d17b2fe8bdc77d89c2ef4e0591d" ], "author": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Mar 06 13:20:31 2012 +0200" }, "committer": { "name": "Tomi Valkeinen", "email": "tomi.valkeinen@ti.com", "time": "Tue Mar 06 13:20:31 2012 +0200" }, "message": "Merge commit \u0027v3.3-rc6\u0027\n\nMerge v3.3-rc6 to get the latest DSS and OMAP arch fixes.\n\nConflicts:\n\tarch/arm/mach-omap1/board-innovator.c\n\tdrivers/video/omap2/dss/apply.c\n" }, { "commit": "0d04c58aa41652f2adc369926bd944cbeb7ba5a2", "tree": "b4dab6b4f4a45c8ead14d36bc0872d5ca3c25cb3", "parents": [ "327e27681c27d3ed5ea470ec483904d1a318cb7f", "a3d0e4aecaa32001e02d5ce860d38f14095d06d2" ], "author": { "name": "Florian Tobias Schandinat", "email": "FlorianSchandinat@gmx.de", "time": "Wed Feb 29 22:42:55 2012 +0000" }, "committer": { "name": "Florian Tobias Schandinat", "email": "FlorianSchandinat@gmx.de", "time": "Wed Feb 29 22:42:55 2012 +0000" }, "message": "Merge branch \u0027fbdev-for-linus\u0027 into fbdev-next\n" } ], "next": "a3d0e4aecaa32001e02d5ce860d38f14095d06d2" }