This patch set AUTOWAKEUP_EN bit to ARM_CORE_CONFIGURATION register
because Exynos3250 removes WFE in secure mode so that turn on automatically
after setting CORE_LOCAL_PWR_EN. Also, This patch use dbs_sev() macro
to guarantee the data synchronization of command instead of IPI_WAKEUP
because Exynos
There's no reason to export these functions, and I have no idea why
they have over time ended up in the header file. As a result, none of
the checker tools caught it (i.e. sparse was silent on it).
Signed-off-by: Olof Johansson
---
I'm guessing with all the churn right now this might not apply,
This solves a problem with building with CONFIG_SMP=n due to missing
sysram_base_addr (or sysram_ns_base_addr) variables.
The new setup method is more awkward than I'd like for it to be, but
it can't be done in init_early() since ioremap is not yet available,
but it needs to happen before SMP.
Re
On Mon, Jun 2, 2014 at 4:42 PM, Russell King - ARM Linux
wrote:
> Spotted with a randconfig today:
>
> arch/arm/mach-exynos/built-in.o: In function `exynos_set_cpu_boot_addr':
> pm_domains.c:(.text+0x19c): undefined reference to `sysram_ns_base_addr'
> arch/arm/mach-exynos/built-in.o:(.data+0x94):
Spotted with a randconfig today:
arch/arm/mach-exynos/built-in.o: In function `exynos_set_cpu_boot_addr':
pm_domains.c:(.text+0x19c): undefined reference to `sysram_ns_base_addr'
arch/arm/mach-exynos/built-in.o:(.data+0x94): undefined reference to
`exynos_enter_aftr'
This should be fixed before
Kukjin,
On Wed, May 28, 2014 at 10:38 AM, Doug Anderson wrote:
> Kukjin,
>
> On Wed, May 21, 2014 at 11:34 AM, Chirantan Ekbote
> wrote:
>> On Wed, May 21, 2014 at 9:20 AM, Tomasz Figa wrote:
>>> On 21.05.2014 15:24, Kukjin Kim wrote:
>>>
BTW, since
exynos5260, exynos5420 and exynos58
> Ok, there was already a patch posted by you for this[1], which had
> quite a much discussion
> on it.
> Would you like to give some pointers based on that ?
> One that Olof had suggested was to use gpio-reset driver which is yet
> to make to mainline.
> But i think with that too we need to take c
On Sat, May 10, 2014 at 04:20:14PM +0900, Pankaj Dubey wrote:
> Let's handle i2c interrupt re-configuration in i2c driver. This will
> help us in removing some soc specific checks from machine files.
> Since only Exynos5250, and Exynos5420 need to do this, added syscon
> based phandle to i2c device
This is needed for suspend/resume and cpuidle AFTR mode support.
Signed-off-by: Chanwoo Choi
Signed-off-by: Bartlomiej Zolnierkiewicz
---
against next-20140602
arch/arm/mach-exynos/pmu.c | 163 +++-
arch/arm/mach-exynos/regs-pmu.h | 128
On 06/02/2014 02:35 PM, Bartlomiej Zolnierkiewicz wrote:
* Use do_idle firmware method instead of cpu_do_idle() on boards with
secure firmware enabled.
* Use sysram_ns_base_addr + 0x24 address for exynos_boot_vector_addr()
and sysram_ns_base_addr + 0x20 one for exynos_boot_vector_flag() on
On 06/02/2014 02:35 PM, Bartlomiej Zolnierkiewicz wrote:
Replace EXYNOS_BOOT_VECTOR_ADDR and EXYNOS_BOOT_VECTOR_FLAG macros
by exynos_boot_vector_addr() and exynos_boot_vector_flag() static
inlines.
This patch shouldn't cause any functionality changes.
Signed-off-by: Bartlomiej Zolnierkiewicz
On 06/02/2014 02:08 PM, Bartlomiej Zolnierkiewicz wrote:
Hi,
On Friday, May 16, 2014 11:03:11 AM Daniel Lezcano wrote:
On 05/05/2014 12:57 PM, Bartlomiej Zolnierkiewicz wrote:
Add S5P_CENTRAL_SEQ_OPTION register setup for EXYNOS4x12 to AFTR
mode code. Without this setup AFTR mode doesn't sho
Tarek Dakhran writes:
> Hi,
>
> On Fri, May 30, 2014 at 7:41 AM, Tushar Behera wrote:
>> On Thu, May 29, 2014 at 11:30 PM, Andreas Färber wrote:
>>> Hi Tarek,
>>>
>>>
>>> And I reproducibly get failures for CPUs 1-3, resulting in only one CPU
>>> in /proc/cpuinfo (compared to 4 on downstream 3.
On Monday, June 02, 2014 03:15:07 PM Tomasz Figa wrote:
> Hi,
>
> On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> > * Use do_idle firmware method instead of cpu_do_idle() on boards with
> > secure firmware enabled.
> >
> > * Use sysram_ns_base_addr + 0x24 address for exynos_boot_vector_
Hi,
On Monday, June 02, 2014 03:05:40 PM Tomasz Figa wrote:
> Hi,
>
> On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> > Replace EXYNOS_BOOT_VECTOR_ADDR and EXYNOS_BOOT_VECTOR_FLAG macros
> > by exynos_boot_vector_addr() and exynos_boot_vector_flag() static
> > inlines.
> >
> > This patc
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> * Use do_idle firmware method instead of cpu_do_idle() on boards with
> secure firmware enabled.
>
> * Use sysram_ns_base_addr + 0x24 address for exynos_boot_vector_addr()
> and sysram_ns_base_addr + 0x20 one for exynos_boot_vector_f
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> Add S5P_CENTRAL_SEQ_OPTION register setup for EXYNOS4x12 to AFTR
> mode code. Without this setup AFTR mode doesn't show any benefit
> over WFI one. When this setup is applied AFTR mode reduces power
> consumption by ~12% (as measured on
On 05/30/2014 01:15 PM, Heiko Stübner wrote:
Am Freitag, 30. Mai 2014, 21:54:13 schrieb Seungwon Jeon:
+ Dinh Nguyen
+ Heiko Stuebner
On Wed, May 28, 2014, Jaehoon Chung wrote:
dw-mmc controller can support the multiple slot.
So each slot's property can be difference.
And "support-highspee
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> Use c15resume firmware method instead of accessing the registers
> directly in exynos_cpu_restore_register() if secure firmware is
> enabled. This affects both PM resume method and cpuidle AFTR mode.
>
> This patch shouldn't cause any f
Hi,
On Monday, June 02, 2014 02:51:14 PM Tomasz Figa wrote:
> Hi,
>
> On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> > From: Kyungmin Park
> >
> > To support multi-platform, it needs to know it's running under secure
> > OS or not. Sometimes it needs to access physical address by SMC
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> Replace EXYNOS_BOOT_VECTOR_ADDR and EXYNOS_BOOT_VECTOR_FLAG macros
> by exynos_boot_vector_addr() and exynos_boot_vector_flag() static
> inlines.
>
> This patch shouldn't cause any functionality changes.
>
> Signed-off-by: Bartlomiej Zo
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> On some platforms (i.e. EXYNOS ones) more than one idle mode is
> available and we need to distinguish them in firmware do_idle method.
>
> Add mode parameter to do_idle firmware method and AFTR mode support
> to EXYNOS do_idle implement
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> From: Tomasz Figa
>
> This change is a preparation for adding secure firmware support to
> EXYNOS cpuidle driver.
>
> This patch shouldn't cause any functionality changes.
>
> Signed-off-by: Tomasz Figa
> [bzolnier: splitted out from
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> From: Kyungmin Park
>
> To support multi-platform, it needs to know it's running under secure
> OS or not. Sometimes it needs to access physical address by SMC calls.
>
> e.g.,
> if (firmware_run()) {
> addr =
Replace EXYNOS_BOOT_VECTOR_ADDR and EXYNOS_BOOT_VECTOR_FLAG macros
by exynos_boot_vector_addr() and exynos_boot_vector_flag() static
inlines.
This patch shouldn't cause any functionality changes.
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
---
arch/arm/mach-exynos/pm.c | 2
From: Tomasz Figa
This change is a preparation for adding secure firmware support to
EXYNOS cpuidle driver.
This patch shouldn't cause any functionality changes.
Signed-off-by: Tomasz Figa
[bzolnier: splitted out from bigger patch]
Acked-by: Kyungmin Park
Signed-off-by: Bartlomiej Zolnierkiew
* Use do_idle firmware method instead of cpu_do_idle() on boards with
secure firmware enabled.
* Use sysram_ns_base_addr + 0x24 address for exynos_boot_vector_addr()
and sysram_ns_base_addr + 0x20 one for exynos_boot_vector_flag() on
boards with secure firmware enabled.
This patch fixes han
Add S5P_CENTRAL_SEQ_OPTION register setup for EXYNOS4x12 to AFTR
mode code. Without this setup AFTR mode doesn't show any benefit
over WFI one. When this setup is applied AFTR mode reduces power
consumption by ~12% (as measured on Trats2 board).
This change is a preparation for adding secure fir
Use c15resume firmware method instead of accessing the registers
directly in exynos_cpu_restore_register() if secure firmware is
enabled. This affects both PM resume method and cpuidle AFTR mode.
This patch shouldn't cause any functionality changes on boards that
don't use secure firmware.
Signe
On some platforms (i.e. EXYNOS ones) more than one idle mode is
available and we need to distinguish them in firmware do_idle method.
Add mode parameter to do_idle firmware method and AFTR mode support
to EXYNOS do_idle implementation.
This change is a preparation for adding secure firmware suppo
From: Kyungmin Park
To support multi-platform, it needs to know it's running under secure
OS or not. Sometimes it needs to access physical address by SMC calls.
e.g.,
if (firmware_run()) {
addr = physical address;
} else {
addr = virtual address;
Hi,
This patch series fixes support for AFTR idle mode on boards with
secure firmware enabled (it also includes fix for register setup on
EXYNOS4x12 SoCs). It has been tested on Trats2 target but should
also work on (EXYNOS4412 based) Insignal Origen board.
v2:
- synced against next-20140602
Hi Julius,
On Thu, May 29, 2014 at 4:07 AM, Julius Werner wrote:
> We originally tried using this driver on ChromiumOS and never got it
> to work reliably. IIRC the issue was that if the hub had already been
> initialized by firmware, the USB stack might enumerate it before the
> usb3503 driver
Hi,
On Friday, May 16, 2014 11:03:11 AM Daniel Lezcano wrote:
> On 05/05/2014 12:57 PM, Bartlomiej Zolnierkiewicz wrote:
> > Add S5P_CENTRAL_SEQ_OPTION register setup for EXYNOS4x12 to AFTR
> > mode code. Without this setup AFTR mode doesn't show any benefit
> > over WFI one. When this setup is
On 06/02/2014 12:42 PM, Andrzej Hajda wrote:
> On 06/02/2014 12:11 PM, Tomasz Figa wrote:
>> Hi Rahul, Andrzej,
>>
>> On 02.06.2014 11:42, Rahul Sharma wrote:
>>> On 2 June 2014 14:41, Andrzej Hajda wrote:
Hi Rahul,
On 05/28/2014 08:11 AM, Rahul Sharma wrote:
> System hangs when
On Fri, May 30, 2014 at 09:01:19PM +0200, Arnd Bergmann wrote:
> On Friday 30 May 2014 12:22:32 Dave Martin wrote:
> > > +
> > > +Examples:
> > > +=
> > > +
> > > +Single-master IOMMU:
> > > +
> > > +
> > > + iommu {
> > > + #address-cells = <0>;
> > > +
On 2014년 06월 02일 18:42, Rahul Sharma wrote:
> On 2 June 2014 14:41, Andrzej Hajda wrote:
>> Hi Rahul,
>>
>> On 05/28/2014 08:11 AM, Rahul Sharma wrote:
>>> System hangs when FIMD registers are accessed to disable
>>> hardware overlays. This is because of the clocks which are
>>> not enabled before
On Fri, May 30, 2014 at 09:11:07PM +0200, Arnd Bergmann wrote:
> On Friday 30 May 2014 12:27:28 Dave Martin wrote:
> > On Fri, May 30, 2014 at 08:30:08AM +0100, Thierry Reding wrote:
> > > On Thu, May 29, 2014 at 09:52:22AM -0600, Stephen Warren wrote:
> > > > On 05/23/2014 02:36 PM, Thierry Reding
On 06/02/2014 12:11 PM, Tomasz Figa wrote:
> Hi Rahul, Andrzej,
>
> On 02.06.2014 11:42, Rahul Sharma wrote:
>> On 2 June 2014 14:41, Andrzej Hajda wrote:
>>> Hi Rahul,
>>>
>>> On 05/28/2014 08:11 AM, Rahul Sharma wrote:
System hangs when FIMD registers are accessed to disable
hardware
On Fri, May 30, 2014 at 09:49:59PM +0200, Arnd Bergmann wrote:
> On Friday 30 May 2014 14:31:55 Rob Herring wrote:
> > On Fri, May 30, 2014 at 2:06 PM, Arnd Bergmann wrote:
> > > On Friday 30 May 2014 08:16:05 Rob Herring wrote:
> > >> On Fri, May 23, 2014 at 3:33 PM, Thierry Reding
> > >> wrote:
On Exynos4 USE_DELAYED_RESET_ASSERTION must be set in
ARM_COREx_OPTION register during CPU power down. This is the proper way
of powering down CPU.
Additionally without this the CPU clock down won't work after powering
down some other CPU and online CPUs will work at full frequency chosen
by CPUfr
Hi Rahul,
On 06/02/2014 06:42 PM, Rahul Sharma wrote:
On 2 June 2014 14:41, Andrzej Hajda wrote:
Hi Rahul,
On 05/28/2014 08:11 AM, Rahul Sharma wrote:
System hangs when FIMD registers are accessed to disable
hardware overlays. This is because of the clocks which are
not enabled before regist
Hi Rahul, Andrzej,
On 02.06.2014 11:42, Rahul Sharma wrote:
> On 2 June 2014 14:41, Andrzej Hajda wrote:
>> Hi Rahul,
>>
>> On 05/28/2014 08:11 AM, Rahul Sharma wrote:
>>> System hangs when FIMD registers are accessed to disable
>>> hardware overlays. This is because of the clocks which are
>>> n
On Mon, May 26, 2014 at 09:23:45PM +0530, Santosh Shukla wrote:
> From: santosh shukla
>
> Add non-global symbol .LLl2x0_regs_phys to avoid build break in thumb2 mode.
>
> IIUC, arm assembler fail to load value of "global" variable
> l2xo_regs_phys for thum2 mode and wrapping it in non-global sy
On 2 June 2014 14:41, Andrzej Hajda wrote:
> Hi Rahul,
>
> On 05/28/2014 08:11 AM, Rahul Sharma wrote:
>> System hangs when FIMD registers are accessed to disable
>> hardware overlays. This is because of the clocks which are
>> not enabled before register access.
>>
>> 'Hardware overlay disable' i
Hi Rahul,
On 05/28/2014 08:11 AM, Rahul Sharma wrote:
> System hangs when FIMD registers are accessed to disable
> hardware overlays. This is because of the clocks which are
> not enabled before register access.
>
> 'Hardware overlay disable' is cleaned from the FIMD probe.
>
> Signed-off-by: Ra
On Wednesday, May 28, 2014 5:26 AM, Christoffer Dall wrote:
> On Mon, May 12, 2014 at 06:40:44PM +0900, Jungseok Lee wrote:
> > This patch adds memory layout and translation lookup information about
> > 48-bit address space with 4K pages. The description is based on 4
> > levels of translation tabl
On Tuesday, May 27, 2014 11:03 PM, Christoffer Dall wrote:
> On Tue, May 27, 2014 at 03:53:49PM +0200, Christoffer Dall wrote:
> > On Mon, May 12, 2014 at 06:40:54PM +0900, Jungseok Lee wrote:
> > > This patch sets TCR_EL2.PS, VTCR_EL2.T0SZ and vttbr_baddr_mask in runtime,
> > > not compile time.
>
On Tuesday, May 27, 2014 10:54 PM, Christoffer Dall wrote:
> On Mon, May 12, 2014 at 06:40:54PM +0900, Jungseok Lee wrote:
> > This patch sets TCR_EL2.PS, VTCR_EL2.T0SZ and vttbr_baddr_mask in runtime,
> > not compile time.
> >
> > In ARMv8, EL2 physical address size (TCR_EL2.PS) and stage2 input a
49 matches
Mail list logo