Since memtest might be used by other architectures pass input parameters
as phys_addr_t instead of long to prevent overflow.
Change-Id: If189b91fb308315369631a5016ca6eda92ca13ab
Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com>
Patch-mainline: linux-arm-kernel @ 03/09/15, 10:27
Signed-off-by: Rohit Vaswani <rvaswani@codeaurora.org>
There is nothing platform dependent in the core memtest code, so other platform
might benefit of this feature too.
Change-Id: I2f1fca080cffe1d887fe724885e337e7117482d8
Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com>
Patch-mainline: linux-arm-kernel @ 03/09/15, 10:27
Signed-off-by: Rohit Vaswani <rvaswani@codeaurora.org>
Add the battery data node for PMI8950 charger to select between
multiple battery-profiles.
Change-Id: I7c5846d4617f89cc9de3c4e13a461f3c590185e3
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
Use batt-id information from FG to detect the battery-profile
in use and update the charger configuration from the profile
parameters.
Change-Id: I41b0e9d93cec00b7274fa22092f340668c05a5d5
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
The idle_task_exit() function may call switch_mm() with next ==
&init_mm. On arm64, init_mm.pgd cannot be used for user mappings, so
this patch simply sets the reserved TTBR0.
Change-Id: I90c16bcb0edcdcf6e1ce9f98a091ad1e0cccb697
Cc: <stable@vger.kernel.org>
Reported-by: Jon Medhurst (Tixy) <tixy@linaro.org>
Tested-by: Jon Medhurst (Tixy) <tixy@linaro.org>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Git-commit: e53f21bce4d35a93b23d8fa1a840860f6c74f59e
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Rohit Vaswani <rvaswani@codeaurora.org>
Overlay buffer allocations are marked as kmemleak because the base
pointer is not being tracked, rather these are tracked as part of a
list. Add kmemleak_not_leak to prevent false positives.
Change-Id: I3c54c15b6d73d3aece8e28b7723e0cf9c4953be5
Signed-off-by: Adrian Salido-Moreno <adrianm@codeaurora.org>
Most of the platforms have D+/D- lines routed to USB PHY and the
charger. And almost all the PHYs pull down the D+/D- lines unless
it is set to active mode. This grounding causes issues with
source detection and results in detecting SDP even when it
is not.
Fix this by setting ALLOW_DETECTION property to inform the PHY to
remove the pull downs. Once done, rerun APSD and inform of the correct
results via the TYPE and PRESENT property. The reruns are necessary
only if an SDP is detected.
To rerun APSD use this following
procedure
1. Set the allowable USB voltage to 9V.
2. Sleep 40mS
3. Set the allowable USB voltage to 5V-9V.
Step 3 causes APSD to run again and raise the src_detect status.
Change-Id: I52a22901f16dea0144d9ed0444af32014d2f5612
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
The current driver calls HVDCP detection work for any type of USB charger.
It should be called only if the initial detection was DCP. While at it
add few log statements to help with debugging.
Change-Id: Iaef4b8e6b4109a6a5033b75823f3f9590ee5ea2c
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Vladimir Murzin
Linux Build Service Account
Anirudh Ghayal
Catalin Marinas
Adrian Salido-Moreno
Abhijeet Dharmapurikar