It is believed that these set_rts functions are not functional in the kernel.
Remove these for now from the btti_uart driver until the true fix can be identified.

Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>

The driver uses port_id, which gets populated from device tree has
1-based indexing, where as common->ports[] array has 0-based indexing.
Using port_id to dereference common->ports[] will causes out-of-bound
null pointer dereference.

Fixes: 48f6254a24fc7 ("FROMLIST: net: ethernet: ti: am65-cpsw: Add AF_XDP zero copy for TX")
Signed-off-by: Meghana Malladi <m-malladi@ti.com>

Disable non-critical configs to reduce boot time for early display.

- Disable audit subsystem, network filtering, network QoS scheduling,
  NFS filesystem, and security hardening features.
- Disable power management features including hibernation, suspend, CPU
  idle, and energy model to minimize initialization time.
- Disable non-essential CGROUP subsystems and CPU hotplug support.
- Disable additional ARM64 features and address randomization.

Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Tested-by: Swamil Jain <s-jain1@ti.com>

For CPSW5G QSGMII ports, CPSW assumes SERDES to be configured. Since it
may not be always true, add SERDES phys to guarantee it.

Link: https://lore.kernel.org/r/20260326134929.1696750-1-c-vankar@ti.com/
Fixes: 496cdc82e05f ("arm64: dts: ti: k3-j7200: Add overlay to enable CPSW5G ports in QSGMII mode")
Signed-off-by: Chintan Vankar <c-vankar@ti.com>

For CPSW9G QSGMII ports, CPSW assumes SERDES to be configured. Since it
may not be always true, add SERDES phys to guarantee it.

Link: https://lore.kernel.org/r/20260326072237.1324027-1-c-vankar@ti.com/
Fixes: 86e7de8bf908 ("arm64: dts: ti: k3-j721e: Add overlay to enable CPSW9G ports in QSGMII mode")
Signed-off-by: Chintan Vankar <c-vankar@ti.com>

The VSC8514 quad-port Ethernet PHY was returning both LINK_INBAND_DISABLE
and LINK_INBAND_ENABLE capabilities, causing autonegotiation issues in
QSGMII mode. This prevented proper link establishment.

Fix this by returning only LINK_INBAND_ENABLE from vsc85xx_inband_caps()
for QSGMII interface, and ensure phylink properly sets the phy_ib_mode
when only inband enable is supported.

This enables proper QSGMII in-band autonegotiation for VSC8514 devices.

Fixes: df979273bd71 ("net: phy: mscc: report and configure in-band auto-negotiation for SGMII/QSGMII")
Signed-off-by: Chintan Vankar <c-vankar@ti.com>

commit c7c6d4f5103864f73ee3a78bfd6da241f84197dd upstream.

Due to errata i2493[0], multi-block write would still fail in retries.

With i2493, the MMC interface has the potential of write failures when
issuing multi-block writes operating in HS200 mode with excessive IO
supply noise.

While the errata provides guidance in hardware design and layout to
minimize the IO supply noise, in theory the write failure cannot be
resolved in hardware. The software solution to ensure the data integrity
is to add minimum 5us delay between block writes. Single-block write is
the practical way to introduce the delay.

This patch reuses recovery_mode flag, and switches to single-block
write in retry when multi-block write fails. It covers both CQE and
non-CQE cases.

[0] https://www.ti.com/lit/pdf/sprz582
Link: https://lore.kernel.org/linux-mmc/20260310160408.3976760-1-b-liu@ti.com/T/#m5c69c0e448e628569dc6df296e76ebed89a41c39
Cc: stable@vger.kernel.org
Suggested-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Bin Liu <b-liu@ti.com>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

Create explicit device link when OPP table has ti,soc-info property.
Prevents unbinding k3-socinfo while ti-cpufreq is using it.

Signed-off-by: Akashdeep Kaur <a-kaur@ti.com>

Link CPU OPP table to k3-socinfo driver for dependency tracking.

Signed-off-by: Akashdeep Kaur <a-kaur@ti.com>

Link CPU OPP table to k3-socinfo driver for dependency tracking.

Signed-off-by: Akashdeep Kaur <a-kaur@ti.com>