Add new property ti,system-power-controller to register the RTC as a
power-off handler.
Some RTC IP revisions can control an external PMIC via the pmic_power_en
pin, which can be configured to transition to OFF on ALARM2 events and
back to ON on subsequent ALARM (wakealarm) events.
This is based
This is an updated patchset, which intends to add support for L2 cache
on Exynos4 SoCs on boards running under secure firmware, which requires
certain initialization steps to be done with help of firmware, as
selected registers are writable only from secure mode.
First four patches extend
From: Tomasz Figa t.f...@samsung.com
Certain platforms (i.e. Exynos) might need to set .write_sec callback
from firmware initialization which is happenning in .init_early callback
of machine descriptor. However current code will overwrite the pointer
with whatever is present in machine
From: Tomasz Figa t.f...@samsung.com
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 t.f...@samsung.com
[rewrote the code
From: Tomasz Figa t.f...@samsung.com
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 writes. To handle this, an
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
without overriding them. This patch introduces bindings to enable
prefetch settings to be specified from DT and
From: Tomasz Figa t.f...@samsung.com
This patch adds device tree nodes for L2 cache controller present on
Exynos4 SoCs.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
arch/arm/boot/dts/exynos4210.dtsi | 9 +
From: Tomasz Figa t.f...@samsung.com
Certain implementations of secure hypervisors (namely the one found on
Samsung Exynos-based boards) do not provide access to individual L2C
registers. This makes the .write_sec()-based interface insufficient and
provoking ugly hacks.
This patch is first step
From: Tomasz Figa t.f...@samsung.com
Because certain secure hypervisor do not allow writes to individual L2C
registers, but rather expect set of parameters to be passed as argument
to secure monitor calls, there is a need to provide an interface for the
L2C driver to ask the firmware to configure
This patch reads charge delay from tsc DT node and writes to
REG_CHARGEDELAY register. If the charge delay is not specified in DT
then default value of 0xB000(CHARGEDLY_OPENDLY) is used.
Signed-off-by: Vignesh R vigne...@ti.com
---
drivers/input/touchscreen/ti_am335x_tsc.c | 8 +++-
1 file
From: Brad Griffis bgrif...@ti.com
TSC interrupt handler had udelay to avoid reporting of false pen-up
interrupt to user space. This patch implements workaround suggesting in
Advisory 1.0.31 of silicon errata for am335x, thus eliminating udelay
and touchscreen lag. This also improves performance
The charge delay value is by default 0xB000. But it can be set to lower
values on some boards as long as false pen-ups are avoided. Lowering the
value increases the sampling rate (though current sampling rate is
sufficient for tsc operation). Hence charge delay has been made a DT
parameter.
From: Brad Griffis bgrif...@ti.com
This patch makes the initial changes required to workaround TSC-false
pen-up interrupts. It is required to implement these changes in order to
remove udelay in the TSC interrupt handler and false pen-up events.
The charge step is to be executed immediately after
This series of patches fix TSC defects related to lag in touchscreen
performance and cursor jump at touch release. The lag was result of
udelay in TSC interrupt handler. Cursor jump due to false pen-up event.
The patches implement Advisory 1.0.31 in silicon errata of am335x-evm
to avoid false
On Mon, Oct 27, 2014 at 12:05:47PM +0100, Marek Szyprowski wrote:
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
without overriding them. This patch
Hello,
On 2014-10-27 12:14, Russell King - ARM Linux wrote:
On Mon, Oct 27, 2014 at 12:05:47PM +0100, Marek Szyprowski wrote:
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes
Since commit 6d178ef2fd5e (mtd: nand: Move ELM driver and rename as
omap_elm), I don't have any mtd devices present on my am335x. This
appears to be related to the link order of the omap_elm and omap2
objects. Fix it by swapping the two in the Makefile.
Signed-off-by: Frans Klaver
Since commit 6d178ef2fd5e (mtd: nand: Move ELM driver and rename as
omap_elm), I don't have any mtd devices present on my am335x. This
appears to be related to the link order of the omap_elm and omap2
objects. Fix it by swapping the two in the Makefile.
Signed-off-by: Frans Klaver
Hi Frans,
On 10/27/2014 03:32 PM, Frans Klaver wrote:
Since commit 6d178ef2fd5e (mtd: nand: Move ELM driver and rename as
omap_elm), I don't have any mtd devices present on my am335x. This
appears to be related to the link order of the omap_elm and omap2
objects. Fix it by swapping the two in
On Mon, Oct 27, 2014 at 03:56:41PM +0200, Roger Quadros wrote:
Hi Frans,
Hi,
On 10/27/2014 03:32 PM, Frans Klaver wrote:
Since commit 6d178ef2fd5e (mtd: nand: Move ELM driver and rename as
omap_elm), I don't have any mtd devices present on my am335x. This
appears to be related to the
Since commit 6d178ef2fd5e (mtd: nand: Move ELM driver and rename as
omap_elm), I don't have any mtd devices present on my am335x. This
changes the link order of the omap_elm and omap2 objects, causing them
to probe in the wrong order.
To fix this, make elm_config defer probing until the omap_elm
* Paul Walmsley p...@pwsan.com [141023 08:21]:
On Mon, 20 Oct 2014, Paul Walmsley wrote:
Boot-time memory difference
(delta in bytes from test_v3.17-rc7
(fe82dcec644244676d55a1384c958d5f67979adb))
avail rsrvd high freed board kconfig
-117908k -13164k . -148k
Register with kernel power-off handler instead of setting pm_power_off
directly. Always use register_power_off_handler_simple as there is no
indication that more than one power-off handler is registered.
If the power-off handler only resets the system or puts the CPU in sleep mode,
select the
On Mon, Oct 27, 2014 at 09:09:28AM +0100, Johan Hovold wrote:
Add new property ti,system-power-controller to register the RTC as a
power-off handler.
Some RTC IP revisions can control an external PMIC via the pmic_power_en
pin, which can be configured to transition to OFF on ALARM2 events
On Mon, Oct 27, 2014 at 11:45:44AM -0500, Felipe Balbi wrote:
On Mon, Oct 27, 2014 at 09:09:28AM +0100, Johan Hovold wrote:
Add new property ti,system-power-controller to register the RTC as a
power-off handler.
Some RTC IP revisions can control an external PMIC via the pmic_power_en
On Mon, Oct 27, 2014 at 05:56:54PM +0100, Johan Hovold wrote:
On Mon, Oct 27, 2014 at 11:45:44AM -0500, Felipe Balbi wrote:
On Mon, Oct 27, 2014 at 09:09:28AM +0100, Johan Hovold wrote:
Add new property ti,system-power-controller to register the RTC as a
power-off handler.
Some RTC
On 10/27/2014 12:08 PM, Vignesh R wrote:
This series of patches fix TSC defects related to lag in touchscreen
I will try to look this in the next few days. Do we really need #3 (and
then #4)? Given the complexity we have already, is there any benefit by
decreasing this value? Would someone want
On 10/27/2014 12:34 PM, Sebastian Andrzej Siewior wrote:
Do we really need #3 (and then #4)? Given the complexity we have already, is
there any benefit by decreasing this value?
I specifically requested we add ti,charge-delay to the device tree because it
is THE critical value to tune for a
On 10/27/2014 10:56 AM, Roger Quadros wrote:
Hi Frans,
On 10/27/2014 03:32 PM, Frans Klaver wrote:
Since commit 6d178ef2fd5e (mtd: nand: Move ELM driver and rename as
omap_elm), I don't have any mtd devices present on my am335x. This
appears to be related to the link order of the omap_elm
Here are some basic OMAP test results for Linux v3.18-rc2.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.18-rc2/20141027002021/
Test summary
Build: uImage:
Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,
* Pali Rohár pali.ro...@gmail.com [141026 15:24]:
On Sunday 26 October 2014 22:55:48 Pavel Machek wrote:
I have root prepared on /dev/mmcblk0p6. I tried 3.17 with
rx51_defconfig, but no, it refuses to mount it.
VFS: Cannot open root device mmcblk0p6 or : error
-19.
* Tony Lindgren t...@atomide.com [141027 08:56]:
* Paul Walmsley p...@pwsan.com [141023 08:21]:
On Mon, 20 Oct 2014, Paul Walmsley wrote:
Boot-time memory difference
(delta in bytes from test_v3.17-rc7
(fe82dcec644244676d55a1384c958d5f67979adb))
avail rsrvd high freed
We're moving omaps to use device tree based booting and already have
omap2, omap4, omap5, am335x and am437x booting in device tree only
mode.
Only omap3 still has legacy booting still around and we really want
to make that device tree only. So let's add a warning about deprecated
legacy booting
Looks like we need to have BCH enabled to get NAND
working and to avoid getting:
nand: error: CONFIG_MTD_NAND_ECC_BCH not enabled
Signed-off-by: Tony Lindgren t...@atomide.com
--- a/arch/arm/configs/omap2plus_defconfig
+++ b/arch/arm/configs/omap2plus_defconfig
@@ -111,6 +111,7 @@
Without that fix connector-analog-tv driver isn't probed when compiled
as module.
Signed-off-by: H. Nikolaus Schaller h...@goldelico.com
---
drivers/video/fbdev/omap2/displays-new/connector-analog-tv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
With legacy booting, the platform init code was taking care of
the configuring of GPIOs. With device tree based booting, things
may or may not work depending what bootloader has configured or
if the legacy platform code gets called.
Let's add support for the pwrdn and reset GPIOs to the smc91x
* Tony Lindgren t...@atomide.com [141027 12:55]:
* Pali Rohár pali.ro...@gmail.com [141026 15:24]:
On Sunday 26 October 2014 22:55:48 Pavel Machek wrote:
I have root prepared on /dev/mmcblk0p6. I tried 3.17 with
rx51_defconfig, but no, it refuses to mount it.
VFS: Cannot
On Mon, 27 Oct 2014 09:09:28 +0100 Johan Hovold jo...@kernel.org wrote:
Add new property ti,system-power-controller to register the RTC as a
power-off handler.
Some RTC IP revisions can control an external PMIC via the pmic_power_en
pin, which can be configured to transition to OFF on
Hi,
On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
+
+ if (!of_have_populated_dt())
+ pr_warn(WARNING: legacy booting deprecated, please update to
boot with .dts\n);
+
Maybe use WARN so that the warning is more verbose and kernel gets tainted?
A.
--
To
On Fri, 24 Oct 2014 21:55:32 +0200 Johan Hovold jo...@kernel.org wrote:
On Fri, Oct 24, 2014 at 02:44:42PM -0500, Felipe Balbi wrote:
On Fri, Oct 24, 2014 at 09:36:55PM +0200, Johan Hovold wrote:
On Fri, Oct 24, 2014 at 02:29:48PM -0500, Felipe Balbi wrote:
Hi,
On Fri, Oct 24,
On Mon, Oct 27, 2014 at 04:22:51PM -0700, Andrew Morton wrote:
On Fri, 24 Oct 2014 21:55:32 +0200 Johan Hovold jo...@kernel.org wrote:
I will. :) Just wanted to see whether Andrew preferred I resend the
whole series or just that one patch first.
The diff is minimal:
diff --git
41 matches
Mail list logo
