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
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
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
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
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
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
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
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
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
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
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
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
On 3/6/2024 12:07 PM, Aniket Limaye wrote:
Add the necessary configs required for OSPI functionality.
Also update the ospi flash partition offsets as per the devicetree.
Signed-off-by: Aniket Limaye
---
configs/j7200_evm_a72_defconfig | 10 --
configs/j7200_evm_r5_defconfig | 9
On 3/6/2024 12:07 PM, Aniket Limaye wrote:
Support for OSPI probe and also read/write is broken and/or missing in current
master branch.
Its broken :)
- sf probe failure from u-boot prompt & OSPI boot failure [0]
This series adds necessary configs, as well as fixes some bugs in the
Thanks For fixing this
On 2/24/2024 5:53 AM, Jonathan Humphreys wrote:
Add boot ROM XSPI bootmode, and set to BOOT_DEVICE_SPI if detected.
Signed-off-by: Jonathan Humphreys
---
arch/arm/mach-k3/include/mach/j721e_spl.h | 5 +++--
arch/arm/mach-k3/j721e_init.c | 3 ++-
2 files
On 2/24/2024 5:53 AM, Jonathan Humphreys wrote:
Set config values to enable OSPI functionality.
Signed-off-by: Jonathan Humphreys
---
configs/j721e_evm_a72_defconfig | 7 +++
configs/j721e_evm_r5_defconfig | 6 ++
2 files changed, 13 insertions(+)
diff --git
Thanks Jon
On 2/24/2024 5:53 AM, Jonathan Humphreys wrote:
The phy calibration pattern partition isn't needed as the Cadence driver isn't
calibrating the phys.
Please do mention Fixes tag here
58d61fb5a77e ("arm: dts: k3-j721e-sk: Add initial A72 specific dts support")
Signed-off-by:
On 2/6/2024 5:51 PM, Manorit Chawdhry wrote:
Patch is sent to upstream linux [0].
[0]:
https://lore.kernel.org/all/20240201-b4-upstream-j721s2-fix-vtm-devid-v2-0-85fd568b7...@ti.com/
Signed-off-by: Manorit Chawdhry
---
arch/arm/dts/k3-j721s2-mcu-wakeup.dtsi | 2 +-
1 file changed, 1
On 1/30/2024 1:11 PM, Neha Malcom Francis wrote:
The number of DDR controllers to be initialised and used should depend
on the device tree with the constraint of the maximum number of
controllers the device supports. Since J721S2 has multiple (2)
controllers, instead of hardcoding the number
Thanks Reid
On 12/7/2023 10:22 PM, Reid Tonking wrote:
From: Bryan Brattlof
In order for the Cortex-A72s to operate at different frequencies other
than the default 2GHz, add in a new 'virtual' mux (a mux that does not
physically exist in the clock tree) that can be selected.
CC: Vishal
On 12/7/2023 2:47 AM, Reid Tonking wrote:
Previously, dynamic frequency scaling supported rates only through fixed
divison.
This virtual clock mux configuration enables more varied rates on A72
clock ID 202 by setting up the required register.
Signed-off-by: Apurva Nandan
Signed-off-by:
On 12/7/2023 2:47 AM, Reid Tonking wrote:
From: Bryan Brattlof
In order for the Cortex-A72s to operate at different frequencies other
than the default 2GHz, add in a new 'virtual' mux (a mux that does not
physically exist in the clock tree) that can be selected.
CC: Vishal Mahaveer
On 12/2/2023 3:03 AM, Reid Tonking wrote:
From: Apurva Nandan
This virtual clock mux configuration enables the use of dynamic frequency
scaling on A72 clock ID 202 by setting up the required register.
IMO, dynamic frequency scaling should be supported without this patch.
But this patch
On 12/2/2023 3:03 AM, Reid Tonking wrote:
From: Bryan Brattlof
In order for the Cortex-A72s to operate at different frequencies other
than the default 2GHz, add in a new 'virtual' mux (a mux that does not
physically exist in the clock tree) that can be selected.
CC: Vishal Mahaveer
On 11/17/2023 4:26 AM, Enric Balletbo i Serra wrote:
Hi Maxime
On Wed, Nov 15, 2023 at 2:54 PM Maxime Ripard wrote:
Hi,
On Sun, Oct 01, 2023 at 10:25:29PM +0530, Apurva Nandan wrote:
This series will introduce basic support (SD and UART) support for Texas
Instruments J784S4 EVM.
The
On 11/16/2023 1:40 PM, Neha Malcom Francis wrote:
Hi Udit
On 14/11/23 11:07, Kumar, Udit wrote:
Thanks Reid for sync.
On 11/14/2023 2:13 AM, Reid Tonking wrote:
Sync u-boot device tree with Linux kernel 6.7-rc1
Signed-off-by: Reid Tonking
---
Boot-log:
https://gist.github.com/reidt1
Thanks Reid for sync.
On 11/14/2023 2:13 AM, Reid Tonking wrote:
Sync u-boot device tree with Linux kernel 6.7-rc1
Signed-off-by: Reid Tonking
---
Boot-log: https://gist.github.com/reidt1/db5426f2a778369db8c3699cf293b94f
arch/arm/dts/k3-j7200-main.dtsi | 2 +-
On 11/6/2023 5:48 PM, Nishanth Menon wrote:
On 15:54-20231104, Kumar, Udit wrote:
On 11/3/2023 6:07 AM, Nishanth Menon wrote:
Commit 5019170970ad ("arch: arm: mach-k3: j721e: add support for UDA
FS") introduced basic UDA FS support, however, we can Take approach
similar
On 11/6/2023 5:49 PM, Nishanth Menon wrote:
On 16:03-20231104, Kumar, Udit wrote:
On 11/3/2023 6:07 AM, Nishanth Menon wrote:
When config is enabled, the esm dt probe makes sense. Simplify by
dropping board specific checks.
Signed-off-by: Nishanth Menon
---
board/ti/j721e/evm.c | 10
On 11/4/2023 4:05 PM, Kumar, Udit wrote:
On 11/3/2023 6:07 AM, Nishanth Menon wrote:
Serdes initialization should be compile flag based instead of being
eeprom based.
Signed-off-by: Nishanth Menon
---
board/ti/j721e/evm.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions
On 11/3/2023 6:07 AM, Nishanth Menon wrote:
Serdes initialization should be compile flag based instead of being
eeprom based.
Signed-off-by: Nishanth Menon
---
board/ti/j721e/evm.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/board/ti/j721e/evm.c
On 11/3/2023 6:07 AM, Nishanth Menon wrote:
When config is enabled, the esm dt probe makes sense. Simplify by
dropping board specific checks.
Signed-off-by: Nishanth Menon
---
board/ti/j721e/evm.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git
On 11/3/2023 6:07 AM, Nishanth Menon wrote:
Commit 5019170970ad ("arch: arm: mach-k3: j721e: add support for UDA
FS") introduced basic UDA FS support, however, we can Take approach
similar to commit 0f1c1e8b368b ("arm: mach-k3: am625: Add support for
UDA FS"). While boot partition support with
Thanks Prasanth
On 10/20/2023 12:31 PM, Prasanth Babu Mantena wrote:
EEPROM detection logic in ti_i2c_eeprom_get() involves reading the total
size followed by reading 1-byte size with an offset 1. This commit fixes
the header matching issue in commit 9f393a2d7af8 ("board: ti: common:
On 10/13/2023 3:59 PM, Neha Malcom Francis wrote:
Currently J721E defines only the main_esm in DTS. Add node for mcu_esm
as well.
According to J721E TRM (12.11.2.2 ESM Environment) [1], we see that the
interrupt line from ESMi (main_esm) is routed to MCU_ESM (mcu_esm). This
is
On 10/3/2023 1:40 PM, Keerthy wrote:
Enable ESM initialization for J7200
Signed-off-by: Keerthy
---
board/ti/j721e/evm.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/board/ti/j721e/evm.c b/board/ti/j721e/evm.c
index 42fa94b7a5..070b28326f 100644
---
Dear All,
On 9/8/2023 10:59 PM, Udit Kumar wrote:
VTM (Voltage and Thermal Manager) IP is used for following purpose
1) AVS class 0
2) Thermal management (setting thermal shutdown TSHUT) temperature.
3) SoC temperature reporting.
In origin boot flow, R5/SPL sets the AVS voltage using
by AVS
Hi Keerthy
On 9/25/2023 7:12 PM, Nishanth Menon wrote:
On 18:56-20230925, Keerthy wrote:
Hi Tom,
https://lore.kernel.org/linux-arm-kernel/5187c590-ee9a-4c46-b326-655f4c371...@linaro.org/T/#me178708007a6b3b9695ae0ff84475fa4f49f283c
I have posted the ESM patches to the linux kernel device tree
Thanks Simon
On 9/25/2023 9:39 PM, Simon Glass wrote:
Hi Udit,
On Sun, 24 Sept 2023 at 22:10, Kumar, Udit wrote:
On 9/24/2023 7:21 PM, Heinrich Schuchardt wrote:
Am 24. September 2023 13:18:32 MESZ schrieb Udit Kumar :
[..]
Assumption
Thanks Heinrich will fix this typo in v2.
Let me
Hi Mark/Tom
On 9/25/2023 9:01 PM, Tom Rini wrote:
On Mon, Sep 25, 2023 at 05:27:26PM +0200, Mark Kettenis wrote:
Date: Mon, 25 Sep 2023 11:21:26 -0400
From: Tom Rini
On Sun, Sep 24, 2023 at 04:48:32PM +0530, Udit Kumar wrote:
In case of new memory range to be added is coalesced
with any
Hi Tom,
On 9/13/2023 10:09 AM, Udit Kumar wrote:
This series, updates enabling mutually exclusive power and clock configs
for TI SOCs.
Sorry to push clock and power changes in one series,
managed by two maintainers. But In my quick grep,
I am not able to active PR raise from both trees.
So
On 9/22/2023 2:45 PM, Neha Malcom Francis wrote:
According to the TRMs of K3 platform of devices, the ROM boot image
Below tear line, giving some link of TRM, with section information
where this format is mentioned will be helpful for reviewers.
format specifies a "Core Options Field"
On 9/24/2023 7:21 PM, Heinrich Schuchardt wrote:
Am 24. September 2023 13:18:32 MESZ schrieb Udit Kumar :
In case of new memory range to be added is coalesced
with any already added non last lmb region.
And there is possibility that, then region in which new memory
range added is not adjacent
Dear Experts,
I am looking for suggestion/guidance, how to use above 4G memory on in u-boot
for ARM 64-bit based architecture.
On our system, we have low memory from
0x8000_ to 0x_ and above 4G
0x8_8000_ to 0x8__
As per my understanding, we have following pointers in
Thanks Nishanth
On 9/20/2023 5:50 PM, Nishanth Menon wrote:
On 17:32-20230920, Udit Kumar wrote:
AVS is enabled at R5 SPL stage, on few platforms like J721E
and J7200 clk-k3 is used instead if clk-sci driver.
[...]
I think it is better to put IS_ENABLED() as the first check.
See other usage:
$
Hi Nishanth,
On 9/19/2023 9:07 PM, Nishanth Menon wrote:
On 19:34-20230919, Udit Kumar wrote:
AVS is enabled at R5 SPL stage, on few platforms like J721E
and J7200 clk-k3 is used instead if clk-sci driver.
Add support in clk-k3 driver as well to notify AVS driver
upon setting clock rate so
On 9/19/2023 4:44 PM, Nishanth Menon wrote:
On 11:36-20230919, Udit Kumar wrote:
AVS is enabled at R5 SPL stage, where clk-k3 is used
instead if clk-sci driver.
[..]
Why drop from here? we do have am64 and am65 that use ti-sci, correct?
Thanks,
am64/am65 slipped out of my mind while
Hi Roger
>
>
>On 08/09/2023 14:05, Apurva Nandan wrote:
>> From: Hari Nagalla
>>
>> The K3 J784S4 SoCs have four dual-core R5F subsystems, one in MCU
>> voltage domain and the other three in MAIN voltage domain. These R5F
>> clusters are similar to the R5F clusters in J7200 and J721S2 SoCs.
>>
Thank you for suggestion Nishanth
On 9/11/2023 6:51 PM, Nishanth Menon wrote:
On 16:49-20230911, Udit Kumar wrote:
[..]
And maybe expand this patch so that it contains something like the
following to prevent this from coming back again elsewhere?
diff --git a/drivers/clk/ti/Kconfig
On 9/7/2023 12:58 AM, reidt wrote:
On 13:06-20230906, Nishanth Menon wrote:
On 13:13-20230905, Reid Tonking wrote:
The ti,j7200-vtm compatible is used for voltage and thermal monitoring
(VTM) by (drivers/thermal/k3_j72xx_bandgap.c) in Linux, but the same
hardware is used for adaptive voltage
Hi Nishanth,
On 9/2/2023 12:40 AM, Nishanth Menon wrote:
On 23:43-20230901, Kumar, Udit wrote:
On 9/1/2023 11:03 PM, Nishanth Menon wrote:
On 22:54-20230901, Kumar, Udit wrote:
+static const struct udevice_id of_k3_j72xx_bandgap_match[] = {
+ {
+ .compatible = "ti,
On 9/1/2023 11:03 PM, Nishanth Menon wrote:
On 22:54-20230901, Kumar, Udit wrote:
+static const struct udevice_id of_k3_j72xx_bandgap_match[] = {
+ {
+ .compatible = "ti,j721e-vtm",
+ .data = (ulong)_j72xx_bandgap_j721e_data,
So what happens to dr
Hi Nishanth
On 9/1/2023 8:36 PM, Nishanth Menon wrote:
On 11:44-20230901, Udit Kumar wrote:
Add support for VTM (Voltage and Thermal Manager), which
is part of TI's K3 series SOC.
Signed-off-by: Udit Kumar
---
drivers/thermal/Kconfig| 6 +
drivers/thermal/Makefile
On 8/17/2023 5:06 PM, Nishanth Menon wrote:
On 09:45-20230817, Kumar, Udit wrote:
On 8/16/2023 5:14 PM, Nishanth Menon wrote:
On 14:53-20230816, Manorit Chawdhry wrote:
The following commit syncs the device tree from Linux tag
next-20230815 to U-boot and fixes the following to be compatible
On 8/16/2023 5:14 PM, Nishanth Menon wrote:
On 14:53-20230816, Manorit Chawdhry wrote:
The following commit syncs the device tree from Linux tag
next-20230815 to U-boot and fixes the following to be compatible with
the future syncs -
[..]
+_timer0 {
+ /delete-property/
>On 07.07.23 15:30, Jerome Forissier wrote:
>>
>>
>> On 7/7/23 14:34, Neha Malcom Francis wrote:
>>> Earlier documentation specified builds for generating bootloader
>>> images using an external TI repository k3-image-gen and
>>> core-secdev-k3. Modify this to using the binman flow so that user
On 5/3/2023 8:21 PM, Nishanth Menon wrote:
On 20:17-20230503, Udit Kumar wrote:
Mark atf, l3-cache and tifs node as reserved.
why? (I am not reading the cover-letter for a 1 patch)
My bad , I should have description in patch itself.
Thanks
[...]
2.34.1
On 5/3/2023 8:15 PM, Nishanth Menon wrote:
On 10:58-20230503, Udit Kumar wrote:
This patch corrects the MMC raw mode sector offset as
per documentation.
Thanks Nishanth
On 5/3/2023 8:01 PM, Nishanth Menon wrote:
On 09:43-20230503, Udit Kumar wrote:
[..]
Needs to get to k.org master.
Noted for whole series
Thanks Nishanth
On 5/3/2023 7:46 PM, Nishanth Menon wrote:
On 09:43-20230503, Udit Kumar wrote:
[..]
Not in upstream k.org. NAK.
i will hold this series till updated in k.org
On 5/3/2023 7:45 PM, Nishanth Menon wrote:
On 09:43-20230503, Udit Kumar wrote:
From: Nishanth Menon
Sync with Kernel.org v6.3-rc6 tag.
we are few days away from rc1 tag. I'd rather we refresh.
Thanks
[..]
Hi Nishanth,
On 5/3/2023 4:30 AM, Nishanth Menon wrote:
On 12:57-20230502, Kumar, Udit wrote:
On 5/1/2023 8:16 PM, Andrew Davis wrote:
On 4/26/23 9:13 AM, Kumar, Udit wrote:
Hi Neha,
On 4/26/2023 5:31 PM, Neha Malcom Francis wrote:
Hi Udit
On 26/04/23 16:09, Kumar, Udit wrote:
Hi Neha
On 5/1/2023 8:16 PM, Andrew Davis wrote:
On 4/26/23 9:13 AM, Kumar, Udit wrote:
Hi Neha,
On 4/26/2023 5:31 PM, Neha Malcom Francis wrote:
Hi Udit
On 26/04/23 16:09, Kumar, Udit wrote:
Hi Neha,
Hi Udit,
[..]
I do have a general doubt; why do we have only atf-sram sub-node
Hi Neha,
On 4/26/2023 5:31 PM, Neha Malcom Francis wrote:
Hi Udit
On 26/04/23 16:09, Kumar, Udit wrote:
Hi Neha,
Hi Udit,
[..]
I do have a general doubt; why do we have only atf-sram sub-node in
msmc_sram in all other devices (j721e, j7200 and am65) except j721s2?
let me know, which
Hi Neha,
> Hi Udit,
[..]
>>>
>>> I do have a general doubt; why do we have only atf-sram sub-node in
>>> msmc_sram in all other devices (j721e, j7200 and am65) except j721s2?
>>
>> let me know, which source code you are referring to
>>
>
>In U-Boot, for j721e, j7200 and am65; they *only*
Hi Neha
On 4/26/2023 2:56 PM, Neha Malcom Francis wrote:
Hi Udit
On 20/04/23 13:41, Udit Kumar wrote:
This patch deletes tifs DT node as part of fixup.
TISCI API reported msmc_size, does not include
64KB reserved size for tifs aka MSMC comms memory.
As part of fixup, original code uses
Thanks for review
On 4/19/2023 9:22 PM, Nishanth Menon wrote:
On 11:43-20230419, Udit Kumar wrote:
This patch deletes tifs DT node as part of fixup.
TISCI API reported msmc_size, does not include
64KB reserved size for tifs aka MSMC comms memory.
As part of fixup, original code uses TISCI
67 matches
Mail list logo
