On 28.07.2015 06:28, Alexey Klimov wrote:
Speedup MCT operation on odroid-xu3 dev board by using
coprocessor 64-bit counter instead of reading same counter
located in mmio region.
Tested on Odroid-xu3.
Signed-off-by: Alexey Klimov klimov.li...@gmail.com
---
Hi,
On Monday, July 27, 2015 02:07:54 PM Viresh Kumar wrote:
On 09-07-15, 17:43, Bartlomiej Zolnierkiewicz wrote:
diff --git a/include/linux/cpufreq-dt.h b/include/linux/cpufreq-dt.h
index 0414009..483ca1b 100644
--- a/include/linux/cpufreq-dt.h
+++ b/include/linux/cpufreq-dt.h
@@
On 27-07-15, 13:14, Bartlomiej Zolnierkiewicz wrote:
Sorry but you don't seem to understand the issue.
:)
No, I did. I understand that if someone uses opp bindings today with
some entries as turbo OPPs, cpufreq will use them as normal
frequencies. And that may harm the board.
BUT, opp-v2 code
On Monday, July 27, 2015 05:03:40 PM Viresh Kumar wrote:
On 27-07-15, 13:01, Bartlomiej Zolnierkiewicz wrote:
First of all, please don't be angry :).. We can discuss and get things
sorted out ...
OK :)
This change was in the original patch posted in April:
Hi,
On Monday, July 27, 2015 04:05:21 PM Viresh Kumar wrote:
On 27-07-15, 12:24, Bartlomiej Zolnierkiewicz wrote:
Have you read my explanation of the issue?
With your OPP-v2 patches cpufreq-dt picks turbo frequencies and uses
them as normal ones.
(More at:
On 27-07-15, 13:58, Bartlomiej Zolnierkiewicz wrote:
Thank you. This is exactly the case here (I would like to get
Exynos4x12 conversion to use cpufreq-dt + exynos-cpufreq removal
in v4.3 if possible and adding new DT bindings will most likely
slow down the process considerably).
Heh, I
On 27-07-15, 13:01, Bartlomiej Zolnierkiewicz wrote:
First of all, please don't be angry :).. We can discuss and get things
sorted out ...
This change was in the original patch posted in April:
https://lkml.org/lkml/2015/4/10/646
Yeah, and I already apologized for missing the request :)
On Monday, July 27, 2015 05:06:41 PM Viresh Kumar wrote:
On 27-07-15, 13:14, Bartlomiej Zolnierkiewicz wrote:
Sorry but you don't seem to understand the issue.
:)
No, I did. I understand that if someone uses opp bindings today with
some entries as turbo OPPs, cpufreq will use them as
This patch moves irq-uart header file into mach-s3c64xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/mach-s3c64xx/common.c | 2 +-
arch/arm/{plat-samsung/include/plat = mach-s3c64xx}/irq-uart.h | 3 +--
This patch moves onenand-core header file into mach-s3c64xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/{plat-samsung/include/plat = mach-s3c64xx}/onenand-core.h | 2 --
arch/arm/mach-s3c64xx/s3c6400.c
This patch moves keypad header file into mach-s3c64xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/{plat-samsung/include/plat = mach-s3c64xx}/keypad.h | 0
arch/arm/mach-s3c64xx/mach-crag6410.c | 2 +-
This patch moves backlight header file into mach-s3c64xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/{plat-samsung/include/plat = mach-s3c64xx}/backlight.h | 3 +--
arch/arm/mach-s3c64xx/dev-backlight.c| 3
This patch moves watchdog-reset header file into mach-s3c64xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/mach-s3c64xx/common.c| 2 +-
arch/arm/mach-s3c64xx/mach-s3c64xx-dt.c
This patch moves regs-srom header file into mach-exynos.
c: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/{plat-samsung/include/plat = mach-exynos}/regs-srom.h | 3 +--
arch/arm/mach-exynos/suspend.c | 4 ++--
This patch moves regs-usb-hsotg-phy header file into mach-s3c64xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
.../{plat-samsung/include/plat = mach-s3c64xx}/regs-usb-hsotg-phy.h | 3 +--
arch/arm/mach-s3c64xx/setup-usb-phy.c
This patch moves fb-core header file into mach-s3c24xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/{plat-samsung/include/plat = mach-s3c24xx}/fb-core.h | 2 --
arch/arm/mach-s3c24xx/s3c2416.c| 2 +-
This patch moves spi-core header file into mach-s3c24xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/mach-s3c24xx/s3c2416.c | 2 +-
arch/arm/mach-s3c24xx/s3c2443.c | 2 +-
This patch moves ata-core header file into mach-s3c64xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/{plat-samsung/include/plat = mach-s3c64xx}/ata-core.h | 3 +--
arch/arm/mach-s3c64xx/s3c6410.c | 2 +-
This patch moves nand-core header file into mach-s3c24xx.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/{plat-samsung/include/plat = mach-s3c24xx}/nand-core.h | 3 +--
arch/arm/mach-s3c24xx/s3c2412.c | 2
Since keypad-core header is not used, this patch removes it.
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
Cc: Joonyoung Shim jy0922.s...@samsung.com
Signed-off-by: Kukjin Kim kg...@kernel.org
---
arch/arm/plat-samsung/include/plat/keypad-core.h | 31
1 file changed,
On Monday, July 27, 2015 at 11:46:25 AM, Michal Suchanek wrote:
On 24 July 2015 at 10:34, Marek Vasut ma...@denx.de wrote:
On Thursday, July 23, 2015 at 07:03:47 PM, Michal Suchanek wrote:
Hi!
[...]
It's probably slower to set up DMA for 2-byte commands but it might
work
On Sat, Jul 25, 2015 at 8:34 AM, Gregory CLEMENT
gregory.clem...@free-electrons.com wrote:
Hi Rob,
On 12/07/2015 16:26, Rob Herring wrote:
set_irq_flags is ARM specific with custom flags which have genirq
equivalents. Convert drivers to use the genirq interfaces directly, so we
can kill off
Hi all,
year(s) ago it was discovered that MCT timer and ARM architectured
timer
are the same hardware with different interface. Here [1].
I followed mail-list discussions about removing MCT and using arch
timer for Exynos5-based SoCs but things aren't moving at least latest
upstream kernel on
It was discovered that 64-bit mmio MCT counter holds
the same value as ARM arch timer 64-bit physical counter.
Even more: arch timer and MCT are same underlying hardware
timer.
Patch adds code to MCT to allow it to read 64-bit counter
from coprocessor cp15 registers since it's way more
faster
Speedup MCT operation on odroid-xu3 dev board by using
coprocessor 64-bit counter instead of reading same counter
located in mmio region.
Tested on Odroid-xu3.
Signed-off-by: Alexey Klimov klimov.li...@gmail.com
---
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 4
1 file changed, 4
Signed-off-by: Alexey Klimov klimov.li...@gmail.com
---
.../devicetree/bindings/timer/samsung,exynos4210-mct.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.txt
On 27 July 2015 at 19:43, Marek Vasut ma...@denx.de wrote:
On Monday, July 27, 2015 at 11:46:25 AM, Michal Suchanek wrote:
On 24 July 2015 at 10:34, Marek Vasut ma...@denx.de wrote:
On Thursday, July 23, 2015 at 07:03:47 PM, Michal Suchanek wrote:
Ok, so here is some summary.
I have a NOR
set_irq_flags is ARM specific with custom flags which have genirq
equivalents. Convert drivers to use the genirq interfaces directly, so we
can kill off set_irq_flags. The translation of flags is as follows:
IRQF_VALID - !IRQ_NOREQUEST
IRQF_PROBE - !IRQ_NOPROBE
IRQF_NOAUTOEN - IRQ_NOAUTOEN
For
set_irq_flags is ARM specific with custom flags which have genirq
equivalents. Convert drivers to use the genirq interfaces directly, so we
can kill off set_irq_flags. The translation of flags is as follows:
IRQF_VALID - !IRQ_NOREQUEST
IRQF_PROBE - !IRQ_NOPROBE
IRQF_NOAUTOEN - IRQ_NOAUTOEN
For
set_irq_flags is ARM specific with custom flags which have genirq
equivalents. Convert drivers to use the genirq interfaces directly, so we
can kill off set_irq_flags. The translation of flags is as follows:
IRQF_VALID - !IRQ_NOREQUEST
IRQF_PROBE - !IRQ_NOPROBE
IRQF_NOAUTOEN - IRQ_NOAUTOEN
For
Hello Michal,
The patch looks good to me, just one small comment below.
On Mon, Jul 27, 2015 at 10:11 PM, Michal Suchanek hramr...@gmail.com wrote:
Although there is only one choice of chipselect it is necessary to
specify it. The driver cannot claim the gpio otherwise.
Signed-off-by: Michal
On 28.07.2015 06:24, Javier Martinez Canillas wrote:
Hello Michal,
The patch looks good to me, just one small comment below.
On Mon, Jul 27, 2015 at 10:11 PM, Michal Suchanek hramr...@gmail.com wrote:
Although there is only one choice of chipselect it is necessary to
specify it. The
On 27.07.2015 23:57, Kukjin Kim wrote:
This patch moves regs-srom header file into mach-exynos.
Hi,
Minor nits:
1. Could you trim it and remove unnecessary empty line before description?
2. Could you answer in commit message: Why? Why are you moving the headers?
c: Krzysztof Kozlowski
Hi,
On Monday, July 27, 2015 02:05:31 PM Viresh Kumar wrote:
$subject is a bit wrong, we aren't fixing any issue here. We are
supporting a new feature and so it should be like:
Have you read my explanation of the issue?
With your OPP-v2 patches cpufreq-dt picks turbo frequencies and uses
Hello Mark,
On 07/20/2015 12:12 PM, Javier Martinez Canillas wrote:
Hello Lee,
Thanks a lot for your feedback.
On 07/20/2015 10:10 AM, Lee Jones wrote:
On Fri, 17 Jul 2015, Javier Martinez Canillas wrote:
The regulator-compatible property from the regulator DT binding was
deprecated.
On Mon, Jul 27, 2015 at 12:28:07PM +0200, Javier Martinez Canillas wrote:
On 07/20/2015 12:12 PM, Javier Martinez Canillas wrote:
This PMIC uses a single I2C address for all the regulators and these are
controlled by writing to different I2C register addresses. So the regulator
nodes don't
Hello Mark,
On 07/27/2015 12:33 PM, Mark Brown wrote:
On Mon, Jul 27, 2015 at 12:28:07PM +0200, Javier Martinez Canillas wrote:
On 07/20/2015 12:12 PM, Javier Martinez Canillas wrote:
This PMIC uses a single I2C address for all the regulators and these are
controlled by writing to different
$subject is a bit wrong, we aren't fixing any issue here. We are
supporting a new feature and so it should be like:
cpufreq: Mark boost frequencies based on OPP's turbo mode
On 09-07-15, 17:43, Bartlomiej Zolnierkiewicz wrote:
Turbo modes should be marked with CPUFREQ_BOOST_FREQ flag in
the
On 09-07-15, 17:43, Bartlomiej Zolnierkiewicz wrote:
+bool dev_pm_opp_get_turbo_mode_setting(struct dev_pm_opp *opp)
This should be named dev_pm_opp_is_turbo().
--
viresh
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to
On 09-07-15, 17:43, Bartlomiej Zolnierkiewicz wrote:
diff --git a/include/linux/cpufreq-dt.h b/include/linux/cpufreq-dt.h
index 0414009..483ca1b 100644
--- a/include/linux/cpufreq-dt.h
+++ b/include/linux/cpufreq-dt.h
@@ -17,6 +17,7 @@ struct cpufreq_dt_platform_data {
* clock.
On 24 July 2015 at 10:34, Marek Vasut ma...@denx.de wrote:
On Thursday, July 23, 2015 at 07:03:47 PM, Michal Suchanek wrote:
Hi!
[...]
It's probably slower to set up DMA for 2-byte commands but it might
work nonetheless.
It is, the overhead will be considerable. It might help the
41 matches
Mail list logo
