Arnd Bergmann wrote:
>
> On Friday 21 November 2014, Kukjin Kim wrote:
> > The following changes since commit 0df1f2487d2f0d04703f142813d53615d62a1da4:
> >
> > Linux 3.18-rc3 (2014-11-02 15:01:51 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/
Arnd Bergmann wrote:
>
> On Thursday 27 November 2014, Kukjin Kim wrote:
> > Hi Arnd, Olof, Kevin
> >
> > Please pull this branch for exynos7 SoC into arm-soc.
> > Note Greg agreed to upstream via arm-soc tree.
>
> I don't really see any dependency on anything else here, so I
> wonder why you are
Arnd Bergmann wrote:
>
> On Thursday 27 November 2014, Kukjin Kim wrote:
> > Samsung arch/arm64 DT updates for v3.19
> >
> > - to support ARMv8 based exynos7 SoC
> > : add initial device tree and add pinctrl, PMU, mmc, i2c, rtc,
> > watchdog, and adc nodes for exynos7 SoC and exynos7 based
>
On Friday, November 28, 2014 11:38:35 AM Ulf Hansson wrote:
> In a step to move away from using genpd's name based APIs, such as the
> pm_genpd_add_subdomain_names(), provide an API to lookup an already
> initialized generic PM domain by its firmware node.
>
> This API would typically be a called
On Friday, November 28, 2014 09:30:01 AM Ulf Hansson wrote:
> It's quite common for PM domains to use PM clocks. Typically from SOC
> specific code, the per device PM clock list is created and
> pm_clk_suspend|resume() are invoked to handle clock gating/ungating.
>
> A step towards consolidation i
On 07/11/14 19:45, Kevin Hilman wrote:
> Sylwester Nawrocki writes:
>> On 04/11/14 07:44, amit daniel kachhap wrote:
>>> On Mon, Nov 3, 2014 at 11:53 PM, Kevin Hilman wrote:
"Rafael J. Wysocki" writes:
> On Monday, November 03, 2014 09:23:01 AM Amit Daniel Kachhap wrote:
[...]
>> Indeed
Russel,
On Fri, Nov 28, 2014 at 05:10:24PM +, Russell King - ARM Linux wrote:
> On Fri, Nov 28, 2014 at 10:53:30AM -0400, Eduardo Valentin wrote:
> > diff --git a/drivers/thermal/samsung/exynos_thermal_common.c
> > b/drivers/thermal/samsung/exynos_thermal_common.c
> > index 3f5ad25..d4eaa1b 1
On Fri, Nov 28, 2014 at 10:53:30AM -0400, Eduardo Valentin wrote:
> diff --git a/drivers/thermal/samsung/exynos_thermal_common.c
> b/drivers/thermal/samsung/exynos_thermal_common.c
> index 3f5ad25..d4eaa1b 100644
> --- a/drivers/thermal/samsung/exynos_thermal_common.c
> +++ b/drivers/thermal/samsu
In this patch, the cpu_cooling code checks for the usability of cpufreq
layer before proceeding with the CPU cooling device registration. The
main reason is: CPU cooling device is not usable if cpufreq cannot
switch frequencies.
Similar checks are spread in thermal drivers. Thus, the advantage now
On Fri, Nov 28, 2014 at 4:39 AM, Vivek Gautam wrote:
> On Fri, Nov 28, 2014 at 9:05 AM, Vivek Gautam
> wrote:
>>> On Mon, Nov 24, 2014 at 6:32 PM, Vivek Gautam
>>> wrote:
USB and Power regulator on Exynos7 require gpios available
in BUS1 pin controller block.
So adding the BUS1
trace).
Thanks for testing. Are you testing this with exynos_defconfig with no
other changes ? Can you please confirm from the bootlog that MCPM and
CCI are not being initialized.
Can you remove these 2 patches and on linux-next check if you are
getting aborts even with 5420_MCPM disabled.
Regar
I tested these 2 patches on Arndale Octa but there are no improvements.
I still got imprecise aborts (some not fatal and sometimes killing init
with full backtrace).
Tested on next-20141128. System booted from microSD (bootloader from
Linaro Ubuntu Saucy server image):
===
On Fri, Nov 28, 2014 at 03:14:04PM +0100, Krzysztof Kozlowski wrote:
> On pią, 2014-11-28 at 11:38 +, Mark Brown wrote:
> > This sort of thing is a sign that we're not saving much by moving the
> > parsing to the core and perhaps there's more flexiblity here...
> The driver receive callbacks
The arm-cci driver completes the probe sequence even if the cci node is
marked as disabled. Add a check in the driver to honour the cci status
in the device tree.
Signed-off-by: Abhilash Kesavan
---
drivers/bus/arm-cci.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/bus/arm-c
The arndale-octa board was giving "imprecise external aborts" during
boot-up with MCPM enabled. CCI enablement of the boot cluster was found
to be the cause of these aborts (possibly because the secure f/w was not
allowing it). Hence, disable CCI for the arndale-octa board.
Signed-off-by: Abhilash
Hi Nicolas,
On Thu, Nov 27, 2014 at 10:36 PM, Nicolas Pitre
wrote:
> On Thu, 27 Nov 2014, Abhilash Kesavan wrote:
>
>> Hi Kevin,
>>
>> On Thu, Nov 27, 2014 at 12:11 AM, Nicolas Pitre
>> wrote:
>> > On Wed, 26 Nov 2014, Kevin Hilman wrote:
>> >
>> >> Abhilash Kesavan writes:
>> >>
>> >> > Hi Kev
On Fri, Nov 28, 2014 at 12:54:27PM +0100, Krzysztof Kozlowski wrote:
> On pią, 2014-11-28 at 11:21 +, Mark Brown wrote:
> > On Fri, Nov 28, 2014 at 10:09:44AM +0100, Krzysztof Kozlowski wrote:
> > > I understand your concerns here however I didn't want to overengineer
> > > this. Is the same G
On pią, 2014-11-28 at 11:38 +, Mark Brown wrote:
> On Fri, Nov 28, 2014 at 11:30:55AM +0100, Krzysztof Kozlowski wrote:
> > On czw, 2014-11-27 at 18:43 +, Mark Brown wrote:
>
> > > Why do we need some special magic operation for GPIO based enables
> > > that's separate to any other enable
On pią, 2014-11-28 at 15:04 +0100, Linus Walleij wrote:
> On Wed, Nov 26, 2014 at 3:24 PM, Krzysztof Kozlowski
> wrote:
>
> > The audio subsystem on Exynos 5420 has separate clocks and GPIO. To
> > operate properly on GPIOs the main block clock 'mau_epll' must be
> > enabled.
> >
> > This was obs
On Wed, Nov 26, 2014 at 3:24 PM, Krzysztof Kozlowski
wrote:
> The audio subsystem on Exynos 5420 has separate clocks and GPIO. To
> operate properly on GPIOs the main block clock 'mau_epll' must be
> enabled.
>
> This was observed on Peach Pi/Pit and Arndale Octa (after enabling i2s0)
> after int
On Fri, Nov 28, 2014 at 01:18:25PM +, Chanwoo Choi wrote:
> Dear Mark,
>
> On 11/27/2014 08:18 PM, Mark Rutland wrote:
> > On Thu, Nov 27, 2014 at 07:35:13AM +, Chanwoo Choi wrote:
> >> This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC
> >> based on Octal core CPUs (quad
Dear Marc,
On 11/27/2014 07:26 PM, Marc Zyngier wrote:
> On 27/11/14 07:35, Chanwoo Choi wrote:
>> This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC
>> based on Octal core CPUs (quad Cortex-A57 and quad Cortex-A53).
>>
>> Cc: Kukjin Kim
>> Cc: Mark Rutland
>> Cc: Arnd Bergmann
On 28 November 2014 at 18:44, Eduardo Valentin wrote:
> Well, I wouldn't say unfortunately, but fortunately! :-)
+1 :)
> However, I would prefer, at least to what comes to deferring, to update
> the drivers altogether with the inclusion of the check in cpu cooling.
> This way the change in behav
Dear Mark,
On 11/27/2014 08:18 PM, Mark Rutland wrote:
> On Thu, Nov 27, 2014 at 07:35:13AM +, Chanwoo Choi wrote:
>> This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC
>> based on Octal core CPUs (quad Cortex-A57 and quad Cortex-A53).
>>
>> Cc: Kukjin Kim
>> Cc: Mark Rutlan
Hello Folks,
On Fri, Nov 28, 2014 at 11:18:24AM +0100, Lukasz Majewski wrote:
> On Fri, 28 Nov 2014 13:35:49 +0530
> Viresh Kumar wrote:
>
> > On 27 November 2014 at 19:42, Eduardo Valentin
> > wrote:
> > > (I'm sorry VireshK, I am still using my normal practice) :-)
> >
> > That's fine :)
>
On Thursday 27 November 2014, Kukjin Kim wrote:
> Samsung arch/arm64 DT updates for v3.19
>
> - to support ARMv8 based exynos7 SoC
> : add initial device tree and add pinctrl, PMU, mmc, i2c, rtc,
> watchdog, and adc nodes for exynos7 SoC and exynos7 based
> espresso board.
>
> NOTE that
Hello Sjoerd,
On 11/28/2014 01:06 PM, Sjoerd Simons wrote:
> CONFIG_FHANDLE is required by systemd, which is the default init system
> in more and more distributions. So lets enable it for Exynos as well
> (it's already enabled in multi_v7_defconfig)
>
> Signed-off-by: Sjoerd Simons
> ---
> arc
On Thursday 27 November 2014, Kukjin Kim wrote:
> Samsung 3rd DT updates for v3.19
>
> - exynos3250
> : remove unused bootargs on exynos3250-rinato
> : add new board dt file for exynos3250-monk
> - exynos4
> : add missing clock for MFC
> : specify default clocks for camera
> - exynos4x12
>
On Thursday 27 November 2014, Kukjin Kim wrote:
> Hi Arnd, Olof, Kevin
>
> Please pull this branch for exynos7 SoC into arm-soc.
> Note Greg agreed to upstream via arm-soc tree.
I don't really see any dependency on anything else here, so I
wonder why you are sending it to me, but I assume there
On Thursday 27 November 2014, Kukjin Kim wrote:
> The following changes since commit c645a598f99768e6cc82129081458dfdd0c273b7:
>
> ARM: EXYNOS: Call regulator core suspend prepare and finish functions
> (2014-11-21 22:49:47 +0900)
>
> are available in the git repository at:
>
> git://git.ker
On Friday 21 November 2014, Kukjin Kim wrote:
> Samsung exynos updates in arch/arm/mach-exynos/ for v3.19
>
> - add SOC_EXYNOS4415 config to be used in audio driver
> - add support platform driver for exynos PMU
> - move PMU specific definitions from common.h to exynos-pmu.h
> - for exynos5420, ad
On Friday 21 November 2014, Kukjin Kim wrote:
> Samsung 2nd DT updates for v3.19
>
> - add micro SD card SDHCI node for exynos4412-trats
> - add exynos4415 DT
> - add exynos3250-rinato DT and sleep mode support
>
> Note: based on previous tags/samsung-dt for v3.19
Pulled into next/dt, thanks!
On Friday 21 November 2014, Kukjin Kim wrote:
> The following changes since commit 0df1f2487d2f0d04703f142813d53615d62a1da4:
>
> Linux 3.18-rc3 (2014-11-02 15:01:51 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
>
On Friday 21 November 2014, Kukjin Kim wrote:
> The following changes since commit 13cfa6c4f7facfc690ba9e99ec382c151fddaced:
>
> ARM: EXYNOS: Fix CPU idle clock down after CPU off (2014-10-21
> 00:06:22 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux
On Friday 21 November 2014, Kukjin Kim wrote:
>
> Samsung non-critical-fixes for v3.19
>
> - fix typo in static struct name "exynos5_list_diable_wfi_wfe"
> : it should be "exynos5_list_disable_wfi_wfe"
Pulled into next/fixes-non-c
Am 28.11.2014 um 13:06 schrieb Sjoerd Simons:
> CONFIG_FHANDLE is required by systemd, which is the default init system
> in more and more distributions. So lets enable it for Exynos as well
> (it's already enabled in multi_v7_defconfig)
>
> Signed-off-by: Sjoerd Simons
Reviewed-by: Andreas Färb
CONFIG_FHANDLE is required by systemd, which is the default init system
in more and more distributions. So lets enable it for Exynos as well
(it's already enabled in multi_v7_defconfig)
Signed-off-by: Sjoerd Simons
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff
Am 28.11.2014 um 12:59 schrieb Linus Walleij:
> On Sat, Nov 22, 2014 at 11:26 PM, Andreas Färber wrote:
>
>> From: Hakjoo Kim
>>
>> Add Samsung EXYNOS5410 SoC specific data to enable pinctrl
>> support for all platforms based on EXYNOS5410.
>>
>> Signed-off-by: Hakjoo Kim
>> [AF: Rebased onto E
On Sat, Nov 22, 2014 at 11:26 PM, Andreas Färber wrote:
> From: Hakjoo Kim
>
> Add Samsung EXYNOS5410 SoC specific data to enable pinctrl
> support for all platforms based on EXYNOS5410.
>
> Signed-off-by: Hakjoo Kim
> [AF: Rebased onto Exynos5260 and irq_chip consolidation]
> Signed-off-by: An
On pią, 2014-11-28 at 11:21 +, Mark Brown wrote:
> On Fri, Nov 28, 2014 at 10:09:44AM +0100, Krzysztof Kozlowski wrote:
>
> > I understand your concerns here however I didn't want to overengineer
> > this. Is the same GPIO (on more complex PMICs) used in different
> > contexts? Like enable con
This patch series adds Display support for exynos3250 Rinato board.
For this, it adds fimd, MIPI-DSI and Panel device nodes to
exynos3250-rinato dts file, and adds a s6e63j0x03 Amoled panel device
driver which is based on MIPI-DSI bus.
Inki Dae (3):
ARM: dts: add fimd device support for exynos32
This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD Panel driver
which uses mipi_dsi bus to communicate with Panel.
Signed-off-by: Inki Dae
Acked-by: Kyungmin Park
---
drivers/gpu/drm/panel/Kconfig|6 +
drivers/gpu/drm/panel/Makefile |1 +
drivers/gpu/drm/panel/pa
This patch adds MIPI-DSI and MIPI-DSI based S6E63J0X03 AMOLED panel
device nodes for Exynos3250 Rinato board.
Signed-off-by: Inki Dae
Acked-by: Kyungmin Park
---
arch/arm/boot/dts/exynos3250-rinato.dts | 59 +++
1 file changed, 59 insertions(+)
diff --git a/arch/a
On Fri, Nov 28, 2014 at 11:30:55AM +0100, Krzysztof Kozlowski wrote:
> On czw, 2014-11-27 at 18:43 +, Mark Brown wrote:
> > Why do we need some special magic operation for GPIO based enables
> > that's separate to any other enable operation? This seems really
> > confusing, if the constraint
This patch adds fimd device node which is a display controller
for Exynos3250 Rinato board.
Signed-off-by: Inki Dae
Acked-by: Kyungmin Park
---
arch/arm/boot/dts/exynos3250-rinato.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts
b/a
On Fri, 28 Nov 2014 13:35:49 +0530
Viresh Kumar wrote:
> On 27 November 2014 at 19:42, Eduardo Valentin
> wrote:
> > (I'm sorry VireshK, I am still using my normal practice) :-)
>
> That's fine :)
>
> > diff --git a/drivers/thermal/cpu_cooling.c
> > b/drivers/thermal/cpu_cooling.c index 1ab001
This series is based on exynos-drm-next branch of Inki Dae's tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
DECON(Display and Enhancement Controller) is the new IP
in exynos7 SOC for generating video signals using pixel data.
DECON driver can be used to drive 2 diff
On Fri, Nov 28, 2014 at 10:09:44AM +0100, Krzysztof Kozlowski wrote:
> I understand your concerns here however I didn't want to overengineer
> this. Is the same GPIO (on more complex PMICs) used in different
> contexts? Like enable control and something more in the same time?
Yes, and it's often
check error status for drm_iommu_attach_device() and make sure
it propagates till the caller.
Signed-off-by: Ajay Kumar
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
ctx->drm_dev is unnecessary since it can be easily
accessed via ctx->manager->drm_dev, cleaning it up.
Signed-off-by: Ajay Kumar
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/exynos/e
On Friday 28 November 2014 09:55:53 Marek Szyprowski wrote:
> On 2014-11-27 23:51, Russell King - ARM Linux wrote:
> > On Mon, Nov 17, 2014 at 12:48:22PM +0100, Marek Szyprowski wrote:
> >>
> >> Changes in this version tested on Exynos4412-based TRATS2 and OdroidU3+
> >> boards (both with secure fi
In a step to move away from using genpd's name based APIs, such as the
pm_genpd_add_subdomain_names(), provide an API to lookup an already
initialized generic PM domain by its firmware node.
This API would typically be a called from SOC specific code, to fetch a
handle to the domain. Especially co
On czw, 2014-11-27 at 18:43 +, Mark Brown wrote:
> On Thu, Nov 27, 2014 at 12:20:50PM +0100, Krzysztof Kozlowski wrote:
> > Use ena_gpio from regulator constraints (filled by parsing generic
> > bindings) to initialize the GPIO enable control. Support also the old
> > way: ena_gpio supplied in
On czw, 2014-11-27 at 18:45 +, Mark Brown wrote:
> On Thu, Nov 27, 2014 at 12:20:49PM +0100, Krzysztof Kozlowski wrote:
>
> > + constraints->ena_gpio = of_get_named_gpio_flags(np, "ena-gpios", 0,
> > + &gpio_flags);
> > + if (gpio_is_valid(
On czw, 2014-11-27 at 18:30 +, Mark Brown wrote:
> On Thu, Nov 27, 2014 at 12:20:48PM +0100, Krzysztof Kozlowski wrote:
>
> > +- ena-gpios: GPIO to use for enable control. Actual implementation depends
> > + on regulator driver. The bindings documentation for given driver
> > describes
> > +
Hello,
On 2014-11-27 23:51, Russell King - ARM Linux wrote:
On Mon, Nov 17, 2014 at 12:48:22PM +0100, Marek Szyprowski wrote:
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 ste
On Thu, Nov 27, 2014 at 7:50 PM, Ulf Hansson wrote:
> On 25 November 2014 at 09:48, amit daniel kachhap
> wrote:
>> On Tue, Nov 25, 2014 at 1:05 PM, Ulf Hansson wrote:
>>> On 24 November 2014 at 14:04, Amit Daniel Kachhap
>>> wrote:
This API may be needed to set the power domain parent/chi
Changes in v3:
-Fixed comments from Rafael for patch 1.
-Change name of define, affects all patches.
Changes in v2:
-Small fixes in patch 1.
It's quite common for PM domains to use PM clocks. Typically from SOC specific
code, the per device PM clock list is created and pm
Instead of using the dev_ops ->stop|start() callbacks for genpd, let's
convert to use genpd's flag field and set it to GENPD_PM_CLK.
Signed-off-by: Ulf Hansson
---
Changes in v3:
Convert to renamed define.
Changes in v2:
None.
---
arch/arm/mach-shmobile/pm-rmobile.c | 3 +--
1
It's quite common for PM domains to use PM clocks. Typically from SOC
specific code, the per device PM clock list is created and
pm_clk_suspend|resume() are invoked to handle clock gating/ungating.
A step towards consolidation is to integrate PM clock support into
genpd, which is what this patch d
Instead of using the dev_ops ->stop|start() callbacks for genpd, let's
convert to use genpd's flag field and set it to GENPD_PM_CLK.
Signed-off-by: Ulf Hansson
---
Changes in v3:
Convert to renamed define.
Changes in v2:
None.
---
arch/arm/mach-shmobile/pm-r8a7779.c | 3 +--
1
On 27 November 2014 at 19:42, Eduardo Valentin wrote:
> (I'm sorry VireshK, I am still using my normal practice) :-)
That's fine :)
> diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
> index 1ab0018..bed3fa2 100644
> --- a/drivers/thermal/cpu_cooling.c
> +++ b/drivers/t
62 matches
Mail list logo
