FORUMS
Remove All Ads from XDA

Build kernel from source and boot to Ubuntu using L4T (Linux for Tegra) rootfs

392 posts
Thanks Meter: 88
 
By yahoo2016, Senior Member on 19th December 2015, 08:47 PM
Post Reply Email Thread
4th February 2018, 03:56 PM |#621  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by deerish

"tegra_powergate_init()" will hang the board when it attempts to powergate the XUSBC partition during boot -- I believe due to USB clock configuration coming out of the bootloader. Moving "tegra_powergate_init()" to subsys ensures that the clocks are properly initialized before it's called.

Ha! I see, thanks
 
 
4th February 2018, 06:39 PM |#622  
Member
Thanks Meter: 7
 
More
It's safe to use "saveenv" in U-Boot, by the way. It writes at the end of mmcblk0boot1, which is totally empty in any case.
8th February 2018, 12:26 PM |#623  
Member
Thanks Meter: 1
 
More
@deerish
Do you know what gk20a 57000000.gpu: railgate is disabled and tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000 mean?
8th February 2018, 11:16 PM |#624  
Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by chtulu

@deerish
Do you know what gk20a 57000000.gpu: railgate is disabled and tegra_soctherm 700e2000.soctherm: soctherm: trip temperature -2147483647 forced to -127000 mean?

I'm not sure where the soctherm driver picks up those values, but the message indicates clamping into the valid trip temperature range -- the unit is millicelsius. Maybe some missing nodes in the device-tree?

If the "railgate is disabled," the GPU will not enter a low-power state. I don't get that message. What does "/sys/devices/57000000.gpu/railgate_enable" say?
9th February 2018, 10:16 AM |#625  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by deerish

I'm not sure where the soctherm driver picks up those values, but the message indicates clamping into the valid trip temperature range -- the unit is millicelsius. Maybe some missing nodes in the device-tree?

If the "railgate is disabled," the GPU will not enter a low-power state. I don't get that message. What does "/sys/devices/57000000.gpu/railgate_enable" say?

Can the clamping message be safely ignored? Do you get that message?

/sys/devices/57000000.gpu/railgate_enable says: 0

Ok, seems that jetson_clocks.sh set railgate_enable to 0 therefore the message railgate is disabled

Also I noticed that the following scaling_available_frequencies are missing: 1836000 1938000 2014500 2116500 2218500 2320500
so the max set by jetson_clocks.sh is 1734000

I remember in 24.2.2 after running jetson_clocks.sh the max freq was 2000000 something
9th February 2018, 09:54 PM |#626  
Member
Thanks Meter: 7
 
More
I thought that you may be using jetson_clocks.sh. I also get those soctherm messages, not too concerned about them.

You might try editing the "cpu-scaling-data" under "cpufreq".
10th February 2018, 10:24 AM |#627  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by deerish

I thought that you may be using jetson_clocks.sh. I also get those soctherm messages, not too concerned about them.

You might try editing the "cpu-scaling-data" under "cpufreq".

Yes, but I would need the dts source code in order to do that, so if you could provide that.....
13th February 2018, 01:20 PM |#628  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by deerish

I thought that you may be using jetson_clocks.sh. I also get those soctherm messages, not too concerned about them.

You might try editing the "cpu-scaling-data" under "cpufreq".

Anyway, thanks for your great work, but I am puzzled why you changed all the TEGRA_PINCONF_PARAM_E_IO_HV to TEGRA_PINCONF_PARAM_RCV_SEL.

And how do you add frequencies for the GPU?
13th February 2018, 11:04 PM |#629  
Member
Thanks Meter: 7
 
More
That is a mistake, thanks for catching it. I didn't read the driver, so I assumed that "nvidia,io-hv" was simply an alias for "nvidia,io-high-voltage".

I don't know if GPU frequencies can be specified through the device-tree.
14th February 2018, 10:25 AM |#630  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by deerish

That is a mistake, thanks for catching it. I didn't read the driver, so I assumed that "nvidia,io-hv" was simply an alias for "nvidia,io-high-voltage".

I don't know if GPU frequencies can be specified through the device-tree.

Does not matter, I found out that, as for pinctrl-tegra.h, rcv_sel_bit and e_io_hv_bit set the same bit.

No, they can not be changed in the device-tree, I was hoping that you knew about the UCM1 and UCM2 tables for GPU.
14th February 2018, 03:06 PM |#631  
Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by chtulu

Does not matter, I found out that, as for pinctrl-tegra.h, rcv_sel_bit and e_io_hv_bit set the same bit.

No, they can not be changed in the device-tree, I was hoping that you knew about the UCM1 and UCM2 tables for GPU.

Haven't looked into it, sorry. I think you're probably already poking around in these, but if not, look at "speedo-tegra210.c" and "tegra210-dvfs.c" to get started.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes