[PATCH] configs: am62x: enable secure device configs by default

2023-04-05 Thread Praneeth Bajjuri 
Enable the CONFIG_TI_SECURE_DEVICE by default

Non-HS devices will continue to boot due to runtime device type detection.

TI's security enforcing SoCs will authenticate each binary it loads by
comparing it's signature with keys etched into the SoC during the boot
up process. The am62x family of SoCs by default will have some level of
security enforcement checking. To keep things as simple as possible,
enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of
secure SoCs will work out of the box

Signed-off-by: Praneeth Bajjuri 
Signed-off-by: Kamlesh Gurudasani 
Signed-off-by: Bryan Brattlof 
---
 configs/am62x_evm_a53_defconfig | 1 +
 configs/am62x_evm_r5_defconfig  | 1 +
 2 files changed, 2 insertions(+)

diff --git a/configs/am62x_evm_a53_defconfig b/configs/am62x_evm_a53_defconfig
index cc9c8eab3e..fc76d88727 100644
--- a/configs/am62x_evm_a53_defconfig
+++ b/configs/am62x_evm_a53_defconfig
@@ -1,5 +1,6 @@
 CONFIG_ARM=y
 CONFIG_ARCH_K3=y
+CONFIG_TI_SECURE_DEVICE=y
 CONFIG_SYS_MALLOC_F_LEN=0x8000
 CONFIG_SPL_LIBCOMMON_SUPPORT=y
 CONFIG_SPL_LIBGENERIC_SUPPORT=y
diff --git a/configs/am62x_evm_r5_defconfig b/configs/am62x_evm_r5_defconfig
index 44a9130d99..cab8c820f9 100644
--- a/configs/am62x_evm_r5_defconfig
+++ b/configs/am62x_evm_r5_defconfig
@@ -1,5 +1,6 @@
 CONFIG_ARM=y
 CONFIG_ARCH_K3=y
+CONFIG_TI_SECURE_DEVICE=y
 CONFIG_SYS_MALLOC_LEN=0x0800
 CONFIG_SYS_MALLOC_F_LEN=0x9000
 CONFIG_SPL_LIBCOMMON_SUPPORT=y
-- 
2.17.1

Re: [PATCH v3 00/10] AM642-EVM: Add USB support

2021-06-06 Thread Praneeth Bajjuri 




On 6/4/21 11:53 AM, Praneeth Bajjuri wrote:

Aswath, Suman, Dave, Gowtham, Vignesh

On 6/4/21 11:49 AM, Aswath Govindraju wrote:

Hi Praneeth,

On 04/06/21 10:18 pm, Praneeth Bajjuri wrote:



On 6/4/21 11:30 AM, Aswath Govindraju wrote:

The following series of patches add support for the following
- Kconfig symbol for giving the load address for ATF
- USB Mass storage boot mode in AM642-EVM
- DFU boot mode in AM642-EVM
- Host and peripheral modes for AM642-EVM in U-Boot
- Set the USB PHY core voltage to 0.85V

changes since v2,
- Increased the max size of ATF in patch 9


Please confirm if this is tested on ATF 2.5 too.



Sorry, for not mentioning it.

Yes, this series was tested using ATF 2.5.


Ok , pulling to ti-u-boot.

Aswath:
1. Please send the updated series to upstream u-boot as well.
2. post the kernel dts change to mainline as well.

Vignesh,
Assuming you are pulling the KIG patch too.

Suman/Dave/Gowtham,
Assuming you are pulling the kernel patch too.


Please ignore this mail. was reviewing product baseline for same feature.







Thanks,
Aswath




- Added reviewed-by from Suman Anna in patch 1
- Reworded the subject of patch 8

changes since v1,
- Corrected the default load address of ATF to
    0x7000

Aswath Govindraju (10):
    tools: k3_fit_atf: Add support for providing ATF load address 
using a

  Kconfig symbol
    arm: mach-k3: am642_init: Add support for USB boot mode
    arm: mach-k3: am642_init: Do USB fixups to facilitate host and 
device

  boot modes
    board: ti: am64x: Set the core voltage of USB PHY to 0.85V
    arm: dts: k3-am64-main: Add USB DT nodes
    arm: dts: k3-am642-*-evm: Add USB support
    arm: dts: k3-am642-evm-u-boot: Add U-Boot tags and fix the 
dr_mode to

  peripheral for USB subsystem
    configs: am64x_evm_*_defconfig: Rearrange the components in SRAM to
  satisfy the limitations for USB DFU boot mode
    arm: dts: k3-am64-main: Update the location of ATF in SRAM and
  increase its max size
    configs: am64: Enable configs to support USB host and device modes

   arch/arm/dts/k3-am64-main.dtsi    | 32 -
   arch/arm/dts/k3-am642-evm-u-boot.dtsi | 13 ++
   arch/arm/dts/k3-am642-evm.dts | 18 
   arch/arm/dts/k3-am642-r5-evm.dts  | 18 
   arch/arm/mach-k3/Kconfig  |  7 +++
   arch/arm/mach-k3/am642_init.c | 46 
++-

   arch/arm/mach-k3/config.mk    |  1 +
   arch/arm/mach-k3/include/mach/am64_hardware.h | 11 +++--
   arch/arm/mach-k3/include/mach/am64_spl.h  |  6 ++-
   board/ti/am64x/evm.c  | 14 ++
   configs/am64x_evm_a53_defconfig   | 40 
   configs/am64x_evm_r5_defconfig    | 38 +--
   include/configs/am64x_evm.h   | 15 +-
   tools/k3_fit_atf.sh   |  9 ++--
   14 files changed, 251 insertions(+), 17 deletions(-)

Re: [PATCH v3 00/10] AM642-EVM: Add USB support

2021-06-04 Thread Praneeth Bajjuri 

Aswath, Suman, Dave, Gowtham, Vignesh

On 6/4/21 11:49 AM, Aswath Govindraju wrote:

Hi Praneeth,

On 04/06/21 10:18 pm, Praneeth Bajjuri wrote:



On 6/4/21 11:30 AM, Aswath Govindraju wrote:

The following series of patches add support for the following
- Kconfig symbol for giving the load address for ATF
- USB Mass storage boot mode in AM642-EVM
- DFU boot mode in AM642-EVM
- Host and peripheral modes for AM642-EVM in U-Boot
- Set the USB PHY core voltage to 0.85V

changes since v2,
- Increased the max size of ATF in patch 9


Please confirm if this is tested on ATF 2.5 too.



Sorry, for not mentioning it.

Yes, this series was tested using ATF 2.5.


Ok , pulling to ti-u-boot.

Aswath:
1. Please send the updated series to upstream u-boot as well.
2. post the kernel dts change to mainline as well.

Vignesh,
Assuming you are pulling the KIG patch too.

Suman/Dave/Gowtham,
Assuming you are pulling the kernel patch too.





Thanks,
Aswath




- Added reviewed-by from Suman Anna in patch 1
- Reworded the subject of patch 8

changes since v1,
- Corrected the default load address of ATF to
    0x7000

Aswath Govindraju (10):
    tools: k3_fit_atf: Add support for providing ATF load address using a
  Kconfig symbol
    arm: mach-k3: am642_init: Add support for USB boot mode
    arm: mach-k3: am642_init: Do USB fixups to facilitate host and device
  boot modes
    board: ti: am64x: Set the core voltage of USB PHY to 0.85V
    arm: dts: k3-am64-main: Add USB DT nodes
    arm: dts: k3-am642-*-evm: Add USB support
    arm: dts: k3-am642-evm-u-boot: Add U-Boot tags and fix the dr_mode to
  peripheral for USB subsystem
    configs: am64x_evm_*_defconfig: Rearrange the components in SRAM to
  satisfy the limitations for USB DFU boot mode
    arm: dts: k3-am64-main: Update the location of ATF in SRAM and
  increase its max size
    configs: am64: Enable configs to support USB host and device modes

   arch/arm/dts/k3-am64-main.dtsi    | 32 -
   arch/arm/dts/k3-am642-evm-u-boot.dtsi | 13 ++
   arch/arm/dts/k3-am642-evm.dts | 18 
   arch/arm/dts/k3-am642-r5-evm.dts  | 18 
   arch/arm/mach-k3/Kconfig  |  7 +++
   arch/arm/mach-k3/am642_init.c | 46 ++-
   arch/arm/mach-k3/config.mk    |  1 +
   arch/arm/mach-k3/include/mach/am64_hardware.h | 11 +++--
   arch/arm/mach-k3/include/mach/am64_spl.h  |  6 ++-
   board/ti/am64x/evm.c  | 14 ++
   configs/am64x_evm_a53_defconfig   | 40 
   configs/am64x_evm_r5_defconfig    | 38 +--
   include/configs/am64x_evm.h   | 15 +-
   tools/k3_fit_atf.sh   |  9 ++--
   14 files changed, 251 insertions(+), 17 deletions(-)

Re: [PATCH v3 00/10] AM642-EVM: Add USB support

2021-06-04 Thread Praneeth Bajjuri 




On 6/4/21 11:30 AM, Aswath Govindraju wrote:

The following series of patches add support for the following
- Kconfig symbol for giving the load address for ATF
- USB Mass storage boot mode in AM642-EVM
- DFU boot mode in AM642-EVM
- Host and peripheral modes for AM642-EVM in U-Boot
- Set the USB PHY core voltage to 0.85V

changes since v2,
- Increased the max size of ATF in patch 9


Please confirm if this is tested on ATF 2.5 too.



- Added reviewed-by from Suman Anna in patch 1
- Reworded the subject of patch 8

changes since v1,
- Corrected the default load address of ATF to
   0x7000

