Replace the custom OMAP DMA API usage by DMA engine. Feature-wise the
driver has lost the ability to get notified of DMA transfers failure
through the completion handler, as the DMA engine API doesn't expose
that status information.
Signed-off-by: Laurent Pinchart
Ok, so I played with RGB LED a bit, and we have quite a gap in
documentation: what 50% brightness means is non-trivial and very
important in case we want to do smooth blinking and color transitions.
Signed-off-by: Pavel Machek pa...@ucw.cz
diff --git a/Documentation/ABI/testing/sysfs-class-led
Function pm_runtime_get_sync could fail and we need to check return
value to prevent kernel crash.
Signed-off-by: Pali Rohár pali.ro...@gmail.com
---
v2: Check return value for all pm_runtime_get_sync() calls
---
drivers/crypto/omap-sham.c | 23 ---
1 file changed, 20
On Friday 06 March 2015 23:23:06 Aaro Koskinen wrote:
Hi,
On Fri, Mar 06, 2015 at 10:36:32AM -0800, Tony Lindgren wrote:
Are there any fixes in this series that should go into
v4.0-rc series, or can it all wait for v4.1?
I think these all should wait for v4.1.
A.
I would suggest to
On Sat, 7 Mar 2015 22:01:02 +0100 Sebastian Reichel s...@debian.org wrote:
Hi,
On Fri, Mar 06, 2015 at 10:24:17PM +0100, Pavel Machek wrote:
According to n900 dts, twl4030-bci (aka charger) should be
included.
its part of twl, but not used on N900 afaik.
(But it does not seem to do
On Sat, 7 Mar 2015, Rafael J. Wysocki wrote:
Well right now it's using threaded irq, and I'd like to get rid of
I'll verify again, but I believe the issue was that without doing
mark_last_busy here the device falls back asleep right away.
That probably should be fixed in pm_runtime in
On Fri, 6 Mar 2015, Tony Lindgren wrote:
I'll verify again, but I believe the issue was that without doing
mark_last_busy here the device falls back asleep right away.
As it should. If you don't increment the usage counter (for example,
by calling pm_runtime_get instead of
On Sat, 7 Mar 2015, Rafael J. Wysocki wrote:
But this is part of a bigger picture. Namely, if a separete wakeup interrupt
is required for a device, the device's power.can_wakeup flag cannot be set
until that interrupt has been successfully requested. Also for devices that
can signal wakeup
On Sun, 8 Mar 2015, Pali Rohár wrote:
On Friday 06 March 2015 23:23:06 Aaro Koskinen wrote:
On Fri, Mar 06, 2015 at 10:36:32AM -0800, Tony Lindgren wrote:
Are there any fixes in this series that should go into
v4.0-rc series, or can it all wait for v4.1?
I think these all should
