Hi,
In the Makefile under
hardware/nvidia/platform/t210/jetson/kernel-dts/
There are rules for creating dtbs for different platforms.
Can you please explain what are:
tegra210-jetson-cv-
tegra210-jetson-e-
platforms. How they differ from tegra210-jetson-tx1
Thanks.
You should only use jetson-cv based dtb. Jetson-e was a tx1 platform for nvidia internal use.
Thanks Wayne.
What’s is the difference between tegra210-jetson-tx1 and tegra210-jetson-cv- ( the tx1 is using the cv)
Can you please share what is CV stand for?
roey.bh,
That naming does not stand for any evident difference.
As I said in previous comment, many dtb are for internal use only.
For example, p2371-2180.conf is using “tegra210-jetson-cv-base-p2597-2180-a00.dtb”. It would enable DSI panel by default. While jetson-tx1.conf, which is actually “p2371-2180-devkit.conf”, is for public users who do not have our internal board to test DSI panel so this dtb does not enable DSI panel by default.
Hi Wayne,
Thanks for the clarification.
When we flash TX1 devkit, the flash script is loading the following dtb
tegra210-jetson-tx1-p2597-2180-a01-devkit.dtb
Looking at the dts source:
/hardware/nvidia/platform/t210/jetson/kernel-dts/tegra210-jetson-tx1-p2597-2180-a01-devkit.dts
Includes the following dts:
#include “tegra210-jetson-cv-base-p2597-2180-a00.dts”
Which, if I understand, will enable the DSI on the devkit. Do I understand it correctly?
Thanks,
Roey
roey.bh,
Please do not rely on the dts name to decide what would be enabled or not. Please note that the DSI panel is for internal use only. Thus, the device tree would only apply to internal panel.
For public user, you should use your own driver and device tree.
If you are asking if “tegra210-jetson-cv-base-p2597-2180-a00.dts” would enable the internal dsi, the answer is yes.