Re: [PATCH 01/45] configs: am335x_baltos_defconfig: Increase aneg timeout to 20000 ms

2025-07-29 Thread Kumar, Udit
Hello Siddharth, On 7/29/2025 10:45 AM, Siddharth Vadapalli wrote: On Mon, Jul 28, 2025 at 09:03:49PM +0530, Kumar, Udit wrote: Hello Udit, On 7/28/2025 8:19 PM, Siddharth Vadapalli wrote: Increase the PHY Auto-Negotiation timeout to 20,000 ms from the current default of 4,000 ms inherited

Re: [PATCH 01/45] configs: am335x_baltos_defconfig: Increase aneg timeout to 20000 ms

2025-07-28 Thread Kumar, Udit
On 7/28/2025 8:19 PM, Siddharth Vadapalli wrote: Increase the PHY Auto-Negotiation timeout to 20,000 ms from the current default of 4,000 ms inherited from "Kconfig" for PHY_ANEG_TIMEOUT. The motivation for this change is that existing devices will continue working as-is (timeout is an upper b

Re: [PATCH v2] board: ti: Clean up formatting in rm-cfg.yaml

2025-07-04 Thread Kumar, Udit
On 7/4/2025 2:42 PM, Neha Malcom Francis wrote: Move to using the latest generated RM YAML configuration files generated by the K3 Resource Partitioning Tool which updates them to have standard formatting with respect to indentation. These files were generated from the untagged commit 41718bd5

Re: [PATCH] board: ti: Clean up formatting in rm-cfg.yaml

2025-07-02 Thread Kumar, Udit
Hello Neha, Thanks for updating these yaml On 7/2/2025 4:25 PM, Neha Malcom Francis wrote: Latest update to the K3 Resource Partitioning Tool updates the YAML configuration files to have standard formatting with respect to indentation. Update the files that require this cleanup. Patch LGTM .

Re: [PATCH v3 1/2] mach-k3: add runtime memory carveouts for MMU table

2025-06-18 Thread Kumar, Udit
On 6/18/2025 5:22 PM, Anshul Dalal wrote: On Wed Jun 18, 2025 at 3:56 PM IST, Udit Kumar wrote: On 6/17/2025 7:28 PM, Anshul Dalal wrote: In u-boot we only provide a single MMU table for all k3 platforms, this does not scale for devices with reserved memory outside the range 0x9e78 - 0xa0

Re: [PATCH v3 1/2] mach-k3: add runtime memory carveouts for MMU table

2025-06-18 Thread Kumar, Udit
On 6/17/2025 7:28 PM, Anshul Dalal wrote: In u-boot we only provide a single MMU table for all k3 platforms, this does not scale for devices with reserved memory outside the range 0x9e78 - 0xa000 (eg j722s[1]) or for devices with < 2GiB of memory (eg am62-SIP with 512MiB of RAM). plea

Re: [PATCH v2 0/7] Add support to boot TI K3 HSM M4 core

2025-05-06 Thread Kumar, Udit
On 5/6/2025 11:42 PM, Andrew Davis wrote: On 5/6/25 12:19 PM, Tom Rini wrote: On Tue, May 06, 2025 at 10:47:57PM +0530, Kumar, Udit wrote: On 5/6/2025 8:38 PM, Andrew Davis wrote: On 5/6/25 9:51 AM, Beleswar Prasad Padhi wrote: Hi Andrew, On 5/6/2025 4:38 PM, Andrew Davis wrote: On 5/6

Re: [PATCH v2 0/7] Add support to boot TI K3 HSM M4 core

2025-05-06 Thread Kumar, Udit
On 5/6/2025 8:38 PM, Andrew Davis wrote: On 5/6/25 9:51 AM, Beleswar Prasad Padhi wrote: Hi Andrew, On 5/6/2025 4:38 PM, Andrew Davis wrote: On 5/6/25 5:41 AM, Beleswar Padhi wrote: Some TI K3 SoCs like J721S2, and J784S4 have a HSM (High Security Module) M4F core in the Wakeup Voltage Doma

Re: [PATCH 1/2] include: env: ti: mmc.h: Find DTB files in dtb directory for AM57xx

2025-04-25 Thread Kumar, Udit
On 4/25/2025 12:19 PM, Neha Malcom Francis wrote: Hi Anurag On 25/04/25 11:04, Anurag Dutta wrote: Add dtb/ to the DTB search path. Signed-off-by: Anurag Dutta --- include/env/ti/mmc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/env/ti/mmc.h b/include/env/

Re: [PATCH 5/9] beagle: beagley-ai: env: Enable DFU env options

2025-04-25 Thread Kumar, Udit
On 4/25/2025 11:01 PM, Nishanth Menon wrote: Just enable dfu options, We have MMC and RAM as options here. Signed-off-by: Nishanth Menon --- Changes Since v2: - Dropped the dfu_alt_info override option, let the users select it - Updated commit message to the effect. V2: https://lore.kernel.o

Re: [PATCH 3/9] beagle: beagley-ai: env: Set up the boot devices and boot methods

2025-04-25 Thread Kumar, Udit
On 4/25/2025 11:01 PM, Nishanth Menon wrote: We just have a single MMC on BeagleY-AI. So drop all other boot options, In the meanwhile, we also will use efiboot and standard boot methods consistent with other K3 Beagle products. Signed-off-by: Nishanth Menon --- Changes Since v2: - None V2:

Re: [PATCH 1/9] board: beagle: beagley-ai: Add pattern match for MAINTAINERS

2025-04-25 Thread Kumar, Udit
On 4/25/2025 11:01 PM, Nishanth Menon wrote: just use beagley_ai as pattern match for the files and folders involved. subject, line v3 :) anyway Reviewed-by: Udit Kumar Signed-off-by: Nishanth Menon --- Changes Since v2: - None V2: https://lore.kernel.org/r/20250418193943.953952-2...@t

Re: [RFC] Expected behavior of the go command

