None of the DMA channel definitions defined in
plat/dma-44xx.h are used. So removing it.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by : Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/plat-omap/include/plat/dma-44xx.h | 147
arch/arm/plat-omap
-omap2
Patch 4:
Move plat/omap-secure.h locally to mach-omap2
Lokesh Vutla (4):
ARM: OMAP: DMA: Removing plat/dma-44xx.h
ARM: OMAP: DMA: Move plat/dma hearder to platform_data/dma-omap
ARM: OMAP: Move omap_reserve() locally to mach-omap1/2
ARM: OMAP: Move plat/omap-secure.h locally
Moving plat/omap-secure.h locally to mach-oamp2/
as part of single zImage work
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by : Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/common.c |2 +-
arch/arm/mach-omap2/omap-secure.c |1
omap_reserve() is a stub for omap1. So creating a
stub locally in mach-omap1. And moving the definition
to mach-omap2.
This helps in moving plat/omap_secure.h local to
mach-omap2
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by : Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm
Move plat/dma.h header to platform_data/dma-omap.h as
part of the single zImage work.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by : Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap1/board-h2.c |2 +-
arch/arm/mach-omap1/board
-omap/dma-omap.h
Patch 5:
Removing omap_reserve() callback from all omap1 board files.
Patch 6:
Defining omap_reserve() locally to mach-omap2.
Patch 7:
Move plat/omap-secure.h locally to mach-omap2
Lokesh Vutla (7):
ARM: OMAP: DMA: Removing plat/dma-44xx.h
ARM: OMAP1: DMA
None of the DMA channel definitions defined in
plat/dma-44xx.h are used. So removing it.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/plat-omap/include/plat/dma-44xx.h | 147
arch/arm/plat-omap/include/plat/dma.h |3 -
2 files changed, 150
-omap1
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap1/board-h2.c |1 +
arch/arm/mach-omap1/board-palmte.c |1 +
arch/arm/mach-omap1/board-palmtt.c |1 +
arch/arm/mach-omap1/board-palmz71.c |1 +
arch
definitions to mach-omap2
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/devices.c |1 +
arch/arm/mach-omap2/dma.h | 131
.../mach-omap2/omap_hwmod_2xxx_3xxx_ipblock_data.c |1 +
arch/arm/mach-omap2
omap_reserve() is a stub for omap1. So dropping
omap_reserve callback from all OMAP1 board files.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap1/board-ams-delta.c |1 -
arch/arm/mach-omap1/board-fsample.c |1 -
arch/arm/mach-omap1/board-generic.c |1
Move plat/dma.h to plat-omap/dma-omap.h as part of single
zImage work
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap1/board-h2.c |2 +-
arch/arm/mach-omap1/board-h3.c |2 +-
arch/arm/mach-omap1/board
omap_reserve() callback is defned only for mach-omap2.
So, moving definition of omap_reserve() to mach-omap2.
This helps is moving plat/omap_secure.h local to
mach-omap2
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/common.c | 20
arch
Moving plat/omap-secure.h locally to mach-omap2/
as part of single zImage work
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/common.c |2 +-
arch/arm/mach-omap2/omap-secure.c |1 -
arch/arm/mach-omap2/omap-secure.h |7
Patch 1:
Renaming elpida_ecb240abacn.dtsi as lpddr2_data.dtsi
Patch 2:
Correcting size of memory defined for omap5
Patch 3:
EMIF and LPDDR2 device tree data for OMAP5 boards
Testing:
- Boot tested on omap5-sevm board
- Built emif as a module
Lokesh Vutla (3):
ARM: dts
Memory present for omap5 is 2GB. But in dt file
it is specified as 1GB. Correcting the same
in this patch
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/omap5-evm.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap5-evm.dts b
Renaming elpida_ecb240abacn.dtsi file generic, so that the
same file can be reused for other parts from different vendors.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/{elpida_ecb240abacn.dtsi = lpddr2_data.dtsi} |0
arch/arm/boot/dts/omap4-panda.dts
Device tree data for the EMIF sdram controllers in OMAP5
and LPDDR2 memory devices attached to OMAP5 boards.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/lpddr2_data.dtsi | 64 +++-
arch/arm/boot/dts/omap5-evm.dts| 11 +++
arch
+ devicetree-discuss
Hi Benoit,
On Wednesday 10 October 2012 08:31 PM, Benoit Cousson wrote:
On 10/10/2012 02:05 PM, Lokesh Vutla wrote:
Device tree data for the EMIF sdram controllers in OMAP5
and LPDDR2 memory devices attached to OMAP5 boards.
Nit: Could you make a sentence with a verb
+ devicetree-discuss
Hi Benoit,
On Wednesday 10 October 2012 08:18 PM, Benoit Cousson wrote:
Hi Lokesh,
On 10/10/2012 02:05 PM, Lokesh Vutla wrote:
Renaming elpida_ecb240abacn.dtsi file generic, so that the
same file can be reused for other parts from different vendors.
Could you elaborate
Hi Venkat,
On Thursday 11 October 2012 12:32 PM, Venkatraman S wrote:
Daily build on Linus's tree is failing for the past 2-3 days
make modules with omap2plus_defconfig..
ERROR: snd_hwparams_to_dma_slave_config
[sound/soc/omap/snd-soc-omap.ko] undefined!
ERROR: snd_dmaengine_pcm_pointer
On Thursday 11 October 2012 01:58 PM, Benoit Cousson wrote:
On 10/11/2012 08:16 AM, Lokesh Vutla wrote:
+ devicetree-discuss
Hi Benoit,
On Wednesday 10 October 2012 08:18 PM, Benoit Cousson wrote:
Hi Lokesh,
On 10/10/2012 02:05 PM, Lokesh Vutla wrote:
Renaming elpida_ecb240abacn.dtsi file
Samsung's K3PE0E000B memory part is used in OMAP5-evm board.
Adding timings and geometry details for Samsung's memory part and
attaching the same to device-handle of EMIF1/2.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/omap5-evm.dts | 11 +
arch/arm/boot
Adding EMIF device tree data for OMAP5 boards.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 5db33f4..445aeea 100644
.
* Passing reg and interrupt fields from dt for EMIF1 and EMIF2.
Lokesh Vutla (3):
ARM: dts: omap5-evm: Fix size of memory defined for EVM
ARM: dts: omap5: EMIF device tree data for OMAP5 boards
ARM: dts: omap5-evm: LPDDR2 memory device details for EVM
arch/arm/boot/dts/omap5-evm.dts
Memory present for OMAP5-evm is 2GB. But in dts file
it is specified as 1GB. Correcting the same.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/omap5-evm.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap5-evm.dts b/arch/arm
module_init() and macros in omap_l3_noc/smx drivers when building
as modules to remove the above warning.
Reported-by: Tony Lindgren t...@atomide.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/bus/omap_l3_noc.c |9 +
drivers/bus/omap_l3_smx.c | 10 ++
2 files changed
:36]:
* Santosh Shilimkar santosh.shilim...@ti.com [121017 06:35]:
(Looping Arnd and Olof)
On Wednesday 17 October 2012 06:58 PM, Lokesh Vutla wrote:
When building omap_l3_noc/smx drivers as modules, the following
warning appears:
CC [M] drivers/bus/omap_l3_smx.o
drivers/bus/omap_l3_smx.c:291
: wd_timer2: _wait_target_disable failed
Below is the patch which might meet your aims.
Please comment on the patch.
Here I enabled delay interrupt and delay period
for petting watchdog before timeout.
watchdog is enabled for all the cases(not only for NOWAYOUT)
Signed-off-by: Lokesh Vutla lokeshvu
Hi,
On Thursday 11 October 2012 06:17 PM, Lokesh Vutla wrote:
This patch series adds Device tree data for the EMIF
sdram controllers in OMAP5 and LPDDR2 memory devices
in OMAP5-evm board.
Testing:
- Boot tested on OMAP5430 evm.
- Built EMIF as a module.
Changes from v1:
* Created a seperate
Hi Benoit,
On Monday 05 November 2012 04:33 PM, Benoit Cousson wrote:
On 11/05/2012 11:51 AM, Benoit Cousson wrote:
Hi Lokesh,
On 11/05/2012 06:58 AM, Lokesh Vutla wrote:
Hi,
On Thursday 11 October 2012 06:17 PM, Lokesh Vutla wrote:
This patch series adds Device tree data for the EMIF
sdram
Memory present for OMAP5-evm is 2GB. But in dts file
it is specified as 1GB. Correcting the same.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/omap5-evm.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap5-evm.dts b/arch/arm
-omap-dt.git
for_3.8/dts
* Addressed few other comments from Benoit.
Lokesh Vutla (3):
ARM: dts: omap5-evm: Fix size of memory defined for EVM
ARM: dts: omap5: EMIF device tree data for OMAP5 boards
ARM: dts: omap5-evm: LPDDR2 memory device details for EVM
arch/arm/boot/dts/omap5-evm.dts
Adding EMIF device tree data for OMAP5 boards.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index ead74c8..790bb2a 100644
Samsung's K3PE0E000B memory part is used in OMAP5-evm board.
Adding timings and geometry details for Samsung's memory part and
attaching the same to device-handle of EMIF1/2.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/boot/dts/omap5-evm.dts | 11 +
arch/arm/boot
Hi,
On Thursday 01 November 2012 04:56 AM, Tony Lindgren wrote:
* Lokesh Vutla lokeshvu...@ti.com [121029 00:03]:
Is the above discussion fine for you ?
Will you pick this patch or
you want any more modifications ?
Let's see what Arnd says.
Gentle ping on this...
Thanks
Lokesh
Regards
parameter.
Lokesh Vutla (1):
memory: emif: Correct the lpmode timeout calculation
Nishanth Menon (5):
memory: emif: setup LP settings on freq update
memory: emif: handle overflow for timing for LP mode
memory: emif: Handle devices which are not rated for 85C
memory: emif: use restart
From: Nishanth Menon n...@ti.com
Program the power management shadow register on freq update
else the concept of threshold frequencies dont really matter
as the system always uses the performance mode timing for LP
which is programmed in at init time.
Signed-off-by: Nishanth Menon n...@ti.com
From: Severine Glock s-gl...@ti.com
MR4 is reported under debugfs with following format MR4=%d.
Remove MR4= string for better convenience.
Signed-off-by: Severine Glock s-gl...@ti.com
---
drivers/memory/emif.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com
The issue was that only the first timings table was added to the
emif platform data at the emif driver registration. All other
timings tables was filled with zeros. Now all emif timings table
are added to the platform data.
Signed-off-by:
The driver tries to round up the specified timeout cycles to
next power of 2 value. But this is done wrongly.
Correcting this here.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/memory
From: Nishanth Menon n...@ti.com
As per OMAP5 TRM, phy_fast_dll_lock is meant for simulations only.
'0' is supposed to be used for normal operations. So, use 0.
Signed-off-by: Nishanth Menon n...@ti.com
---
drivers/memory/emif.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Nishanth Menon n...@ti.com
In case the custom timings provide values which overflow
the maximum possible field value, warn and use maximum
permissible value.
Signed-off-by: Nishanth Menon n...@ti.com
---
drivers/memory/emif.c | 36
1 file changed, 28
From: Nishanth Menon n...@ti.com
As per JESD209-2E specification for LPDDR2,
http://www.jedec.org/standards-documents/results/jesd209-2E
Table 73, LPDDR2 memories come in two flavors - Standard and
Extended. The Standard types can operate from -25C to +85C
However, beyond that and upto
From: Nishanth Menon n...@ti.com
Some machine or kernel variants might have missed implementation
of power off handlers. We DONOT want to let the system be in
out of spec state in this condition. So, WARN and attempt
a machine restart in the hopes of clearing the out-of-spec
temperature
From: Ambresh K ambr...@ti.com
In-case of low power mode selected and custom parameters
are not configured, then use default configuration.
Signed-off-by: Ambresh K ambr...@ti.com
---
drivers/memory/emif.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git
Sorry to Spam you in-box.
Please discard this message...
Thanks
Lokesh
On Monday 10 December 2012 12:38 PM, a...@dbdp33.itg.ti.com wrote:
From: Lokesh Vutla lokeshvu...@ti.com
This series resolves a few minor issues for EMIF driver.
Tested all the patches on OMAP4-sdp, OMAP5-sevm.
Patch
Hi Garcia,
On Friday 21 December 2012 05:41 AM, Ezequiel Garcia wrote:
Hello Tony,
On Thu, Dec 20, 2012 at 12:55 PM, Tony Lindgren t...@atomide.com wrote:
* Tony Lindgren t...@atomide.com [121219 11:28]:
Hi all,
These patches enable multiplatform support for omap2plus.
To build and boot it
n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c | 27 +++
include/linux/platform_data/emif_plat.h |1 +
2 files changed, 28 insertions(+)
diff --git a/drivers/memory/emif.c b/drivers/memory/emif.c
index 37e0c77
-by: Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/memory/emif.c b/drivers/memory/emif.c
index 02a94fc..f75806a 100644
--- a/drivers/memory/emif.c
-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/memory/emif.c b/drivers/memory/emif.c
index 119503a..4866f1b 100644
--- a/drivers/memory/emif.c
+++ b/drivers/memory/emif.c
@@ -1258,7 +1258,7 @@ static void
From: Nishanth Menon n...@ti.com
In case the custom timings provide values which overflow
the maximum possible field value, warn and use maximum
permissible value.
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c | 36
.
NOTE: This is not the safest option, but safer than leaving the
system in unstable conditions.
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
Strashko (1):
memory: emif: errata i743: Prohibit usage of Power-Down mode
Lokesh Vutla (2):
memory: emif: Correct the lpmode timeout calculation
memory: emif: Load the correct custom config values from dt
Nishanth Menon (3):
memory: emif: handle overflow for timing for LP mode
memory
Signed-off-by: Ambresh K ambr...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/memory/emif.c b/drivers/memory/emif.c
index 622638c..16f5089 100644
--- a/drivers/memory/emif.c
+++ b/drivers/memory/emif.c
grygorii.stras...@ti.com
Signed-off-by: Vitaly Chernooky vitaly.cherno...@ti.com
Signed-off-by: Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c | 35 +++
1 file changed, 35 insertions(+)
diff
The driver tries to round up the specified timeout cycles to
the next power of 2 value. But this is done wrongly.
Correcting this here.
Reported-by: Nishanth Menon n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/memory/emif.c |4 ++--
1 file changed, 2 insertions(+), 2
Hi,
On Monday 11 March 2013 11:20 AM, Santosh Shilimkar wrote:
On Monday 11 March 2013 10:36 AM, Lokesh Vutla wrote:
From: Grygorii Strashko grygorii.stras...@ti.com
ERRATA DESCRIPTION :
The EMIF supports power-down state for low power. The EMIF
automatically puts the SDRAM into power-down
to avoid the mentioned issue.
Cc: Dietmar Eggemann dietmar.eggem...@arm.com
Cc: Will Deacon will.dea...@arm.com
Reported-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/kernel
Hi Dietmar,
On Wednesday 13 March 2013 05:35 PM, Dietmar Eggemann wrote:
On 13/03/13 06:52, Lokesh Vutla wrote:
Commit {9a6eb31 ARM: hw_breakpoint: Debug powerdown support for
self-hosted
debug} introduces debug powerdown support for self-hosted debug.
While merging the patch 'has_ossr' check
On Friday 15 March 2013 11:38 PM, Greg KH wrote:
On Mon, Mar 11, 2013 at 10:35:57AM +0530, Lokesh Vutla wrote:
This series resolves a few minor issues for EMIF driver.
Tested all patches on OMAP4430-sdp.
Patch : memory: emif: setup LP settings on freq update
is tested on a local tree, since
Strashko (1):
memory: emif: errata i743: Prohibit usage of Power-Down mode
Lokesh Vutla (2):
memory: emif: Fix the lpmode timeout calculation
memory: emif: Load the correct custom config values from dt
Nishanth Menon (3):
memory: emif: handle overflow for timing for LP mode
memory: emif
-by: Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
Changes since V1: Updated $subject
drivers/memory/emif.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/memory
used in OMAP4 Soc's.
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
Signed-off-by: Vitaly Chernooky vitaly.cherno...@ti.com
Signed-off-by: Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
Changes since V1: No changes
drivers/memory/emif.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/memory/emif.c b/drivers/memory/emif.c
index 9b27c2b..475174a 100644
From: Nishanth Menon n...@ti.com
In case the custom timings provide values which overflow
the maximum possible field value, warn and use maximum
permissible value.
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim
.
NOTE: This is not the safest option, but safer than leaving the
system in unstable conditions.
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
Changes since V1:
Added a new extra line before
n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
Changes since V1: No changes
drivers/memory/emif.c | 27 +++
include/linux/platform_data/emif_plat.h |1 +
2 files changed, 28
The driver tries to round up the specified timeout cycles to
the next power of 2 value. This should be done defore updating
timeout variable.
Correcting this here.
Reported-by: Nishanth Menon n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim
Signed-off-by: Ambresh K ambr...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
Changes since V1: No changes
drivers/memory/emif.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/memory/emif.c b/drivers/memory/emif.c
builds.
2) If we enable CPU_IDLE on OMAP4430, debug message flood from
reset_ctrl_regs() will appear.
As this is already disussed and a patch is already sent on Mainline
Will get more info on this here[3]
Tested-by: Lokesh Vutla lokeshvu...@ti.com
Thanks and Regards,
Lokesh
[1
Hi Kevin,
On Friday 07 June 2013 03:57 AM, Kevin Hilman wrote:
Paul Walmsley p...@pwsan.com writes:
On Wed, 29 May 2013, Santosh Shilimkar wrote:
From: Vaibhav Hiremath hvaib...@ti.com
AM33XX only supports DT boot mode and with addition of
extracting module resources like, irq, dma and
Hi Paul,
On Monday 10 June 2013 02:05 PM, Lokesh Vutla wrote:
Hi Kevin,
On Friday 07 June 2013 03:57 AM, Kevin Hilman wrote:
Paul Walmsley p...@pwsan.com writes:
On Wed, 29 May 2013, Santosh Shilimkar wrote:
From: Vaibhav Hiremath hvaib...@ti.com
AM33XX only supports DT boot mode
Hi Paul,
On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
Hi folks -- particularly TIers working on mainline,
There are several regressions that started with v3.10-rc that no one's
fixed for over a month. Some of them should be quite easy:
* 37xx EVM: boot fails
- as of v3.10-rc1
Hi Kevin,
On Monday 10 June 2013 10:33 PM, Kevin Hilman wrote:
Hi Lokesh,
Lokesh Vutla lokeshvu...@ti.com writes:
Hi Kevin,
On Friday 07 June 2013 03:57 AM, Kevin Hilman wrote:
Paul Walmsley p...@pwsan.com writes:
On Wed, 29 May 2013, Santosh Shilimkar wrote:
From: Vaibhav Hiremath
/msg90399.html
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/board-omap3evm.c |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-omap2/board-omap3evm.c
b/arch/arm/mach-omap2/board-omap3evm.c
index f76d0de..278bf25 100644
--- a/arch/arm/mach-omap2/board
Hi Tony,
On Wednesday 12 June 2013 11:18 PM, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [130610 00:27]:
Hi folks -- particularly TIers working on mainline,
There are several regressions that started with v3.10-rc that no one's
fixed for over a month. Some of them should be quite
Hi Paul,
On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
Hi folks -- particularly TIers working on mainline,
There are several regressions that started with v3.10-rc that no one's
fixed for over a month. Some of them should be quite easy:
* 37xx EVM: boot fails
- as of v3.10-rc1
Hi Paul,
On Tuesday 25 June 2013 11:50 PM, Paul Walmsley wrote:
+ Vaibhav and Kevin
Hi,
On Tue, 25 Jun 2013, Felipe Balbi wrote:
On Mon, Jun 17, 2013 at 05:23:17AM +, Paul Walmsley wrote:
Boot to userspace:
FAIL ( 3/12): 37xxevm, am335xbone, am335xbonelt
Paul, we have at least 2
Hi Paul,
On Wednesday 26 June 2013 10:56 PM, Paul Walmsley wrote:
On Wed, 26 Jun 2013, Rajendra Nayak wrote:
Apart from confirming if you are manually enabling these options, can you also
give some
details on how you append the dtb to the kernel image?
Most of us use an out-of-tree patch
*.dtb used to be generated in the *arch/arm/boot* directory
which is different from where it is generated now.
Current rules delete the previously generated files only for
*make dtbs*.
Let distclean delete all the generated dtb files.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Signed-off
Hi Mark,
On Wednesday 17 July 2013 04:59 AM, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
Add the generic AM33XX SHAM module's device tree data and
enable it for the am335x-evm, am335x-evmsk, and am335x-bone
platforms. Also add Documentation file describing the data
for
, and first 8 registers are duplicated from SHA_DIGEST_i
registers) registers are added at the end of register set.
So adding the above register offsets and module info in pdata.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/crypto/omap-sham.c | 44
This patch series adds support for SHA348 and SHA512 in addition to MD5,
SHA1, SHA224 SHA256 that the omap sha module supports. Also adding the pdata
for OMAP5 and AM43xx Soc's.
And using devm_* calls to make cleanup paths simpler.
Lokesh Vutla (4):
crypto: omap-sham: Add SHA384 and SHA512
Using devm_request_irq() rather than request_irq().
So removing free_irq() calls from the probe error
path and the remove handler.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/crypto/omap-sham.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/crypto/omap-sham.c | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
index b82b140..ae1ca8b2
info.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/crypto/Kconfig | 11 +-
drivers/crypto/omap-sham.c | 245
2 files changed, 209 insertions(+), 47 deletions(-)
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
index
Hi Chen,
On Tuesday 30 July 2013 09:08 AM, Chen Baozi wrote:
Hi all,
I'm trying to boot my OMAP5432 uEVM devboard with the lastest kernel of
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git.
Which branch are you using ?
However, after u-boot loading uImage DTB, there is
Hi Chen,
On Wednesday 31 July 2013 01:19 PM, Chen Baozi wrote:
On Jul 30, 2013, at 11:52 AM, Lokesh Vutla lokeshvu...@ti.com wrote:
You can also use Linus's kernel with the above clk data branch.( OMAP5 uEVM
boots)
Please let me know if you need more info.
And the ethernet driver
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/char/hw_random/omap-rng.c |9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/char/hw_random/omap-rng.c
b/drivers/char/hw_random/omap-rng.c
index
The omap_init_rng() routine in devices.c only needs to be
called when there is no device tree present.
Cc: Tony Lindgren t...@atomide.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/devices.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch
module_platform_driver() makes the code simpler.
Using the macro in the driver.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/char/hw_random/omap-rng.c | 18 ++
1 file changed, 2 insertions(+), 16 deletions(-)
diff --git a/drivers/char/hw_random/omap-rng.c
b
platform_set_drvdata() is called twice in driver probe.
Removing the duplicated call.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/char/hw_random/omap-rng.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/hw_random/omap-rng.c
b/drivers/char/hw_random/omap-rng.c
This patch series adds support for OMAP4 version of RNG module.
This module produce a 64 bit random number and also allows to
de tune FROs when repeated pattern is coming out of FROs.
This series also has few fixes for the driver.
Lokesh Vutla (6):
hwrng: OMAP: Use module_platform_driver macro
routine pointers, register offsets. OMAP2
specific routines are prefixed with 'omap2_' and OMAP4
specific routines are prefixed with 'omap4_'.
Note: Few Hard coded values are from the TI AM33xx SDK.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/char/hw_random/Kconfig|6 +-
drivers
Add Device Tree suport to the omap-rng driver.
Currently, only support for OMAP2 and OMAP3 is
being added but support for OMAP4 and OMAP5 will
be added in a subsequent patch.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
drivers/char/hw_random/omap-rng.c | 12
1 file changed
Add the generic AM33xx RNG module's device tree data and
enable it for the am335x-evm, am335x-evmsk, and am335x-bone
platforms. Also add Documentation file describing the data
for the RNG module.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
.../devicetree/bindings/hwrng/omap_rng.txt
Add clock data for RNG module on AM33xx SoC.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/cclock33xx_data.c |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/mach-omap2/cclock33xx_data.c
b/arch/arm/mach-omap2/cclock33xx_data.c
index ba6534d..865d30e
This patch series adds HWMOD, CLOCK and DT data for
RNG module.
Lokesh Vutla (3):
ARM: AM33XX: hwmod: Add rng module data
ARM: AM33xx: Add rng clock data
ARM: dts: AM33xx: Add RNG node
.../devicetree/bindings/hwrng/omap_rng.txt | 22
arch/arm/boot/dts/am335x
Add RNG hwmod data for AM33xx SoC.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 35
1 file changed, 35 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
b/arch/arm/mach-omap2
On Tuesday 06 August 2013 11:47 PM, Russ Dill wrote:
On Tue, Aug 6, 2013 at 1:33 AM, Lokesh Vutla lokeshvu...@ti.com wrote:
Add the generic AM33xx RNG module's device tree data and
enable it for the am335x-evm, am335x-evmsk, and am335x-bone
platforms. Also add Documentation file describing
1 - 100 of 292 matches
Mail list logo
