On Tue, Aug 26, 2014 at 04:17:58PM +0200, Tomasz Figa wrote:
Exynos4 SoCs equipped with an L2C-310 cache controller and running under
secure firmware require certain registers of aforementioned IP to be
accessed only from secure mode. This means that SMC calls are required
for certain register
On Tue, Aug 26, 2014 at 04:17:59PM +0200, Tomasz Figa wrote:
On Exynos SoCs it is necessary to resume operation of L2C early in
assembly code, because otherwise certain systems will crash. This patch
adds necessary code to non-secure resume handler.
Signed-off-by: Tomasz Figa
In case the optional dr_mode property isn't set in the dwc3 nodes the
the controller will go into OTG mode iff both USB host and USB gadget
functionality are enabled in the kernel configuration. Unfortunately this
results in USB not working on exynos5420-peach-pit and
exynos5800-peach-pi with such
When building a kernel with support for both USB host and USB Gadget support on
the dwc3 controller on the Exynos5 soc will go into USB OTG mode unless
otherwise specified in the dtb, which is unhelpful for boards hooked up to run
as USB host.
First patch in this set explicitely set the dual-role
Explicitly set the dr_mode for the second dwc3 controller on the
Arndale Octa board to host mode. This is required to ensure the
controller is initialized in the right mode if the kernel is build with
USB gadget support
Reported-By: Andreas Färber afaer...@suse.de
Signed-off-by: Sjoerd Simons
Enable USB gadget support without support for any specific gadgets to
more easily catch cases where a devices dts doesn't specify the usb
controllers dr_mode while it should.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1
Hi Kukjin,
On 09/13/2014 07:08 PM, Kukjin Kim wrote:
On 09/09/14 22:09, Jacek Anaszewski wrote:
Signed-off-by: Jacek Anaszewskij.anaszew...@samsung.com
Signed-off-by: Kyungmin Parkkyungmin.p...@samsung.com
Cc: Kukjin Kimkgene@samsung.com
---
arch/arm/boot/dts/exynos3250.dtsi | 12
Signed-off-by: Jacek Anaszewski j.anaszew...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
Cc: Kukjin Kim kgene@samsung.com
---
arch/arm/boot/dts/exynos3250.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos3250.dtsi
Currently the DP_PHY_ENABLE register is mapped in the driver,
and accessed to control power to the PHY.
With mfd-syscon and regmap interface available at our disposal,
it's wise to use that instead of using a 'reg' property for the
controller and allocating a memory resource for that.
To
Now that we have moved to generic phy based bindings,
we don't need to have any code related to older dptx-phy.
Nobody is using this dptx-phy anymore, so removing the
same.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Cc: Jingoo Han jg1@samsung.com
---
DP PHY now require pmu-system-controller to handle PMU register
to control PHY's power isolation. Adding the same to dp-phy
node.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Cc: Jingoo Han jg1@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi |2 +-
These patches are based on 'for-next' branch of kgene's linux-samsung tree.
Refactoring the exynos-dp-video phy to use pmu-system-controller handle
and access the register using mfd-syscon and regmap.
Simultaneously, removing the support for older dptx-phy, since it's obsolete
now and noone uses
Hello Andrew,
Thanks a lot for taking a look to these patches!
On 09/13/2014 12:05 AM, Andrew Morton wrote:
On Fri, 12 Sep 2014 10:17:39 +0200 Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
From: Doug Anderson diand...@chromium.org
The max77686 includes an RTC that
Hello Andrew,
On 09/13/2014 12:13 AM, Andrew Morton wrote:
On Fri, 12 Sep 2014 10:17:43 +0200 Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
This patch adds support for the RTC and is based on a driver
added by
Hello Krzysztof,
On Fri, Sep 12, 2014 at 2:03 PM, Krzysztof Kozlowski
k.kozlow...@samsung.com wrote:
+ i2c_max77693: i2c-gpio-1 {
+ compatible = i2c-gpio;
+ gpios = gpm2 0 0, gpm2 1 0 ;
Can you please include dt-bindings/gpio/gpio.h and use
GPIO_ACTIVE_HIGH
On pon, 2014-09-15 at 16:36 +0200, Javier Martinez Canillas wrote:
Hello Krzysztof,
On Fri, Sep 12, 2014 at 2:03 PM, Krzysztof Kozlowski
k.kozlow...@samsung.com wrote:
+ i2c_max77693: i2c-gpio-1 {
+ compatible = i2c-gpio;
+ gpios = gpm2 0 0, gpm2 1 0 ;
The MAX77693 is a companion power management IC for smart phones and tablets.
The MAX77693 contains input over-voltage protection (OVP),
a fully-integrated 2.5A switching charger for Lithium Ion battery with
integrated battery disconnect, OTG/accessory 5V output power,
a high-current white LED
On Mon, Sep 15, 2014 at 11:57:09AM +0100, Build bot for Mark Brown wrote:
Today's -next got a build failure in ARM allmodconfig due to platsmp.c:
| arch/arm/mach-exynos/platsmp.c:198:31: warning: incorrect type in return
expression (different address spaces)
|
Hi Ajay,
Thank you for the patch.
I think we're moving in the right direction, but we're not there yet.
On Saturday 26 July 2014 00:52:08 Ajay Kumar wrote:
This patch tries to seperate drm_bridge implementation
into 2 parts, a drm part and a non_drm part.
A set of helper functions are
On Mon, Sep 15, 2014 at 09:34:58AM -0700, Mark Brown wrote:
On Mon, Sep 15, 2014 at 11:57:09AM +0100, Build bot for Mark Brown wrote:
Today's -next got a build failure in ARM allmodconfig due to platsmp.c:
| arch/arm/mach-exynos/platsmp.c:198:31: warning: incorrect type in return
Pageflipping currently causes some inconsistencies that lead to
crashes. Just run an app that causes a CRTC pageflip in a raw X session
and check that it exits cleanly and can be restarted - you'll see
crashes like:
Unable to handle kernel NULL pointer dereference at virtual address 0334
PC
On 15.09.2014 11:03, Russell King - ARM Linux wrote:
diff --git a/arch/arm/mach-exynos/firmware.c
b/arch/arm/mach-exynos/firmware.c
index 554b350..71bcfbd 100644
--- a/arch/arm/mach-exynos/firmware.c
+++ b/arch/arm/mach-exynos/firmware.c
@@ -102,7 +102,9 @@ static int exynos_suspend(void)
Currently the DP_PHY_ENABLE register is mapped in the driver,
and accessed to control power to the PHY.
With mfd-syscon and regmap interface available at our disposal,
it's wise to use that instead of using a 'reg' property for the
controller and allocating a memory resource for that.
To
23 matches
Mail list logo
