[GIT PULL] OMAP DSS for v3.5

Started by Tomi Valkeinen on May 22, 2012 · 5 messages from 3 authors · Last reply Jun 5, 2012

open the first message on its own page

Message details and related content
Hi Florian,

Here are the OMAP DSS changes for 3.5.

I really tried this time to send the pull request early, but here I am
again, sending it when the merge window has already opened... A few
late-found bugs caused some unnecessary delays.

I'm using github this time instead of gitorious, as gitorious seems to
be down. This is my first pull request with a signed tag, I hope
everything is correct.

Note that there's a merge for small branch with omap board file changes
(e4a9e94cc58ed6e4efb02b80be3a9bf57f448d07) that is also pulled by Tony
for the linux-omap tree. This is meant to help avoid conflicts in the
board files.

 Tomi


The following changes since commit 66f75a5d028beaf67c931435fdc3e7823125730c:

  Linux 3.4-rc4 (2012-04-21 14:47:52 -0700)

are available in the git repository at:

  git://github.com/tomba/linux.git tags/omapdss-for-3.5

for you to fetch changes up to e92a5b28f71aea01b281f9c89d97a4bc5b24748f:

  OMAPDSS: HDMI: OMAP4: Update IRQ flags for the HPD IRQ request (2012-05-22 11:00:09 +0300)

----------------------------------------------------------------
Omapdss driver changes for 3.5 merge window.

Lots of normal development commits, but perhaps most notable changes are:

* HDMI rework to properly decouple the HDMI audio part from the HDMI video part.
* Restructure omapdss core driver so that it's possible to implement device
  tree support. This included changing how platform data is passed to the

174 more lines

Message details and related content
On 05/22/2012 10:09 AM, Tomi Valkeinen wrote:
Hi Florian,

Here are the OMAP DSS changes for 3.5.
Merged.


Thanks,

Florian Tobias Schandinat
I really tried this time to send the pull request early, but here I am
again, sending it when the merge window has already opened... A few
late-found bugs caused some unnecessary delays.

I'm using github this time instead of gitorious, as gitorious seems to
be down. This is my first pull request with a signed tag, I hope
everything is correct.

Note that there's a merge for small branch with omap board file changes
(e4a9e94cc58ed6e4efb02b80be3a9bf57f448d07) that is also pulled by Tony
for the linux-omap tree. This is meant to help avoid conflicts in the
board files.

 Tomi


The following changes since commit 66f75a5d028beaf67c931435fdc3e7823125730c:

  Linux 3.4-rc4 (2012-04-21 14:47:52 -0700)

are available in the git repository at:

  git://github.com/tomba/linux.git tags/omapdss-for-3.5

for you to fetch changes up to e92a5b28f71aea01b281f9c89d97a4bc5b24748f:

  OMAPDSS: HDMI: OMAP4: Update IRQ flags for the HPD IRQ request (2012-05-22 11:00:09 +0300)

----------------------------------------------------------------
Omapdss driver changes for 3.5 merge window.

Lots of normal development commits, but perhaps most notable changes are:

* HDMI rework to properly decouple the HDMI audio part from the HDMI video part.
* Restructure omapdss core driver so that it's possible to implement device
  tree support. This included changing how platform data is passed to the
  drivers, changing display device registration and improving the panel driver's
  ability to configure the underlying video output interface.
* Basic support for DSI packet interleaving

171 more quoted lines

Message details and related content
Hi Tomi,

On Tue, May 22, 2012 at 12:09 PM, Tomi Valkeinen [off-list ref] wrote:
Hi Florian,

Here are the OMAP DSS changes for 3.5.

I really tried this time to send the pull request early, but here I am
again, sending it when the merge window has already opened... A few
late-found bugs caused some unnecessary delays.

I'm using github this time instead of gitorious, as gitorious seems to
be down. This is my first pull request with a signed tag, I hope
everything is correct.

Note that there's a merge for small branch with omap board file changes
(e4a9e94cc58ed6e4efb02b80be3a9bf57f448d07) that is also pulled by Tony
for the linux-omap tree. This is meant to help avoid conflicts in the
board files.

 Tomi


The following changes since commit 66f75a5d028beaf67c931435fdc3e7823125730c:

 Linux 3.4-rc4 (2012-04-21 14:47:52 -0700)

are available in the git repository at:

 git://github.com/tomba/linux.git tags/omapdss-for-3.5

for you to fetch changes up to e92a5b28f71aea01b281f9c89d97a4bc5b24748f:

 OMAPDSS: HDMI: OMAP4: Update IRQ flags for the HPD IRQ request (2012-05-22 11:00:09 +0300)

----------------------------------------------------------------
Omapdss driver changes for 3.5 merge window.

Lots of normal development commits, but perhaps most notable changes are:

* HDMI rework to properly decouple the HDMI audio part from the HDMI video part.
* Restructure omapdss core driver so that it's possible to implement device
 tree support. This included changing how platform data is passed to the

4 more quoted lines

