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
jnn has joined #linux-sunxi
jn has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
Kirby64 has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
flyback has quit [Ping timeout: 480 seconds]
flyback has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
aggi has quit [Remote host closed the connection]
aggi has joined #linux-sunxi
bauen1 has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
Kirby64 has quit [Ping timeout: 480 seconds]
smaeul has joined #linux-sunxi
smaeul_ has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
Hypfer has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
warpme has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
bauen1 has joined #linux-sunxi
apritzel has joined #linux-sunxi
sdfgsdfs has quit [Remote host closed the connection]
sdfgsdfs has joined #linux-sunxi
<dlan> apritzel: do you have any suggestion which branch I could work on in uboot? to prepare an EMAC0 patch for A523/T527.. as I think the basic A523 patch has not been accepted into mainline?
radxanaoki has quit [Quit: radxanaoki]
<apritzel> dlan: you wouldn't need any patch, would you? Beauty of DT fallbacks: it just works the moment you give it the right DT
<apritzel> so just update the DT, from Linux' sunxi/next branch
<apritzel> once sunxi/next reaches Linus' tree, it will be synced into the git rebasing repo, and I can cherry-pick it from there, into U-Boot - or we could wait until it gets pulled automatically
MoeIcenowy has quit [Quit: ZNC 1.9.1 - https://znc.in]
MoeIcenowy has joined #linux-sunxi
evgeny_boger has joined #linux-sunxi
<dlan> apritzel: oh, that's sweet! so, probably we could switch to OF_UPSTREAM in future..
<spawacz> Is it possible to overclock D1 just a tiny bit via the dtb?
<apritzel> dlan: that was the plan from the beginning: it would be OF_UPSTREAM only. I just need to wait for the DTs to actually appear in upstream, which would probably be in like 3-4 weeks from now
<apritzel> spawacz: have you tried just changing the frequency in opp_table_cpu, in arch/riscv/boot/dts/allwinner/sun20i-d1s.dtsi?
chewitt has joined #linux-sunxi
tvc has quit [Quit: tvc]
tvc has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit []
warpme has joined #linux-sunxi
warpme has quit []
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Read error: Connection reset by peer]
luka177 has joined #linux-sunxi
<luka177> Hello, ive made a custom board arounf allwinner t113-s4 with ADV7513 rgb to hdmi bridge, i booted linux on it with no issues, and bridge do work, BUT there is an issue, after tcon driver is probbed one of signal (specifically d21 on PD15) is stuck high, resulting in a slight red tint. Anything obvious i might be missing? Pin is clearly used by tcon ```pin 111 (PD15): device 5461000.lcd-controller function lcd0 group PD15```
cnxsoft1 has quit [Ping timeout: 480 seconds]
luka177 has quit [Remote host closed the connection]
luka177 has joined #linux-sunxi
colinsane has quit []
<apritzel> luka177: maybe it's the internal pull-up accidentally configured for that pin?
colinsane has joined #linux-sunxi
<luka177> apritzel: ```
<luka177> ```lcd0_rgb888_pins: lcd0-rgb888 { pins = "PB2", "PB3", "PD0", "PD1", "PD2", "PD3", "PD4", "PD5", "PB4", "PB5", "PD6", "PD7", "PD8", "PD9", "PD10", "PD11", "PB6", "PB7", "PD12", "PD13", "PD14", "PD15", "PD16", "PD17", "PD21", "PD20", "PD18", "PD19"; function = "lcd0"; bias-pull-down; drive-strength = <10>; };``` ive tried enabling even pull down, with no effect
<apritzel> Linux wouldn't change that setting, unless explicitly told so. You can force that off with "bias-disable;" in the pinctrl DT node
dsimic is now known as Guest15486
dsimic has joined #linux-sunxi
Guest15486 has quit [Ping timeout: 480 seconds]
<luka177> apritzel: Just tried bias-disable, no result either, also it takes +/- what is specified in drive-strength to sink it (tested with 40ma and 10ma) so i'd assume its not a pupd
<apritzel> luka177: that's all with non-upstream drivers, right? As on a quick glance I don't see any display support in mainline ...
<luka177> apritzel: That is with upstream kernel with no edits beside DT
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
<spawacz> apritzel: it worked \o/
<apritzel> ah, scratch that, was looking at the wrong DT
<spawacz> I set it to 1.2 GHz. How far can I push it further?
<luka177> also here is my dt: https://bpa.st/BTBA
<apritzel> luka177: have you tried it with the existing rgb666 pins?
colinsane has quit [Ping timeout: 480 seconds]
<luka177> apritzel: i just did, its the same
Kirby64 has joined #linux-sunxi
<luka177> PD15 is still at 3v3 resulting in red tint
diego71_ has joined #linux-sunxi
diego71 has quit [Ping timeout: 480 seconds]
<apritzel> I dimly remember people reporting that sometimes tints are a software/driver issue? Not sure how well tested the display is on this SoC
<luka177> apritzel: Wekk it is very likely to be software issue but i am not sure what can be the culprit
<apritzel> just to make sure: I meant a display pipeline issue, not a pinctrl issue. But I have no clue about the internals, I guess jernej might know more here
ftg has joined #linux-sunxi
evgeny_boger has quit [Quit: evgeny_boger]
hentai has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
Kirby64 has quit [Ping timeout: 480 seconds]
<spawacz> I'd like o be able to read temperatures, how can I find out what kernel module is missing to populate /sys/class/thermal on D1? Debian's stock kernel has very little options enabled on riscv.
<spawacz> It is CONFIG_SUN8I_THERMAL, correct?
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Quasar 5.2.6, revision: 5.2.6+git-7614-6f23368f1, build type: debug, sources date: 20160102, built on: 2025-03-30 13:34:35 UTC 5.2.6+git-7614-]
macromorgan has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
macromorgan has joined #linux-sunxi
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
Kirby64 has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
luka177 has quit [Remote host closed the connection]
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
luka177 has joined #linux-sunxi
<luka177> Ok so i did try to set invert in SUN4I_TCON0_IO_POL_REG and now its stuck at 0v so i doubt its a hardware issue, but a software iss that leads specifically to D21 not working sounds strange
Kirby64 has quit [Ping timeout: 480 seconds]
<luka177> I followed https://groups.google.com/g/linux-sunxi/c/HxDBpY5HbbQ/m/mX2O2OYlCwAJ?pli=1 and indeed disabling mixer1 helped, but question is, what is the underlying issue
apritzel has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
<apritzel> spawacz: in general you do: "git grep allwinner,sun20i-d1-ths drivers/" to find the driver, then search for the driver filename in the Makefile in that same directory to find the Kconfig symbol
<apritzel> spawacz: interestingly there is the binding and driver support in mainline, but for some reason the DT node is missing
luka177 has quit [Quit: Page closed]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
Kirby64 has joined #linux-sunxi
<apritzel> ah, I see, there were actually two patches posted end of February, but there were comments, and the v2 that was advertised was never sent
warpme has joined #linux-sunxi