2025-04-25 Thread Kumar, Udit
Hi Ahmad On 4/25/2025 4:28 PM, Ahmad Fatoum wrote: Hi Udit, On 4/25/25 12:35, Kumar, Udit wrote: On 4/25/2025 11:09 AM, Ahmad Fatoum wrote: Thinking about it, I am wondering whether U-Boot go is inherently broken, even for the jump-table use case, if caches are enabled: Correct, this is

Re: [RFC] Expected behavior of the go command

2025-04-25 Thread Kumar, Udit
Thanks Ahmad On 4/25/2025 11:09 AM, Ahmad Fatoum wrote: Hi Udit, On 25.04.25 06:35, Kumar, Udit wrote: On 4/23/2025 7:52 PM, Ahmad Fatoum wrote: I went with the FIT route for barebox, because we can now ship device trees for all enabled boards in the same FIT image alongside one generic

Re: [RFC] Expected behavior of the go command

2025-04-24 Thread Kumar, Udit
On 4/23/2025 7:52 PM, Ahmad Fatoum wrote: Hi, On 4/23/25 14:28, Simon Glass wrote: Hi Anshul, On Wed, 23 Apr 2025 at 04:04, Anshul Dalal wrote: Hi all, I was trying to understand how the go command is expected to work when used to load custom OSes. My use case requires getting a proprieta

Re: [PATCH 4/4] arm: mach-k3: r5: common: Add support to boot HSM M4 core

2025-04-24 Thread Kumar, Udit
On 4/24/2025 3:17 PM, Beleswar Prasad Padhi wrote: Hi Udit, On 22/04/25 20:14, Kumar, Udit wrote: Hello Beleswar On 4/22/2025 3:24 PM, Beleswar Padhi wrote: The tispl.bin fit image is packed with the HSM firmware image. Populate the "os" info of the image so that it can be de

Re: [PATCH 2/2] arm: dts: k3-j721e-r5-common-proc-board: Enable HBMC in R5 SPL stage

2025-04-23 Thread Kumar, Udit
On 4/16/2025 11:46 AM, Anurag Dutta wrote: Enable HBMC in the R5 SPL stage Please add Fixes c9df79ee64d0: ("arm: dts: k3-j721e-r5-common: Add HBMC overrides for R5 SPL") Signed-off-by: Anurag Dutta --- arch/arm/dts/k3-j721e-r5-common-proc-board.dts | 1 + 1 file changed, 1 insertion(

Re: [PATCH 1/2] mtd: Kconfig: Add SPL_MUX_MMIO dependency to HBMC driver

2025-04-23 Thread Kumar, Udit
On 4/16/2025 11:46 AM, Anurag Dutta wrote: The MUX_MMIO is enabled both in SPL as well as U-Boot proper. Hence, add SPL_MUX_MMIO dependency from HBMC driver. May be you can reword commit message MUX_MMIO is needed by HBMC , So enable it at SPL and u-boot proper stage. Signed-off-by: Anura

Re: [PATCH 4/4] arm: mach-k3: r5: common: Add support to boot HSM M4 core

2025-04-22 Thread Kumar, Udit
Hello Beleswar On 4/22/2025 3:24 PM, Beleswar Padhi wrote: The tispl.bin fit image is packed with the HSM firmware image. Populate the "os" info of the image so that it can be detected and loaded at corresponding DDR address. Further, invoke the load and boot of HSM core at R5 SPL stage. Boot fl

Re: [PATCH 1/4] arm: mach-k3: Add config option for booting HSM core

2025-04-22 Thread Kumar, Udit
On 4/22/2025 3:24 PM, Beleswar Padhi wrote: Some K3 SoCs like J721S2, and J784S4 have a HSM (High Security Module) M4F core in the Wakeup Voltage Domain which could be used to run secure services like Authentication. Add a config option which indicates that the SoC has a HSM core and the firmwa

Re: [PATCH v3 0/4] omap24xx_i2c: Enable Repeated Start functionality

2025-04-22 Thread Kumar, Udit
Thanks for patch Aniket On 4/22/2025 3:49 PM, Aniket Limaye wrote: This series implements Repeated Start functionality for the DM_I2C xfer API (omap_i2c_xfer()) First, split out the actual implementation for each individual i2c msg transfer into a new function __omap24_i2c_xfer_msg() and use th

Re: [PATCH V2 9/9] doc: beagle: Add BeagleY-AI documentation

2025-04-19 Thread Kumar, Udit
On 4/19/2025 1:09 AM, Nishanth Menon wrote: Document the BeagleY-AI usage, build and basic debug hints Signed-off-by: Nishanth Menon --- Changes Since v1: - Included the manual partitioning option suggested by Andrew V1: https://lore.kernel.org/r/20250411225717.3117370-10...@ti.com doc/bo

Re: [PATCH V2 5/9] beagle: beagley-ai: env: Enable DFU env options

2025-04-19 Thread Kumar, Udit
Hello Nishanth On 4/19/2025 1:09 AM, Nishanth Menon wrote: We just have sd/mmc, so set things up for the same Signed-off-by: Nishanth Menon --- Changes Since v1: - None V1: https://lore.kernel.org/r/20250411225717.3117370-6...@ti.com board/beagle/beagley-ai/beagley-ai.env | 2 ++ 1 file c

Re: [PATCH V2 3/9] beagle: beagley-ai: env: Set up the boot devices and boot methods

2025-04-19 Thread Kumar, Udit
On 4/19/2025 1:09 AM, Nishanth Menon wrote: We just have a single MMC on BeagleY-AI. So drop all other boot options, In the meanwhile, we also will use efiboot and standard boot methods consistent with other K3 Beagle products. Signed-off-by: Nishanth Menon --- Changes Since v1: - None V1:

Re: [RFC PATCH 1/2 v2] tools: binman: control.py: Propagate bootph-* properties to supernodes

2025-04-16 Thread Kumar, Udit
Hello Moteen On 4/16/2025 1:23 PM, Moteen Shah wrote: Hey Simon, I missed some essential build instructions I should have given to you, apologies. I assume our u-boot public document should capture this information, It not, then please fix 1. Clone ti-linux-firmware: https://git.ti.com

Re: [PATCH V2] firmware: ti_sci: Scan all device instances when releasing exclusive devices

2025-04-11 Thread Kumar, Udit
On 4/11/2025 4:53 PM, Nishanth Menon wrote: On 11:04-20250411, Kumar, Udit wrote: Hi Nishanth, Sorry for basic question On 4/7/2025 5:45 PM, Nishanth Menon wrote: [..] This creates a problem when Device Manager(DM) firmware starts up later on in the boot process and identifies that this

Re: [PATCH V2] firmware: ti_sci: Scan all device instances when releasing exclusive devices

2025-04-10 Thread Kumar, Udit
Hi Nishanth, Sorry for basic question On 4/7/2025 5:45 PM, Nishanth Menon wrote: [..] This creates a problem when Device Manager(DM) firmware starts up later on in the boot process and identifies that this instance of i2c is Do we need to do clean up, where DM is loaded as different binary .

Re: [PATCH v2] mach-k3: common_fdt: Move carveout struct

2025-04-10 Thread Kumar, Udit
On 4/10/2025 1:25 PM, Daniel Schultz wrote: Labels are not allowed before declarations. Move the carveout struct at the beginning and only update 'end' at this point. This will fix following error: arch/arm/mach-k3/common_fdt.c: In function 'fdt_fixup_reserved': arch/arm/mach-k3/common_fdt.c:

Re: [PATCH] mach-k3: common_fdt: Fix Label Issue

2025-04-07 Thread Kumar, Udit
Hi Daniel. Thanks for patch On 4/7/2025 11:37 AM, Daniel Schultz wrote: Labels are not allowed before declarations. Add a semicolon after the label to introduce an empty statement. This will fix following error: arch/arm/mach-k3/common_fdt.c: In function 'fdt_fixup_reserved': arch/arm/mach-k3/

Re: [PATCH] configs: am68_sk_r5: Enable AVS config

2025-03-16 Thread Kumar, Udit
On 3/17/2025 9:25 AM, Neha Malcom Francis wrote: Hi Udit On 14/03/25 18:08, Udit Kumar wrote: Enable AVS config Signed-off-by: Udit Kumar --- Test logs https://gist.github.com/uditkumarti/9b30461e66aa27e4a813a65f1c552e51#file-gistfile1-txt-L298 Following print was added to see AVS voltage

Re: [PATCH v2] board: ti: j784s4: Update Resource Management configs

2025-02-28 Thread Kumar, Udit
On 2/28/2025 11:12 AM, Neha Malcom Francis wrote: From: Vaishnav Achath Update rm-cfg.yaml and tifs-rm-cfg.yaml to account for the changes added in the K3 Resource Partitioning Tool v1.18 The change enables resource sharing between A72_2 and MAIN_0_R5_0 for the BCDMA CSI RX and TX channels,

Re: [PATCH] board: ti: j784s4: Update Resource Management configs

2025-02-27 Thread Kumar, Udit
On 2/27/2025 12:19 PM, Neha Malcom Francis wrote: From: Vaishnav Achath Update rm-cfg.yaml and tifs-rm-cfg.yaml to account for the latest changes added in the K3 Resource Partitioning Tool. Please give the version of this tool instead of latest :) The change enables resource sharing bet