Aswath Govindraju (10):
   tools: k3_fit_atf: Add support for providing ATF load address using a
 Kconfig symbol
   arm: mach-k3: am642_init: Add support for USB boot mode
   arm: mach-k3: am642_init: Do USB fixups to facilitate host and device
 boot modes
   board: ti: am64x: Set the core voltage of USB PHY to 0.85V
   arm: dts: k3-am64-main: Add USB DT nodes
   arm: dts: k3-am642-*-evm: Add USB support
   arm: dts: k3-am642-evm-u-boot: Add U-Boot tags and fix the dr_mode to
 peripheral for USB subsystem
   configs: am64x_evm_*_defconfig: Rearrange the components in SRAM to
 satisfy the limitations for USB DFU boot mode
   arm: dts: k3-am64-main: Update the location of ATF in SRAM and
 increase its max size
   configs: am64: Enable configs to support USB host and device modes

  arch/arm/dts/k3-am64-main.dtsi| 32 -
  arch/arm/dts/k3-am642-evm-u-boot.dtsi | 13 ++
  arch/arm/dts/k3-am642-evm.dts | 18 
  arch/arm/dts/k3-am642-r5-evm.dts  | 18 
  arch/arm/mach-k3/Kconfig  |  7 +++
  arch/arm/mach-k3/am642_init.c | 46 ++-
  arch/arm/mach-k3/config.mk|  1 +
  arch/arm/mach-k3/include/mach/am64_hardware.h | 11 +++--
  arch/arm/mach-k3/include/mach/am64_spl.h  |  6 ++-
  board/ti/am64x/evm.c  | 14 ++
  configs/am64x_evm_a53_defconfig   | 40 
  configs/am64x_evm_r5_defconfig| 38 +--
  include/configs/am64x_evm.h   | 15 +-
  tools/k3_fit_atf.sh   |  9 ++--
  14 files changed, 251 insertions(+), 17 deletions(-)

[PATCH] arm: dts: k3-j7200: ddr: Update to 0.5.0 version of DDR for LPDDR 2666MTs

2021-06-03 Thread praneeth 
From: Kevin Scholz 

Update the ddr settings to use the DDR reg config tool rev 0.5.0.
This enables 2666MTs LPDDR configuration on J7200.

Signed-off-by: Kevin Scholz 
Signed-off-by: Praneeth Bajjuri 
Tested-by: Suman Anna 
---
 ...00.dtsi => k3-j7200-ddr-evm-lp4-2666.dtsi} | 437 +-
 .../arm/dts/k3-j7200-r5-common-proc-board.dts |   2 +-
 2 files changed, 220 insertions(+), 219 deletions(-)
 rename arch/arm/dts/{k3-j7200-ddr-evm-lp4-1600.dtsi => 
k3-j7200-ddr-evm-lp4-2666.dtsi} (90%)

diff --git a/arch/arm/dts/k3-j7200-ddr-evm-lp4-1600.dtsi 
b/arch/arm/dts/k3-j7200-ddr-evm-lp4-2666.dtsi
similarity index 90%
rename from arch/arm/dts/k3-j7200-ddr-evm-lp4-1600.dtsi
rename to arch/arm/dts/k3-j7200-ddr-evm-lp4-2666.dtsi
index 12ffd913d1..42ac8c5c89 100644
--- a/arch/arm/dts/k3-j7200-ddr-evm-lp4-1600.dtsi
+++ b/arch/arm/dts/k3-j7200-ddr-evm-lp4-2666.dtsi
@@ -1,13 +1,14 @@
 // SPDX-License-Identifier: GPL-2.0+
 /*
- * This file was generated by the AM752x_DRA82x_TDA4x_DDRSS_RegConfigTool, 
Revision: 0.3.0
- * This file was generated on 06/08/2020
- * Includes hand edits
+ * Copyright (C) 2019 Texas Instruments Incorporated - http://www.ti.com/
+ * This file was generated by the Jacinto7_DDRSS_RegConfigTool, Revision: 0.5.0
+ * This file was generated on 08/07/2020
+ * Includes hand-edits
  */
 
 #define DDRSS_PLL_FHS_CNT 10
-#define DDRSS_PLL_FREQUENCY_1 4
-#define DDRSS_PLL_FREQUENCY_2 4
+#define DDRSS_PLL_FREQUENCY_1 66650
+#define DDRSS_PLL_FREQUENCY_2 66650
 
 #define DDRSS_CTL_00_DATA 0x0B00
 #define DDRSS_CTL_01_DATA 0x
@@ -20,14 +21,14 @@
 #define DDRSS_CTL_08_DATA 0x000186A0
 #define DDRSS_CTL_09_DATA 0x0005
 #define DDRSS_CTL_10_DATA 0x0064
-#define DDRSS_CTL_11_DATA 0x00027100
-#define DDRSS_CTL_12_DATA 0x00186A00
+#define DDRSS_CTL_11_DATA 0x000411AB
+#define DDRSS_CTL_12_DATA 0x0028B0AB
 #define DDRSS_CTL_13_DATA 0x0005
-#define DDRSS_CTL_14_DATA 0x0640
-#define DDRSS_CTL_15_DATA 0x00027100
-#define DDRSS_CTL_16_DATA 0x00186A00
+#define DDRSS_CTL_14_DATA 0x0A6B
+#define DDRSS_CTL_15_DATA 0x000411AB
+#define DDRSS_CTL_16_DATA 0x0028B0AB
 #define DDRSS_CTL_17_DATA 0x0005
-#define DDRSS_CTL_18_DATA 0x0640
+#define DDRSS_CTL_18_DATA 0x0A6B
 #define DDRSS_CTL_19_DATA 0x0101
 #define DDRSS_CTL_20_DATA 0x02011001
 #define DDRSS_CTL_21_DATA 0x0201
@@ -37,66 +38,66 @@
 #define DDRSS_CTL_25_DATA 0x
 #define DDRSS_CTL_26_DATA 0x
 #define DDRSS_CTL_27_DATA 0x02020200
-#define DDRSS_CTL_28_DATA 0x2020
+#define DDRSS_CTL_28_DATA 0x3636
 #define DDRSS_CTL_29_DATA 0x0010
 #define DDRSS_CTL_30_DATA 0x
 #define DDRSS_CTL_31_DATA 0x
 #define DDRSS_CTL_32_DATA 0x
 #define DDRSS_CTL_33_DATA 0x
 #define DDRSS_CTL_34_DATA 0x040C
-#define DDRSS_CTL_35_DATA 0x081C081C
+#define DDRSS_CTL_35_DATA 0x0C300C30
 #define DDRSS_CTL_36_DATA 0x00050804
 #define DDRSS_CTL_37_DATA 0x09040008
-#define DDRSS_CTL_38_DATA 0x08000204
-#define DDRSS_CTL_39_DATA 0x0B240034
-#define DDRSS_CTL_40_DATA 0x08001910
-#define DDRSS_CTL_41_DATA 0x0B240034
-#define DDRSS_CTL_42_DATA 0x20001910
+#define DDRSS_CTL_38_DATA 0x0D000204
+#define DDRSS_CTL_39_DATA 0x113C0057
+#define DDRSS_CTL_40_DATA 0x0D00291B
+#define DDRSS_CTL_41_DATA 0x113C0057
+#define DDRSS_CTL_42_DATA 0x2000291B
 #define DDRSS_CTL_43_DATA 0x000A0A09
 #define DDRSS_CTL_44_DATA 0x040006DB
-#define DDRSS_CTL_45_DATA 0x0C0A0904
-#define DDRSS_CTL_46_DATA 0x06006DB0
-#define DDRSS_CTL_47_DATA 0x0C0A0906
-#define DDRSS_CTL_48_DATA 0x06006DB0
-#define DDRSS_CTL_49_DATA 0x02030406
-#define DDRSS_CTL_50_DATA 0x11040500
-#define DDRSS_CTL_51_DATA 0x08121112
+#define DDRSS_CTL_45_DATA 0x130E0B04
+#define DDRSS_CTL_46_DATA 0x0A00B6D0
+#define DDRSS_CTL_47_DATA 0x130E0B0A
+#define DDRSS_CTL_48_DATA 0x0A00B6D0
+#define DDRSS_CTL_49_DATA 0x0203040A
+#define DDRSS_CTL_50_DATA 0x1C040500
+#define DDRSS_CTL_51_DATA 0x081D1C1D
 #define DDRSS_CTL_52_DATA 0x14000D0A
 #define DDRSS_CTL_53_DATA 0x02010A0A
 #define DDRSS_CTL_54_DATA 0x01010002
-#define DDRSS_CTL_55_DATA 0x0408
-#define DDRSS_CTL_56_DATA 0x04131304
-#define DDRSS_CTL_57_DATA 0x1313
+#define DDRSS_CTL_55_DATA 0x04383808
+#define DDRSS_CTL_56_DATA 0x041F1F04
+#define DDRSS_CTL_57_DATA 0x1F1F
 #define DDRSS_CTL_58_DATA 0x00010100
 #define DDRSS_CTL_59_DATA 0x0301
 #define DDRSS_CTL_60_DATA 0x0E08
 #define DDRSS_CTL_61_DATA 0x00BB
-#define DDRSS_CTL_62_DATA 0x00E0
-#define DDRSS_CTL_63_DATA 0x0C28
-#define DDRSS_CTL_64_DATA 0x00E0
-#define DDRSS_CTL_65_DATA 0x0C28
+#define DDRSS_CTL_62_DATA 0x0176
+#define DDRSS_CTL_63_DATA 0x1448
+#define DDRSS_CTL_64_DATA 0x0176
+#define DDRSS_CTL_65_DATA 0x1448
 #define DDRSS_CTL_66_DATA 0x0005
 #define DDRSS_CTL_67_DATA 0x0003
-#define DDRSS_CTL_68_DATA 0x00380010
-#define DDRSS_CTL_69_DATA 0x0038017E
-#define DDRSS_CTL_70_DATA 0x0040017E
+#define DDRSS_CTL_68_DATA 0x005D0010
+#

[PATCH] arm: dts: k3-j721e: ddr: Update to 0.5.0 version of DDR config tool

2020-12-03 Thread praneeth 
From: Praneeth Bajjuri 

Update the ddr settings to use the DDR reg config tool rev 0.5.0.
This enables 4266MTs DDR configuration.

