Hi,
On Wed, Jun 4, 2014 at 12:41 AM, Paul Zimmerman
paul.zimmer...@synopsys.com wrote:
From: linux-usb-ow...@vger.kernel.org
[mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Vivek Gautam
Sent: Tuesday, June 03, 2014 3:40 AM
Putting together the code related to getting the
On 2 June 2014 15:40, Dave Martin dave.mar...@arm.com wrote:
On Mon, May 26, 2014 at 09:23:45PM +0530, Santosh Shukla wrote:
From: santosh shukla santosh.shu...@linaro.org
Add non-global symbol .LLl2x0_regs_phys to avoid build break in thumb2 mode.
IIUC, arm assembler fail to load value of
Putting together the code related to getting the 'IORESOURCE_MEM'
and assigning the same to dwc-xhci_resources, for increasing
the readability.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Changes from v1:
- Fixed issue with 'res-start' as pointed out by Paul Zimmerman
by
Hi,
On Sat, May 10, 2014 at 5:30 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls
Hi Arun, Ben,
From: arunkk.sams...@gmail.com [mailto:arunkk.sams...@gmail.com] On
Behalf Of Arun Kumar K
Sent: Wednesday, June 04, 2014 7:32 AM
Hi Ben,
On Wed, Jun 4, 2014 at 4:56 AM, Ben Hutchings b...@decadent.org.uk
wrote:
On Tue, 2014-06-03 at 20:34 +0100, Ben Hutchings wrote:
On 05/29/2014 11:28 AM, Inki Dae wrote:
This patch makes sure that exynos drm framework handles deferred
probe case correctly.
Sub drivers could be probed before resources, clock, regulator,
phy or panel, are ready for them so we should make sure that exynos
drm core waits until all
On 05/29/2014 11:28 AM, Inki Dae wrote:
This patch makes sure that exynos drm framework handles deferred
probe case correctly.
Sub drivers could be probed before resources, clock, regulator,
phy or panel, are ready for them so we should make sure that exynos
drm core waits until all
Hi,
On Mon, Jun 2, 2014 at 10:52 AM, YoungJun Cho yj44@samsung.com wrote:
This patch adds relevant to exynos5 compatible for exynos5 SoCs.
This change is not required. Please check the latest 'for-next' branch
of linux-samsung tree.
Recently a patch dfbbdbf ARM: dts: Add sysreg sytem
On Mon, Jun 2, 2014 at 10:52 AM, YoungJun Cho yj44@samsung.com wrote:
This patch adds sysreg device node, and sysreg property
to fimd device node which is required to use I80 interface.
Same here. The system register nodes have been added to exynos5250 and
exynos5420 by the patch:
dfbbdbf
On Wed, 2014-06-04 at 13:08 +0200, Kamil Debski wrote:
Hi Arun, Ben,
From: arunkk.sams...@gmail.com [mailto:arunkk.sams...@gmail.com] On
Behalf Of Arun Kumar K
Sent: Wednesday, June 04, 2014 7:32 AM
Hi Ben,
On Wed, Jun 4, 2014 at 4:56 AM, Ben Hutchings b...@decadent.org.uk
On Mon, Jun 02, 2014 at 05:11:39PM +0900, Jungseok Lee wrote:
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,
On Wed, Jun 04, 2014 at 03:41:20PM +0530, Vivek Gautam wrote:
Hi,
On Sat, May 10, 2014 at 5:30 PM, Vivek Gautam gautam.vi...@samsung.com
wrote:
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
On Sun, Jun 01, 2014 at 10:55:46AM +0100, Will Deacon wrote:
On Fri, May 30, 2014 at 08:54:37PM +0100, Arnd Bergmann wrote:
On Friday 30 May 2014 22:29:13 Hiroshi Doyu wrote:
Tegra,SMMU has a similar problem and we have used a fixed size bitmap(64
bit) to afford 64 stream IDs so that a
On Fri, May 30, 2014 at 09:54:37PM +0200, Arnd Bergmann wrote:
On Friday 30 May 2014 22:29:13 Hiroshi Doyu wrote:
IIUC the original problem, a master with 8 streamIDs means something
like below, where some devices have multiple IDs but some have a
single. A sinle #address-cells cannot
On Wednesday 04 June 2014 15:44:03 Thierry Reding wrote:
Well, the iommu specific binding could allow a variable #address-cells.
That way, you just need to know the number of stream IDs for that instance
of the iommu.
That sounds fairly complicated to me. I don't see what that buys us
On Wed, Jun 04, 2014 at 02:44:03PM +0100, Thierry Reding wrote:
On Fri, May 30, 2014 at 09:54:37PM +0200, Arnd Bergmann wrote:
On Friday 30 May 2014 22:29:13 Hiroshi Doyu wrote:
The disadvantage of this is that this limits the max number of streamIDs
to support. If # of streamID is
On Wednesday 04 June 2014 14:56:01 Will Deacon wrote:
On Wed, Jun 04, 2014 at 02:44:03PM +0100, Thierry Reding wrote:
On Fri, May 30, 2014 at 09:54:37PM +0200, Arnd Bergmann wrote:
On Friday 30 May 2014 22:29:13 Hiroshi Doyu wrote:
The disadvantage of this is that this limits the max
On Mon, Jun 02, 2014 at 11:41:04AM +0100, Dave Martin wrote:
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 a...@arndb.de wrote:
On Friday 30 May 2014 08:16:05 Rob Herring
On Wed, Jun 04, 2014 at 03:01:15PM +0100, Arnd Bergmann wrote:
On Wednesday 04 June 2014 14:56:01 Will Deacon wrote:
On Wed, Jun 04, 2014 at 02:44:03PM +0100, Thierry Reding wrote:
On Fri, May 30, 2014 at 09:54:37PM +0200, Arnd Bergmann wrote:
On Friday 30 May 2014 22:29:13 Hiroshi Doyu
On Wed, Jun 04, 2014 at 03:35:10PM +0100, Thierry Reding wrote:
On Mon, Jun 02, 2014 at 11:41:04AM +0100, Dave Martin wrote:
In the strictest sense, no.
But for a large set of sane configurations, this probably works.
Small sets of randomly-assigned IDs can just be enumerated one by
As we saw in (clocksource: exynos_mct: cache mct upper count), the
time spent reading the MCT shows up fairly high in real-world
profiles. That means that it's worth some optimization.
We get a roughly 10% speedup in userspace gettimeofday() by using an
ldmia to read the two halfs of the MCT.
From: Mandeep Singh Baines m...@chromium.org
Saves one register read. Note that the upper count only changes every
~178 seconds with a 24MHz source clock, so it's likely it hasn't
changed from call to call.
Before: 1323852 us for 100 gettimeofday in userspace
After: 1173084 us for 100
In (93bfb76 clocksource: exynos_mct: register sched_clock callback) we
supported using the MCT as a scheduler clock. We properly marked
exynos4_read_sched_clock() as notrace. However, we then went and
called another function that _wasn't_ notrace. That means if you do:
cd
On Wed, 4 Jun 2014, Doug Anderson wrote:
As we saw in (clocksource: exynos_mct: cache mct upper count), the
time spent reading the MCT shows up fairly high in real-world
profiles. That means that it's worth some optimization.
We get a roughly 10% speedup in userspace gettimeofday() by
Thomas,
On Wed, Jun 4, 2014 at 11:05 AM, Thomas Gleixner t...@linutronix.de wrote:
On Wed, 4 Jun 2014, Doug Anderson wrote:
As we saw in (clocksource: exynos_mct: cache mct upper count), the
time spent reading the MCT shows up fairly high in real-world
profiles. That means that it's worth
On Wed, Jun 04, 2014 at 05:41:32PM +0100, Will Deacon wrote:
On Wed, Jun 04, 2014 at 03:35:10PM +0100, Thierry Reding wrote:
On Mon, Jun 02, 2014 at 11:41:04AM +0100, Dave Martin wrote:
In the strictest sense, no.
But for a large set of sane configurations, this probably works.
On Fri, May 30, 2014 at 12:27:28PM +0100, Dave Martin wrote:
On Fri, May 30, 2014 at 08:30:08AM +0100, Thierry Reding wrote:
[...]
Arnd, can you take another look at this binding and see if there's
anything else missing? If not I'll go through the document again and
update all
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;
+ #size-cells = 0;
+ };
+
Signed-off-by: Doug Anderson diand...@chromium.org
---
arch/arm/boot/dts/exynos5250-snow.dts | 93 ++-
1 file changed, 3 insertions(+), 90 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250-snow.dts
b/arch/arm/boot/dts/exynos5250-snow.dts
index
On Tue, 2014-06-03 at 11:53 +0200, Arnd Bergmann wrote:
commit e4ac92df2791 (serial: samsung: Neaten dbg uses) introduced
a regression in the conversion from vsprintf to vsnprintf.
This fixes the build error by passing the correct variable name.
Signed-off-by: Arnd Bergmann a...@arndb.de
Hi Vivek,
On 06/04/2014 08:50 PM, Vivek Gautam wrote:
On Mon, Jun 2, 2014 at 10:52 AM, YoungJun Cho yj44@samsung.com wrote:
This patch adds sysreg device node, and sysreg property
to fimd device node which is required to use I80 interface.
Same here. The system register nodes have been
On Wed, Jun 04, 2014 at 06:20:41PM -0700, Joe Perches wrote:
On Tue, 2014-06-03 at 11:53 +0200, Arnd Bergmann wrote:
commit e4ac92df2791 (serial: samsung: Neaten dbg uses) introduced
a regression in the conversion from vsprintf to vsnprintf.
This fixes the build error by passing the
On 2014년 06월 04일 20:24, Andrzej Hajda wrote:
On 05/29/2014 11:28 AM, Inki Dae wrote:
This patch makes sure that exynos drm framework handles deferred
probe case correctly.
Sub drivers could be probed before resources, clock, regulator,
phy or panel, are ready for them so we should make sure
Hi Ben,
On Wed, Jun 4, 2014 at 5:43 PM, Ben Hutchings b...@decadent.org.uk wrote:
On Wed, 2014-06-04 at 13:08 +0200, Kamil Debski wrote:
Hi Arun, Ben,
From: arunkk.sams...@gmail.com [mailto:arunkk.sams...@gmail.com] On
Behalf Of Arun Kumar K
Sent: Wednesday, June 04, 2014 7:32 AM
Hi
Hi YoungJun,
On Thu, Jun 5, 2014 at 8:22 AM, YoungJun Cho yj44@samsung.com wrote:
Hi Vivek,
On 06/04/2014 08:50 PM, Vivek Gautam wrote:
On Mon, Jun 2, 2014 at 10:52 AM, YoungJun Cho yj44@samsung.com
wrote:
This patch adds sysreg device node, and sysreg property
to fimd device
35 matches
Mail list logo
