On 07/11/2013 12:17 PM, Rajendra Nayak wrote:
On Wednesday 10 July 2013 09:37 PM, Felipe Balbi wrote:
how about something like below ? It makes omap_device/hwmod and
pm_runtime agree on the initial state of the device and will prevent
->runtime_resume() from being called on first pm_runtime_get*() done
during probe.

This is similar to what PCI bus does (if you look at pci_pm_init()).

I tried something similar [1] but what I found is that the serial
runtime resume was called despite it being marked as active using
pm_runtime_set_active().

That seems to be because of the pm_runtime_set_autosuspend_delay()
because we have the autosuspend_delay = -1

-----
static void update_autosuspend(struct device *dev, int old_delay, int old_use)
{
         int delay = dev->power.autosuspend_delay;

         /* Should runtime suspend be prevented now? */
         if (dev->power.use_autosuspend && delay < 0) {

                 /* If it used to be allowed then prevent it. */
                 if (!old_use || old_delay >= 0) {
                         atomic_inc(&dev->power.usage_count);
                         rpm_resume(dev, 0); <------------------------------- 
calls serial runtime resume.
It's strange - the check for status is inside rpm_resume()

if (dev->power.runtime_status == RPM_ACTIVE) {
                retval = 1;
                goto out;
        }

So, if status is set to RPM_ACTIVE before first call to:
 pm_runtime_use_autosuspend(&pdev->dev);
 pm_runtime_set_autosuspend_delay(&pdev->dev,
                        omap_up_info->autosuspend_timeout);
-- or --
 pm_runtime_get*()
everything should be ok.

May be the problem is inside serial_omap_set_termios() where pm_runtime_get_sync is called before context is initialized.
probe:
 get - status is ACTIVE and serial resume is not called
 put - status is IDLE

set_termios
 get - status is IDLE and serial resume is called


                 }
         }
-----

So we end up with the same issue with serial resume being called before 
set_termios()

[1]

diff --git a/arch/arm/mach-omap2/omap_device.c 
b/arch/arm/mach-omap2/omap_device.c
index 5cc9287..c71d47d 100644
--- a/arch/arm/mach-omap2/omap_device.c
+++ b/arch/arm/mach-omap2/omap_device.c
@@ -129,6 +129,7 @@ static int omap_device_build_from_dt(struct platform_device 
*pdev)
         struct device_node *node = pdev->dev.of_node;
         const char *oh_name;
         int oh_cnt, i, ret = 0;
+       bool device_active = false;

         oh_cnt = of_property_count_strings(node, "ti,hwmods");
         if (oh_cnt <= 0) {
@@ -152,6 +153,9 @@ static int omap_device_build_from_dt(struct platform_device 
*pdev)
                         goto odbfd_exit1;
                 }
                 hwmods[i] = oh;
+               if (oh->flags & HWMOD_INIT_NO_IDLE)
+                       device_active = true;
+
         }

         od = omap_device_alloc(pdev, hwmods, oh_cnt);
@@ -172,6 +176,11 @@ static int omap_device_build_from_dt(struct 
platform_device *pdev)

         pdev->dev.pm_domain = &omap_device_pm_domain;

+       if (device_active) {
+               omap_device_enable(pdev);
+               pm_runtime_set_active(&pdev->dev);
+       }
+
  odbfd_exit1:
         kfree(hwmods);
  odbfd_exit:

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to