Fix compile error when ARCH_EXYNOS5 is only enabled without ARCH_EXYNOS4.
arch/arm/mach-exynos/built-in.o: In function `exynos4_pm_prepare':
linux/arch/arm/mach-exynos/pm.c:185: undefined reference to
`exynos4_sys_powerdown_conf'
arch/arm/mach-exynos/built-in.o: In function `__virt_to_phys':
linu
> Cc: rpur...@rpsys.net, florianschandi...@gmx.de,
> devicetree-disc...@lists.ozlabs.org, linux-fb...@vger.kernel.org,
> linux-samsung-soc@vger.kernel.org, grant.lik...@secretlab.ca,
> rob.herr...@calxeda.com, kgene@samsung.com, jg1@samsung.com,
> broo...@opensource.wolfsonmicro.com, k
Hi Kgene,
Am Mittwoch 28 März 2012, 14:08:05 schrieb Tushar Behera:
> On 03/28/2012 04:58 PM, Heiko Stübner wrote:
> > Am Mittwoch, 28. März 2012, 12:50:35 schrieb Tushar Behera:
> >> The patches are based on Kukjin's for-next branch and they fix a couple
> >> of compile-time errors and warnings.
Hello.
On 06-04-2012 12:00, Marek Szyprowski wrote:
Some bootloadered
Bootloaders?
disable unused power domains, so kernel code should
read the actual state from the hardware registers instead of assuming
that their initial state is 'on'.
Signed-off-by: Marek Szyprowski
Signed-off-by:
Some bootloaders disable power domains on boot and the platform startup
code registers them in the 'disabled' state. Current gen_pd code assumed
that the devices can be registered only to the power domain which is in
'enabled' state and these devices are active at the time of the
registration. This
EXYNOS4_CLKGATE_BLOCK register can be used to disable the respective
multimedia block hardware planes. It acts similar to the power domains.
This patch adds transparent support for this method of gating of
multimedia blocks. New clocks are added as parents to the respective
block bus clocks. This p
Some bootloadered disable unused power domains, so kernel code should
read the actual state from the hardware registers instead of assuming
that their initial state is 'on'.
Signed-off-by: Marek Szyprowski
Signed-off-by: Kyungmin Park
---
arch/arm/mach-exynos/pm_domains.c |8 +---
1 fil
Some patches for s3c-sdhci driver which changed support for Exynos4 SoC
have not been merged to v3.4-rc1, while some of their followups have been
applied to mach-universal.c and mach-nuri.c. This patch reverts that
changes and add missing MMC_CAP2_BROKEN_VOLTAGE capability which got lost
together w
The atmel_mxt_ts driver has been extended to support more 'configuration
objects' in commit 81c88a711 ("Input: atmel_mxt_ts - update object list"),
what broke the configuration values for NURI board. These values are
optional anyway, so remove them to get the driver working correctly.
Signed-off-b
Hi Kukjin,
I've just checked the support for Samsung NURI and UniversalC210 boards
in v3.4-rc1 and found some issues. The attached patches fixes the
leftovers from missing s3c-sdhci driver changes, fixes division by
zero caused by missing initial value for xusbxti clock and removes broken
optional
On some versions of NURI and UniversalC210 boards, camera clocks are
routed directly to xusbxti clock source. This patch sets the correct
value for this clock to let usb and camera sensors to work correctly and
avoid division by zero on driver's probe.
Signed-off-by: Marek Szyprowski
Signed-off-b
Regulator names should not contain slash to avoid issues with debugfs.
Signed-off-by: Marek Szyprowski
Signed-off-by: Kyungmin Park
---
arch/arm/mach-exynos/mach-nuri.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-exynos/mach-nuri.c b/arch/arm/mach-exy
12 matches
Mail list logo