Re: [PATCH 1/2] arm: mach-k3: j722s: Initialize MCU & MAIN Domain ESMs

2025-02-24 Thread Kumar, Udit
On 2/17/2025 4:27 PM, Keerthy wrote: Initialize MCU & MAIN Domain ESMs as a prerequisite to enable watchdog reset functionality. The ESM aka error signalling module is primarily responsible for sensing the watchdog reset event. Signed-off-by: Keerthy --- arch/arm/mach-k3/j722s/j722s_init.c

Re: [UBOOT PATCH] spi: spi-uclass: Fix reduced read speed when parallel config is enabled

2025-02-21 Thread Kumar, Udit
Hello Venkatesh On 2/21/2025 3:27 PM, Venkatesh Yadav Abbarapu wrote: From: Prasad Kummari When SPI_STACKED_PARALLEL is enabled, the chip selects properties are read from the device tree using the reg property and stored in the plat->cs[] array. However, the function dev_read_u32_array() retur

Re: [RFC PATCH] power: regulator: Avoid probing of regulators at pre-ram stage

2025-02-21 Thread Kumar, Udit
Thanks Jonas On 2/21/2025 7:49 PM, Jonas Karlman wrote: Hi Udit and Quentin, On 2025-02-21 14:54, Quentin Schulz wrote: Hi Udit, On 2/21/25 1:45 PM, Udit Kumar wrote: commit 51c4679d2f84 ("power: regulator: Trigger probe of regulators which are always-on or boot-on") allow always on and boo

Re: [PATCH 0/2] Remove "saveenv" functionality from am57xx evms

2025-02-18 Thread Kumar, Udit
On 2/10/2025 8:13 PM, Tom Rini wrote: On Mon, Feb 10, 2025 at 09:55:22AM +0530, Kumar, Udit wrote: Hi Tom On 2/9/2025 10:50 PM, Tom Rini wrote: On Sat, Feb 08, 2025 at 10:09:36AM +0530, Anurag Dutta wrote: Previously saved environment introduce discrepancies and may lead to

Re: [RFC PATCH 2/2 v1] drivers: core: lists.c: Bind drivers using bootph* property in subnodes

2025-02-12 Thread Kumar, Udit
Hello Moteen On 2/12/2025 2:48 PM, Moteen Shah wrote: Add a function to scan through all the subnodes of a given node recusively for bootph* property. If found, propagate it to all of its parent node up the hierarchy so as to bind the respective drivers of the nodes in the pre-relocation stage.

Re: [RFC PATCH 1/2 v1] arch: arm: Kconfig: Add config to use subnode's bootph property for binding drivers

2025-02-12 Thread Kumar, Udit
On 2/12/2025 2:48 PM, Moteen Shah wrote: Add a new config when set will traverse through all the subnodes of a given node scanning for bootph-all property and propagate it to all of its parent node up the hierarchy. Signed-off-by: Moteen Shah --- arch/arm/Kconfig | 11 +++ 1 file c