Signed-off-by: Praneeth Bajjuri 
Signed-off-by: Kevin Scholz 
---
 ...33.dtsi => k3-j721e-ddr-evm-lp4-4266.dtsi} | 436 +-
 .../arm/dts/k3-j721e-r5-common-proc-board.dts |   2 +-
 2 files changed, 219 insertions(+), 219 deletions(-)
 rename arch/arm/dts/{k3-j721e-ddr-evm-lp4-3733.dtsi => 
k3-j721e-ddr-evm-lp4-4266.dtsi} (90%)

diff --git a/arch/arm/dts/k3-j721e-ddr-evm-lp4-3733.dtsi 
b/arch/arm/dts/k3-j721e-ddr-evm-lp4-4266.dtsi
similarity index 90%
rename from arch/arm/dts/k3-j721e-ddr-evm-lp4-3733.dtsi
rename to arch/arm/dts/k3-j721e-ddr-evm-lp4-4266.dtsi
index 5ac32a0ffa..ca05e06e93 100644
--- a/arch/arm/dts/k3-j721e-ddr-evm-lp4-3733.dtsi
+++ b/arch/arm/dts/k3-j721e-ddr-evm-lp4-4266.dtsi
@@ -1,13 +1,13 @@
 // SPDX-License-Identifier: GPL-2.0+
 /*
  * Copyright (C) 2019 Texas Instruments Incorporated - http://www.ti.com/
- * This file was generated by the AM752x_DRA82x_TDA4x_DDRSS_RegConfigTool, 
Revision: 0.2.0
- * This file was generated on 10/09/2019
+ * This file was generated by the Jacinto7_DDRSS_RegConfigTool, Revision: 0.5.0
+ * This file was generated on 09/25/2020
 */
 
 #define DDRSS_PLL_FHS_CNT 10
-#define DDRSS_PLL_FREQUENCY_1 93300
-#define DDRSS_PLL_FREQUENCY_2 93300
+#define DDRSS_PLL_FREQUENCY_1 106650
+#define DDRSS_PLL_FREQUENCY_2 106650
 
 #define DDRSS_CTL_00_DATA 0x0B00
 #define DDRSS_CTL_01_DATA 0x
@@ -20,14 +20,14 @@
 #define DDRSS_CTL_08_DATA 0x000186A0
 #define DDRSS_CTL_09_DATA 0x0005
 #define DDRSS_CTL_10_DATA 0x0064
-#define DDRSS_CTL_11_DATA 0x0005B18F
-#define DDRSS_CTL_12_DATA 0x0038EF90
+#define DDRSS_CTL_11_DATA 0x000681C8
+#define DDRSS_CTL_12_DATA 0x004111C9
 #define DDRSS_CTL_13_DATA 0x0005
-#define DDRSS_CTL_14_DATA 0x0E94
-#define DDRSS_CTL_15_DATA 0x0005B18F
-#define DDRSS_CTL_16_DATA 0x0038EF90
+#define DDRSS_CTL_14_DATA 0x10A9
+#define DDRSS_CTL_15_DATA 0x000681C8
+#define DDRSS_CTL_16_DATA 0x004111C9
 #define DDRSS_CTL_17_DATA 0x0005
-#define DDRSS_CTL_18_DATA 0x0E94
+#define DDRSS_CTL_18_DATA 0x10A9
 #define DDRSS_CTL_19_DATA 0x0101
 #define DDRSS_CTL_20_DATA 0x02011001
 #define DDRSS_CTL_21_DATA 0x0201
@@ -37,66 +37,66 @@
 #define DDRSS_CTL_25_DATA 0x
 #define DDRSS_CTL_26_DATA 0x
 #define DDRSS_CTL_27_DATA 0x02020200
-#define DDRSS_CTL_28_DATA 0x4B4B
+#define DDRSS_CTL_28_DATA 0x5656
 #define DDRSS_CTL_29_DATA 0x0010
 #define DDRSS_CTL_30_DATA 0x
 #define DDRSS_CTL_31_DATA 0x
 #define DDRSS_CTL_32_DATA 0x
 #define DDRSS_CTL_33_DATA 0x
 #define DDRSS_CTL_34_DATA 0x040C
-#define DDRSS_CTL_35_DATA 0x10401040
+#define DDRSS_CTL_35_DATA 0x12481248
 #define DDRSS_CTL_36_DATA 0x00050804
 #define DDRSS_CTL_37_DATA 0x09040008
-#define DDRSS_CTL_38_DATA 0x12000204
-#define DDRSS_CTL_39_DATA 0x1854007A
-#define DDRSS_CTL_40_DATA 0x12003A26
-#define DDRSS_CTL_41_DATA 0x1854007A
-#define DDRSS_CTL_42_DATA 0x20003A26
+#define DDRSS_CTL_38_DATA 0x15000204
+#define DDRSS_CTL_39_DATA 0x1B60008B
+#define DDRSS_CTL_40_DATA 0x1500422B
+#define DDRSS_CTL_41_DATA 0x1B60008B
+#define DDRSS_CTL_42_DATA 0x2000422B
 #define DDRSS_CTL_43_DATA 0x000A0A09
 #define DDRSS_CTL_44_DATA 0x040006DB
-#define DDRSS_CTL_45_DATA 0x1B130F04
-#define DDRSS_CTL_46_DATA 0x0E00FFCD
-#define DDRSS_CTL_47_DATA 0x1B130F0E
-#define DDRSS_CTL_48_DATA 0x0E00FFCD
-#define DDRSS_CTL_49_DATA 0x0203040E
-#define DDRSS_CTL_50_DATA 0x26040500
-#define DDRSS_CTL_51_DATA 0x08282628
+#define DDRSS_CTL_45_DATA 0x1E161104
+#define DDRSS_CTL_46_DATA 0x10012458
+#define DDRSS_CTL_47_DATA 0x1E161110
+#define DDRSS_CTL_48_DATA 0x10012458
+#define DDRSS_CTL_49_DATA 0x02030410
+#define DDRSS_CTL_50_DATA 0x2C040500
+#define DDRSS_CTL_51_DATA 0x082D2C2D
 #define DDRSS_CTL_52_DATA 0x14000D0A
-#define DDRSS_CTL_53_DATA 0x03010A0A
-#define DDRSS_CTL_54_DATA 0x01010003
-#define DDRSS_CTL_55_DATA 0x044E4E08
-#define DDRSS_CTL_56_DATA 0x042B2B04
-#define DDRSS_CTL_57_DATA 0x2B2B
+#define DDRSS_CTL_53_DATA 0x04010A0A
+#define DDRSS_CTL_54_DATA 0x01010004
+#define DDRSS_CTL_55_DATA 0x04585808
+#define DDRSS_CTL_56_DATA 0x04313104
+#define DDRSS_CTL_57_DATA 0x3131
 #define DDRSS_CTL_58_DATA 0x00010100
 #define DDRSS_CTL_59_DATA 0x0301
 #define DDRSS_CTL_60_DATA 0x0E08
 #define DDRSS_CTL_61_DATA 0x00BB
-#define DDRSS_CTL_62_DATA 0x020B
-#define DDRSS_CTL_63_DATA 0x1C64
-#define DDRSS_CTL_64_DATA 0x020B
-#define DDRSS_CTL_65_DATA 0x1C64
+#define DDRSS_CTL_62_DATA 0x0256
+#define DDRSS_CTL_63_DATA 0x2073
+#define DDRSS_CTL_64_DATA 0x0256
+#define DDRSS_CTL_65_DATA 0x2073
 #define DDRSS_CTL_66_DATA 0x0005
 #define DDRSS_CTL_67_DATA 0x0003
-#define DDRSS_CTL_68_DATA 0x00830010
-#define DDRSS_CTL_69_DATA 0x00830386
-#define DDRSS_CTL_70_DATA 0x00400386
+#define DDRSS_CTL_68_DATA 0x00950010
+#

[PATCH] ddr: k3-am654: EMIF Tool update to 2.02 for IO optimizations and fixes

2020-05-07 Thread praneeth 
From: Praneeth Bajjuri 

EMIF tool for AM65x [1] is now updated from rev 1.98 to 2.02

This update includes
* Optimizations in IO configuration.
* Fix for byte enablement in GCR registers.
* Fixes for PG2.0 including ZQ control.

[1]: http://www.ti.com/lit/zip/sprcah7