I am using a mainline kernel (3.5.0-rc1) with the patches below integrated.
I have an issue with suspend/resume on OMAP3 Beagleboard, where the
system hangs at resume time.

Here below is a log with the option no_console_suspend set and a few
added messages in case of null pointer in _od_resume_noirq.
It looks like there is no omap_device associated to the "omapdss_dpi" pdev.

What do you think? How to fix this?
Sorry I know there have been some discussions on the lists but I am
not aware of all the details in the devices creation for DSS.

/ # echo mem > /sys/power/state
[   23.262298] PM: Syncing filesystems ... done.
[   23.295501] Freezing user space processes ... (elapsed 0.02 seconds) done.
[   23.326507] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) don
e.
[   23.502197] PM: suspend of devices complete after 163.766 msecs
[   23.511932] PM: late suspend of devices complete after 3.418 msecs
[   23.524444] PM: noirq suspend of devices complete after 5.860 msecs
[   23.531249] Disabling non-boot CPUs ...
[   24.476562] Powerdomain (per_pwrdm) didn't enter target state 1
[   24.482818] Powerdomain (core_pwrdm) didn't enter target state 1
[   24.489166] Could not enter target state in pm_suspend
[   24.495147] *** _od_resume_noirq: od=NULL, dev=0xc78bcc08
[   24.500915] *** _od_resume_noirq: od=NULL, pdev=0xc78bcc00
[   24.506805] *** _od_resume_noirq: od=NULL, pdev->name:omapdss_dpi
[   24.513336] Unable to handle kernel NULL pointer dereference at virtual addre
ss 00000018
[   24.521942] pgd = c62f0000
[   24.524841] [00000018] *pgd†2c1831, *pte000000, *ppte000000
[   24.531524] Internal error: Oops: 17 [#1] SMP ARM
[   24.536529] Modules linked in:
[   24.539764] CPU: 0    Not tainted  (3.5.0-rc1-00010-g5041caa-dirty #131)
[   24.546844] PC is at _od_resume_noirq+0x1c/0xac
[   24.551635] LR is at _od_resume_noirq+0x94/0xac
...

Regards,

2 more lines

----------------------------------------------------------------
Archit Taneja (19):
     OMAPDSS: DISPC/RFBI: Use dispc_mgr_set_lcd_timings() for setting lcd size
     OMAPDSS: DISPC: Use a common function to set manager timings
     OMAPDSS: DISPC: Clean up manager timing/size functions
     OMAPDSS: HDMI: Fix ti_hdmi_4xxx_core_dump
     OMAPDSS: HDMI: define and dump CORE registers in correct order
     OMAPDSS: Fix DSI_FCLK clock source selection
     OMAPDSS: DISPC: Remove Fake VSYNC support
     OMAPDSS: APPLY: Add manager timings as extra_info in private data
     OMAPDSS: Apply manager timings instead of direct DISPC writes
     OMAPDSS: MANAGER: Create a function to check manager timings
     OMAPDSS: APPLY: Don't check manager settings if it is disabled
     OMAPDSS: APPLY: Remove display dependency from overlay and manager checks
     OMAPDSS: DPI/HDMI: Apply manager timings even if panel is disabled
     OMAPDSS: APPLY: Remove an unnecessary omap_dss_device pointer
     OMAPDSS: DISPC: Remove omap_dss_device pointer usage from dispc_mgr_pclk_rate()
     OMAPDSS: DISPC: Remove usage of dispc_mgr_get_device()
     OMAPDSS: DSI: Support command mode interleaving during video mode blanking periods
     OMAPDSS: VENC/DISPC: Delay dividing Y resolution for managers connected to VENC
     OMAPDSS: Apply VENC timings even if panel is disabled

Axel Castaneda Gonzalez (1):
     OMAPDSS: HDMI: Decouple wrapper enable/disable and audio start/stop

Chandrabhanu Mahapatra (5):
     OMAPDSS: DISPC: Enable predecimation
     OMAPDSS: DISPC: Handle synclost errors in OMAP3
     OMAPDSS: DISPC: Correct DISPC functional clock usage
     OMAPDSS: DISPC: Update Accumulator configuration for chroma plane
     OMAPDSS: DISPC: Support rotation through TILER

Grazvydas Ignotas (5):
     OMAPDSS: OMAPFB: check for matching memory size early
     OMAPDSS: provide default get_timings function for panels
     OMAPDSS: TPO-TD03MTEA1: add set/check timing functions
     OMAPDSS: VENC: allow switching venc output type at runtime
     OMAPDSS: OMAPFB: always allow to configure overlay

Jan Weitzel (1):

130 more quoted lines

Message details and related content
Hi Jean,

On Tue, 2012-06-05 at 14:17 +0200, Jean Pihet wrote:
Hi Tomi,
I am using a mainline kernel (3.5.0-rc1) with the patches below integrated.
I have an issue with suspend/resume on OMAP3 Beagleboard, where the
system hangs at resume time.

Here below is a log with the option no_console_suspend set and a few
added messages in case of null pointer in _od_resume_noirq.
It looks like there is no omap_device associated to the "omapdss_dpi" pdev.

What do you think? How to fix this?
Sorry I know there have been some discussions on the lists but I am
not aware of all the details in the devices creation for DSS.

/ # echo mem > /sys/power/state
[   23.262298] PM: Syncing filesystems ... done.
[   23.295501] Freezing user space processes ... (elapsed 0.02 seconds) done.
[   23.326507] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) don
e.
[   23.502197] PM: suspend of devices complete after 163.766 msecs
[   23.511932] PM: late suspend of devices complete after 3.418 msecs
[   23.524444] PM: noirq suspend of devices complete after 5.860 msecs
[   23.531249] Disabling non-boot CPUs ...
[   24.476562] Powerdomain (per_pwrdm) didn't enter target state 1
[   24.482818] Powerdomain (core_pwrdm) didn't enter target state 1
[   24.489166] Could not enter target state in pm_suspend
[   24.495147] *** _od_resume_noirq: od=NULL, dev=0xc78bcc08
[   24.500915] *** _od_resume_noirq: od=NULL, pdev=0xc78bcc00
[   24.506805] *** _od_resume_noirq: od=NULL, pdev->name:omapdss_dpi
[   24.513336] Unable to handle kernel NULL pointer dereference at virtual addre
ss 00000018
[   24.521942] pgd = c62f0000
[   24.524841] [00000018] *pgd=862c1831, *pte=00000000, *ppte=00000000
[   24.531524] Internal error: Oops: 17 [#1] SMP ARM
[   24.536529] Modules linked in:
[   24.539764] CPU: 0    Not tainted  (3.5.0-rc1-00010-g5041caa-dirty #131)
[   24.546844] PC is at _od_resume_noirq+0x1c/0xac
[   24.551635] LR is at _od_resume_noirq+0x94/0xac
...
I'm on leave currently, so I can't test it right now. But can you try
the attached patch? Or even better, try merging the tag:

git://gitorious.org/linux-omap-dss2/linux.git tags/omapdss-for-3.5-rc2

which contains the included patch plus a couple other fixes.

 Tomi
Message details and related content
Hi Tomi,

On Tue, Jun 5, 2012 at 2:33 PM, Tomi Valkeinen [off-list ref] wrote:
Hi Jean,

On Tue, 2012-06-05 at 14:17 +0200, Jean Pihet wrote:
quoted
Hi Tomi,
quoted
I am using a mainline kernel (3.5.0-rc1) with the patches below integrated.
I have an issue with suspend/resume on OMAP3 Beagleboard, where the
system hangs at resume time.

Here below is a log with the option no_console_suspend set and a few
added messages in case of null pointer in _od_resume_noirq.
It looks like there is no omap_device associated to the "omapdss_dpi" pdev.

What do you think? How to fix this?
Sorry I know there have been some discussions on the lists but I am
not aware of all the details in the devices creation for DSS.

/ # echo mem > /sys/power/state
[   23.262298] PM: Syncing filesystems ... done.
[   23.295501] Freezing user space processes ... (elapsed 0.02 seconds) done.
[   23.326507] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) don
e.
[   23.502197] PM: suspend of devices complete after 163.766 msecs
[   23.511932] PM: late suspend of devices complete after 3.418 msecs
[   23.524444] PM: noirq suspend of devices complete after 5.860 msecs
[   23.531249] Disabling non-boot CPUs ...
[   24.476562] Powerdomain (per_pwrdm) didn't enter target state 1
[   24.482818] Powerdomain (core_pwrdm) didn't enter target state 1
[   24.489166] Could not enter target state in pm_suspend
[   24.495147] *** _od_resume_noirq: od=NULL, dev=0xc78bcc08
[   24.500915] *** _od_resume_noirq: od=NULL, pdev=0xc78bcc00
[   24.506805] *** _od_resume_noirq: od=NULL, pdev->name:omapdss_dpi
[   24.513336] Unable to handle kernel NULL pointer dereference at virtual addre
ss 00000018
[   24.521942] pgd = c62f0000
[   24.524841] [00000018] *pgd†2c1831, *pte000000, *ppte000000
[   24.531524] Internal error: Oops: 17 [#1] SMP ARM
[   24.536529] Modules linked in:
[   24.539764] CPU: 0    Not tainted  (3.5.0-rc1-00010-g5041caa-dirty #131)
[   24.546844] PC is at _od_resume_noirq+0x1c/0xac

4 more quoted lines

Oh sorry about that!
the attached patch? Or even better, try merging the tag:
That fixes it! I am able to suspend/resume correctly now.
git://gitorious.org/linux-omap-dss2/linux.git tags/omapdss-for-3.5-rc2

which contains the included patch plus a couple other fixes.
Thanks for the link, that is certainly useful!

Have a nice time on leave ;-p
 Tomi
Regards,
Jean
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help