Re: [PATCH 0/2] Remove "saveenv" functionality from am57xx evms

2025-02-09 Thread Kumar, Udit
Hi Tom On 2/9/2025 10:50 PM, Tom Rini wrote: On Sat, Feb 08, 2025 at 10:09:36AM +0530, Anurag Dutta wrote: Previously saved environment introduce discrepancies and may lead to incompatibilities without default settings. This series removes the saved environment functionality on am57xx evms so

Re: [PATCH v2 2/3] DONOTMERGE: arm: dts: k3-j784s4-main: Add PBIST_14 node

2025-02-04 Thread Kumar, Udit
On 2/4/2025 6:01 PM, Neha Malcom Francis wrote: Add DT node for PBIST_14 that is responsible for triggering the PBIST self-tests for the MAIN_R5_2_x cores. Signed-off-by: Neha Malcom Francis --- Link to kernel DT upstreaming: https://lore.kernel.org/all/20241128140825.263216-1-n-fran...@ti.co

Re: [PATCH v2 3/3] arm: mach-k3: j784s4_init: Trigger LBIST and PBIST on MAIN R5 2_0

2025-02-04 Thread Kumar, Udit
On 2/4/2025 6:01 PM, Neha Malcom Francis wrote: Trigger all tests of PBIST and LBIST using appropriate calls to set the core under test (MAIN R5 2_0) to it's required state. Signed-off-by: Neha Malcom Francis --- arch/arm/mach-k3/j784s4/j784s4_init.c | 47 +++ 1 fil

Re: [PATCH v2 1/3] drivers: misc: k3_bist: Add K3 BIST driver

2025-02-04 Thread Kumar, Udit
On 2/4/2025 6:01 PM, Neha Malcom Francis wrote: Add a driver for the BIST module that support triggering of both PBIST (Memory BIST) and LBIST (Logic BIST) tests. Also expose the relevant operations and functions that would be required for an end user to trigger the tests. Signed-off-by: Neha

Re: [PATCH 2/8] ram: k3-ddrss: Use DDR address instead of system address for ecc_regions

2025-01-27 Thread Kumar, Udit
On 1/27/2025 7:52 PM, Neha Malcom Francis wrote: Let ecc_regions[x].start reflect the start of the ECC region in terms of DDR addressing rather than system addressing. This will make it easier to extend the usage of the same ecc_regions structure for multi-DDR systems as well. Signed-off-by: N

Re: [PATCH 4/8] ram: k3-ddrss: Add support for a partial inline ECC region

2025-01-27 Thread Kumar, Udit
On 1/27/2025 7:52 PM, Neha Malcom Francis wrote: Instead of defaulting to choosing the entire DDR region when enabling inline ECC, allow picking of a range within the DDR space using DT to enable. It expects such a node within the memory node, in the absence of which we resort to enabling inli

Re: [PATCH 3/8] ram: k3-ddrss: Add comment about ecc_reserved_space

2025-01-27 Thread Kumar, Udit
On 1/27/2025 7:52 PM, Neha Malcom Francis wrote: The reserved space needed for storing the parity remains the same no matter the size of the region that is being protected. Add this as a comment for better code understanding. Signed-off-by: Neha Malcom Francis --- drivers/ram/k3-ddrss/k3-dd

Re: [PATCH v6] mtd: spi-nor: Fix the spi_nor_read() when config SPI_STACKED_PARALLEL is enabled

2024-12-30 Thread Kumar, Udit
Hello Venkatesh, On 12/30/2024 12:32 PM, Venkatesh Yadav Abbarapu wrote: Update the spi_nor_read() function based on the config SPI_FLASH_BAR and update the length and bank calculation by spliting the memory of 16MB size banks only when the address width is 3byte. Fix the read issue for 4byte ad

Re: [PATCH RFC 8/8] configs: Introduce configs for J742S2

2024-12-22 Thread Kumar, Udit
On 12/17/2024 4:37 PM, Manorit Chawdhry wrote: Based off j784s4 configs with delta changes for J742S2 [ Add AVS support for J742S2 ] Signed-off-by: Keerthy Signed-off-by: Manorit Chawdhry --- board/ti/j784s4/MAINTAINERS | 2 ++ configs/j742s2_evm_a72_defconfig | 9 + configs

Re: [PATCH RFC 5/8] arm: mach-k3: j742s2: Introduce clock and device files for J742S2 SoC

2024-12-22 Thread Kumar, Udit
On 12/17/2024 4:37 PM, Manorit Chawdhry wrote: Re-use j784s4 clocks and power domains for j742s2 family of device. Signed-off-by: Manorit Chawdhry --- drivers/clk/ti/clk-k3.c| 4 drivers/power/domain/ti-power-domain.c | 4 2 files changed, 8 insertions(+) diff -

Re: [PATCH RFC 4/8] soc: Add information to identify the J742S2 SoC family

2024-12-22 Thread Kumar, Udit
On 12/17/2024 4:37 PM, Manorit Chawdhry wrote: J742S2 has the same part number as J784S4 but JTAG_DEVICE_ID has a PKG bit that tells about J742S2. Add support for reading JTAG_DEVICE_ID and set family as J742S2 based on that. Link: https://www.ti.com/lit/pdf/spruje3 (TRM) Signed-off-by: Manor

Re: [PATCH RFC 2/8] arm: dts: k3-j784s4-binman.dtsi: Clean up and templatize boot binaries

2024-12-22 Thread Kumar, Udit
On 12/17/2024 4:37 PM, Manorit Chawdhry wrote: From: Neha Malcom Francis Clean up templatized boot binaries for j784s4 soc. This includes modifying the k3-j784s4-binman.dtsi to use SPL_BOARD_DTB, BOARD_DESCRIPTION and UBOOT_BOARD_DESCRIPTION from the files that include it to further reuse cod

Re: [PATCH v2 0/4] Fix OSPI boot for J722S