Acked-by: James Doublesin 
Signed-off-by: Praneeth Bajjuri 
---
 .../dts/k3-am654-base-board-ddr4-1600MTs.dtsi | 28 +--
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/arch/arm/dts/k3-am654-base-board-ddr4-1600MTs.dtsi 
b/arch/arm/dts/k3-am654-base-board-ddr4-1600MTs.dtsi
index d07aaea93f..5638321903 100644
--- a/arch/arm/dts/k3-am654-base-board-ddr4-1600MTs.dtsi
+++ b/arch/arm/dts/k3-am654-base-board-ddr4-1600MTs.dtsi
@@ -1,7 +1,7 @@
 // SPDX-License-Identifier: GPL-2.0+
 /*
- * Copyright (C) 2018 Texas Instruments Incorporated - http://www.ti.com/
- * This file was generated by AM65x_DRA80xM_EMIF_Tool_1.98.xlsm
+ * Copyright (C) 2020 Texas Instruments Incorporated - http://www.ti.com/
+ * This file was generated by AM65x_DRA80xM_EMIF_Tool_2.02.xlsm
  * http://www.ti.com/lit/pdf/spracj0
  * Configuration Parameters
  * Memory Type: DDR4
@@ -24,7 +24,7 @@
 #define DDRCTL_INIT4 0x0020
 #define DDRCTL_INIT5 0x0010
 #define DDRCTL_INIT6 0x0480
-#define DDRCTL_INIT7 0x04E8
+#define DDRCTL_INIT7 0x0497
 #define DDRCTL_DRAMTMG0 0x0C0A1B0D
 #define DDRCTL_DRAMTMG1 0x00030313
 #define DDRCTL_DRAMTMG2 0x0506050A
@@ -33,10 +33,10 @@
 #define DDRCTL_DRAMTMG5 0x04040302
 #define DDRCTL_DRAMTMG6 0x0004
 #define DDRCTL_DRAMTMG7 0x0404
-#define DDRCTL_DRAMTMG8 0x03030A05
+#define DDRCTL_DRAMTMG8 0x03030C05
 #define DDRCTL_DRAMTMG9 0x00020208
 #define DDRCTL_DRAMTMG10 0x001C180A
-#define DDRCTL_DRAMTMG11 0x0E06010E
+#define DDRCTL_DRAMTMG11 0x1106010E
 #define DDRCTL_DRAMTMG12 0x00020008
 #define DDRCTL_DRAMTMG13 0x0B12
 #define DDRCTL_DRAMTMG14 0x
@@ -84,33 +84,33 @@
 #define DDRPHY_DCR 0x040C
 #define DDRPHY_DTPR0 0x041A0B06
 #define DDRPHY_DTPR1 0x2814
-#define DDRPHY_DTPR2 0x0034E255
-#define DDRPHY_DTPR3 0x01D50800
+#define DDRPHY_DTPR2 0x0034E300
+#define DDRPHY_DTPR3 0x02800800
 #define DDRPHY_DTPR4 0x31180805
 #define DDRPHY_DTPR5 0x00250B06
 #define DDRPHY_DTPR6 0x0505
 #define DDRPHY_ZQCR 0x008A2A58
 #define DDRPHY_ZQ0PR0 0x77DD
-#define DDRPHY_ZQ1PR0 0x77DD
+#define DDRPHY_ZQ1PR0 0x7799
 #define DDRPHY_MR0 0x0214
 #define DDRPHY_MR1 0x0501
 #define DDRPHY_MR2 0x
 #define DDRPHY_MR3 0x0020
 #define DDRPHY_MR4 0x
 #define DDRPHY_MR5 0x0480
-#define DDRPHY_MR6 0x04E8
+#define DDRPHY_MR6 0x0497
 #define DDRPHY_MR11 0x
 #define DDRPHY_MR12 0x
 #define DDRPHY_MR13 0x
 #define DDRPHY_MR14 0x
 #define DDRPHY_MR22 0x
-#define DDRPHY_VTCR0 0xF3C32028
+#define DDRPHY_VTCR0 0xF3C32017
 #define DDRPHY_DX8SL0PLLCR0 0x021c4000
 #define DDRPHY_DX8SL1PLLCR0 0x021c4000
 #define DDRPHY_DX8SL2PLLCR0 0x021c4000
 #define DDRPHY_DTCR0 0x8000B1C7
 #define DDRPHY_DTCR1 0x00010236
-#define DDRPHY_ACIOCR0 0x3007
+#define DDRPHY_ACIOCR0 0xF007
 #define DDRPHY_ACIOCR3 0x0001
 #define DDRPHY_ACIOCR5 0x0480
 #define DDRPHY_IOVCR0 0x0F0C0C0C
@@ -157,6 +157,6 @@
 #define DDRPHY_DX8SL0DXCTL2 0x00141830
 #define DDRPHY_DX8SL1DXCTL2 0x00141830
 #define DDRPHY_DX8SL2DXCTL2 0x00141830
-#define DDRPHY_DX8SL0DQSCTL 0x01264000
-#define DDRPHY_DX8SL1DQSCTL 0x01264000
-#define DDRPHY_DX8SL2DQSCTL 0x01264000
+#define DDRPHY_DX8SL0DQSCTL 0x01264300
+#define DDRPHY_DX8SL1DQSCTL 0x01264300
+#define DDRPHY_DX8SL2DQSCTL 0x01264300
-- 
2.17.1

Re: [PATCH] tools: image-host.c: remove uboot_aes.h

2020-02-19 Thread Bajjuri, Praneeth 



On 2/19/2020 11:17 AM, Andrew F. Davis wrote:

+Praneeth

On 2/18/20 11:23 AM, Philippe Reynes wrote:

The include uboot_aes.h is not usefull and
it breaks the compilation on android, so
we remove it.



Thanks for the fix.




Signed-off-by: Philippe Reynes 



Reported-by: Praneeth Bajjuri 



---
  tools/image-host.c | 1 -
  1 file changed, 1 deletion(-)

diff --git a/tools/image-host.c b/tools/image-host.c
index 9483561..76a361b 100644
--- a/tools/image-host.c
+++ b/tools/image-host.c
@@ -12,7 +12,6 @@
  #include 
  #include 
  #include 
-#include 
  
  /**

   * fit_set_hash_value - set hash value in requested has node

Re: [PATCH v4 00/10] am57xx: Implement Android 10 boot flow

2020-01-24 Thread Bajjuri, Praneeth 



On 1/24/2020 9:53 AM, Sam Protsenko wrote:

Android 10 brings a lot of new requirements for bootloaders: [1]. This
patch series attempts to implement such a boot process on BeagleBoard
X15 platform. Some common code is added too, which can be reused later
for other platforms (see "abootimg" command and associated C API).

Changes in v4:
  - fixed broken build due to recent load_addr -> image_load_addr
renaming
  - added "doc: android: Convert to Sphinx format" patch to series
  - addressed pending comments for v3 on mailing list
  - rebased series on top of current master

Changes in v3:
  - rename command to "abootimg" (requested by Simon Glass)
  - rework command interface (as discussed with Eugeniu)
  - add command documentation
  - address other comments

[1] https://source.android.com/devices/bootloader


Verified Key functionality as mentioned in [1] on AM57x X15
A/B , AVB , fastbootd, super image ( vendor + system), recovery mode
on AOSP master

For the series
Acked-by: Praneeth Bajjuri 




Sam Protsenko (10):
   image: android: Add functions for handling dtb field
   image: android: Add routine to get dtbo params
   cmd: abootimg: Add abootimg command
   doc: android: Add documentation for Android Boot Image
   doc: android: Convert to Sphinx format
   test/py: android: Add test for abootimg
   configs: am57xx_evm: Enable Android commands
   env: ti: boot: Respect slot_suffix in AVB commands
   env: ti: boot: Boot Android with dynamic partitions
   arm: ti: boot: Use correct dtb and dtbo on Android boot

  MAINTAINERS   |   4 +-
  cmd/Kconfig   |  12 +-
  cmd/Makefile  |   1 +
  cmd/abootimg.c| 258 
  common/Makefile   |   2 +-
  common/image-android.c| 282 ++
  configs/am57xx_evm_defconfig  |   6 +
  configs/am57xx_hs_evm_defconfig   |   6 +
  configs/am57xx_hs_evm_usb_defconfig   |   6 +
  configs/sandbox_defconfig |   1 +
  doc/android/{ab.txt => ab.rst}|  39 +--
  doc/android/avb2.rst  | 133 +
  doc/android/avb2.txt  | 115 ---
  doc/android/bcb.rst   | 100 +++
  doc/android/bcb.txt   |  89 --
  doc/android/boot-image.rst| 154 ++
  ...oot-protocol.txt => fastboot-protocol.rst} |  45 +--
  doc/android/{fastboot.txt => fastboot.rst}|  92 +++---
  doc/android/index.rst |  14 +
  doc/index.rst |  12 +
  include/configs/ti_armv7_common.h |   7 +
  include/environment/ti/boot.h | 154 +-
  include/image.h   |   6 +
  test/py/tests/test_android/test_abootimg.py   | 159 ++
  test/py/tests/test_android/test_avb.py|   2 +-
  25 files changed, 1335 insertions(+), 364 deletions(-)
  create mode 100644 cmd/abootimg.c
  rename doc/android/{ab.txt => ab.rst} (52%)
  create mode 100644 doc/android/avb2.rst
  delete mode 100644 doc/android/avb2.txt
  create mode 100644 doc/android/bcb.rst
  delete mode 100644 doc/android/bcb.txt
  create mode 100644 doc/android/boot-image.rst
  rename doc/android/{fastboot-protocol.txt => fastboot-protocol.rst} (82%)
  rename doc/android/{fastboot.txt => fastboot.rst} (79%)
  create mode 100644 doc/android/index.rst
  create mode 100644 test/py/tests/test_android/test_abootimg.py

Re: [PATCH v3 0/9] am57xx: Implement Android 10 boot flow

2020-01-22 Thread Bajjuri, Praneeth 

+ Sam Protsenko's current email address

On 1/22/2020 11:51 AM, Bajjuri, Praneeth wrote:

Tom,

On 12/24/2019 1:54 PM, Sam Protsenko wrote:

Android 10 brings a lot of new requirements for bootloaders: [1]. This
patch series attempts to implement such a boot process on BeagleBoard
X15 platform. Some common code is added too, which can be reused later
for other platforms (see "abootimg" command and associated C API).

This patch series must be applied on top of these recently sent patches
by Eugeniu:

 [PATCH 0/3] cmd: dtimg: Rename to adtimg and refactor usage style

Changes in v3:
  - rename command to "abootimg" (requested by Simon Glass)
  - rework command interface (as discussed with Eugeniu)
  - add command documentation
  - address other comments



Since this series is functionally mature,
can this series be pulled as-is in the next merge window,
verified v3 with current aosp master and functionality is working
as expected.

the comments on changing to a more suitable names , adding a
new test script for the functionality can be done as a incremental
update on the top during the next cycle.




[1] https://source.android.com/devices/bootloader

Sam Protsenko (9):
   image: android: Add functions for handling dtb field
   image: android: Add routine to get dtbo params
   cmd: abootimg: Add abootimg command
   doc: android: Add documentation for Android Boot Image
   test/py: android: Add test for abootimg
   configs: am57xx_evm: Enable Android commands
   env: ti: boot: Respect slot_suffix in AVB commands
   env: ti: boot: Boot Android with dynamic partitions
   arm: ti: boot: Use correct dtb and dtbo on Android boot

  cmd/Kconfig |  10 +
  cmd/Makefile    |   1 +
  cmd/abootimg.c  | 242 +
  common/Makefile |   2 +-
  common/image-android.c  | 275 
  configs/am57xx_evm_defconfig    |   6 +
  configs/am57xx_hs_evm_defconfig |   6 +
  configs/am57xx_hs_evm_usb_defconfig |   6 +
  configs/sandbox_defconfig   |   1 +
  doc/android/boot-image.rst  | 154 +++
  include/configs/ti_armv7_common.h   |   7 +
  include/environment/ti/boot.h   | 146 ++-
  include/image.h |   6 +
  test/py/tests/test_android/test_abootimg.py | 159 +++
  14 files changed, 954 insertions(+), 67 deletions(-)
  create mode 100644 cmd/abootimg.c
  create mode 100644 doc/android/boot-image.rst
  create mode 100644 test/py/tests/test_android/test_abootimg.py

Re: [PATCH v3 0/9] am57xx: Implement Android 10 boot flow

2020-01-22 Thread Bajjuri, Praneeth 

Tom,

On 12/24/2019 1:54 PM, Sam Protsenko wrote:

Android 10 brings a lot of new requirements for bootloaders: [1]. This
patch series attempts to implement such a boot process on BeagleBoard
X15 platform. Some common code is added too, which can be reused later
for other platforms (see "abootimg" command and associated C API).

This patch series must be applied on top of these recently sent patches
by Eugeniu:

 [PATCH 0/3] cmd: dtimg: Rename to adtimg and refactor usage style

Changes in v3:
  - rename command to "abootimg" (requested by Simon Glass)
  - rework command interface (as discussed with Eugeniu)
  - add command documentation
  - address other comments



Since this series is functionally mature,
can this series be pulled as-is in the next merge window,
verified v3 with current aosp master and functionality is working
as expected.

the comments on changing to a more suitable names , adding a
new test script for the functionality can be done as a incremental
update on the top during the next cycle.




[1] https://source.android.com/devices/bootloader

Sam Protsenko (9):
   image: android: Add functions for handling dtb field
   image: android: Add routine to get dtbo params
   cmd: abootimg: Add abootimg command
   doc: android: Add documentation for Android Boot Image
   test/py: android: Add test for abootimg
   configs: am57xx_evm: Enable Android commands
   env: ti: boot: Respect slot_suffix in AVB commands
   env: ti: boot: Boot Android with dynamic partitions
   arm: ti: boot: Use correct dtb and dtbo on Android boot

  cmd/Kconfig |  10 +
  cmd/Makefile|   1 +
  cmd/abootimg.c  | 242 +
  common/Makefile |   2 +-
  common/image-android.c  | 275 
  configs/am57xx_evm_defconfig|   6 +
  configs/am57xx_hs_evm_defconfig |   6 +
  configs/am57xx_hs_evm_usb_defconfig |   6 +
  configs/sandbox_defconfig   |   1 +
  doc/android/boot-image.rst  | 154 +++
  include/configs/ti_armv7_common.h   |   7 +
  include/environment/ti/boot.h   | 146 ++-
  include/image.h |   6 +
  test/py/tests/test_android/test_abootimg.py | 159 +++
  14 files changed, 954 insertions(+), 67 deletions(-)
  create mode 100644 cmd/abootimg.c
  create mode 100644 doc/android/boot-image.rst
  create mode 100644 test/py/tests/test_android/test_abootimg.py

Re: [PATCH] MAINTAINERS: Fix mail

2020-01-14 Thread Bajjuri, Praneeth 



On 1/14/2020 11:54 AM, Sam Protsenko wrote:

Sam doesn't work for Linaro anymore, so Linaro mail is not valid. Change
it to his home mail instead.

Signed-off-by: Sam Protsenko 



Acked-by: Praneeth Bajjuri 



---
  MAINTAINERS | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index b9e7cd9944..fa4bf0f2d4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -52,7 +52,7 @@ Maintainers List (try to look for most precise areas first)
---
  ANDROID AB
  M:Igor Opaniuk 
-R: Sam Protsenko 
+R: Sam Protsenko 
  S:Maintained
  F:cmd/ab_select.c
  F:common/android_ab.c

Re: [U-Boot] [PATCH v3 3/7] common: Implement A/B metadata

2019-03-18 Thread Bajjuri, Praneeth 

Eugeniu,

On 3/18/2019 3:21 PM, Eugeniu Rosca wrote:

I received the following bounce:


Thank you for your email.

Igor Opaniuk no longer works for Linaro.

If your email is related to Linaro business, please use the Contact
form (https://www.linaro.org/contact/) if you do not have another
Linaro email address to use.

I hope this is a glitch? Otherwise, any suggestions how to proceed here?



Not a glitch, Igor's linaro email id is no longer active. He might 
respond with updated email

address soon.




Thanks,
Eugeniu.

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH] arm: ti: boot: Fix am57xx evm fdtfile name

2019-01-09 Thread Praneeth Bajjuri 
am57xx evm uses am57xx-evm-reva3.dtb.
update findfdt to pick the correct default dtb

Signed-off-by: Praneeth Bajjuri 
---
 include/environment/ti/boot.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h
index 86ff6d3ea7c6..c9ad3046acaa 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -125,7 +125,7 @@
"if test $board_name = am57xx_evm; then " \
"setenv fdtfile am57xx-beagle-x15.dtb; fi;" \
"if test $board_name = am57xx_evm_reva3; then " \
-   "setenv fdtfile am57xx-beagle-x15.dtb; fi;" \
+   "setenv fdtfile am57xx-evm-reva3.dtb; fi;" \
"if test $board_name = am571x_idk; then " \
"setenv fdtfile am571x-idk.dtb; fi;" \
"if test $fdtfile = undefined; then " \
-- 
2.7.4

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: ti: boot: Remove legacy Android partitions

2019-01-04 Thread Bajjuri, Praneeth 


On 1/4/2019 2:09 PM, Sam Protsenko wrote:

Remove unused Android partitions:
   - efs, crypto, cache: we don't use it anymore (images are not built
 in AOSP
   - ipu1, ipu2: IPU firmware is now a part of vendor image and doesn't
 reside as a separate partition

While at it, rename "reserved" partition to "uboot-env", as it's
actually stores U-Boot environment.

Signed-off-by: Sam Protsenko 

Signed-off-by: Praneeth Bajjuri 

---
  include/environment/ti/boot.h | 7 +--
  1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h
index 86ff6d3ea7..05bdbbc23e 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -35,17 +35,12 @@
"uuid_disk=${uuid_gpt_disk};" \
"name=xloader,start=128K,size=256K,uuid=${uuid_gpt_xloader};" \
"name=bootloader,size=2048K,uuid=${uuid_gpt_bootloader};" \
-   "name=reserved,start=2432K,size=256K,uuid=${uuid_gpt_reserved};" \
+   "name=uboot-env,start=2432K,size=256K,uuid=${uuid_gpt_reserved};" \
"name=misc,size=128K,uuid=${uuid_gpt_misc};" \
-   "name=efs,size=16M,uuid=${uuid_gpt_efs};" \
-   "name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
"name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=1024M,uuid=${uuid_gpt_system};" \
"name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
-   "name=cache,size=256M,uuid=${uuid_gpt_cache};" \
-   "name=ipu1,size=1M,uuid=${uuid_gpt_ipu1};" \
-   "name=ipu2,size=1M,uuid=${uuid_gpt_ipu2};" \
VBMETA_PART \
"name=userdata,size=-,uuid=${uuid_gpt_userdata}"
  #endif /* PARTS_DEFAULT */

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: ti: boot: Increase system partition size

