Re: [U-Boot] [PATCH 2/3] ARM: OMAP5: clocks: Do not enable sgx clocks

On Wednesday 29 May 2013 06:10 PM, Tom Rini wrote: > On Wed, May 29, 2013 at 03:39:54PM +0530, Lokesh Vutla wrote: > >> From: Sricharan R >> >> SGX clocks should be enabled only for OMAP5 ES1.0. >> So this can be removed. >> >> Signed-off-by: Sricha

Re: [U-Boot] [PATCH 08/12] ARM: DRA7xx: Correct SRAM END address

On Wednesday 29 May 2013 06:36 PM, Tom Rini wrote: > On Wed, May 29, 2013 at 04:32:43PM +0530, Lokesh Vutla wrote: > >> From: Sricharan R >> >> NON SECURE SRAM is 512KB in DRA7xx devices. >> So fixing it here. >> >> Signed-off-by: Sricharan R >>

Re: [U-Boot] [PATCH V2 0/5] ARM: OMAP: Cleanup save_boot_params function

Hi Tom, On Friday 31 May 2013 07:52 PM, Tom Rini wrote: > On Fri, May 31, 2013 at 10:18:46AM -0400, Tom Rini wrote: >> On Wed, Apr 24, 2013 at 04:11:20PM +0530, Sricharan R wrote: >> >>> The save_boot_params function does not store the data in a >>> always writabl

Re: [U-Boot] [PATCH 3/3] am33xx/omap: Move save_omap_boot_params to omap-common/boot-common.c

On Friday 31 May 2013 11:48 PM, Tom Rini wrote: > We need to call the save_omap_boot_params function on am33xx/ti81xx and > other newer TI SoCs, so move the function to boot-common. Only OMAP4+ > has the omap_hw_init_context function so add ifdefs to not call it on > am33xx/ti81xx. Call save_omap

Re: [U-Boot] [PATCH V2 0/5] ARM: OMAP: Cleanup save_boot_params function

On Monday 03 June 2013 11:39 AM, Sricharan R wrote: > Hi Tom, > > On Friday 31 May 2013 07:52 PM, Tom Rini wrote: >> On Fri, May 31, 2013 at 10:18:46AM -0400, Tom Rini wrote: >>> On Wed, Apr 24, 2013 at 04:11:20PM +0530, Sricharan R wrote: >>> >>>> The

Re: [U-Boot] arm, arm335x: save_omap_boot_params question

On Wednesday 12 June 2013 06:19 PM, Tom Rini wrote: > On Wed, Jun 12, 2013 at 02:39:13PM +0200, Heiko Schocher wrote: >> Hello Tom, >> >> Am 12.06.2013 14:28, schrieb Tom Rini: >>> On Wed, Jun 12, 2013 at 10:56:01AM +0200, Heiko Schocher wrote: Hello tom, your commit 4596dc

Re: [U-Boot] arm, arm335x: save_omap_boot_params question

On Thursday 13 June 2013 10:49 AM, Heiko Schocher wrote: > Hello Sricharan, > > Am 13.06.2013 07:08, schrieb Sricharan R: >> On Wednesday 12 June 2013 06:19 PM, Tom Rini wrote: >>> On Wed, Jun 12, 2013 at 02:39:13PM +0200, Heiko Schocher wrote: >>>> Hell

