Wrap the distro_boot options with CONFIG_DISTRO_DEFAULTS.
This is an intermediate step for us to switch over to
CONFIG_BOOTSTD_DEFAULTS and drop this section in follow on patches.
Reviewed-by: Tom Rini
Tested-by: Mattijs Korpershoek
Signed-off-by: Nishanth Menon
---
No change other than
@ti.com/
V1: https://lore.kernel.org/all/20230725185253.2123433-1...@ti.com/
Jan Kiszka (1):
configs: am62x_evm_a53_defconfig: Disable semi-functional PSCI reset
support
Nishanth Menon (18):
include: env: ti: mmc: envboot/mmcboot: Check result of mmc dev before
proceeding
include: env: ti
Tested-by: Mattijs Korpershoek
Signed-off-by: Nishanth Menon
---
No change other than picking up reviews, tested tags along the way.
V5: https://lore.kernel.org/r/20230824031101.3460411-12...@ti.com
arch/arm/mach-k3/am625_init.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a
akes
power-off under Linux work again when booting via EFI.
[1]
https://uefi.org/specs/UEFI/2.9_A/08_Services_Runtime_Services.html?highlight=efiresetshutdown#resetsystem
Signed-off-by: Jan Kiszka
Signed-off-by: Nishanth Menon
---
New patch picked from Jan
https://lore.kernel.org/all/c93b19ed-43fe
If mmc dev reports that the device is not present, there is no point in
proceeding further to attempt to load the files.
Signed-off-by: Nishanth Menon
---
new patch - noticed a series of 'MMC: no card present' in boot log
and was wondering why, now I know - shaves off 2 seconds or so
Korpershoek
Tested-by: Mattijs Korpershoek
Signed-off-by: Nishanth Menon
---
No change other than picking up reviews, tested tags along the way.
V5: https://lore.kernel.org/r/20230824031101.3460411-14...@ti.com
V4: https://lore.kernel.org/r/20230822184135.2328409-4...@ti.com
arch/arm/mach-k3
Add base documentation for BeaglePlay
Reviewed-by: Mattijs Korpershoek
Tested-by: Mattijs Korpershoek
Signed-off-by: Nishanth Menon
---
Cc: Heinrich Schuchardt
Since V5:
- Updated to point at how to get serial console
- Introduce on using sd card and some tips and tricks I personally
learnt
-..020078|]
https://beagleplay.org/
https://git.beagleboard.org/beagleplay/beagleplay
baseline of base device tree is v6.5-rc1.
Reviewed-by: Tom Rini
Reviewed-by: Mattijs Korpershoek
Tested-by: Mattijs Korpershoek
Signed-off-by: Robert Nelson
Co-developed-by: Nishanth Menon
Signed-off-by
T button
> > When even more leds turn on, lift up on the USR button.
> >
> > At this point the serial should be loading/booting linux, and then
> > running the eMMC flasher in single user mode. Within 5 minutes or so,
> > it should shutdown with a new image in the eMMC..
>
> Thank you, that worked!
Thanks Robert, I did not know of that little trick. Once the everything
settles down in master, will patch that little secret into the
documentation as well.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
;
> > @@ -486,10 +487,11 @@ mmcdev) and set the environments.
> > If manually needs to be done then the environment can be read from the
> > filesystem and then imported
> >
> > -.. code-block::
> > +.. prompt:: bash
> > + :prompts: =>
>
> nitpick: S
?
> +
> +Debugging U-Boot
> +
> +
> +See :ref:`Common Debugging environment - OpenOCD`: for
> +detailed setup information.
> +
> +.. warning::
> +
> + **OpenOCD support since**: v0.12.0
> +
> + If the default package version of OpenOCD in your development
> + environment's distribution needs to be updated, it might be necessary to
> + build OpenOCD from the source.
> +
> +.. include:: k3.rst
> +:start-after: .. k3_rst_include_start_openocd_connect_XDS110
> +:end-before: .. k3_rst_include_end_openocd_connect_XDS110
> +
> +To start OpenOCD and connect to the board
> +
> +.. code-block:: bash
> +
> + openocd -f board/ti_j721s2evm.cfg
> diff --git a/doc/board/ti/k3.rst b/doc/board/ti/k3.rst
> index 5f9bd4dfcbe9..423d55526dc5 100644
> --- a/doc/board/ti/k3.rst
> +++ b/doc/board/ti/k3.rst
> @@ -36,6 +36,7 @@ K3 Based SoCs
> am65x_evm
> j7200_evm
> j721e_evm
> + j721s2_evm
>
> Boot Flow Overview
> --
>
> --
> 2.41.0
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
mpatible = "fixed-clock";
> - #clock-cells = <0>;
> - clock-frequency = <1920>;
> +&mcu_timer0 {
> + clock-frequency = <25000>;
> bootph-pre-ram;
Check your tabs for the clock-frequency and bootph property (you have
one extra tab tab).
> - };
> };
>
[...]
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
gt; / {
> chosen {
> - firmware-loader = &fs_loader0;
> stdout-path = &main_uart8;
Does'nt this come from board.dts?
[...]
> &mcu_ringacc {
> @@ -191,4 +85,3 @@
> ti,sci = <&dm_tifs>;
> };
>
There is an extra EoL here.
> -#include "k3-am68-sk-base-board-u-boot.dtsi"
[...]
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
7,7 @@ static struct ti_lpsc soc_lpsc_list[] = {
> };
>
> static struct ti_dev soc_dev_list[] = {
> + PSC_DEV(35, &soc_lpsc_list[0]),
Reviewed that mcu_timer0 with device ID 35 maps to LPSC_wkup_alwayson
which maps to index 0.
Reviewed-by: Nishanth Menon
> PSC_DEV(108, &soc_lpsc_l
/dts/k3-j721s2-r5-common-proc-board.dts
> F: arch/arm/dts/k3-j721s2-ddr.dtsi
> F: arch/arm/dts/k3-j721s2-ddr-evm-lp4-4266.dtsi
I suggest adding additional patch to include AM68 as well.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
LE_LEN=0x14
> CONFIG_SPL_SEPARATE_BSS=y
> CONFIG_SYS_SPL_MALLOC=y
> CONFIG_HAS_CUSTOM_SPL_MALLOC_START=y
Though this makes me curious who AM62x did'nt need this.. but anyways..
Reviewed-by: Nishanth Menon
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
ot;default";
+ pinctrl-0 = <&wkup_i2c0_pins_default>;
+ clock-frequency = <40>;
+
+ eeprom@50 {
+ /* CAV24C256WE-GT3 */
+ compatible = "atmel,24c256";
+ reg = <0x50>;
+ };
+};
+
&ospi0 {
pinctrl-nam
t;okay";
> clock-frequency = <4800>;
> };
>
> -&main_uart0 {
> - pinctrl-names = "default";
> - pinctrl-0 = <&main_uart0_pins_default>;
> - status = "okay";
> - power-domains = <&k3_pds 146 TI_SCI_PD_SHARED>;
> -};
> -
> &main_sdhci0 {
> /delete-property/ power-domains;
> /delete-property/ assigned-clocks;
> /delete-property/ assigned-clock-parents;
NAK. no explanation why we have to delete these properties. and why not
we add data to handle it if it is mandatory.
> clock-names = "clk_xin";
> clocks = <&clk_200mhz>;
NAK again. please explain why.
> - ti,driver-strength-ohm = <50>;
Will this even work?
> - non-removable;
> bus-width = <8>;
> };
[.. skipping the rest.. since pattern of comments seem to be repeated..]
[1] https://lore.kernel.org/lkml/20230822215042.yjaqtwhuhls57pbu@glamour/T/
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
dtsi
> delete mode 100644 arch/arm/dts/k3-j721e-r5-sk-u-boot.dtsi
> create mode 100644 arch/arm/dts/k3-j721e-thermal.dtsi
>
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
r5_defconfig + dfu.config
4. am62x_beagleplay_r5_dfu_defconfig = am62x_evm_r5_defconfig +
beagleplay_r5.config + dfu.config
This information can be in a single txt file Rather than have a
defconfig file for each combination.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
On 09:31-20230830, Andrew Davis wrote:
> On 8/30/23 7:31 AM, Nishanth Menon wrote:
> > On 17:14-20230829, Andrew Davis wrote:
> > > Add am62x_beagleplay_r5_defconfig for R5 SPL and
> > > am62x_beagleplay_a53_defconfig for A53 SPL and U-Boot support.
> > >
On 13:51-20230831, Neha Malcom Francis wrote:
> Hi Nishanth
>
> On 28/08/23 22:39, Nishanth Menon wrote:
> > On 17:01-20230828, Neha Malcom Francis wrote:
> > > Sync k3-j721e DTS with kernel.org v6.5-rc1.
> > > * pcie_epx nodes have been deleted, they are not ne
On 13:56-20230831, Neha Malcom Francis wrote:
> Hi Nishanth
>
> On 28/08/23 23:03, Nishanth Menon wrote:
> > On 17:01-20230828, Neha Malcom Francis wrote:
> > > This series aims to sync kernel.org v6.5-rc1 DTS with that of U-Boot. It
> > > also includes cleanups w
(4));
> + writel(val, data[id].bgp->cfg2_base + data[id].ctrl_offset);
> +
> + bgp->ts_data[id] = &data[id];
> + }
> +
> + /*
> + * Program TSHUT thresholds
> + * Step 1: set the thresholds to ~123C and 105C WKUP_VTM_MISC_CTRL2
> + * Step 2: WKUP_VTM_TMPSENS_CTRL_j set the MAXT_OUTRG_EN bit
> + * This is already taken care as per of init
> + * Step 3: WKUP_VTM_MISC_CTRL set the ANYMAXT_OUTRG_ALERT_EN bit
> + */
> + high_max = k3_j72xx_bandgap_temp_to_adc_code(MAX_TEMP);
> + low_temp = k3_j72xx_bandgap_temp_to_adc_code(COOL_DOWN_TEMP);
> +
> + writel((low_temp << 16) | high_max, data[0].bgp->cfg2_base +
> +K3_VTM_MISC_CTRL2_OFFSET);
> + mdelay(100);
> + writel(K3_VTM_ANYMAXT_OUTRG_ALERT_EN, data[0].bgp->cfg2_base +
> +K3_VTM_MISC_CTRL_OFFSET);
> +
> + print_look_up_table(dev, ref_table);
> + /*
> + * Now that the derived_table has the appropriate look up values
> + * Free up the ref_table
> + */
> + kfree(ref_table);
> +
> + return 0;
> +
> +err_free_ref_table:
> + kfree(ref_table);
> +
> +err_alloc:
> +
> + return ret;
> +}
> +
> +static const struct k3_j72xx_bandgap_data k3_j72xx_bandgap_j721e_data = {
> + .has_errata_i2128 = true,
> +};
> +
> +static const struct k3_j72xx_bandgap_data k3_j72xx_bandgap_j7200_data = {
> + .has_errata_i2128 = false,
> +};
> +
> +static const struct udevice_id of_k3_j72xx_bandgap_match[] = {
> + {
> + .compatible = "ti,j721e-vtm",
> + .data = (ulong)&k3_j72xx_bandgap_j721e_data,
So what happens to drivers/misc/k3_avs.c ?
> + },
> + {
> + .compatible = "ti,j7200-vtm",
> + .data = (ulong)&k3_j72xx_bandgap_j7200_data,
> + },
> + { /* sentinel */ },
> +};
> +
> +U_BOOT_DRIVER(ti_bandgap_thermal) = {
> + .name = "ti_bandgap_thermal",
> + .id = UCLASS_THERMAL,
> + .ops= &k3_of_thermal_ops,
> + .probe = k3_j72xx_bandgap_probe,
> + .of_match = of_k3_j72xx_bandgap_match,
> + .priv_auto = sizeof(struct k3_j72xx_bandgap),
> +};
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
/A72 u-boot when needed.
you are saying the drivers are mutually exclusive - how about detecting
over-temp scenario at R5 boot? switching on A53 will be a mistake at
that point, no?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
sectability.
>
> Reviewed-by: Neha Malcom Francis
> Signed-off-by: Manorit Chawdhry
Thank you for cleaning this up
Reviewed-by: Nishanth Menon
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
bisectability.
>
> Reviewed-by: Neha Malcom Francis
> Signed-off-by: Manorit Chawdhry
> ---
Thank you for cleaning this up.
Reviewed-by: Nishanth Menon
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
e-property/ from sdhci nodes
>
> We have the necessary clock and dev data so remove these.
>
> - Remove dummy_clocks and fs_loader0
>
> These weren't being used anywhere so remove it.
>
> All these have been put in a single commit to not break the
> bisect
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[] = {
> > > > > + {
> >
y 20
if { ![info exists SOC] } {
# Set the SoC of interest
set SOC j721s2
}
source [find target/ti_k3.cfg]
ftdi tdo_sample_edge falling
# Speeds for FT2232H are in multiples of 2, and 32MHz is tops
# max speed we seem to achieve is ~20MHz.. so we pick 16MHz
adapter speed
gt;
> Reviewed-by: Neha Malcom Francis
> Signed-off-by: Manorit Chawdhry
> ---
Reviewed-by: Nishanth Menon
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
t; 1 file changed, 9 insertions(+), 2 deletions(-)
>
For whatever it is worth:
Reviewed-by: Nishanth Menon
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
t need the null terminator?
> };
>
> U_BOOT_DRIVER(k3_avs) = {
> --
> 2.34.1
>
https://lore.kernel.org/all/1fed9388-dfc4-0b9c-4502-b5020b2ae...@ti.com/
Will let Udit and you sort this out.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
ed-by: Nishanth Menon
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
$subject: s/dtb/device tree or dts
On 13:13-20230905, Reid Tonking wrote:
> Sync j7200 device tree files with Linux 6.5-rc1
With that..
Reviewed-by: Nishanth Menon
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
if (ret)
> - panic("Failed to initialize clk-k3!\n");
> - }
> -
> /* Prepare console output */
> preloader_console_init();
>
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
LED(CONFIG_K3_DM_FW))
> + ret = ti_sci_cmd_get_revision(&info->handle);
> + else
> + ret = 0;
>
> INIT_LIST_HEAD(&info->dev_list);
>
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
t; CONFIG_SYS_FLASH_CFI=y
> -CONFIG_HBMC_AM654=y
> CONFIG_DM_SPI_FLASH=y
> CONFIG_SPI_FLASH_SFDP_SUPPORT=y
> CONFIG_SPI_FLASH_STMICRO=y
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
> --
> 2.34.1
>
https://lore.kernel.org/all/52a7c0b2-7a87-c74e-e63f-d07821ffc...@ti.com/
we are going to end up creating a dependency nightmare.
Can we just do a single series(might be just a single patch) for
compatible additions for k3_avs.c and make the dts syncs dependent on this?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
update the serial environment variable with the same.
>
> Signed-off-by: Dasnavis Sabiya
> Signed-off-by: Apurva Nandan
NAK. go with the approach similar to AM62x. AM69-SK has it's own
fragment.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
On 10:59-20230908, Andrew Davis wrote:
> On 9/8/23 9:42 AM, Nishanth Menon wrote:
> > On 16:35-20230908, Apurva Nandan wrote:
> > > From: Dasnavis Sabiya
> > >
> > > The board name is programmed in the EEPROM. Add support for board
> > > detection and
e.dts
> +++ b/arch/arm/dts/am335x-pocketbeagle.dts
> @@ -15,6 +15,7 @@
>
> chosen {
> stdout-path = &uart0;
> + tick-timer = &timer2;
> };
>
> leds {
> --
> 2.41.0.327.gaa9166bcc0ba
>
Does enabling CONFIG_SYS_ARCH_TIMER solve this?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
On 12:20-20230908, Andrew Davis wrote:
> On 9/8/23 12:03 PM, Nishanth Menon wrote:
> > On 10:59-20230908, Andrew Davis wrote:
> > > On 9/8/23 9:42 AM, Nishanth Menon wrote:
> > > > On 16:35-20230908, Apurva Nandan wrote:
> > > > > From: Dasnavis S
On 09:27-20230909, Trevor Woerner wrote:
> On Fri 2023-09-08 @ 12:36:17 PM, Nishanth Menon wrote:
> > On 11:25-20230830, Trevor Woerner wrote:
> > > Commit 4b2be78ab66c ("time: Fix get_ticks being non-monotonic")
> > > requires '/chosen/ti
;fifos", "proxy_gcfg", "proxy_target", "cfg";
> + bootph-pre-ram;
> +};
>
> - chipid@4314 {
> +&mcu_udmap {
> + reg = <0x0 0x285c 0x0 0x100>,
> + <0x0 0x284c 0x0 0x4000>,
> + <0x0 0x2a80 0x0 0x4>,
> + <0x0 0x284a 0x0 0x4000>,
> + <0x0 0x2aa0 0x0 0x4>,
> + <0x0 0x2840 0x0 0x2000>;
> + reg-names = "gcfg", "rchan", "rchanrt", "tchan",
> + "tchanrt", "rflow";
> bootph-pre-ram;
> - };
> };
NOTE: v6.6-rc1 has been tagged yesterday - so it is probably time for us
to sync with that and drop these.
[...]
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
ds on POWER_DOMAIN && TI_SCI_PROTOCOL && !TI_POWER_DOMAIN
help
Generic power domain implementation for TI devices implementing the
TI SCI protocol.
config TI_POWER_DOMAIN
bool "Enable the TI K3 Power domain driver"
- depends on POWER_DOMAIN && ARCH_K3
+ depends on POWER_DOMAIN && ARCH_K3 && !TI_SCI_POWER_DOMAIN
help
Generic power domain implementation for TI K3 devices.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
Sync device tree with v6.6-rc1
Bootlog: beagleplay:
https://gist.github.com/nmenon/b46863248e8cf0cdaaeca0d55c966af4
Nishanth Menon (2):
arm: dts: k3-pinctrl: Sync with kernel v6.6-rc1
arm: dts: k3-am625: Sync with kernel v6.6-rc1
arch/arm/dts/k3-am62-main.dtsi | 52 -
arch
Sync pinctrl header with v6.6-rc1
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-pinctrl.h | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/dts/k3-pinctrl.h b/arch/arm/dts/k3-pinctrl.h
index c97548a3f42d..2a4e0e084d69 100644
--- a/arch/arm/dts/k3-pinctrl.h
+++ b
Sync device tree with v6.6-rc1
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am62-main.dtsi | 52 -
arch/arm/dts/k3-am62-mcu.dtsi| 24 +
arch/arm/dts/k3-am62-verdin-dev.dtsi | 50 +
arch/arm/dts/k3-am62-verdin.dtsi | 45 +++-
arch/arm/dts/k3
Sync device tree with v6.6-rc1
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am64-main.dtsi | 48 +++---
arch/arm/dts/k3-am642-evm.dts | 2 ++
arch/arm/dts/k3-am642-sk.dts | 6 ++---
3 files changed, 25 insertions(+), 31 deletions(-)
diff --git a/arch/arm
Sync with kernel v6.6-rc1
Bootlog: am642-sk:
https://gist.github.com/nmenon/35f509e2f63b0ab0b434625e68e4f37d
Nishanth Menon (4):
arm: dts: Introduce k3-serdes.h from v6.6-rc1
arm: dts: k3*: Use local header for SERDES MUX idle-state values
dt-bindings: ti-serdes: Deprecate header with
The DTS uses constants for SERDES MUX idle state values which were earlier
provided as bindings header. But they are unsuitable for bindings.
So move these constants in a header next to DTS.
NOTE: sync with v6.6-rc1 will bring in this change naturally.
Signed-off-by: Nishanth Menon
---
arch
erences to bindings header are removed.
So add a warning to mark this bindings header as deprecated.
We could probably drop this header, but let us wait for kernel to
cleanup.
Signed-off-by: Nishanth Menon
---
include/dt-bindings/mux/ti-serdes.h | 70 +
1 file c
Introduce the new serdes header from kernel v6.6-rc1
The DTS uses constants for SERDES MUX idle state values which were earlier
provided as bindings header. But they are unsuitable for bindings.
So move these constants in a header next to DTS.
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3
On 20:29-20230911, Kumar, Udit wrote:
> 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
h drivers in line with the same
> compatibles.
>
> Since the j7200 uses the config as the j721e, the data is inherited
> from j721e vs creating a duplicate
>
> Signed-off-by: Neha Francis
> Signed-off-by: Reid Tonking
> ---
Reviewed-by: Nishanth Menon
--
Regards,
Ni
quot;;
> > break;
> > + case JTAG_ID_PARTNO_J784S4:
> > + family = "J784S4";
> > + break;
> > default:
> > family = "Unknown Silicon";
> > };
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
-sk", "ti,j784s4";
> > + model = "Texas Instruments AM69 SK";
>
> I never understood TI's naming. Somewhere they call it Evaluation Module
> (EVM), somewhere Starter Kit (SK) and
> even at other places Evaluation Board (EVB).
>
Hehe - neither do we understand marketing speak - changes over time
etc.. overall pattern: SK is cost optimized (aka "low cost"
and limited expansion) vs evm - relatively large expansion and expensive ;)
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
their device trees with a more permissive
> license like GPL-2.0-or-later OR MIT
> like most others do?
We can check again, but some sort of corporate policy thing, I suspect.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
On 18:36-20230912, Udit Kumar wrote:
> TI SOC has two power domain TI_SCI_POWER_DOMAIN and
> TI_POWER_DOMAIN. These are mutually exclusive.
> So adding rule to select one, in case defconfig enabled both.
>
> Suggested-by: Nishanth Menon
> Signed-off-by: Udit Kumar
> ---
&g
On 18:36-20230912, Udit Kumar wrote:
> TI SOC has two clock domains CLK_TI_SCI and
> CLK_K3. These are mutually exclusive.
>
> Adding conditional check for CLK_TI_SCI
> and CLK_K3 along with other associated configs options.
>
> Suggested-by: Nishanth Menon
> S
--- a/configs/j7200_evm_r5_defconfig
> +++ b/configs/j7200_evm_r5_defconfig
> @@ -126,7 +126,6 @@ CONFIG_SPL_PINCTRL=y
> # CONFIG_SPL_PINCTRL_GENERIC is not set
> CONFIG_PINCTRL_SINGLE=y
> CONFIG_POWER_DOMAIN=y
> -CONFIG_TI_SCI_POWER_DOMAIN=y
> CONFIG_TI_POWER_DOMAIN=y
> CONFIG_DM_PMIC=y
r5_defconfig
> @@ -126,7 +126,6 @@ CONFIG_SPL_PINCTRL=y
> # CONFIG_SPL_PINCTRL_GENERIC is not set
> CONFIG_PINCTRL_SINGLE=y
> CONFIG_POWER_DOMAIN=y
> -CONFIG_TI_SCI_POWER_DOMAIN=y
> CONFIG_TI_POWER_DOMAIN=y
> CONFIG_DM_PMIC=y
> CONFIG_PMIC_TPS65941=y
> --
> 2.34.1
>
Reviewed
done;
> get_kern_mmc=load mmc ${bootpart} ${loadaddr}
>
> base-commit: 2fe4b54556ea6271237b35de68dc458bfceab94c
we should move to stdboot and simplify this.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
rrect data.
This costs us an extra ~3 milliseconds, which is a minor penalty
compared to the consistent image support we need to have.
Reported-by: Jason Kridner
Fixes: a58147c2dbbf ("board: ti: common: board_detect: Do 1byte address checks
first.")
Signed-off-by: Nishanth Menon
---
_CUSTOM_SYS_INIT_SP_ADDR=y
CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x4030ff00
@@ -102,6 +105,9 @@ CONFIG_DRIVER_TI_CPSW=y
CONFIG_DM_PMIC=y
# CONFIG_SPL_DM_PMIC is not set
CONFIG_PMIC_TPS65217=y
+CONFIG_DEBUG_UART_OMAP=y
+CONFIG_DEBUG_UART_SHIFT=2
+CONFIG_DEBUG_UART_ANNOUNCE=y
CONFIG_SPI=y
CONFIG_DM_SPI=y
CONFIG_OMAP3_SPI=y
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
of
eeproms we are seeing in the wild.
You can find the data (analog+digital capture) here:
https://github.com/nmenon/data-captures/tree/main/i2c-eeprom-1byte-captures
Tool used to capture (and view): https://www.saleae.com/downloads/
Tom, Robert, folks: what do you folks think?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
On 08:56-20220819, Robert Nelson wrote:
> On Fri, Aug 19, 2022 at 4:30 AM Nishanth Menon wrote:
> >
> > On 11:28-20220818, Matwey V. Kornilov wrote:
[..]
> >
> > Tom, Robert, folks: what do you folks think?
>
>
> I'm okay with the delay. if we only
ggest to add a note that this was measured as adding extra
time in startup time.
With that:
Acked-by: Nishanth Menon
>
> Cc: Nishanth Menon
> Fixes: a58147c2dbbf ("board: ti: common: board_detect: Do 1byte address
> checks first.")
> Reference:
> https://lore.k
> 2.17.1
>
We should just delete the entire node. this does'nt exist in upstream[1]
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5
849D 1736 249D
"setenv name_fdt ti_${default_device_tree};"\
> "if test $board_name = j721s2; then " \
> - "setenv name_fdt k3-j721s2-common-proc-board.dtb; fi;" \
> + "setenv name_f
e cpsw3g pinctrl. It moved to a subnode in the
> linux dtsi that u-boot doesn't use/support
>
> Signed-off-by: Sjoerd Simons
>
> ---
>
> Changes in v2:
> - Update dts sync to v6.3-rc5
Reviewed-by: Nishanth Menon
Note to self: I think we should probably re
in
range), this experience should be used to never to have to face this
kind of challenge again.
While it is possible for the phy drivers to practically use the enum's
directly, drivers such as dp83867, dp83869, marvell, micrel_ksz90x1 etc
use the same.
Reported-by: Tom Rini
Signed-of
as much as possible and
let compiler optimize where applicable
or
b) be very explicit in phy drivers and drop these helpers.
I have chosen to go with (a) approach.
Tested on am64x, though the dp83867 is used elsewhere as well.
Nishanth Menon (2):
net: phy: Make phy_interface_is_sgmii a switch state
as dp83867 use this helper to manage the
configuration of the phy correctly.
Reported-by: Tom Rini
Signed-off-by: Nishanth Menon
---
include/phy.h | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/include/phy.h b/include/phy.h
index a837fed72352..1c4dc23bc5ba 10064
On 13:07-20230413, Nishanth Menon wrote:
> Originally reported by Tom[1], turned out to be that recent commit
> 75d28899e3e9 ("net: phy: Synchronize PHY interface modes with Linux")
> reordered the enum definitions which in turn broke the range checks.
>
> we are left wit
On 20:56-20230413, Marek Behún wrote:
> On Thu, Apr 13, 2023 at 01:07:12PM -0500, Nishanth Menon wrote:
> > Recent commit 75d28899e3e9 ("net: phy: Synchronize PHY interface modes
> > with Linux") reordered the enum definitions. This caused the range of
> > enums t
On 23:22-20230413, Marek Behún wrote:
> On Thu, Apr 13, 2023 at 02:02:34PM -0500, Nishanth Menon wrote:
> > On 20:56-20230413, Marek Behún wrote:
> > > On Thu, Apr 13, 2023 at 01:07:12PM -0500, Nishanth Menon wrote:
> > > > Recent commit 75d28899e3e9 ("net: p
in
range), this experience should be used to never to have to face this
kind of challenge again.
While it is possible for the phy drivers to practically use the enum's
directly, drivers such as dp83867, dp83869, marvell, micrel_ksz90x1 etc
use the same.
Reported-by: Tom Rini
Signed-of
as dp83867 use this helper to manage the
configuration of the phy correctly.
Reported-by: Tom Rini
Signed-off-by: Nishanth Menon
---
Changes Since v1:
* Switch update based on feedback from Marek
V1: https://lore.kernel.org/r/20230413180713.2922524-2...@ti.com
include/phy.h | 11 +--
1
stion)
V1: https://lore.kernel.org/all/20230413180713.2922524-1...@ti.com/
Nishanth Menon (2):
net: phy: Make phy_interface_is_sgmii a switch statement
net: phy: Make phy_interface_is_rgmii a switch statement
include/phy.h | 22 ++
1 file changed, 18 insertions(+), 4
for these patches:
9e804638bfe2 Merge tag 'for-v2023-07-rc1' of
https://source.denx.de/u-boot/custodians/u-boot-i2c
Nishanth Menon (23):
Revert "ARM: dts: k3-am642-sk-u-boot: add PMIC node"
arm: dts: k3-am64: Update devicetree to sync with v6.3-rc6
arm: dts: k3-am642-s
We do not need that property to be defined as it is already defined in
am642-sk.dts
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642-sk-u-boot.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/dts/k3-am642-sk-u-boot.dtsi
b/arch/arm/dts/k3-am642-sk-u-boot.dtsi
index
Add missing main_i2c0 node and eeprom property.
This is a pending upstream kernel updates as of v6.3-rc6.
Signed-off-by: Nishanth Menon
---
Sent to kernel.org
https://lore.kernel.org/linux-devicetree/20230414073328.381336-1...@ti.com/
arch/arm/dts/k3-am642-evm.dts | 22
we need to configure the pinmux for main_uart0 to get console
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642-sk-u-boot.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/dts/k3-am642-sk-u-boot.dtsi
b/arch/arm/dts/k3-am642-sk-u-boot.dtsi
index 57797a59e05d
Armstrong
Cc: Kevin Hilman
Signed-off-by: Nishanth Menon
---
https://www.ti.com/tool/SK-AM64B seems to be TPS6522053RHBR, but
anyways, it is not this dts - revert, and when the board dts is added to
kernel.org, we can see how to backport it - this just adds to all kind
of confusion when syncing with
Drop the i2c and mux description, since we have it on main board dts.
Signed-off-by: Nishanth Menon
---
This causes a bisect break with some weird dependency on r5-sk.dts on
u-boot.dtsi
arch/arm/dts/k3-am642-sk-u-boot.dtsi | 14 --
1 file changed, 4 insertions(+), 10 deletions
stdout is provided in evm.dts, add documentation that timer needs to be
fixed in upstream. While at it, fix a minor formatting error
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642-evm-u-boot.dtsi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/dts/k3
Mark the timer as missing in upstream kernel.
Signed-off-by: Nishanth Menon
---
Sent to kernel.org
https://lore.kernel.org/linux-devicetree/20230414073328.381336-1...@ti.com/
once the patches are merged, we can consider integrating the same in the
appropriate sync, I have tried to stay off main
Move to using .env file for setting up environment variables for am64x.
Signed-off-by: Nishanth Menon
---
I think this was long time pending.. but anyways..
board/ti/am64x/Kconfig | 3 +
board/ti/am64x/am64x.env| 37
include/configs/am64x_evm.h | 117
These are inherited from am642-sk.dts itself.
While at this, fix up a minor formatting error with main_cbass.
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642-sk-u-boot.dtsi | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/arch/arm/dts/k3-am642-sk-u-boot.dtsi
b
Until MDIO is converted to DM model, it won't be possible to probe for
pinmux from the MDIO node. To work around this, lets hack the board dts
to set the default mux option to include MDIO. This hack is a limitation
for now till we get u-boot MDIO driver into DM model.
Signed-off-by: Nis
Use am642-evm.dts to represent the Board and selectively
enable/override the configurations necessary. And since
am642-evm-u-boot.dtsi also needs to setup common properties, instead
of re-inventing everything, just reuse the definitions.
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642
Add missing main_i2c0 node and eeprom property.
This is a pending upstream kernel updates as of v6.3-rc6.
Signed-off-by: Nishanth Menon
---
Sent to kernel.org
https://lore.kernel.org/linux-devicetree/20230414073328.381336-1...@ti.com/
arch/arm/dts/k3-am642-sk.dts | 21
Use am642-sk.dts to represent the Board and selectively enable/override
the configurations necessary. And since am642-sk-u-boot.dtsi also needs
to setup common properties, instead of re-inventing everything, just
reuse the definitions.
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642-r5
Reorder the pinmux to place it above the interface for easier tracking.
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642-evm-u-boot.dtsi | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/arm/dts/k3-am642-evm-u-boot.dtsi
b/arch/arm/dts/k3-am642-evm
is a limitation
for now till we get u-boot MDIO driver into DM model.
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642-evm-u-boot.dtsi | 4
arch/arm/dts/k3-am642-evm.dts | 3 ++-
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/arch/arm/dts/k3-am642-evm-u-boot.dtsi
b
Add required pinmux spl notations for pinmux entries that are missing.
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642-evm-u-boot.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/dts/k3-am642-evm-u-boot.dtsi
b/arch/arm/dts/k3-am642-evm-u-boot.dtsi
Just use distroboot when we are attempting to enable that by default.
Signed-off-by: Nishanth Menon
---
we should probably do this for all other defconfigs instead of the weird
hacks folks have been doing inconsistenly in am62x, j721e defconfig.
if we are distroboot, just do it.. envboot is
Sync with Kernel.org v6.3-rc6 tag.
Signed-off-by: Nishanth Menon
---
arch/arm/dts/k3-am642.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/dts/k3-am642.dtsi b/arch/arm/dts/k3-am642.dtsi
index 8a76f4821b11..7a6eedea3aae 100644
--- a/arch/arm/dts/k3-am642.dtsi
+++ b/arch/arm/dts
201 - 300 of 1467 matches
Mail list logo
