On Tue, Jan 7, 2014 at 8:52 PM, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 07 January 2014, Linus Walleij wrote:
It appears that these problems appear if you explicitly
enable the DT board support, can't we just put that into
the defconfig then, so we don't miss such things?
I don't
Hello Wim Van Sebroeck,
I believe that I addressed all the comments given by reviewers.
So can you look into this series and take necessary action..?
Best Wishes,
Leela Krishna.
On Wed, Dec 18, 2013 at 9:01 PM, Leela Krishna Amudala
l.kris...@samsung.com wrote:
Hello Wim Van Sebroeck,
Can
On Wed, Jan 08, 2014 at 10:15:25AM +0900, Inki Dae wrote:
2014/1/8 Daniel Vetter dan...@ffwll.ch:
Oops, looks like something slipped past between me making the patches and
them getting merged. Thanks for taking care of this. Both patches are
These patches already were posted by Seung-Woo
Hello,
On 2014년 01월 08일 21:03, Mark Brown wrote:
On Wed, Jan 08, 2014 at 10:15:25AM +0900, Inki Dae wrote:
2014/1/8 Daniel Vetter dan...@ffwll.ch:
Oops, looks like something slipped past between me making the patches and
them getting merged. Thanks for taking care of this. Both patches are
On Tue, Dec 31, 2013 at 02:00:39PM +0530, Sachin Kamat wrote:
fiq.h contains only a function declaration and is not used by anyone
else. Move the declaration to the driver header file and remove the
unnecessary platform dependency from the driver.
Applied, thanks.
signature.asc
Description:
The erratum-773769 occurs on Arm Coretex-A15 (rev r2p0),
when L2 Data Ram latency is set to 4 cycles or more; or
when ACP is in use, or with L2 Data RAM slice configured.
Therefore, the effective latency as calculated in Table 7-2 of
Cotex-A15 (rev r2p0) trm should be 3 cycles or less.
On
Hi John,
On Sat, Jan 4, 2014 at 3:30 AM, John Dulaney jdula...@redhat.com wrote:
I build 3.13-rc6 for exynso-5250. After installing the kernel and
rebooting my machine, everything worked (lpae out of the box, even)
except for usb; I rebuilt the kernel a couple of times, poking at
USB config
On Wed, Jan 08, 2014 at 01:33:11PM +, Vivek Gautam wrote:
The erratum-773769 occurs on Arm Coretex-A15 (rev r2p0),
when L2 Data Ram latency is set to 4 cycles or more; or
when ACP is in use, or with L2 Data RAM slice configured.
Therefore, the effective latency as calculated in Table 7-2
On Wednesday 08 January 2014, Arnd Bergmann wrote:
On Wednesday 08 January 2014, Linus Walleij wrote:
On Tue, Jan 7, 2014 at 8:52 PM, Arnd Bergmann a...@arndb.de wrote:
b
I was wrong about this, too much in my head. As Tomasz says,
pinctrl-samsung can be used, but mandates that everything
WIll,
Thanks for your comments!
On Wed, Jan 8, 2014 at 6:35 AM, Will Deacon will.dea...@arm.com wrote:
On Wed, Jan 08, 2014 at 01:33:11PM +, Vivek Gautam wrote:
The erratum-773769 occurs on Arm Coretex-A15 (rev r2p0),
when L2 Data Ram latency is set to 4 cycles or more; or
when ACP is in
On Wednesday 08 of January 2014 08:31:38 Mike Turquette wrote:
Quoting Tomasz Figa (2014-01-02 07:22:12)
On Tuesday 31 of December 2013 11:42:15 Mike Turquette wrote:
Quoting Tomasz Figa (2013-12-12 08:07:13)
This series intends to improve clock provider impementation of max77686
On Tue, Jan 07, 2014 at 07:27:49PM +0100, Linus Walleij wrote:
I think the S3C driver is a different piece of hardware unfortunately.
It's not, the IP is basically the same - the difference between s3c, s5p
and Exynos is a marketing one, Samsung have generally just reused IP
where that is
Quoting Tomasz Figa (2013-12-05 02:09:10)
Hi,
On Saturday 09 of November 2013 03:17:34 Tomasz Figa wrote:
From: Tomasz Figa t.f...@samsung.com
This patch adds an entry for Samsung SoC clock drivers located under
drivers/clk/samsung/ directory, with me taking the maintainer role.
I believe Lee has already applied this one, but in future, to avoid such
confusion, if it's more convenient for you, I can send you any clock
series as pull requests.
Me? I haven't applied any clk patches.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source
Hi Kishon,
Thank you for your review.
From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
Sent: Monday, January 06, 2014 11:24 AM
Hi,
On Friday 20 December 2013 06:54 PM, Kamil Debski wrote:
This the alternative version of the support for Exynos 421x USB 2.0
PHY in the Generic PHY
* Heikki Krogerus heikki.kroge...@linux.intel.com [131209 07:10]:
Provide a complete association for the phy and it's user
(musb) with the new phy_lookup_table.
This seems safe to queue via the USB list:
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Heikki Krogerus
Hi,
From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
Sent: Monday, January 06, 2014 11:12 AM
Hi,
On Friday 20 December 2013 06:54 PM, Kamil Debski wrote:
Add a new driver for the Exynos USB 2.0 PHY. The new driver uses the
generic PHY framework. The driver includes support for the
Quoting Lee Jones (2014-01-08 09:15:44)
I believe Lee has already applied this one, but in future, to avoid such
confusion, if it's more convenient for you, I can send you any clock
series as pull requests.
Me? I haven't applied any clk patches.
I have taken patches 1-7 into clk-next
On Wednesday 08 of January 2014 09:59:39 Mike Turquette wrote:
Quoting Lee Jones (2014-01-08 09:15:44)
I believe Lee has already applied this one, but in future, to avoid such
confusion, if it's more convenient for you, I can send you any clock
series as pull requests.
Me? I haven't
Hi Mike,
Please consider pulling following Samsung Clock changes for v3.14.
The following changes since commit 2bb00c68e094271b79deac993893461cc051b721:
Merge branch 'samsung-fixes' into samsung-next-base (2013-12-30 18:15:23
+0100)
are available in the git repository at:
On Wed, Jan 08, 2014 at 08:21:21AM -0800, Doug Anderson wrote:
WIll,
Thanks for your comments!
On Wed, Jan 8, 2014 at 6:35 AM, Will Deacon will.dea...@arm.com wrote:
NAK. Whilst I appreciate that you may not be able to fix your bootloader,
this isn't the right change to make in the
Hi,
On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Wed, Jan 08, 2014 at 08:21:21AM -0800, Doug Anderson wrote:
WIll,
Thanks for your comments!
On Wed, Jan 8, 2014 at 6:35 AM, Will Deacon will.dea...@arm.com wrote:
NAK. Whilst I appreciate that
Hi Doug,
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998 seconds and
reporting a timeout of
Hi Doug,
On modern SoCs the watchdog timer is parented on a clock that doesn't
change every time we have a cpufreq change. That means we don't need
to constantly adjust the watchdog timer, so avoid registering for and
dealing with cpufreq transitions unless we've actually got
Hi,
On 01/01/2014 12:39 AM, m silverstri wrote:
Hi,
I am looking for an example which uses samsung jpeg v4l2 mem2mem driver.
For example the 'Exynos4 JPEG codec v4l2 driver' described here
http://lwn.net/Articles/468547
I am new to linux v4l2 driver. I am looking for example to pass an
input
On Wed, Jan 08, 2014 at 11:43:29AM -0800, Doug Anderson wrote:
Olof came up with the idea that you could update the RW firmware
(affects initial boot) and then cache away the value and restore it in
the kernel after resume. That would still require a kernel patch but
perhaps a less
On Wed, 8 Jan 2014, Doug Anderson wrote:
Hi,
On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
No, we're saying to put the work-around in the boot loader, not the kernel.
Unfortunately the resume path of the firmware runs from Read Only
firmware code (yes, it sucks), so it's
On Wed, 8 Jan 2014, Doug Anderson wrote:
On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
We've been through these arguments many times, you're not the first to
raise it, and we've decided upon the policy. We want as _few_ work-
arounds in the
Nicolas,
On Wed, Jan 8, 2014 at 12:58 PM, Nicolas Pitre n...@fluxnic.net wrote:
On Wed, 8 Jan 2014, Doug Anderson wrote:
On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
We've been through these arguments many times, you're not the first to
raise it,
Russell,
On Wed, Jan 8, 2014 at 1:02 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Wed, Jan 08, 2014 at 11:43:29AM -0800, Doug Anderson wrote:
Olof came up with the idea that you could update the RW firmware
(affects initial boot) and then cache away the value and restore it in
Nicolas,
On Wed, Jan 8, 2014 at 1:08 PM, Nicolas Pitre n...@fluxnic.net wrote:
On Wed, 8 Jan 2014, Doug Anderson wrote:
Hi,
On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
No, we're saying to put the work-around in the boot loader, not the kernel.
Unfortunately the resume path
On Wednesday 08 of January 2014 13:54:32 Mike Turquette wrote:
Quoting Tomasz Figa (2014-01-08 10:04:57)
On Wednesday 08 of January 2014 09:59:39 Mike Turquette wrote:
Quoting Lee Jones (2014-01-08 09:15:44)
I believe Lee has already applied this one, but in future, to avoid
such
Hi,
I am looking at the source code for samsung exynos driver in here:
https://android.googlesource.com/kernel/exynos/+/android-exynos-3.4/drivers/media/video/exynos/jpeg/jpeg_enc.c#
What I don't understand it while it advertise it can support multiple
plane format (set
On Wednesday 08 of January 2014 14:07:49 Mike Turquette wrote:
Quoting Tomasz Figa (2014-01-08 11:13:38)
Hi Mike,
Please consider pulling following Samsung Clock changes for v3.14.
The following changes since commit 2bb00c68e094271b79deac993893461cc051b721:
Hi Tomasz,
Commit
Quoting Tomasz Figa (2014-01-08 14:43:24)
On Wednesday 08 of January 2014 14:07:49 Mike Turquette wrote:
Quoting Tomasz Figa (2014-01-08 11:13:38)
Hi Mike,
Please consider pulling following Samsung Clock changes for v3.14.
The following changes since commit
Quoting Mike Turquette (2014-01-08 14:59:43)
Quoting Tomasz Figa (2014-01-08 14:43:24)
On Wednesday 08 of January 2014 14:07:49 Mike Turquette wrote:
Quoting Tomasz Figa (2014-01-08 11:13:38)
Hi Mike,
Please consider pulling following Samsung Clock changes for v3.14.
This patch adds support for SCALER device which is a new device
for scaling, blending, color fill and color space conversion
on EXYNOS5410 and EXYNOS5420 SoCs.
This device supports the followings as key feature.
input image format
- YCbCr420 2P(UV/VU), 3P
- YCbCr422
This patch adds the DT binding documentation for the
Exynos5420/5410 based SCALER device driver.
Signed-off-by: Shaik Ameer Basha shaik.am...@samsung.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
.../devicetree/bindings/media/exynos5-scaler.txt | 22
1
This patch adds the core functionality for the SCALER driver.
Signed-off-by: Shaik Ameer Basha shaik.am...@samsung.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
drivers/media/platform/exynos-scaler/scaler.c | 1231 +
This patch adds the Makefile and memory to memory (m2m) interface
functionality for the SCALER driver.
[arun...@samsung.com: fix compilation issues]
Signed-off-by: Shaik Ameer Basha shaik.am...@samsung.com
Signed-off-by: Arun Kumar K arun...@samsung.com
Reviewed-by: Sylwester Nawrocki
Hello Tomasz,
On 8 January 2014 06:02, Tomasz Figa tomasz.f...@gmail.com wrote:
On Tuesday 07 of January 2014 17:21:49 Naveen Krishna Ch wrote:
From: Naveen Krishna Chatradhi ch.nav...@samsung.com
this patch adds the device tree nodes for SSS module found on Exynos5420
nit: Sentences in
Hello Tomasz,
On 8 January 2014 06:00, Tomasz Figa tomasz.f...@gmail.com wrote:
On Tuesday 07 of January 2014 17:21:48 Naveen Krishna Ch wrote:
This patch modifies Kconfig such that ARCH_EXYNOS5 SoCs
can also select Samsung SSS(Security SubSystem) driver.
Signed-off-by: Naveen Krishna Ch
From: Naveen Krishna Ch ch.nav...@samsung.com
This patch uses the platform_get_irq() instead of the
platform_get_irq_byname(). Making feeder control interrupt
as resource 0 and hash interrupt as 1.
reasons for this change.
1. Cannot find any Arch which is currently using this driver
2. Samsung
From: Naveen Krishna Ch ch.nav...@samsung.com
This patch modifies Kconfig such that ARCH_EXYNOS SoCs
which includes (Exynos4210, Exynos5250 and Exynos5420)
can also select Samsung SSS(Security SubSystem) driver.
Signed-off-by: Naveen Krishna Ch ch.nav...@samsung.com
CC: Herbert Xu
This patch adds device tree support to the s5p-sss.c crypto driver.
Implements a varient struct to address the changes in SSS hardware
on various SoCs from Samsung.
Also, Documentation under devicetree/bindings added.
Signed-off-by: Naveen Krishna Ch ch.nav...@samsung.com
CC: Herbert Xu
This patch adds the device tree node for SSS module
found on Exynos5420
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
TO: linux-samsung-soc@vger.kernel.org
CC: Kukjin Kim kgene@samsung.com
CC: linux-cry...@vger.kernel.org
---
Changes since v1:
Modified dt node name from sss to
This patch adds code to validate iv buffer before trying to
memcpy the contents
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
---
Changes since v1:
None
drivers/crypto/s5p-sss.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/s5p-sss.c
Hi,
On Wednesday 08 January 2014 11:26 PM, Kamil Debski wrote:
Hi,
From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
Sent: Monday, January 06, 2014 11:12 AM
Hi,
On Friday 20 December 2013 06:54 PM, Kamil Debski wrote:
Add a new driver for the Exynos USB 2.0 PHY. The new driver uses
Hi Rafael, Zhang,
On Tuesday, January 07, 2014 07:58:24 AM Lukasz Majewski wrote:
Hi Rafael,
Hi,
This patch series introduces support for CPU overclocking
technique called Boost.
It is a follow up of a LAB governor proposal. Boost is a LAB
component:
49 matches
Mail list logo
