From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: vinod.koul@intel.com, dan.j.williams@intel.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
nsekhar@ti.com, t-kristo@ti.com
Subject: Re: [PATCH] dmaengine: edma: Remove dynamic TPTC power management feature
Date: Wed, 27 Jan 2016 07:54:23 -0800 [thread overview]
Message-ID: <20160127155422.GH19432@atomide.com> (raw)
In-Reply-To: <1453885906-17652-1-git-send-email-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [160127 01:12]:
> The dynamic or on demand pm_runtime does not work correctly on am335x and
> am437x due to interference with hwmod.
Hmm care expand a bit what is the problem with this "interference"?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: edma: Remove dynamic TPTC power management feature
Date: Wed, 27 Jan 2016 07:54:23 -0800 [thread overview]
Message-ID: <20160127155422.GH19432@atomide.com> (raw)
In-Reply-To: <1453885906-17652-1-git-send-email-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [160127 01:12]:
> The dynamic or on demand pm_runtime does not work correctly on am335x and
> am437x due to interference with hwmod.
Hmm care expand a bit what is the problem with this "interference"?
Regards,
Tony
next prev parent reply other threads:[~2016-01-27 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 9:11 [PATCH] dmaengine: edma: Remove dynamic TPTC power management feature Peter Ujfalusi
2016-01-27 9:11 ` Peter Ujfalusi
2016-01-27 9:11 ` Peter Ujfalusi
2016-01-27 15:54 ` Tony Lindgren [this message]
2016-01-27 15:54 ` Tony Lindgren
2016-01-28 9:00 ` Peter Ujfalusi
2016-01-28 9:00 ` Peter Ujfalusi
2016-01-28 9:00 ` Peter Ujfalusi
2016-01-28 17:11 ` Tony Lindgren
2016-01-28 17:11 ` Tony Lindgren
2016-01-28 17:11 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160127155422.GH19432@atomide.com \
--to=tony@atomide.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
--cc=vinod.koul@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.