2024-12-18 Thread Kumar, Udit
On 12/18/2024 6:43 PM, Prasanth Babu Mantena wrote: This series fixes OSPI boot for J722S. It contains fixes for DMSC communication, R5 regmap for ospi and dma specific overrides for ospi. Test log: https://gist.github.com/PrasanthBabuMantena/ad469dd09ab7263f85f87dadda46c86d v2 <==> v1 * Add

Re: [PATCH 2/4] arm: dts: k3-j722s-r5-evm: Fix DM2TIFS secproxy thread ID

2024-12-10 Thread Kumar, Udit
On 12/10/2024 7:27 PM, Prasanth Babu Mantena wrote: From: Vaishnav Achath Fix the DM2TIFS secureproxy thread ID as per the latest TISCI documentation for J722S. Please use Fixes tag https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/sec_proxy.html Signed-off-by: Vaishnav Achath

Re: [PATCH 4/4] arm: dts: k3-j722s*: Add overrides specific to OSPI

2024-12-10 Thread Kumar, Udit
On 12/10/2024 7:27 PM, Prasanth Babu Mantena wrote: From: Vaishnav Achath OSPI Booot requires overrides specific to R5 and also Booot to Boot please to use DMA in R5 SPL stage the DM_TIFS needs to be enabled. Sorry but, you are not enabling DM_TIFS, rather using it, Please update comm

Re: [PATCH 1/4] mailbox: k3-sec-proxy: Add DM to DMSC communication thread for J722S

2024-12-10 Thread Kumar, Udit
On 12/10/2024 7:27 PM, Prasanth Babu Mantena wrote: From: Vaishnav Achath J722S R5 SPL uses sec-proxy threads 28 and 29 for communication with TIFS. Mark these as valid threads in the driver. Please mention doc link also, Also is this only for R5 SPL Signed-off-by: Vaishnav Achath Sign

Re: [PATCH 0/4] Fix OSPI boot for J722S

2024-12-10 Thread Kumar, Udit
On 12/10/2024 7:27 PM, Prasanth Babu Mantena wrote: This series fixes OSPI boot for J722S. It contains fixes for DMSC communication, R5 regmap for ospi and dma specific overrides for ospi. Subject of series, If you are fixing then one or more patch should have Fixes Tag Test log: https

Re: [PATCH] arm64: dts: ti: k3-j7200: Fix OSPI boot

2024-11-29 Thread Kumar, Udit
On 11/29/2024 7:06 PM, Tom Rini wrote: On Fri, Nov 29, 2024 at 12:33:04PM +0530, Sumit Garg wrote: Hi Tom, On Sat, 23 Nov 2024 at 08:12, Tom Rini wrote: On Tue, Nov 19, 2024 at 03:37:20PM +0530, Udit Kumar wrote: OSPI boot is broken due to missing bootph property in pin mux of OSPI. So ad

Re: [PATCH 2/4] drivers: misc: k3_bist: Add K3 BIST driver

2024-11-27 Thread Kumar, Udit
On 11/27/2024 8:23 PM, Neha Malcom Francis wrote: Add a driver for the BIST module that support triggering of both PBIST (Memory BIST) and LBIST (Logic BIST) tests. Also expose the relevant In general , please think of treating err as error in prints instead of debug , Also, few function c

Re: [PATCH 4/4] DONOTMERGE: arm: mach-k3: j784s4_init: Trigger LBIST and PBIST on MAIN R5 2_0

2024-11-27 Thread Kumar, Udit
Thanks Neha. On 11/27/2024 8:23 PM, Neha Malcom Francis wrote: Trigger all tests of PBIST and LBIST using appropriate calls to set the core under test (MAIN R5 2_0) to it's required state. Signed-off-by: Neha Malcom Francis --- arch/arm/mach-k3/j784s4/j784s4_init.c | 48 +

Re: [PATCH 1/4] arm: dts: k3-j784s4-main: Add PBIST_14 node

2024-11-27 Thread Kumar, Udit
On 11/27/2024 8:23 PM, Neha Malcom Francis wrote: Add DT node for PBIST_14 that is responsible for triggering the PBIST self-tests for the MAIN_R5_2_x cores. Signed-off-by: Neha Malcom Francis --- dts/upstream/src/arm64/ti/k3-j784s4-main.dtsi | 12 1 file changed, 12 insertion

Re: [PATCH] mtd: spi-nor-core: Fixup SNOR_F_IO_MODE_EN_VOLATILE for MT35X

2024-11-25 Thread Kumar, Udit
Thanks for fix On 11/25/2024 4:19 PM, Prasanth Babu Mantena wrote: From: Vaishnav Achath MT35XU512ABA has only BFPT and 4-Byte Address Instruction Table in SFDP. commit bebdc237507c ("mtd: spi-nor: Parse SFDP SCCR Map") added checks in spi_nor_octal_dtr_enable() to bail out if the 22nd DWORD

Re: [PATCH v2 1/5] board: ti: am64x: evm: Set "dfu_alt_info" only if interface is Serial Flash

2024-11-25 Thread Kumar, Udit
On 11/25/2024 10:55 AM, Siddharth Vadapalli wrote: On Mon, Nov 25, 2024 at 09:27:50AM +0530, Kumar, Udit wrote: On 11/24/2024 12:37 PM, Siddharth Vadapalli wrote: Commit 5b84d2de5e6c ("board: am64x: Define capsule update firmware info") updated the "dfu_alt_info" var

Re: [PATCH v2 5/5] board: ti: j784s4: evm: Set "dfu_alt_info" only if interface is Serial Flash

2024-11-24 Thread Kumar, Udit
Hi Siddharth On 11/24/2024 12:37 PM, Siddharth Vadapalli wrote: Commit a4d5e5daa847 ("board: sk-am69: Define capsule update firmware info") updated the "dfu_alt_info" variable to support use-cases with Serial Flash. However, this breaks use-cases where interface is not Serial Flash ("sf"). Fix t

Re: [PATCH v2 1/5] board: ti: am64x: evm: Set "dfu_alt_info" only if interface is Serial Flash