2018-12-14 Thread Bajjuri, Praneeth 


On 12/14/2018 7:15 AM, Sam Protsenko wrote:

Hi Praneeth,

On Fri, Dec 14, 2018 at 1:37 AM Bajjuri, Praneeth  wrote:

Sam,

On 12/11/2018 10:26 AM, Bajjuri, Praneeth wrote:

On 12/11/2018 10:20 AM, Sam Protsenko wrote:

Android code base is growing, so since Android "Pie" the size of
system.img grew up to be about 740 MiB. Let's increase system.img to
1 GiB to accommodate for those changes and leave some margin for future
changes. We don't want to make it more than 1 GiB, because we should
keep userdata partition big enough (for user files, like media etc.),
and eMMC size on BeagleBoard-X15 is only 3.5 GiB.

Signed-off-by: Sam Protsenko 

Acked-by: Praneeth Bajjuri 

---
   include/environment/ti/boot.h | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/environment/ti/boot.h
b/include/environment/ti/boot.h
index 5891009a5a..86ff6d3ea7 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -41,7 +41,7 @@
   "name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
   "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
   "name=boot,size=10M,uuid=${uuid_gpt_boot};" \
-"name=system,size=768M,uuid=${uuid_gpt_system};" \
+"name=system,size=1024M,uuid=${uuid_gpt_system};" \

while at it,

Can you remove the legacy partitions which are not applicable anymore
for X15.

remove : reserved, efs,crypto,cache,ipu1,ipu2. This will give more
storage for userdata


Actually this file is also used for DRA7 and OMAP5 boards. Do you know
if we need ipu* partitions on DRA7?

Can be removed for DRA7.
IPU firmware is part of vendor image and doesnt reside as a separate 
partition




"reserved" is actually used to mark U-Boot environment, so I guess I
will rename it rather them remove.

As for the other partitions, like cache, I think you're right. We
shouldn't try and support old Androids in new U-Boot, we have older
release tags for this. But I'd prefer to send that change in a
separate patch, due to commit message and atomicity.


the current fix itself for increasing system image size  is fine.
Ok on cleaning up legacy partitions with a patch on top




Thanks.


we can still use misc for reboot reason storage for the purpose of
fastboot reboot to (bootloader or recovery)


"name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
   "name=cache,size=256M,uuid=${uuid_gpt_cache};" \
   "name=ipu1,size=1M,uuid=${uuid_gpt_ipu1};" \

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: ti: boot: Increase system partition size

2018-12-13 Thread Bajjuri, Praneeth 

Sam,

On 12/11/2018 10:26 AM, Bajjuri, Praneeth wrote:


On 12/11/2018 10:20 AM, Sam Protsenko wrote:

Android code base is growing, so since Android "Pie" the size of
system.img grew up to be about 740 MiB. Let's increase system.img to
1 GiB to accommodate for those changes and leave some margin for future
changes. We don't want to make it more than 1 GiB, because we should
keep userdata partition big enough (for user files, like media etc.),
and eMMC size on BeagleBoard-X15 is only 3.5 GiB.

