koty0f has quit [Read error: Connection reset by peer]
apritzel has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
PizDOS_6-22 has quit [Ping timeout: 480 seconds]
vpeter has quit [Remote host closed the connection]
<wens>
the bit seems pokeable from the kernel
vpeter has joined #linux-sunxi
PizDOS_6-22 has joined #linux-sunxi
apritzel has joined #linux-sunxi
<apritzel>
wens, do you mean the H616 GPU "enable bit"? As an indication that it's non-secure?
<apritzel>
because unfortunately this doesn't mean too much, because on AW many secure bits are accessible from non-secure world, unless you boot with the secure fuse burnt
junari__ has joined #linux-sunxi
<apritzel>
prominent example is "secure" SRAM A2, on at least the A64, but I believe all nearby SoCs as well: It's perfectly writable from U-Boot or Linux ...
junari_ has quit [Ping timeout: 480 seconds]
bauen1 has quit [Ping timeout: 480 seconds]
hentai has quit [Read error: Connection reset by peer]
hentai has joined #linux-sunxi
bauen1 has joined #linux-sunxi
JohnDoe_71Rus has quit []
JohnDoe_71Rus has joined #linux-sunxi
JohnDoe_71Rus has quit []
bauen1_ has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
<wens>
oh right...
junari_ has joined #linux-sunxi
PizDOS_6-22 has quit [Ping timeout: 480 seconds]
junari__ has quit [Ping timeout: 480 seconds]
stipa has joined #linux-sunxi
<apritzel>
I think smaeul has at least one "secure" box for each SoC, so he might be able to test this
<apritzel>
if it's indeed non-secure: should we explore the "power-domains" DT property route? That would be a first for Allwinner, if I see correctly?
<apritzel>
or is there a simpler (and more pragmatic?) way of getting this bit flipped?
JohnDoe_71Rus has joined #linux-sunxi
PizDOS_6-22 has joined #linux-sunxi
pmp-p has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
junari_ has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
<jernej>
apritzel: I think power domain isn't the question, more like if driver will flip bit itself or it will call secure firmware function
<jernej>
it seems scmi support power domains, at least arm reference boards use it
junari_ has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
ftg has joined #linux-sunxi
<apritzel>
yeah, that would be the only way it this bit is secure, so it's probably the safer way
<apritzel>
the question is just if it's worth the effort
<apritzel>
many years back I had the idea to make every regulator a firmware controlled power domain, but that didn't go down well with the community
koty0f has quit [Read error: Connection reset by peer]
<apritzel>
because it would rely on firmware updates to fix things, plus the version dependencies between firmware and kernel, in contrast to just a kernel patch
junari_ has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
<apritzel>
so if it's really a non-secure bit, I'd lean toward the driver flipping this
<apritzel>
SCMI sounds neat, but not sure it's worth introducing this for this one bit
<jernej>
apritzel: I'm one of those people, who likes kernel only approach over firmware
<jernej>
however, if bit can be secured, firmware approach sounds safer
bauen1_ has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
<apritzel>
jernej: what's the address of this bit, anyway? Is it in the PRCM range?