2024-11-24 Thread Kumar, Udit
On 11/24/2024 12:37 PM, Siddharth Vadapalli wrote: Commit 5b84d2de5e6c ("board: am64x: Define capsule update firmware info") updated the "dfu_alt_info" variable to support use-cases with Serial Flash. However, this breaks use-cases where interface is not Serial Flash ("sf"). Fix this by setting "

Re: [PATCH v2 2/5] board: ti: j721e: evm: Set "dfu_alt_info" only if interface is Serial Flash

2024-11-24 Thread Kumar, Udit
Hi Siddharth On 11/24/2024 12:37 PM, Siddharth Vadapalli wrote: Commit 9bd6cc292fa8 ("board: j721e: Define capsule update firmware info") updated the "dfu_alt_info" variable to support use-cases with Serial Flash. However, this breaks use-cases where interface is not Serial Flash ("sf"). Fix thi

Re: [PATCH] arm: dts: k3-j722s-r5-evm: Add LPDDR4 4000 MT/s configs

2024-10-16 Thread Kumar, Udit
On 10/17/2024 2:01 AM, Bryan Brattlof wrote: Hi Vaishnav! On October 16, 2024 thus sayeth Vaishnav Achath: Add the latest 4000 MT/s DDR config generated by Jacinto7_DDRSS_RegConfigTool Rev 0.11 for J722S , make it the default config and update A53 default clock to 1.4 GHz matching the default

Re: [PATCH] boardf: Modify DRAM message

2024-10-10 Thread Kumar, Udit
On 10/10/2024 12:39 PM, Neha Malcom Francis wrote: The message "DRAM: 2 GiB (effective 32 GiB)" can be a little confusing, modify the message to show exactly what is meant: "DRAM: 2 GiB (available for U-Boot out of total 32 GiB)" Still confusing for me atleast :) can this be "DRAM: 2 GiB

Re: [PATCH 1/4] mach-k3: common.c: Add dma device remove in spl exit

2024-10-06 Thread Kumar, Udit
Hi Prasanth, On 10/6/2024 2:26 PM, Prasanth Mantena wrote: On 20:09-20241004, Kumar, Udit wrote: Hi Udit, Hi Prasant, Thanks for series, Could we update the subject of patch something like Remove dma device in spl exit, Sorry but Add dma device remove in spl exit looks little confusing

Re: [PATCH 4/4] dma: ti: k3-udma: Move DMA channel[0] allocation to probe and add udma_remove()

2024-10-04 Thread Kumar, Udit
On 10/4/2024 6:50 PM, Prasanth Babu Mantena wrote: From: Santhosh Kumar K Currently, the allocation of DMA channel[0] for memcpy is happening in udma_transfer() for every transfer, which leads to a huge overhead for each transfer, especially in case of nand page reads. So, move this [..]

Re: [PATCH 1/4] mach-k3: common.c: Add dma device remove in spl exit

2024-10-04 Thread Kumar, Udit
Hi Prasant, Thanks for series, Could we update the subject of patch something like Remove dma device in spl exit, Sorry but Add dma device remove in spl exit looks little confusing , are we adding or removing ? On 10/4/2024 6:50 PM, Prasanth Babu Mantena wrote: While exiting from spl, rem

Re: [PATCH v3 5/7] arm: mach-k3: j721s2_init: Initialize AVS Class 0

2024-10-01 Thread Kumar, Udit
On 10/1/2024 2:18 PM, Manorit Chawdhry wrote: Hi Udit, On 08:46-20240815, Kumar, Udit wrote: On 8/13/2024 11:40 AM, Manorit Chawdhry wrote: Initialize AVS Class 0. Signed-off-by: Manorit Chawdhry --- arch/arm/mach-k3/j721s2/j721s2_init.c | 10 ++ 1 file changed, 10 insertions

Re: [PATCH v3 6/7] arm: dts: j721s2: Add VTM node in R5

2024-10-01 Thread Kumar, Udit
On 10/1/2024 4:27 PM, Manorit Chawdhry wrote: Hi Udit, On 08:47-20240815, Kumar, Udit wrote: On 8/13/2024 11:40 AM, Manorit Chawdhry wrote: Add bootph-pre-ram property to VTM node and the pmic node. Signed-off-by: Manorit Chawdhry --- arch/arm/dts/k3-j721s2-r5-common-proc-board.dts | 9

Re: [PATCH v3 3/7] arm: dts: k3-j7*-r5: Add MPU clock in clocks property

2024-10-01 Thread Kumar, Udit
On 10/1/2024 2:15 PM, Manorit Chawdhry wrote: Hi Udit, On 08:32-20240815, Kumar, Udit wrote: On 8/13/2024 11:40 AM, Manorit Chawdhry wrote: MPU clock had been missing. Distinguish multiple clocks with clock-names and add MPU clock as well. Signed-off-by: Manorit Chawdhry --- arch/arm

Re: [PATCH] dts: beagleboneai64: Add boothph in chipid node