Signed-off-by: Sam Protsenko 

Acked-by: Praneeth Bajjuri 

---
  include/environment/ti/boot.h | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/environment/ti/boot.h 
b/include/environment/ti/boot.h

index 5891009a5a..86ff6d3ea7 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -41,7 +41,7 @@
  "name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
  "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
  "name=boot,size=10M,uuid=${uuid_gpt_boot};" \
-    "name=system,size=768M,uuid=${uuid_gpt_system};" \
+    "name=system,size=1024M,uuid=${uuid_gpt_system};" \


while at it,

Can you remove the legacy partitions which are not applicable anymore 
for X15.


remove : reserved, efs,crypto,cache,ipu1,ipu2. This will give more 
storage for userdata


we can still use misc for reboot reason storage for the purpose of 
fastboot reboot to (bootloader or recovery)



"name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
  "name=cache,size=256M,uuid=${uuid_gpt_cache};" \
  "name=ipu1,size=1M,uuid=${uuid_gpt_ipu1};" \

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: ti: boot: Increase system partition size

2018-12-11 Thread Bajjuri, Praneeth 


On 12/11/2018 10:20 AM, Sam Protsenko wrote:

Android code base is growing, so since Android "Pie" the size of
system.img grew up to be about 740 MiB. Let's increase system.img to
1 GiB to accommodate for those changes and leave some margin for future
changes. We don't want to make it more than 1 GiB, because we should
keep userdata partition big enough (for user files, like media etc.),
and eMMC size on BeagleBoard-X15 is only 3.5 GiB.

Signed-off-by: Sam Protsenko 

Acked-by: Praneeth Bajjuri 

---
  include/environment/ti/boot.h | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h
index 5891009a5a..86ff6d3ea7 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -41,7 +41,7 @@
"name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
"name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
-   "name=system,size=768M,uuid=${uuid_gpt_system};" \
+   "name=system,size=1024M,uuid=${uuid_gpt_system};" \
"name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
"name=cache,size=256M,uuid=${uuid_gpt_cache};" \
"name=ipu1,size=1M,uuid=${uuid_gpt_ipu1};" \

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: ti: boot: Fix U-Boot environment partition address

2018-11-26 Thread Bajjuri, Praneeth 


On 11/26/2018 8:27 AM, Sam Protsenko wrote:

Hi Tom,

Can you please pull this in? It fixes the regression I introduced by
accident earlier...

Thanks!

On Thu, Nov 15, 2018 at 10:26 PM Sam Protsenko
 wrote:

Recent removal of obsolete partition led to shifting of starting address
of "reserved" partition (which reflects U-Boot environment). Fix its
start address to keep it in sync with ENV_OFFSET and DFU environment.

This patch also provides fixed start address for "reserved" partition,
so that we can track when it's shifted next time.

While at it, move it before "misc" partition to keep all Android
partitions together.

Signed-off-by: Sam Protsenko 

Acked-By: Praneeth Bajjuri 

---
  include/environment/ti/boot.h | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h
index 3c9c87f21b..5891009a5a 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -34,9 +34,9 @@
 "partitions_android=" \
 "uuid_disk=${uuid_gpt_disk};" \
 "name=xloader,start=128K,size=256K,uuid=${uuid_gpt_xloader};" \
-   "name=bootloader,size=1792K,uuid=${uuid_gpt_bootloader};" \
+   "name=bootloader,size=2048K,uuid=${uuid_gpt_bootloader};" \
+   "name=reserved,start=2432K,size=256K,uuid=${uuid_gpt_reserved};" \
 "name=misc,size=128K,uuid=${uuid_gpt_misc};" \
-   "name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
 "name=efs,size=16M,uuid=${uuid_gpt_efs};" \
 "name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
 "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
--
2.19.1


___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: ti: boot: Remove environment partition

2018-10-18 Thread Bajjuri, Praneeth 



On 10/18/2018 2:47 PM, Sam Protsenko wrote:

Remove "environment" partition and do not read it when booting Android
from eMMC. We don't use this partition anymore, so this is just an
unintentional leftover.

Earlier we were reading dtb file from "environment" partition to feed it
further to kernel. Now we are using dtb from FIT image ("boot" partition
contains boot_fit.img image), which can be seen from this command:

 bootm ${loadaddr}#${fdtfile}

where "#" character means we have FIT image in ${loadaddr} RAM address.

Signed-off-by: Sam Protsenko 


Acked-by: Praneeth Bajjuri 


---
  include/environment/ti/boot.h | 3 ---
  1 file changed, 3 deletions(-)

diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h
index 2893cd4287..560753ae4c 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -35,7 +35,6 @@
"uuid_disk=${uuid_gpt_disk};" \
"name=xloader,start=128K,size=256K,uuid=${uuid_gpt_xloader};" \
"name=bootloader,size=1792K,uuid=${uuid_gpt_bootloader};" \
-   "name=environment,size=128K,uuid=${uuid_gpt_environment};" \
"name=misc,size=128K,uuid=${uuid_gpt_misc};" \
"name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
"name=efs,size=16M,uuid=${uuid_gpt_efs};" \
@@ -92,8 +91,6 @@
"mmc dev $mmcdev; " \
"mmc rescan; " \
AVB_VERIFY_CHECK \
-   "part start mmc ${mmcdev} environment fdt_start; " \
-   "part size mmc ${mmcdev} environment fdt_size; " \
"part start mmc ${mmcdev} boot boot_start; " \
"part size mmc ${mmcdev} boot boot_size; " \
"mmc read ${fdtaddr} ${fdt_start} ${fdt_size}; " \


___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH] configs: am57xx: change default board name to beagle_x15

2018-08-21 Thread Praneeth Bajjuri 
beagleboard x15 is the first supported platform variant of am57xx
in AOSP (android open source project) now.

changing board name to stay in consistent with aosp target name.

Signed-off-by: Praneeth Bajjuri 
---
 configs/am57xx_evm_defconfig| 2 +-
 configs/am57xx_hs_evm_defconfig | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/configs/am57xx_evm_defconfig b/configs/am57xx_evm_defconfig
index 1572dc80db03..07ab01e921bf 100644
--- a/configs/am57xx_evm_defconfig
+++ b/configs/am57xx_evm_defconfig
@@ -14,7 +14,7 @@ CONFIG_NR_DRAM_BANKS=2
 CONFIG_SPL_LOAD_FIT=y
 CONFIG_OF_BOARD_SETUP=y
 CONFIG_USE_BOOTARGS=y
-CONFIG_BOOTARGS="androidboot.serialno=${serial#} console=ttyS2,115200 
androidboot.console=ttyS2 androidboot.hardware=am57xevmboard"
+CONFIG_BOOTARGS="androidboot.serialno=${serial#} console=ttyS2,115200 
androidboot.console=ttyS2 androidboot.hardware=beagle_x15board"
 # CONFIG_USE_BOOTCOMMAND is not set
 CONFIG_SYS_CONSOLE_INFO_QUIET=y
 # CONFIG_MISC_INIT_R is not set
diff --git a/configs/am57xx_hs_evm_defconfig b/configs/am57xx_hs_evm_defconfig
index 895719286dc5..0522c10b01c4 100644
--- a/configs/am57xx_hs_evm_defconfig
+++ b/configs/am57xx_hs_evm_defconfig
@@ -20,7 +20,7 @@ CONFIG_SPL_LOAD_FIT=y
 CONFIG_SPL_FIT_IMAGE_POST_PROCESS=y
 CONFIG_OF_BOARD_SETUP=y
 CONFIG_USE_BOOTARGS=y
-CONFIG_BOOTARGS="androidboot.serialno=${serial#} console=ttyS2,115200 
androidboot.console=ttyS2 androidboot.hardware=am57xevmboard"
+CONFIG_BOOTARGS="androidboot.serialno=${serial#} console=ttyS2,115200 
androidboot.console=ttyS2 androidboot.hardware=beagle_x15board"
 # CONFIG_USE_BOOTCOMMAND is not set
 CONFIG_SYS_CONSOLE_INFO_QUIET=y
 # CONFIG_MISC_INIT_R is not set
-- 
2.7.4

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH 1/3] arm: dra76: fastboot: extend cpu type for getvar command

2018-04-25 Thread Bajjuri, Praneeth 

Only one patch in the series.

Wrong subject [PATCH 1/3]


On 4/25/2018 3:56 PM, Praneeth Bajjuri wrote:

'commit dda0bd674481 ("arm: dra762: Add support for device package 
identification")'
introduces ABZ and ACD package identification.

This patch is to extend usage of "fastboot getvar cpu" for
DRA76x ABZ and ACD devices.

Helps in fixing the boot warning.

Warning: fastboot.cpu: unknown CPU rev: 123863298
on
CPU  : DRA762-GP ES1.0 ABZ package
Model: TI AM5748 IDK
Board: AM574x IDK REV 1.0A

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
  arch/arm/mach-omap2/utils.c | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/arch/arm/mach-omap2/utils.c b/arch/arm/mach-omap2/utils.c
index 1d39625..391055e 100644
--- a/arch/arm/mach-omap2/utils.c
+++ b/arch/arm/mach-omap2/utils.c
@@ -30,6 +30,8 @@ static void omap_set_fastboot_cpu(void)
  
  	switch (cpu_rev) {

case DRA762_ES1_0:
+   case DRA762_ABZ_ES1_0:
+   case DRA762_ACD_ES1_0:
cpu = "DRA762";
break;
case DRA752_ES1_0:


___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 0/2] Boot android with FIT image

2018-04-25 Thread Praneeth Bajjuri 
Enable the FDT library overlay support for all TI SOC family
and while at it
Enable android over emmc by default thru FIT image


Praneeth Bajjuri (2):
  configs: TI: Enable FIT Library overlay support
  env: ti: android: boot with FIT Image

 include/environment/ti/boot.h | 3 ++-
 lib/Kconfig   | 1 +
 2 files changed, 3 insertions(+), 1 deletion(-)