Re: [U-Boot] [[PATCH v2 3/6] ARM: OMAP5: USB: Add OMAP5 common USB EHCI information

On Thursday 11 July 2013 01:28 PM, Roger Quadros wrote: > On 07/11/2013 06:51 AM, Lokesh Vutla wrote: >> On Thursday 11 July 2013 01:35 AM, Dan Murphy wrote: >>> * Enable the OMAP5 EHCI host clocks >>> * Add OMAP5 EHCI register definitions >>> * Add OMAP5 ES2 host revision >>> >>> Signed-off-by: Da

Re: [U-Boot] [[PATCH v2 3/6] ARM: OMAP5: USB: Add OMAP5 common USB EHCI information

On Thursday 11 July 2013 02:25 PM, Roger Quadros wrote: > On 07/11/2013 11:35 AM, Sricharan R wrote: >> On Thursday 11 July 2013 01:28 PM, Roger Quadros wrote: >>> On 07/11/2013 06:51 AM, Lokesh Vutla wrote: >>>> On Thursday 11 July 2013 01:35 AM, Dan Murphy wrote:

Re: [U-Boot] [PATCH] omap4_common: config: remove I2C for SPL mode

f CONFIG_SYS_I2C > +#undef CONFIG_SYS_I2C_OMAP24XX > +#endif > + > #endif /* __CONFIG_OMAP4_COMMON_H */ correct. Thanks for the fix. Also with size remaining still as 32224 bytes OMAP4 HS devices might not boot up. Anyways thats separate and something more like this patch has to be remov

Re: [U-Boot] [PATCH] DRA7: Add support for ES1.1 silicon ID code

2_CONTROL_ID_CODE_ES1_1 0x1B99002F > > /* UART */ > #define UART1_BASE (OMAP54XX_L4_PER_BASE + 0x6a000) > diff --git a/arch/arm/include/asm/omap_common.h > b/arch/arm/include/asm/omap_common.h > index a78f990..9b1f495 100644 > --- a/arch/arm/include/asm/omap_common.h > +++ b/arch/arm/include/asm/omap_common.h > @@ -643,6 +643,7 @@ static inline u8 is_dra7xx(void) > > /* DRA7XX */ > #define DRA752_ES1_0 0x07520100 > +#define DRA752_ES1_1 0x07520110 > > /* > * SRAM scratch space entries Reviewed By: Sricharan R Regards, Sricharan ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH] OMAP5432: do not apply 5430 non-essential pad-confs to 5432

Hi, > > Signed-off-by: Sebastien Jan > > One of the things that's been discussed before is that enabling > "non-essential" things can lead to PM problems later in the kernel, so > should we be enabling anything U-Boot doesn't really need, ever, in > these cases? > Yes, in fact non- essential muxe

Re: [U-Boot] [PATCH 1/5] ARM: cache: Move the cp15 CR register read before flushing the cache.

Ping.. Thanks, Sricharan > -Original Message- > From: R, Sricharan [mailto:r.sricha...@ti.com] > Sent: Tuesday, May 29, 2012 8:24 PM > To: U-Boot@lists.denx.de; albert.u.b...@aribaud.net > Cc: tr...@ti.com > Subject: Re: [U-Boot] [PATCH 1/5] ARM: cache: Move the cp15 CR register > read

Re: [U-Boot] [PATCH 2/4] cache_v7: Check for dcache enablement in dcache flush functions

Hi, [snip..] > On 06/15/2012 07:48 AM, R, Sricharan wrote: > > Hi, > > > >>> On Fri, Jun 15, 2012 at 12:31 AM, Tom Rini wrote: > If we are built with D-CACHE enabled but have run 'dcache off' and > then > attempt to flush unaligned regions we spam the console with > problems > that

Re: [U-Boot] [PATCH v4 5/6] omap4_panda: Disable DCACHE since USB EHCI is enabled

Hi Tom, [snip..] > #define CONFIG_USB_HOST > #define CONFIG_USB_EHCI > #define CONFIG_USB_EHCI_OMAP > +#define CONFIG_SYS_DCACHE_OFF/* USB_EHCI is unusable with DCACHE > support */ > #define CONFIG_USB_STORAGE > #define CONFIG_SYS_USB_EHCI_MAX_ROOT_PORTS 3 While, this looks like to b

[U-Boot] [PATCH RESEND 0/3] ARM: mmu: Set domain permissions to client access

Currently for ARM based cpu's, mmu pagetable attributes are set with manager permissions for all 4GB address space. Because of this the 'execute never (XN)' permission is never checked on read sensitive regions which results in speculative aborts. This series changes the domain permissions of the

[U-Boot] [PATCH RESEND 1/3] ARM: cache: declare set_section_dcache

From: Vincent Stehlé We declare the set_section_dcache function globally in the cache header, for later use by e.g. machine specific code. Signed-off-by: Vincent Stehlé ti.com> Cc: Tom Rini ti.com> Cc: Albert ARIBAUD --- arch/arm/include/asm/cache.h |1 + 1 file changed, 1 insertion(+)

[U-Boot] [PATCH RESEND 2/3] ARM: mmu: Introduce weak dram_bank_setup function

From: R Sricharan Introduce a weak version of dram_bank_setup function to allow a platform specific function. This is used in the subsequent patch to setup dram region without 'XN' attribute in order to enable the region under client permissions. Signed-off-by: R Sricharan Cc: Vincent Stehle

[U-Boot] [PATCH RESEND 3/3] ARM: mmu: Set domain permissions to client access

From: R Sricharan The 'XN' execute never bit is set in the pagetables. This will prevent speculative prefetches to non executable regions. But the domain permissions are set as master in the DACR register. So the pagetable attribute for 'XN' is not effective. Change the permissions to client

Re: [U-Boot] [PATCH 0/2] ARM: mmu: Set domain permissions to client access - build warnings!

Hi, On Monday 04 March 2013 03:38 PM, Vincent Stehlé wrote: > On 03/02/2013 11:46 PM, Albert ARIBAUD wrote: >> (..) Basically, this means we need Vincent's series >> to be applied first, then we can apply Sricharan's. > Hi, > > I think this is too much trouble for a "one liner". Please feel free to

Re: [U-Boot] [U-Boot, 6/7] arm: dra7xx: Add board files for DRA7XX socs

On Tuesday 12 March 2013 12:05 AM, Tom Rini wrote: > On Tue, Feb 12, 2013 at 09:29:08PM -, Lokesh Vutla wrote: > >> Adding new board files for DRA7XX socs. >> The pad registers layout is changed completely from OMAP5 >> So introducing the new structure here and also adding the >> minimal data.

Re: [U-Boot] [PATCH RESEND 0/3] ARM: mmu: Set domain permissions to client access

Hi Albert, On Tuesday 05 March 2013 11:34 AM, Sricharan R wrote: > Currently for ARM based cpu's, mmu pagetable attributes are > set with manager permissions for all 4GB address space. > Because of this the 'execute never (XN)' permission is > never checked on read sens

Re: [U-Boot] [PATCH] power: twl6035: cleanup register access API

nction. TWL6035 belongs to > the palmas family, so instead of having an palmas API, > we could use twl6035 API instead (which is used elsewhere > as well). > > Account for the parameter change while doing the change and > remove palmas register accessors. > > Cc: Balaj

Re: [U-Boot] [RFC] command/cache: Add flush_cache command

On Thursday 21 March 2013 06:01 AM, Scott Wood wrote: > On 03/20/2013 07:27:29 PM, Michael Cashwell wrote: >> On Mar 20, 2013, at 7:48 PM, Scott Wood wrote: >> >> > On 03/20/2013 06:33:41 PM, Michael Cashwell wrote: >> > >> >> What is the purpose of limiting the memory range to be flushed? Is ther

[U-Boot] [PATCH] ARM: OMAP5: Set fdt_high to enable booting with Device tree

While booting with dtblob, if fdt_high is not set to 0x, the dt blob is relocated to a higher address, which the kernel is not able to use without HIGHMEM. So set it to 0x to avoid the issue. Signed-off-by: Sricharan R --- include/configs/omap5_common.h |1 + 1 file changed

Re: [U-Boot] [PATCH] ARM: OMAP5: Set fdt_high to enable booting with Device tree

Hi Tom, On Thursday 21 March 2013 05:29 PM, Tom Rini wrote: > On Thu, Mar 21, 2013 at 12:25:17PM +0530, Sricharan R wrote: > >> While booting with dtblob, if fdt_high is not set to >> 0x, the dt blob is relocated to a higher address, >> which the kernel is not abl

[U-Boot] [PATCH 0/5] ARM: OMAP4/5: Add support to boot with device tree as default

With the kernel moving all towards device tree, this series adds support to make the device tree boot as the default for OMAP4/5 platforms. Sricharan R (5): ARM: OMAP5: Rename omap5_evm.h to omap5_uevm.h ARM: OMAP5: Set fdt_high to enable booting with Device tree ARM: OMAP5: Support loading

[U-Boot] [PATCH 2/5] ARM: OMAP5: Set fdt_high to enable booting with Device tree

While booting with dt blob, if fdt_high is not set to 0x, the dt blob gets relocated to a high ram address, which the kernel is not able to use without HIGHMEM. So set it to 0x to avoid the issue. Signed-off-by: Sricharan R --- include/configs/omap5_common.h |1 + 1 file

[U-Boot] [PATCH 3/5] ARM: OMAP5: Support loading environment variables from txt file

instead boot scripts) Signed-off-by: Sricharan R --- include/configs/omap5_common.h | 16 +--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/include/configs/omap5_common.h b/include/configs/omap5_common.h index f0416df..6d7aa7b 100644 --- a/include/configs

[U-Boot] [PATCH 5/5] ARM: OMAP4/5: Make bootz as the default boot command

So with OMAP added to multi platform kernel, the uImage no more contains a valid load address. With the uboot already supporting zImage, change the default boot command to bootz instead. Signed-off-by: Sricharan R --- include/configs/omap4_common.h |6 +++--- include/configs/omap5_common.h

[U-Boot] [PATCH 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

Now with kernel moving to all device tree, the default boot command is changed to pass the device tree blob. Also, adding the findfdt command to get the dt-blob based on the board. Thanks to Tom Rini for suggesting this. Signed-off-by: Sricharan R --- include/configs/omap4_common.h | 13

[U-Boot] [PATCH 1/5] ARM: OMAP5: Rename omap5_evm.h to omap5_uevm.h

The omap5-uevm is the reference board name for OMAP5 soc based platform. So rename it accordingly. Signed-off-by: Sricharan R --- board/ti/omap5_evm/Makefile| 49 --- board/ti/omap5_evm/evm.c | 101 - board/ti/omap5_evm/mux_data.h | 304

Re: [U-Boot] [PATCH 1/5] ARM: OMAP5: Rename omap5_evm.h to omap5_uevm.h

On Saturday 23 March 2013 01:54 PM, Sricharan R wrote: > The omap5-uevm is the reference board name for OMAP5 soc > based platform. So rename it accordingly. > > Signed-off-by: Sricharan R > --- > board/ti/omap5_evm/Makefile| 49 --- > board/ti/omap5_e

[U-Boot] [PATCH V2 1/5] ARM: OMAP5: Rename omap5_evm to omap5_uevm

The omap5-uevm is the reference board name for OMAP5 soc based platform. So rename it accordingly. Signed-off-by: Sricharan R --- board/ti/{omap5_evm => omap5_uevm}/Makefile |0 board/ti/{omap5_evm => omap5_uevm}/evm.c |0 board/ti/{omap5_evm => omap5_uevm}/mux_data

Re: [U-Boot] [PATCH] omap5: Allow use of a plain text env file

Hi Nishanth, On Saturday 23 March 2013 08:57 PM, Nishanth Menon wrote: > On 03/22/2013 08:03 PM, Tom Rini wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 03/22/2013 06:43 PM, Nishanth Menon wrote: >>> For production systems it is better to use script images since they >>> are p

[U-Boot] [PATCH V2 0/5] ARM: OMAP4/5: Add support to boot with device tree as default

With the kernel moving all towards device tree, this series adds support to make the device tree boot as the default for OMAP4/5 platforms. Sricharan R (5): ARM: OMAP5: Rename omap5_evm to omap5_uevm ARM: OMAP5: Set fdt_high to enable booting with Device tree ARM: OMAP5: Support loading

[U-Boot] [PATCH V2 3/5] ARM: OMAP5: Support loading environment variables from txt file

instead boot scripts) Signed-off-by: Sricharan R --- include/configs/omap5_common.h | 16 +--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/include/configs/omap5_common.h b/include/configs/omap5_common.h index f0416df..6d7aa7b 100644 --- a/include/configs

[U-Boot] [PATCH V2 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

Now with kernel moving to all device tree, the default boot command is changed to pass the device tree blob. Also, adding the findfdt command to get the dt-blob based on the board. Thanks to Tom Rini for suggesting this. Signed-off-by: Sricharan R --- [V2] Corrected the board file name for

[U-Boot] [PATCH V2 2/5] ARM: OMAP5: Set fdt_high to enable booting with Device tree

While booting with dt blob, if fdt_high is not set to 0x, the dt blob gets relocated to a high ram address, which the kernel is not able to use without HIGHMEM. So set it to 0x to avoid the issue. Signed-off-by: Sricharan R --- include/configs/omap5_common.h |1 + 1 file

[U-Boot] [PATCH V2 1/5] ARM: OMAP5: Rename omap5_evm to omap5_uevm

The omap5-uevm is the reference board name for OMAP5 soc based platform. So rename it accordingly. Signed-off-by: Sricharan R --- [V2] Formatted the patch using -M option to detect renames and edited the subject board/ti/{omap5_evm => omap5_uevm}/Makefile |0 board/ti/{omap5_

[U-Boot] [PATCH V2 5/5] ARM: OMAP4/5: Make bootz as the default boot command

So with OMAP added to multi platform kernel, the uImage no more contains a valid load address. With the uboot already supporting zImage, change the default boot command to bootz instead. Signed-off-by: Sricharan R --- include/configs/omap4_common.h |6 +++--- include/configs/omap5_common.h

Re: [U-Boot] [PATCH] omap5: Allow use of a plain text env file

On Monday 25 March 2013 08:09 AM, Nishanth Menon wrote: > On 03/23/2013 11:20 PM, Sricharan R wrote: >> Hi Nishanth, >> >> On Saturday 23 March 2013 08:57 PM, Nishanth Menon wrote: >>> On 03/22/2013 08:03 PM, Tom Rini wrote: >>>> -BEGIN PGP SIGNED ME

Re: [U-Boot] [PATCH V2 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

On Sunday 24 March 2013 07:39 PM, Tom Rini wrote: > On Sun, Mar 24, 2013 at 11:54:07AM +0530, Sricharan R wrote: > >> Now with kernel moving to all device tree, the default >> boot command is changed to pass the device tree blob. >> Also, adding the findfdt command to get

Re: [U-Boot] [PATCH 0/5] ARM: OMAP4/5: Add support to boot with device tree as default

On Monday 25 March 2013 09:31 PM, Nishanth Menon wrote: > On 13:54-20130323, Sricharan R wrote: >> With the kernel moving all towards device tree, this series >> adds support to make the device tree boot as the default >> for OMAP4/5 platforms. >> >> Srichar

Re: [U-Boot] [PATCH V2 0/9] OMAP3-5: TWL[46]03[05]: cleanup register access and misc minimal cleanups

Hi Nishanth, On Saturday 23 March 2013 03:03 AM, Nishanth Menon wrote: > V1: http://patchwork.ozlabs.org/patch/227112/ > > This series helps standardize register parameters for TWL4030, 6030 and 6035 > used in various OMAP3,4,5 based platforms. > For historical reasons, we have been following val

[U-Boot] [PATCH V3 5/5] ARM: OMAP4/5: Make bootz as the default boot command

So with OMAP added to multi platform kernel, the uImage no more contains a valid load address. With the uboot already supporting zImage, change the default boot command to bootz instead. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth Menon --- include/configs

[U-Boot] [PATCH V3 2/5] ARM: OMAP5: Set fdt_high to enable booting with Device tree

While booting with dt blob, if fdt_high is not set to 0x, the dt blob gets relocated to a high ram address, which the kernel is not able to use without HIGHMEM. So set it to 0x to avoid the issue. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth Menon

[U-Boot] [PATCH V3 1/5] ARM: OMAP5: Rename omap5_evm to omap5_uevm

The omap5-uevm is the reference board name for OMAP5 soc based platform. So rename it accordingly. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth Menon --- [V2] Formatted the patch using -M option to detect renames and edited the subject [V3] No change board

[U-Boot] [PATCH V3 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

Now with kernel moving to all device tree, the default boot command is changed to pass the device tree blob. Also, adding the findfdt command to get the dt-blob based on the board. Thanks to Tom Rini for suggesting this. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth

[U-Boot] [PATCH V3 0/5] ARM: OMAP4/5: Add support to boot with device tree as default

With the kernel moving all towards device tree, this series adds support to make the device tree boot as the default for OMAP4/5 platforms. Nishanth Menon (1): omap5: Allow use of a plain text env file Sricharan R (4): ARM: OMAP5: Rename omap5_evm to omap5_uevm ARM: OMAP5: Set fdt_high to

[U-Boot] [PATCH V3 3/5] ARM: OMAP5: Allow use of a plain text env file

v.txt was loaded. If uenvcmd doesn't exist the default boot sequence will be started. Inspired by commit: d70f54808dfa83b574e1239c3eccbcf3317343e1 (omap4: allow the use of a plain text env file instead boot scripts) Signed-off-by: Sricharan R Signed-off-by: Nishanth Menon Tested-by: S

Re: [U-Boot] [PATCH V2 0/9] OMAP3-5: TWL[46]03[05]: cleanup register access and misc minimal cleanups

Hi Nishanth, On Monday 25 March 2013 11:50 PM, Nishanth Menon wrote: > Hi Sricharan, > > On Mon, Mar 25, 2013 at 12:47 PM, Sricharan R wrote: >>All of TWL[46]03[05]_i2c_[write/read]_u8 is doing the same. (ie) >> i2c_write(chip_no, reg, 1, &val, 1); >>

Re: [U-Boot] [PATCH V2 0/9] OMAP3-5: TWL[46]03[05]: cleanup register access and misc minimal cleanups

On Tuesday 26 March 2013 06:55 PM, Nishanth Menon wrote: > On 15:01-20130326, Sricharan R wrote: >> approach we will end up creating a new tps659038.h which does exactly >> the same thing. This does not feel correct. Can't we differentiate >> using register nam

Re: [U-Boot] [PATCH V3 00/10] OMAP3-5: TWL[46]03[05]: cleanup register access and misc minimal cleanups

Hi Nishanth, On Tuesday 26 March 2013 08:50 PM, Nishanth Menon wrote: > This series helps standardize register parameters for TWL4030, 6030 and 6035 > used in various OMAP3,4,5 based platforms. > > For historical reasons, we have been following val, reg as the order of > parameters while we have

Re: [U-Boot] [PATCH] arm: omap: emif: Support for ddr3 after warm reset

On Wednesday 27 March 2013 09:55 AM, Lokesh Vutla wrote: > EMIF supports a global warm reset mode, during which the > EMIF keeps the SDRAM content. But if leveling is enabled > at the time of warm reset for DDR3, the following steps > needs to be done after warm reset: > 1) Keep EMIF in self refres

Re: [U-Boot] [PATCH V3 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

On Wednesday 27 March 2013 09:15 PM, Tom Rini wrote: > On Tue, Mar 26, 2013 at 09:57:35AM +0530, Sricharan R wrote: > >> Now with kernel moving to all device tree, the default >> boot command is changed to pass the device tree blob. >> Also, adding the findfdt command to

[U-Boot] [PATCH V4 2/5] ARM: OMAP5: Set fdt_high to enable booting with Device tree

While booting with dt blob, if fdt_high is not set to 0x, the dt blob gets relocated to a high ram address, which the kernel is not able to use without HIGHMEM. So set it to 0x to avoid the issue. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth Menon

[U-Boot] [PATCH V4 1/5] ARM: OMAP5: Rename omap5_evm to omap5_uevm

The omap5-uevm is the reference board name for OMAP5 soc based platform. So rename it accordingly. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth Menon --- board/ti/{omap5_evm => omap5_uevm}/Makefile |0 board/ti/{omap5_evm => omap5_uevm}/evm.c

[U-Boot] [PATCH V4 3/5] omap5: Allow use of a plain text env file

v.txt was loaded. If uenvcmd doesn't exist the default boot sequence will be started. Inspired by commit: d70f54808dfa83b574e1239c3eccbcf3317343e1 (omap4: allow the use of a plain text env file instead boot scripts) Signed-off-by: Sricharan R Signed-off-by: Nishanth Menon Tested-by: S

[U-Boot] [PATCH V4 5/5] ARM: OMAP4/5: Make bootz as the default boot command

So with OMAP added to multi platform kernel, the uImage no more contains a valid load address. With the uboot already supporting zImage, change the default boot command to bootz instead. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth Menon --- include/configs

[U-Boot] [PATCH V4 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

Now with kernel moving to all device tree, the default boot command is changed to pass the device tree blob. Also, adding the findfdt command to get the dt-blob based on the board. Thanks to Tom Rini for suggesting this. Signed-off-by: Sricharan R --- [V4] Added environment variables bootdir

[U-Boot] [PATCH V4 0/5] ARM: OMAP4/5: Add support to boot with device tree as default

With the kernel moving all towards device tree, this series adds support to make the device tree boot as the default for OMAP4/5 platforms. Nishanth Menon (1): omap5: Allow use of a plain text env file Sricharan R (4): ARM: OMAP5: Rename omap5_evm to omap5_uevm ARM: OMAP5: Set fdt_high to

Re: [U-Boot] Potential issue with recent OMAP PRCM struct unification

Hi Mike Cashwell, On Monday 01 April 2013 09:12 PM, Michael Cashwell wrote: > Greetings, > > I think or something related to > it has confused OMAP4 clock init. I haven't entirely unraveled the onion but > wanted to ping the list to see if this is kno

Re: [U-Boot] Potential issue with recent OMAP PRCM struct unification

On Tuesday 02 April 2013 05:59 PM, Michael Cashwell wrote: > On Apr 2, 2013, at 5:32 AM, Sricharan R wrote: > >>> On first blush, it looks like having both cm_l3instr_intrconn_wp1_clkct and >>> cm_l3instr_intrconn_wp1_clkctrl is a mistake. >> >> First, on whi

Re: [U-Boot] [PATCH V4 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

Hi Tom, On Tuesday 02 April 2013 12:50 AM, Tom Rini wrote: > On Mon, Apr 01, 2013 at 09:22:41PM +0530, Sricharan R wrote: > >> Now with kernel moving to all device tree, the default >> boot command is changed to pass the device tree blob. >> Also, adding the findfdt co

Re: [U-Boot] Potential issue with recent OMAP PRCM struct unification

On Tuesday 02 April 2013 08:47 PM, Tom Rini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/02/2013 11:06 AM, Sricharan R wrote: >> On Tuesday 02 April 2013 05:59 PM, Michael Cashwell wrote: >>> On Apr 2, 2013, at 5:32 AM, Sricharan R >>> w

Re: [U-Boot] [PATCH V4 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

On Tuesday 02 April 2013 09:43 PM, Tom Rini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/02/2013 11:33 AM, Sricharan R wrote: >> Hi Tom, >> >> On Tuesday 02 April 2013 12:50 AM, Tom Rini wrote: >>> On Mon, Apr 01, 2013 at 09:22:41PM

Re: [U-Boot] Potential issue with recent OMAP PRCM struct unification

On Tuesday 02 April 2013 10:12 PM, Tom Rini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/02/2013 11:55 AM, Sricharan R wrote: >> On Tuesday 02 April 2013 08:47 PM, Tom Rini wrote: >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> >

[U-Boot] [PATCH V4 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

Now with kernel moving to all device tree, the default boot command is changed to pass the device tree blob. Also, adding the findfdt command to get the dt-blob based on the board. Thanks to Tom Rini for suggesting this. Signed-off-by: Sricharan R --- [V4] Added environment variables bootdir

[U-Boot] [PATCH V4 5/5] ARM: OMAP4/5: Make bootz as the default boot command

So with OMAP added to multi platform kernel, the uImage no more contains a valid load address. With the uboot already supporting zImage, change the default boot command to bootz instead. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth Menon --- include/configs

Re: [U-Boot] [PATCH V4 5/5] ARM: OMAP4/5: Make bootz as the default boot command

Hi Albert, On Friday 05 April 2013 12:36 PM, Albert ARIBAUD wrote: > Hi Sricharan, > > On Fri, 5 Apr 2013 11:24:34 +0530, Sricharan R > wrote: > >> So with OMAP added to multi platform kernel, >> the uImage no more contains a valid load address. >> With th

Re: [U-Boot] [PATCH V4 5/5] ARM: OMAP4/5: Make bootz as the default boot command

On Friday 05 April 2013 01:38 PM, Albert ARIBAUD wrote: > Hi Sricharan, > > On Fri, 5 Apr 2013 12:44:45 +0530, Sricharan R > wrote: > >> Hi Albert, >> >> On Friday 05 April 2013 12:36 PM, Albert ARIBAUD wrote: >>> Hi Sricharan, >>> >>&g

[U-Boot] [PATCH V4 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

Now with kernel moving to all device tree, the default boot command is changed to pass the device tree blob. Also, adding the findfdt command to get the dt-blob based on the board. Thanks to Tom Rini for suggesting this. Signed-off-by: Sricharan R --- [V4] Added environment variables bootdir

[U-Boot] [PATCH V4 5/5] ARM: OMAP4/5: Make bootz as the default boot command

So with OMAP added to multi platform kernel, the uImage no more contains a valid load address. With the uboot already supporting zImage, change the default boot command to bootz instead. Acked-by: Nishanth Menon Signed-off-by: Sricharan R Tested-by: Nishanth Menon --- [V4] Just rebased on top

Re: [U-Boot] [PATCH v2] OMAP5: USB: hsusbtll_clkctrl has to be in hw_auto for USB to work

On Thursday 04 April 2013 09:21 PM, Lubomir Popov wrote: > V2 fixes line wrap issue of the patch itself. > > This fix is needed (but not sufficient) for USB EHCI operation. > > Signed-off-by: Lubomir Popov > > --- > arch/arm/cpu/armv7/omap5/hw_data.c |2 +- > 1 file changed, 1 insertion(+)

Re: [U-Boot] [PATCH v2] OMAP: Fix copy-paste bug that did not enable UART4 clock

On Thursday 04 April 2013 09:21 PM, Lubomir Popov wrote: > V2 fixes line wrap issue of the patch itself. > > UART3 was enabled twice instead of UART4. > > One more cosmetic change in a comment on EMIF clock. > > Signed-off-by: Lubomir Popov > > --- > arch/arm/cpu/armv7/omap-common/clocks-comm

Re: [U-Boot] [PATCH v2] OMAP5: I2C: Enable i2c5 clocks

On Thursday 04 April 2013 09:22 PM, Lubomir Popov wrote: > V2 fixes line wrap issue of the patch itself. > > I2C5 is used on all known OMAP5 hardware platforms, therefore enable. > > Signed-off-by: Lubomir Popov > > --- > arch/arm/cpu/armv7/omap5/hw_data.c |1 + > 1 file changed, 1 inserti

Re: [U-Boot] OMAP (4) boot_params

Hi Mike Cashwell, On Thursday 04 April 2013 07:48 PM, Michael Cashwell wrote: > On Apr 4, 2013, at 1:52 AM, Wolfgang Denk wrote: > >> Dear Tom, >> >> On Apr 3, 2013, at 11:34 AM, Albert ARIBAUD >> wrote: ... except, as I said above, at this point your code should not write at all, be

Re: [U-Boot] [PATCH 1/3] OMAP3/4/5/AM33xx: Correct logic for checking FAT or RAW MMC

Hi Tom, On Friday 05 April 2013 09:51 PM, Tom Rini wrote: > In the case of booting from certain peripherals, such as UART, we must > not see what the device descriptor says for RAW or FAT mode because in > addition to being nonsensical, it leads to a hang. This is why we have > a test currently f

Re: [U-Boot] [PATCH v2] OMAP5: USB: hsusbtll_clkctrl has to be in hw_auto for USB to work

Hi Lubomir, On Monday 08 April 2013 03:05 PM, Lubomir Popov wrote: > Hello Sricharan, > > On 08/04/13 09:05, Sricharan R wrote: >> On Thursday 04 April 2013 09:21 PM, Lubomir Popov wrote: >>> V2 fixes line wrap issue of the patch itself. >>> >>> This

Re: [U-Boot] [PATCH v2] OMAP5: I2C: Enable i2c5 clocks

Hi Lubomir, On Monday 08 April 2013 03:05 PM, Lubomir Popov wrote: > Hi Sricharan, > > On 08/04/13 09:09, Sricharan R wrote: >> On Thursday 04 April 2013 09:22 PM, Lubomir Popov wrote: >>> V2 fixes line wrap issue of the patch itself. >>> >>> I2C5 is

Re: [U-Boot] [PATCH V3 1/3] OMAP5: I2C: Enable i2c5 clocks

Hi Lubomir, On Monday 08 April 2013 04:03 PM, Lubomir Popov wrote: > Signed-off-by: Lubomir Popov > --- > V3 consolidates this patch into a series. > > arch/arm/cpu/armv7/omap5/hw_data.c |1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm/cpu/armv7/omap5/hw_data.c > b/arch/ar

Re: [U-Boot] [PATCH V3 1/3] OMAP5: I2C: Enable i2c5 clocks

On Tuesday 09 April 2013 12:09 PM, Lubomir Popov wrote: > Hi Sricharan, > > On 09/04/13 09:34, Sricharan R wrote: >> Hi Lubomir, >> >> On Monday 08 April 2013 04:03 PM, Lubomir Popov wrote: >>> Signed-off-by: Lubomir Popov >>> --- >>> V3 co

Re: [U-Boot] [PATCH V2 00/18] OMAP5: Add the Changes required for OMAP5 ES1.0 silicon

Tom, > -Original Message- > From: Tom Rini [mailto:tom.r...@gmail.com] On Behalf Of Tom Rini > Sent: Monday, March 05, 2012 11:14 PM > To: R Sricharan > Cc: u-boot@lists.denx.de > Subject: Re: [U-Boot] [PATCH V2 00/18] OMAP5: Add the Changes required > for OMAP5 ES1.0 silicon > > On Thu, Ma

Re: [U-Boot] [PATCH V2 05/18] OMAP5: palmas: Configure nominal opp vdd values

Hi, > -Original Message- > From: tom.r...@gmail.com [mailto:tom.r...@gmail.com] On Behalf Of Tom > Rini > Sent: Thursday, March 08, 2012 2:04 AM > To: Menon, Nishanth; sricharan > Cc: u-boot@lists.denx.de > Subject: Re: [U-Boot] [PATCH V2 05/18] OMAP5: palmas: Configure nominal > opp vdd v

Re: [U-Boot] [PATCH V3] OMAP5: reset: Use cold reset in case of 5430ES1.0

Thanks, Sricharan > -Original Message- > From: Tom Rini [mailto:tr...@ti.com] > Sent: Thursday, March 08, 2012 12:15 AM > To: Menon, Nishanth > Cc: R Sricharan; u-boot@lists.denx.de > Subject: Re: [U-Boot] [PATCH V3] OMAP5: reset: Use cold reset in case > of 5430ES1.0 > > On 03/07/2012 1

Re: [U-Boot] [PATCH v4 0/6] Enable Thumb build for ARM platforms

Tom, > > > > Is an #error in a common omap4/5 file sufficient or does it need > to be > > > > sooner than that? > > > > > > If it can be tested there, it can probably also tested before we > start > > > building at all? > > > > I suspect no just because the kernel does this in > > > > I take it

Re: [U-Boot] [PATCH 0/2] ARM: mmu: Set domain permissions to client access - build warnings!

Hi Albert, On Thursday 28 February 2013 08:35 PM, Albert ARIBAUD wrote: On Thu, 28 Feb 2013 15:20:44 +0100, Albert ARIBAUD wrote: (sorry for any duplicate of this mail) Hi R Sricharan, On Tue, 8 Jan 2013 23:38:22 +0530, R Sricharan wrote: Currently for ARM based cpu's, mmu pagetable attr

[U-Boot] [PATCH RESEND] ARM: cache: declare set_section_dcache

From: Vincent Stehlé We declare the set_section_dcache function globally in the cache header, for later use by e.g. machine specific code. Signed-off-by: Vincent Stehlé ti.com> Cc: Tom Rini ti.com> Cc: Albert ARIBAUD --- arch/arm/include/asm/cache.h |1 + 1 file changed, 1 insertion(+)

Re: [U-Boot] [PATCH] omap5_common: Add optargs variable for kernel command line args

On Thursday 11 April 2013 08:52 PM, Tom Rini wrote: > Add 'optargs' variable to be set to additional kernel arguments, similar > to omap3*/am3* usage. > > Cc: Sricharan R > Signed-off-by: Tom Rini > --- > include/configs/omap5_common.h |2 ++ > 1 file

[U-Boot] [PATCH 5/5] ARM: OMAP: Add arch_cpu_init function

The boot parameters passed from SPL to UBOOT must be saved as a part of uboot's gd data as early as possible, before we will inadvertently overwrite it. So adding a arch_cpu_init for the required Socs to save it. Signed-off-by: Sricharan R --- arch/arm/cpu/armv7/omap-common/hwinit-com

[U-Boot] [PATCH 3/5] ARM: OMAP: Correct save_boot_params and replace with 'C' function

27;C' function instead of an assembly code that is more readable. Signed-off-by: Sricharan R --- There is a checkpatch warning because of multiple assignments. The code looks readable this way. arch/arm/cpu/armv7/omap-common/hwinit-common.c | 50 +--- arch

[U-Boot] [PATCH 0/5] ARM: OMAP: Cleanup save_boot_params function

added in this. Tested this on omap5 uevm board with SD boot. omap4/5 boards does not have a XIP flash. So yet to test XIP with this series. Also verfied a MAKEALL for armv7. Sricharan R (5): ARM: OMAP: Make omap_boot_parameters common across socs ARM: OMAP4/5: Make OMAPx_SRAM_SCRATCH_ defin

[U-Boot] [PATCH 1/5] ARM: OMAP: Make omap_boot_parameters common across socs

omap_boot_parameters is same and defined for each soc. So move this to a common place to reuse it across socs. Signed-off-by: Sricharan R --- arch/arm/include/asm/arch-am33xx/omap.h | 25 arch/arm/include/asm/arch-omap4/omap.h | 24 --- arch/arm/include/asm

[U-Boot] [PATCH 2/5] ARM: OMAP4/5: Make OMAPx_SRAM_SCRATCH_ defines common

These defines are same across OMAP4/5. So move them to omap_common.h. This is required for the patches that follow. Signed-off-by: Sricharan R --- arch/arm/cpu/armv7/omap4/emif.c|6 +++--- arch/arm/cpu/armv7/omap4/hw_data.c |2 +- arch/arm/cpu/armv7/omap4/hwinit.c

[U-Boot] [PATCH 4/5] ARM: OMAP: Cleanup boot parameters usage

The boot parameters are read from individual variables assigned for each of them. This been corrected and now they are stored as a part of the global data 'gd' structure. So read them from 'gd' instead. Signed-off-by: Sricharan R --- arch/arm/cpu/armv7/lowlevel_init.

Re: [U-Boot] [PATCH 3/5] ARM: OMAP: Correct save_boot_params and replace with 'C' function

On Monday 15 April 2013 08:58 PM, Tom Rini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/15/2013 11:08 AM, Sricharan R wrote: >> Currently save_boot_params saves the boot parameters passed from >> romcode. But this is not stored in a writable location

Re: [U-Boot] [PATCH 4/5] ARM: OMAP: Cleanup boot parameters usage

On Monday 15 April 2013 09:05 PM, Tom Rini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/15/2013 11:08 AM, Sricharan R wrote: >> The boot parameters are read from individual variables assigned >> for each of them. This been corrected and now they ar

Re: [U-Boot] [PATCH 4/5] ARM: OMAP: Cleanup boot parameters usage

On Monday 15 April 2013 09:13 PM, Tom Rini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/15/2013 11:39 AM, Sricharan R wrote: >> On Monday 15 April 2013 09:05 PM, Tom Rini wrote: >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> >

Re: [U-Boot] [PATCH 3/5] ARM: OMAP: Correct save_boot_params and replace with 'C' function

On Monday 15 April 2013 09:52 PM, Michael Cashwell wrote: > Hi Sricharan, > > I very much like how you've structured this. A vast improvement! > > I haven't yet tried to apply the whole series but have one quick comment. In > the new function: > > static void save_omap_boot_params(void) > { > .

  1   2   >