2024-09-17 Thread Kumar, Udit
On 9/17/2024 10:24 PM, Tom Rini wrote: On Tue, Sep 17, 2024 at 01:43:29PM +0530, Udit Kumar wrote: beagleboneai64 boot was broken after OF_UPSTREAM support for J721E SOC. So add bootph in chipid node similar to other boards of this SOC. Fixes: 46bb1405b461 ("arm: dts: k3-j721e: Move to OF_UPS

Re: [PATCH RFC/RFT v2 0/4] k3-j784s4-r5-evm: Enable ESMs and related PMIC

2024-09-12 Thread Kumar, Udit
Andrew Thanks, On 9/11/2024 11:09 PM, Andrew Halaney wrote: NOTE: this relies on the linked devicetree changes to land in Linux first and get synced here, otherwise the board will fail to boot! I'm leaving this as a RFC/RFT at this time for that reason until things get merged and synced over (if

Re: [PATCH RFC/RFT 2/3] board: ti: j784s4: Initialize the ESM & PMIC ESM

2024-09-10 Thread Kumar, Udit
On 9/10/2024 10:52 PM, Andrew Halaney wrote: On Sat, Sep 07, 2024 at 11:12:05AM GMT, Kumar, Udit wrote: Hi Andrew, On 9/7/2024 2:54 AM, Andrew Halaney wrote: From: Keerthy Initialize the ESM & PMIC ESM. This allows things like the watchdog to reset the board when tripped. Signed-of

Re: [PATCH RFC/RFT 0/3] k3-j784s4-r5-evm: Enable ESMs and related PMIC

2024-09-10 Thread Kumar, Udit
Hi Andrew On 9/7/2024 2:54 AM, Andrew Halaney wrote: This enables the ESMs and the associated PMIC. Programming these bits is a requirement to make the watchdog actually reset the board. Note, this relies on the linked devicetree changes to land in Linux first and get synced here, otherwise the

Re: [PATCH RFC/RFT 2/3] board: ti: j784s4: Initialize the ESM & PMIC ESM

2024-09-07 Thread Kumar, Udit
Hi Andrew, On 9/7/2024 2:54 AM, Andrew Halaney wrote: From: Keerthy Initialize the ESM & PMIC ESM. This allows things like the watchdog to reset the board when tripped. Signed-off-by: Keerthy Signed-off-by: Neha Malcom Francis Link: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/board/

Re: [RFC PATCH 4/6] drivers: misc: k3_bist: Add K3 BIST driver

2024-09-05 Thread Kumar, Udit
On 9/5/2024 3:11 PM, Neha Malcom Francis wrote: On 04/09/24 10:35, Kumar, Udit wrote: On 9/3/2024 5:14 PM, Neha Malcom Francis wrote: Add a driver for the BIST module which currently includes support for BIST IPs that trigger PBIST (Memory BIST). Signed-off-by: Neha Malcom Francis

Re: [RFC PATCH 4/6] drivers: misc: k3_bist: Add K3 BIST driver

2024-09-04 Thread Kumar, Udit
On 9/3/2024 5:14 PM, Neha Malcom Francis wrote: Add a driver for the BIST module which currently includes support for BIST IPs that trigger PBIST (Memory BIST). Signed-off-by: Neha Malcom Francis --- drivers/misc/Kconfig | 8 + drivers/misc/Makefile | 1 + d

Re: [RFC PATCH 3/6] arm: dts: k3-j784s4-main: Add clock and power domains for MAIN_R5_2_x

2024-09-04 Thread Kumar, Udit
On 9/3/2024 5:13 PM, Neha Malcom Francis wrote: Add bootph-pre-ram as well as the clocks and power-domains for MAIN_R5_2_x. This ensures that LPSC sets the appropriate power and clock and allows for BIST to turn the cores on and off for running the self-test at R5 SPL stage. Signed-off-by: Neh

Re: [RFC PATCH 2/6] arm: dts: k3-j784s4-main: Add PBIST_14 node

2024-09-04 Thread Kumar, Udit
On 9/3/2024 5:13 PM, Neha Malcom Francis wrote: Add DT node for PBIST_14 that is responsible for triggering the BIST self-tests for the MAIN_R5_2_x cores. Signed-off-by: Neha Malcom Francis --- dts/upstream/src/arm64/ti/k3-j784s4-main.dtsi | 10 ++ 1 file changed, 10 insertions(+)

Re: [RFC PATCH 1/6] arm: mach-k3: j784s4: Add clk and power support for MAIN_R5_2_x PBIST

2024-09-04 Thread Kumar, Udit
On 9/3/2024 5:13 PM, Neha Malcom Francis wrote: Add clock and power domains for MAIN_R5_2_0, MAIN_R5_2_1 and PBIST_14. Please keep provision for other R core as well, BIST may be needed in future on those Signed-off-by: Neha Malcom Francis --- arch/arm/mach-k3/r5/j784s4/clk-data.c |

Re: [PATCH v3 7/7] configs: j721s2_evm_r5_defconfig: Add AVS Configs

2024-08-14 Thread Kumar, Udit
On 8/13/2024 11:40 AM, Manorit Chawdhry wrote: Add AVS and PMIC regulator configs Signed-off-by: Manorit Chawdhry --- configs/am68_sk_r5_defconfig| 4 configs/j721s2_evm_r5_defconfig | 6 ++ 2 files changed, 10 insertions(+) diff --git a/configs/am68_sk_r5_defconfig b/config

Re: [PATCH v3 6/7] arm: dts: j721s2: Add VTM node in R5

2024-08-14 Thread Kumar, Udit
On 8/13/2024 11:40 AM, Manorit Chawdhry wrote: Add bootph-pre-ram property to VTM node and the pmic node. Signed-off-by: Manorit Chawdhry --- arch/arm/dts/k3-j721s2-r5-common-proc-board.dts | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm/dts/k3-j721s2-r5-common-proc-b

Re: [PATCH v3 5/7] arm: mach-k3: j721s2_init: Initialize AVS Class 0

2024-08-14 Thread Kumar, Udit
On 8/13/2024 11:40 AM, Manorit Chawdhry wrote: Initialize AVS Class 0. Signed-off-by: Manorit Chawdhry --- arch/arm/mach-k3/j721s2/j721s2_init.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm/mach-k3/j721s2/j721s2_init.c b/arch/arm/mach-k3/j721s2/j721s2_init.c in

Re: [PATCH v3 4/7] drivers: misc: k3_avs: Extract MPU clk and dev ID from DT

2024-08-14 Thread Kumar, Udit
On 8/13/2024 11:40 AM, Manorit Chawdhry wrote: Different devices have different MPU clk and dev ID. Currently it had been hardcoded. Move it to DT based extraction. Signed-off-by: Manorit Chawdhry --- drivers/misc/k3_avs.c | 37 + 1 file changed, 37 inse

Re: [PATCH v3 3/7] arm: dts: k3-j7*-r5: Add MPU clock in clocks property

2024-08-14 Thread Kumar, Udit
On 8/13/2024 11:40 AM, Manorit Chawdhry wrote: MPU clock had been missing. Distinguish multiple clocks with clock-names and add MPU clock as well. Signed-off-by: Manorit Chawdhry --- arch/arm/dts/k3-am69-r5-sk.dts | 3 ++- arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 3

Re: [PATCH] configs: j784s4_evm : Increase Dynamic memory allocation size

2024-07-16 Thread Kumar, Udit
Hi Francesco On 7/17/2024 1:35 AM, Francesco Dolcini wrote: Hello, On Mon, Jul 15, 2024 at 11:13:01PM +0530, Udit Kumar wrote: Increase malloc size to 32 MB to align with other J7 family devices. Is this needed for any specific reason? I am asking to understand if other boards using the same

Re: [PATCH 3/6] arm: dts: k3-j7200-r5-common: Hook buckb1 to vtm supply

2024-05-31 Thread Kumar, Udit
On 5/31/2024 6:38 PM, Aniket Limaye wrote: From: Gowtham Tammana Hook buckb1 to vtm avs supply. Signed-off-by: Gowtham Tammana Signed-off-by: Aniket Limaye --- arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/dts/k3-j7200-r5-com

Re: [PATCH 2/6] arm: dts: k3-j7200-r5: Fix indentation to use tabs

2024-05-31 Thread Kumar, Udit
On 5/31/2024 6:38 PM, Aniket Limaye wrote: To avoid whitespace diff, use tabs throughout the file for indent Signed-off-by: Aniket Limaye --- arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/dts/k3-j7200-r5-

Re: [PATCH 1/6] arm: dts: k3-j7200-r5: Add the pmic node in R5 dt

2024-05-31 Thread Kumar, Udit
On 5/31/2024 6:38 PM, Aniket Limaye wrote: Add bootph-pre-ram property to the buck node in the pmic needed for ESM error event handling. Signed-off-by: Aniket Limaye --- arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm/dts

Re: [PATCH v2 7/7] configs: j721s2_evm_r5_defconfig: Add AVS Configs

2024-05-28 Thread Kumar, Udit
On 5/28/2024 1:43 PM, Manorit Chawdhry wrote: Add AVS and PMIC regulator configs Signed-off-by: Manorit Chawdhry --- configs/am68_sk_r5_defconfig| 4 configs/j721s2_evm_r5_defconfig | 6 ++ 2 files changed, 10 insertions(+) diff --git a/configs/am68_sk_r5_defconfig b/configs

Re: [PATCH v2 3/7] drivers: misc: k3_avs: Check return code while programming AVS

2024-05-28 Thread Kumar, Udit
On 5/28/2024 1:43 PM, Manorit Chawdhry wrote: Check if AVS could not be programmed and print a warning. Signed-off-by: Manorit Chawdhry --- drivers/misc/k3_avs.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/misc/k3_avs.c b/drivers/misc/k3_avs.c index a0d7

Re: [PATCH v2 2/7] drivers: misc: k3_avs: Use soc_match_device instead of compatible.

2024-05-28 Thread Kumar, Udit
Hi Manorit On 5/28/2024 1:43 PM, Manorit Chawdhry wrote: vd_data remains the same for most of the SoCs but there are some differences in power domains and clocks that don't need a change to compatible and can be handled at SoC level. Change the data population logic from compatible to soc_match

Re: [PATCH 0/4] Adding support to load secure firmware for HS devices

2024-05-21 Thread Kumar, Udit
On 5/21/2024 7:59 PM, Andy Shevchenko wrote: On Tue, May 21, 2024 at 04:26:44PM +0530, Udit Kumar wrote: Some use case needs rproc firmware to be loaded at u-boot stage, using following commands at u-boot shell, firmware could be loaded => setenv dorprocboot 1 => run boot_rprocs For Secure d

Re: [PATCH v2 2/2] lmb: Fix adjacent region merge in lmb_add_region_flags()

2024-04-15 Thread Kumar, Udit
Hello Patrice On 4/15/2024 12:33 PM, Patrice CHOTARD wrote: On 4/14/24 13:10, Kumar, Udit wrote: Hello Patrice, On 4/13/2024 1:54 PM, Patrice CHOTARD wrote: On 4/12/24 17:53, Patrice Chotard wrote: In case a new region is adjacent to a previous region with similar flag, this region is

Re: [PATCH v2 2/2] lmb: Fix adjacent region merge in lmb_add_region_flags()

2024-04-14 Thread Kumar, Udit
Hello Patrice, On 4/13/2024 1:54 PM, Patrice CHOTARD wrote: On 4/12/24 17:53, Patrice Chotard wrote: In case a new region is adjacent to a previous region with similar flag, this region is merged with its predecessor, but no check are done if this new added region is overlapping another region

Re: [PATCH 1/2] lmb: Avoid to add identical region in lmb_add_region_flags()

2024-03-11 Thread Kumar, Udit
On 3/11/2024 8:09 PM, Patrice Chotard wrote: In case lmb_add_region_flags() is called with the same parameter than an already existing lmb and this lmb is adjacent to its previous lmb with different flag, this lmb is added again. Same parameter means , addr and size and different flags corre

Re: [PATCH 3/4] arm: dts: k3-j7200-r5-common: fix the mcu_timer0 clock frequency

2024-03-06 Thread Kumar, Udit
On 3/6/2024 12:07 PM, Aniket Limaye wrote: Correcting the clock-frequency property of the mcu_timer0 node Fixes: df73e791ce09 ("arm: dts: j7200: dts sync with Linux 6.6-rc1") Signed-off-by: Aniket Limaye --- arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 2 +- 1 file changed, 1 insertion

Re: [PATCH 2/4] arm: dts: k3-j7200: Fix support for OSPI flash

2024-03-06 Thread Kumar, Udit
On 3/6/2024 12:07 PM, Aniket Limaye wrote: - Add the missing bootph-all property in the flash subnode for ospi - Add the missing overrides for the ospi node in the r5 devicetree Please see , if you can add more on this why we are adding this also, if this patch fixes some previous commit

  1   2   >