-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 1/2] configs: TI: Enable FIT Library overlay support

2018-04-25 Thread Praneeth Bajjuri 
Enable the FDT library overlay support for all TI SOC family.

Without this option, when Loading fdt from FIT image, the
following warning is seen.

"config with overlays but CONFIG_OF_LIBFDT_OVERLAY not set".

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
Suggested-by: Andrew F.Davis <a...@ti.com>
---
 lib/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/Kconfig b/lib/Kconfig
index 436b90f..6d5306a 100644
--- a/lib/Kconfig
+++ b/lib/Kconfig
@@ -252,6 +252,7 @@ config OF_LIBFDT
 
 config OF_LIBFDT_OVERLAY
bool "Enable the FDT library overlay support"
+   default y if ARCH_OMAP2PLUS || ARCH_KEYSTONE
help
  This enables the FDT library (libfdt) overlay support.
 
-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 2/2] env: ti: android: boot with FIT Image

2018-04-25 Thread Praneeth Bajjuri 
Boot android over emmc by default thru FIT image

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
Suggested-by: Andrew F.Davis <a...@ti.com>
---
 include/environment/ti/boot.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h
index 24b7783..a1767b4 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -37,6 +37,7 @@
"run mmcboot;\0" \
"emmc_android_boot=" \
"echo Trying to boot Android from eMMC ...; " \
+   "run update_to_fit; " \
"setenv eval_bootargs setenv bootargs $bootargs; " \
"run eval_bootargs; " \
"setenv mmcdev 1; " \
@@ -49,7 +50,7 @@
"part size mmc ${mmcdev} boot boot_size; " \
"mmc read ${fdtaddr} ${fdt_start} ${fdt_size}; " \
"mmc read ${loadaddr} ${boot_start} ${boot_size}; " \
-   "bootm $loadaddr $loadaddr $fdtaddr;\0"
+   "bootm ${loadaddr}#${fdtfile};\0 "
 
 #ifdef CONFIG_OMAP54XX
 
-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 1/3] arm: dra76: fastboot: extend cpu type for getvar command

2018-04-25 Thread Praneeth Bajjuri 
'commit dda0bd674481 ("arm: dra762: Add support for device package 
identification")'
introduces ABZ and ACD package identification.

This patch is to extend usage of "fastboot getvar cpu" for
DRA76x ABZ and ACD devices.

Helps in fixing the boot warning.

Warning: fastboot.cpu: unknown CPU rev: 123863298
on
CPU  : DRA762-GP ES1.0 ABZ package
Model: TI AM5748 IDK
Board: AM574x IDK REV 1.0A

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
 arch/arm/mach-omap2/utils.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/mach-omap2/utils.c b/arch/arm/mach-omap2/utils.c
index 1d39625..391055e 100644
--- a/arch/arm/mach-omap2/utils.c
+++ b/arch/arm/mach-omap2/utils.c
@@ -30,6 +30,8 @@ static void omap_set_fastboot_cpu(void)
 
switch (cpu_rev) {
case DRA762_ES1_0:
+   case DRA762_ABZ_ES1_0:
+   case DRA762_ACD_ES1_0:
cpu = "DRA762";
break;
case DRA752_ES1_0:
-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] dra7x: fastboot: Increase recovery partition size

2017-11-20 Thread Bajjuri, Praneeth 

Hi Tom,

if there is nothing waiting to be addressed, Can you pull this patch.

-- Praneeth

On 11/10/2017 1:22 PM, Sam Protsenko wrote:

On 9 November 2017 at 01:12, Praneeth Bajjuri <prane...@ti.com> wrote:

As per current android recommendation
https://source.android.com/devices/architecture/kernel/modular-kernels

1. Android recovery mode should contain both SOC and ODM
kernel modules in the recovery partition.

2. If a kernel module is required both in recovery and normal boot
mode,  the module has to be located in recovery and vendor
partition seperately.

3. Kernel modules used in recovery mode should be independent
of vendor and odm partition

4. Recovery image should contain atleast
storage, display, keypad, battery and pmic modules.

Due to these requirements, recovery image size has increased
to >10MB.

This patch is to increase recovery partition size for TI devices
so that we dont see such flashing error

log:
sending 'recovery' (12560 KB)...
OKAY [  0.436s]
writing 'recovery'...
FAILED (remote: too large for partition)
finished. total time: 0.458s

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
  include/configs/am57xx_evm.h | 2 +-
  include/configs/dra7xx_evm.h | 2 +-
  2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/configs/am57xx_evm.h b/include/configs/am57xx_evm.h
index ebb0474..dc05bea 100644
--- a/include/configs/am57xx_evm.h
+++ b/include/configs/am57xx_evm.h
@@ -56,7 +56,7 @@
 "name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
 "name=efs,size=16M,uuid=${uuid_gpt_efs};" \
 "name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
-   "name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
+   "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
 "name=boot,size=10M,uuid=${uuid_gpt_boot};" \
 "name=system,size=768M,uuid=${uuid_gpt_system};" \
 "name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
diff --git a/include/configs/dra7xx_evm.h b/include/configs/dra7xx_evm.h
index 34a4555..f84c1f0 100644
--- a/include/configs/dra7xx_evm.h
+++ b/include/configs/dra7xx_evm.h
@@ -63,7 +63,7 @@
 "name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
 "name=efs,size=16M,uuid=${uuid_gpt_efs};" \
 "name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
-   "name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
+   "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
 "name=boot,size=10M,uuid=${uuid_gpt_boot};" \
 "name=system,size=768M,uuid=${uuid_gpt_system};" \
 "name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
--
1.9.1


Reviewed-by: Sam Protsenko <semen.protse...@linaro.org>


___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] dra7x: fastboot: Increase recovery partition size

2017-11-20 Thread Bajjuri, Praneeth 

Tom,

Can you pull this , if there is nothing waiting to be addressed on this one.

--praneeth
On 11/10/2017 1:22 PM, Sam Protsenko wrote:

On 9 November 2017 at 01:12, Praneeth Bajjuri <prane...@ti.com> wrote:

As per current android recommendation
https://source.android.com/devices/architecture/kernel/modular-kernels

1. Android recovery mode should contain both SOC and ODM
kernel modules in the recovery partition.

2. If a kernel module is required both in recovery and normal boot
mode,  the module has to be located in recovery and vendor
partition seperately.

3. Kernel modules used in recovery mode should be independent
of vendor and odm partition

4. Recovery image should contain atleast
storage, display, keypad, battery and pmic modules.

Due to these requirements, recovery image size has increased
to >10MB.

This patch is to increase recovery partition size for TI devices
so that we dont see such flashing error

log:
sending 'recovery' (12560 KB)...
OKAY [  0.436s]
writing 'recovery'...
FAILED (remote: too large for partition)
finished. total time: 0.458s

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
  include/configs/am57xx_evm.h | 2 +-
  include/configs/dra7xx_evm.h | 2 +-
  2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/configs/am57xx_evm.h b/include/configs/am57xx_evm.h
index ebb0474..dc05bea 100644
--- a/include/configs/am57xx_evm.h
+++ b/include/configs/am57xx_evm.h
@@ -56,7 +56,7 @@
 "name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
 "name=efs,size=16M,uuid=${uuid_gpt_efs};" \
 "name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
-   "name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
+   "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
 "name=boot,size=10M,uuid=${uuid_gpt_boot};" \
 "name=system,size=768M,uuid=${uuid_gpt_system};" \
 "name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
diff --git a/include/configs/dra7xx_evm.h b/include/configs/dra7xx_evm.h
index 34a4555..f84c1f0 100644
--- a/include/configs/dra7xx_evm.h
+++ b/include/configs/dra7xx_evm.h
@@ -63,7 +63,7 @@
 "name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
 "name=efs,size=16M,uuid=${uuid_gpt_efs};" \
 "name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
-   "name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
+   "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
 "name=boot,size=10M,uuid=${uuid_gpt_boot};" \
 "name=system,size=768M,uuid=${uuid_gpt_system};" \
 "name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
--
1.9.1


Reviewed-by: Sam Protsenko <semen.protse...@linaro.org>


___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH] dra7x: fastboot: Increase recovery partition size

2017-11-08 Thread Praneeth Bajjuri 
As per current android recommendation
https://source.android.com/devices/architecture/kernel/modular-kernels

1. Android recovery mode should contain both SOC and ODM
kernel modules in the recovery partition.

2. If a kernel module is required both in recovery and normal boot
mode,  the module has to be located in recovery and vendor
partition seperately.

3. Kernel modules used in recovery mode should be independent
of vendor and odm partition

4. Recovery image should contain atleast
storage, display, keypad, battery and pmic modules.

Due to these requirements, recovery image size has increased
to >10MB.

This patch is to increase recovery partition size for TI devices
so that we dont see such flashing error

log:
sending 'recovery' (12560 KB)...
OKAY [  0.436s]
writing 'recovery'...
FAILED (remote: too large for partition)
finished. total time: 0.458s

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
 include/configs/am57xx_evm.h | 2 +-
 include/configs/dra7xx_evm.h | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/configs/am57xx_evm.h b/include/configs/am57xx_evm.h
index ebb0474..dc05bea 100644
--- a/include/configs/am57xx_evm.h
+++ b/include/configs/am57xx_evm.h
@@ -56,7 +56,7 @@
"name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
"name=efs,size=16M,uuid=${uuid_gpt_efs};" \
"name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
-   "name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
+   "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=768M,uuid=${uuid_gpt_system};" \
"name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
diff --git a/include/configs/dra7xx_evm.h b/include/configs/dra7xx_evm.h
index 34a4555..f84c1f0 100644
--- a/include/configs/dra7xx_evm.h
+++ b/include/configs/dra7xx_evm.h
@@ -63,7 +63,7 @@
"name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
"name=efs,size=16M,uuid=${uuid_gpt_efs};" \
"name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
-   "name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
+   "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=768M,uuid=${uuid_gpt_system};" \
"name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 2/4] arm: dra7xx: Add vendor partition to Android GPT table for eMMC

