ChanServ changed the topic of #linux-sunxi to: Allwinner/sunxi development - Did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait for an answer! - This channel is logged at https://oftc.irclog.whitequark.org/linux-sunxi
ftg^ has quit [Read error: Connection reset by peer]
apritzel has quit [Ping timeout: 480 seconds]
evgeny_boger1 has quit [Remote host closed the connection]
jernej has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
jernej has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
Danct12 is now known as Guest3440
Danct12 has joined #linux-sunxi
Danct12 has quit []
koty0f has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
kilobyte1 has quit [Ping timeout: 480 seconds]
kilobyte1 has joined #linux-sunxi
apritzel has joined #linux-sunxi
digetx has quit [Ping timeout: 480 seconds]
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
freemangordon has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
<DasChaos> Hey, i have a more general question? How does rebooting work in a allwinner CPU? Do I need to set a special register or is it working via Watchdog?
koty0f has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
JosephWatson[m] has quit []
Newbyte has quit [Quit: Bridge terminating on SIGTERM]
MattTrescott[m] has quit []
mripard has quit [Quit: Bridge terminating on SIGTERM]
ungeskriptet[m] has quit []
exkc has quit []
exkcmoeAdmin[m] has quit []
aerospace[m] has quit []
sajattack[m] has quit [Quit: Bridge terminating on SIGTERM]
oliv3r[m] has quit []
aperezdc has quit [Quit: Bridge terminating on SIGTERM]
vulpes2[m] has quit [Quit: Bridge terminating on SIGTERM]
obbardc has quit []
Tooniis[m] has quit []
pgwipeout[m] has quit []
DasChaos has quit [Quit: Bridge terminating on SIGTERM]
cperon has quit []
KAmlogicAllwinnerRockchipMedia has quit [Write error: connection closed]
movedon5b2z4xywybidzannet[m] has quit [Write error: connection closed]
insep has quit [Write error: connection closed]
JuniorJPDJ has quit []
dittid[m] has quit [Write error: connection closed]
chuang[m] has quit []
error2[m] has quit []
szemzoa has quit [Ping timeout: 480 seconds]
szemzoa has joined #linux-sunxi
apritzel has joined #linux-sunxi
<apritzel> DasChaos: yes, it's via the watchdog. Program it to the shortest period, disable interrupts and wait (WFI)
evgeny_boger has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
evgeny_boger has quit [Quit: evgeny_boger]
evgeny_boger has joined #linux-sunxi
bauen1 has joined #linux-sunxi
DanielakaCyReVolt[m] has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
DasChaos has joined #linux-sunxi
DasChaos is now known as Guest3475
szemzoa has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
Guest3475 has quit []
DasChaos1 has joined #linux-sunxi
DasChaos1 has quit []
DasChaos1 has joined #linux-sunxi
karlp has quit [Quit: WeeChat 3.5]
DasChaos1 has quit []
karlp has joined #linux-sunxi
DasChaos1 has joined #linux-sunxi
ndufresne9 has joined #linux-sunxi
DasChaos1 has left #linux-sunxi [#linux-sunxi]
sunshavi has joined #linux-sunxi
DasChaos1 has joined #linux-sunxi
DasChaos1 has quit []
szemzoa has quit []
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
digetx has joined #linux-sunxi
Guest3481 has joined #linux-sunxi
pg12 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit []
freemangordon has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
evgeny_boger has quit [Quit: evgeny_boger]
daschaos has joined #linux-sunxi
<daschaos> This is a test from a new client because matrix bridge is terrible 😄
<daschaos> It seems to work, now my answer can also be send
<gamiee> welcome chaos
pg12 has joined #linux-sunxi
<daschaos> apritzel: thanks for the linked snipped is it basically the same for the kernel? I know it will do more for cleanup, but does it also trigger watchdog in the end?
Guest3481 has quit []
ftg has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 480 seconds]
evgeny_boger has joined #linux-sunxi
evgeny_boger has quit []
JohnDoe_71Rus has joined #linux-sunxi
mkazantsev has joined #linux-sunxi
<mkazantsev> Hey, did anyone try making 8080 parallel interface work in D1/T113 Display Engine?
<mkazantsev> Like sending commands to the panel using LCD_CPU_IF_REG's DA and CA bits
<mkazantsev> My Data/Command line is switching as it should but WR and RD lines are always high
<mkazantsev> Manual says "When CPU I/F is in IDLE state, it can generate WR/RD timing by setting “Lcd_CPUI/F”. The CS strobe is one DCLK
<mkazantsev> width, and the WR/RD strobe is half DCLK width.". What does this even mean
pg12_ has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
vagrantc has joined #linux-sunxi
pg12 has quit [Ping timeout: 480 seconds]
<apritzel> daschaos: yes, for 32-bit parts we also use the watchdog, AFAIK that's the only way to reset the system. You can reset individual cores, separately, but that doesn't really help for a system reset
<apritzel> for 64-bit parts the kernel uses a PSCI call, which TF-A then translates into the same watchdog programming
<apritzel> actually if you boot with UEFI, the UEFI system reset is used, which brings that back on U-Boot's table
<daschaos> Is uefi aarch64 only?
apritzel has quit [Ping timeout: 480 seconds]
evgeny_boger has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
bigunclemax has joined #linux-sunxi
<bigunclemax> Hi, can anyone help me clarify the thermal sensor calibration process for T113/D1 SoCs?
<bigunclemax> User manual says that read the value from eFuse and write it to the THS_CDATA register
<bigunclemax> But the BSP driver from TinaLinux does some calculations with this value and only after that writes it to THS_CDATA
apritzel has joined #linux-sunxi
<bigunclemax> For example, I get 50C in the first case and 26C in the second. At the same time uncalibrated measurement is 38C.
JohnDoe_71Rus has quit []
<apritzel> bigunclemax: if in doubt, I'd follow the BSP code, not the manual
Daanct12 has joined #linux-sunxi
Guest3440 has quit [Ping timeout: 480 seconds]
evgeny_boger1 has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
<bigunclemax> apritzel: yes, I think the same. However, when measured the SoCs temperature with a thermal imager, I got a value of about 7-8C more than from a calibrated internal sensor. It seems a little bit strange to me :)
ftg has quit [Read error: Connection reset by peer]
freemangordon has quit [Ping timeout: 480 seconds]
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #linux-sunxi
mkazantsev has quit [Remote host closed the connection]