Clock and reset names are being removed from upstream device-tree for
devices that only have a single clock or reset. The QSPI driver does not
use the 'reset-names' property and so this can be removed for these
devices.
UART devices may use either the 8250 serial driver or the Tegra HS
serial driver. The default is the 8250 driver. When the Tegra HS serial
driver is used, the 'reset-names' property is required because the
driver specifically uses the reset name although there is only one. The
clock-names and reset-names for the 0x3100000 UART can be removed from
the base overlay file because the reset-names is correctly specified
in the files where the compatibility string for the Tegra HS serial
driver is set.
Bug 4037899
Change-Id: I501cd36609824e5703a6b756fc5f5389dd8d2368
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/device/hardware/nvidia/t23x-public-dts/+/3074829
Reviewed-by: Brad Griffis <bgriffis@nvidia.com>
GVS: Gerrit_Virtual_Submit <buildbot_gerritrpt@nvidia.com>
When booting Linux with GRUB, the serial console does not show the
kernel boot messages as expected. By default GRUB does not add the
'console' kernel parameter and relies on device-tree to configure the
default serial port. Device-tree configures the default serial port by
setting the property 'stdout-path=serial0:115200n8' where 'serial0' is
an alises to one of the devices serial ports. The default serial port
for Tegra234 devices is the TCU0 and so 'serial0' should be mapped to
this interface. However, the 'serial0' is being updated to be mapped to
a different UART.
Fix this by removing the additional 'serialX' aliases in the base
overlay file and add any alises that are not already defined to the
appropriate board file. This does change the mapping of some aliases but
this aligns the boards with the aliases as they are defined upstream.
Bug 4264560
Change-Id: Icf6bdb1e7d5c9abf5bdbf5378b4ed8122910b507
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/device/hardware/nvidia/t23x-public-dts/+/3072368
Reviewed-by: Brad Griffis <bgriffis@nvidia.com>
Reviewed-by: Paritosh Dixit <paritoshd@nvidia.com>
GVS: Gerrit_Virtual_Submit <buildbot_gerritrpt@nvidia.com>
This change binds thermal trip event cooling devices to the following
events:
- sw throttling event
- hot surface event
When the bound trip point temperature gets crossed, the associated
cooling device will become active, and its state can be learnt from the
user space to take the action accordingly.
The thermal trip event cooling device is not needed for safety IGX so
disable it.
Bug 4261645
Bug 1688327
Signed-off-by: Yi-Wei Wang <yiweiw@nvidia.com>
Change-Id: Ifa7f2dfb5c95113e9902e3ea4dfc03197065c5e5
Reviewed-on: https://git-master.nvidia.com/r/c/device/hardware/nvidia/t23x-public-dts/+/3015753
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
In this commit:
1. The large platform overlays are being directly built into
a new base "nv" dtb. The names of these new dtbs directly tracks the
name of the upstream dtb that it extends. For an upstream dtb named
<base>.dtb the new corresponding new file is named <base>-nv.dtb.
2. The source files for <base>-nv.dtb are located in the nv-soc/ and
nv-platform/ files. Those files originated in the overlay/
directory but are moved to reflect that they are no longer part of
an overlay.
This new layout seeks to simplify building and handling of dtb files
while retaining close compatibility with the upstream dts sources.
Bug 4290389
Change-Id: Ic812e8e16c5515bb3e17b99a23815a99f67c42a2
Signed-off-by: Brad Griffis <bgriffis@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/device/hardware/nvidia/t23x-public-dts/+/2996468
Reviewed-by: svcacv <svcacv@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Gautham Srinivasan <gauthams@nvidia.com>
GVS: Gerrit_Virtual_Submit <buildbot_gerritrpt@nvidia.com>