2017-10-12 Thread Praneeth Bajjuri 
From: Vishal Mahaveer <vish...@ti.com>

Add vendor partition to Android GPT table for eMMC.

A Vendor image contains SoC-specific code and configuration.

Prior to Android 8.0, the vendor partition was optional ;
files belonging to these images were placed in boot.img or system.img
with symlinks (such as /vendor >/system/vendor ) when absent.

Android 8.0 makes the vendor partition mandatory

The goal is to modularize Android partitions with standard interface between
the Android Platform (on system.img ) and vendor-provided code(on vendor.img).

This standard interface enables the Android Platform to be updated
without affecting the SoC partitions. This makes it possible to upgrade a
device system.img from Android 8.0 to Android P while other images (such as
vendor.img) remain at Android 8.0. This modularity enables timely
Android platform upgrades (such as monthly security updates )
without requiring SoC/ODM partners to update SoC- and device-specific code.

Signed-off-by: Vishal Mahaveer <vish...@ti.com>
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
 include/configs/dra7xx_evm.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/configs/dra7xx_evm.h b/include/configs/dra7xx_evm.h
index 717861f..e5e 100644
--- a/include/configs/dra7xx_evm.h
+++ b/include/configs/dra7xx_evm.h
@@ -66,6 +66,7 @@
"name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=768M,uuid=${uuid_gpt_system};" \
+   "name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
"name=cache,size=256M,uuid=${uuid_gpt_cache};" \
"name=ipu1,size=1M,uuid=${uuid_gpt_ipu1};" \
"name=ipu2,size=1M,uuid=${uuid_gpt_ipu2};" \
-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 3/4] omap-common: fastboot: extend cpu type for DRA71x rev 2.1

2017-10-12 Thread Praneeth Bajjuri 
From: Vishal Mahaveer <vish...@ti.com>

DRA71x processors are reduced pin and software compatible
derivative of DRA72 processors. Extend support for this
revision in "getvar cpu" command.

Signed-off-by: Vishal Mahaveer <vish...@ti.com>
[prane...@ti.com: rebase to u-boot master]
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
 arch/arm/mach-omap2/utils.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm/mach-omap2/utils.c b/arch/arm/mach-omap2/utils.c
index d4f171b..2bd8290 100644
--- a/arch/arm/mach-omap2/utils.c
+++ b/arch/arm/mach-omap2/utils.c
@@ -33,6 +33,7 @@ static void omap_set_fastboot_cpu(void)
break;
case DRA722_ES1_0:
case DRA722_ES2_0:
+   case DRA722_ES2_1:
cpu = "DRA722";
break;
default:
-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 4/4] arm: dra76: fastboot: extend cpu type for getvar command

2017-10-12 Thread Praneeth Bajjuri 
'commit fa24eca1f20a ("omap: Add routine for setting fastboot variables")'
adds initial support and usage of "fastboot getvar" command
for DRA75x and DRA72x devices.

and
'commit 0f9e6aee9dbc ("arm: dra76: Add support for ES1.0 detection")'
adds initial dra76 device definition

This patch is to extend usage of "fastboot getvar" for DRA76 device.

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
 arch/arm/mach-omap2/utils.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/arch/arm/mach-omap2/utils.c b/arch/arm/mach-omap2/utils.c
index 2bd8290..2e87780 100644
--- a/arch/arm/mach-omap2/utils.c
+++ b/arch/arm/mach-omap2/utils.c
@@ -26,6 +26,9 @@ static void omap_set_fastboot_cpu(void)
u32 cpu_rev = omap_revision();
 
switch (cpu_rev) {
+   case DRA762_ES1_0:
+   cpu = "DRA762";
+   break;
case DRA752_ES1_0:
case DRA752_ES1_1:
case DRA752_ES2_0:
-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 1/4] arm: am57xx: Add vendor partition to Android GPT table for eMMC

2017-10-12 Thread Praneeth Bajjuri 
Add vendor partition to Android GPT table for eMMC.

A Vendor image contains SoC-specific code and configuration.

Prior to Android 8.0, the vendor partition was optional ;
files belonging to these images were placed in boot.img or system.img
with symlinks (such as /vendor >/system/vendor ) when absent.

Android 8.0 makes the vendor partition mandatory

The goal is to modularize Android partitions with standard interface between
the Android Platform (on system.img ) and vendor-provided code(on vendor.img).

This standard interface enables the Android Platform to be updated
without affecting the SoC partitions. This makes it possible to upgrade a
device system.img from Android 8.0 to Android P while other images (such as
vendor.img) remain at Android 8.0. This modularity enables timely
Android platform upgrades (such as monthly security updates )
without requiring SoC/ODM partners to update SoC- and device-specific code.

Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
 include/configs/am57xx_evm.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/configs/am57xx_evm.h b/include/configs/am57xx_evm.h
index 5427974..ebb0474 100644
--- a/include/configs/am57xx_evm.h
+++ b/include/configs/am57xx_evm.h
@@ -59,6 +59,7 @@
"name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=768M,uuid=${uuid_gpt_system};" \
+   "name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
"name=cache,size=256M,uuid=${uuid_gpt_cache};" \
"name=ipu1,size=1M,uuid=${uuid_gpt_ipu1};" \
"name=ipu2,size=1M,uuid=${uuid_gpt_ipu2};" \
-- 
1.9.1

___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: am57xx: Update bootloader partition size

2017-02-21 Thread Bajjuri, Praneeth 



On 2/21/2017 3:48 PM, Felipe Balbi wrote:

Hi,

Sam Protsenko <semen.protse...@linaro.org> writes:

On Tue, Feb 21, 2017 at 10:35 PM, Felipe Balbi
<felipe.ba...@linux.intel.com> wrote:

Hi,

Sam Protsenko <semen.protse...@linaro.org> writes:

From: Praneeth Bajjuri <prane...@ti.com>

The current size of u-boot is already ~840 KiB.

This patch is to increase bootloader partition size up to 1 MiB
and thereby fix flashing error like below:

 sending 'bootloader' (840 KB)...
 OKAY [  0.048s]
 writing 'bootloader'...
 FAILED (remote: too large for partition)

Signed-off-by: Sam Protsenko <semen.protse...@linaro.org>

Missing Praneeth's Signed-off-by?


Yes. But not sure If I should resend.

Tom, will you please add Praneeth's Signed-off-by line when applying patch?

Only if Praneeth agrees, right ? ;-)

agreed and ok with me
thanks felipe , sam




___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: am57xx: Update bootloader partition size

2017-02-21 Thread Bajjuri, Praneeth 



On 2/21/2017 1:51 PM, Sam Protsenko wrote:

From: Praneeth Bajjuri <prane...@ti.com>

The current size of u-boot is already ~840 KiB.

This patch is to increase bootloader partition size up to 1 MiB
and thereby fix flashing error like below:

 sending 'bootloader' (840 KB)...
 OKAY [  0.048s]
 writing 'bootloader'...
 FAILED (remote: too large for partition)

Signed-off-by: Sam Protsenko <semen.protse...@linaro.org>

Verified
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>

---
  include/configs/am57xx_evm.h | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/configs/am57xx_evm.h b/include/configs/am57xx_evm.h
index 3d8b996054..aa63b24ca4 100644
--- a/include/configs/am57xx_evm.h
+++ b/include/configs/am57xx_evm.h
@@ -45,7 +45,7 @@
"partitions_android=" \
"uuid_disk=${uuid_gpt_disk};" \
"name=xloader,start=128K,size=256K,uuid=${uuid_gpt_xloader};" \
-   "name=bootloader,size=768K,uuid=${uuid_gpt_bootloader};" \
+   "name=bootloader,size=1M,uuid=${uuid_gpt_bootloader};" \
"name=environment,size=128K,uuid=${uuid_gpt_environment};" \
"name=misc,size=128K,uuid=${uuid_gpt_misc};" \
"name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \


___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH] arm: dra7xx: Update bootloader partition size

2017-02-21 Thread Bajjuri, Praneeth 



On 2/21/2017 1:51 PM, Sam Protsenko wrote:

The current size of U-Boot is already ~840 KiB.

This patch is to increase bootloader partition size up to 1 MiB
and thereby fix flashing error.

Also fix U-Boot environment address on eMMC ("reserved" partition), as
it's being shifted by above change.

Signed-off-by: Sam Protsenko <semen.protse...@linaro.org>

Verified
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>

---
  include/configs/dra7xx_evm.h | 7 ---
  1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/include/configs/dra7xx_evm.h b/include/configs/dra7xx_evm.h
index 549439e8b4..1e67c386a0 100644
--- a/include/configs/dra7xx_evm.h
+++ b/include/configs/dra7xx_evm.h
@@ -13,6 +13,7 @@
  #define __CONFIG_DRA7XX_EVM_H
  
  #include 

+#include 
  
  #define CONFIG_DRA7XX
  
@@ -28,8 +29,8 @@

  /* MMC ENV related defines */
  #define CONFIG_ENV_IS_IN_MMC
  #define CONFIG_SYS_MMC_ENV_DEV1   /* SLOT2: eMMC(1) */
-#define CONFIG_ENV_SIZE(128 << 10)
-#define CONFIG_ENV_OFFSET  0xE
+#define CONFIG_ENV_SIZESZ_128K
+#define CONFIG_ENV_OFFSET  0x1A/* "reserved" part. */
  #define CONFIG_ENV_OFFSET_REDUND  (CONFIG_ENV_OFFSET + CONFIG_ENV_SIZE)
  #define CONFIG_SYS_REDUNDAND_ENVIRONMENT
  #endif
@@ -56,7 +57,7 @@
"partitions_android=" \
"uuid_disk=${uuid_gpt_disk};" \
"name=xloader,start=128K,size=256K,uuid=${uuid_gpt_xloader};" \
-   "name=bootloader,size=768K,uuid=${uuid_gpt_bootloader};" \
+   "name=bootloader,size=1M,uuid=${uuid_gpt_bootloader};" \
"name=environment,size=128K,uuid=${uuid_gpt_environment};" \
"name=misc,size=128K,uuid=${uuid_gpt_misc};" \
"name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \


___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot