<apritzel>
so does anyone have a user manual for the T527, specifically? There is just a data sheet, which helps with the pins, but doesn't mention any clocks :-(
<apritzel>
I got most from some BSP files (ccu-sun55iw3.c on Github), but those seem unreliable, and there are definitely mistakes in there
<apritzel>
anyway, I got compiling clock drivers (for normal and PRCM) now, but will leave the testing for tomorrow ...
apritzel has quit [Ping timeout: 480 seconds]
<dsimic>
FWIW, I tried to find the T527 user manual, which yielded nothing
<MoeIcenowy>
T527 should be (at least mostly) the same with A523
<MoeIcenowy>
although I think A523 only claims one Ethernet MAC
iscle has joined #linux-sunxi
<iscle>
So, any of you know how reboot works in sunxi platforms? I'm trying out the port for V853 and for some reason "reboot" won't work, it gets stuck at "[ 11.685719] Reboot failed -- System halted"
<iscle>
I've checked other devices (such as D1 which is what I'm basing it on) and can't see any references to "reset" or "reboot"
<dsimic>
iscle: have a look how devm_register_sys_off_handler() is used in drivers/mfd/axp20x.c
<dsimic>
s/a look/a look at/
<dsimic>
oh, wait, you asked about restarting
<iscle>
Yep, exactly. I've just seen that it is normally handled by the wdt, in the "sunxi_wdt_restart" function. I'll take a deeper look as I might have not configured it correctly for the SoC (I assumed it was 1:1 with the D1, which is what everything else is based on)
iscle has quit [Remote host closed the connection]
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
zoenggit 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
JohnDoe_71Rus has quit [Read error: Connection reset by peer]
Schimsalabim has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
zoenggit has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
apritzel has quit []
apritzel has joined #linux-sunxi
<apritzel>
MoeIcenowy: yes, I was building on this "mostly the same with A523", and it's definitely helpful
<apritzel>
but it only goes so far: the second EMAC is one example, but there is more: CAN, HDMI, second LVDS, ...
<apritzel>
and for the clocks this does matter, and I'd rather have all the clocks in from the beginning
<apritzel>
I see the obvious gaps in the memory map, and can compare this to the other recent SoCs (like D1 and H616), but it would be good to have it for real
<apritzel>
for instance some clocks subtly changed in the A523 (like the already mentioned MMC clock), and I think there are others who lost a .P factor and such
<apritzel>
and for instance the second EMAC seems to be a bit special, at least in the T527 datasheet it's described separately, and there is a second reset bit in a separate BGR register
<apritzel>
so if someone saw a T527 user manual falling off a lorry, I'd be grateful to hear about it ;-)
<IlikeTech>
If I want to use one of the X-Powers PMICs (over I2C), I just need to choose one that actually can provide the appropriate voltage rails, correct? Trying to figure out what goes with the F1C100s, and it looks like the AXP192.
<IlikeTech>
though there's also the AXP199 which is maybe the same?
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
<apritzel>
IlikeTech: there is no real technical relationship between AXP models and SoCs, it seems just that AW bundles pairs of them. I guess the rails provided somehow match the requirements of a particular SoC, maybe?
<IlikeTech>
okay, that's what I figured
<IlikeTech>
looks like the 192 should work for the F1C100 as it has 3 buck rails and a few LDOs