<apritzel>
smaeul: do you know what's the story with "enable-active-high;" vs. "gpio = <&pio 3 25 GPIO_ACTIVE_HIGH>;", in a "regulator-fixed" DT node?
<apritzel>
do I need both, or must not have both, or is one version deprecated? Or is the latter only available with some GPIO controller bindings (ours being one of them)?
<apritzel>
the regulator-fixed binding mentions the explicit property
sunshavi_ has quit [Remote host closed the connection]
sunshavi_ has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
<smaeul>
apritzel: you want both enable-active-high and GPIO_ACTIVE_HIGH if a positive voltage turns on the regulator
vagrantc has quit [Quit: leaving]
sunshavi_ has quit [Ping timeout: 480 seconds]
sunshavi_ has joined #linux-sunxi
<smaeul>
it is like the MMC CD and SPI CS bindings where the default interpretation is "low == active", and you can invert that both with a property (cd-inverted/spi-cs-high) and GPIO_ACTIVE_LOW
<smaeul>
that is, the property and the GPIO flag XOR each other
Danct12 has quit [Ping timeout: 480 seconds]
DarkNeutrino has quit [Quit: Page closed]
DarkNeutrino has joined #linux-sunxi
sunshavi_ has quit [Remote host closed the connection]
sunshavi_ has joined #linux-sunxi
Danct12 has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
sunshavi_ has quit [Remote host closed the connection]
sunshavi_ has joined #linux-sunxi
sunshavi_ has quit [Read error: Connection reset by peer]
sunshavi_ has joined #linux-sunxi
Danct12 has quit [Ping timeout: 480 seconds]
Danct12 has joined #linux-sunxi
sunshavi_ has quit [Read error: Connection reset by peer]
sunshavi_ has joined #linux-sunxi
sunshavi_ has quit [Remote host closed the connection]
sunshavi_ has joined #linux-sunxi
Danct12 has quit [Quit: Leaving]
junari__ has joined #linux-sunxi
arti has quit [Ping timeout: 480 seconds]
junari_ has joined #linux-sunxi
arti has joined #linux-sunxi
junari__ has quit [Ping timeout: 480 seconds]
stipa is now known as Guest1807
stipa has joined #linux-sunxi
Guest1807 has quit [Ping timeout: 480 seconds]
sh1 has joined #linux-sunxi
DarkNeutrino has quit [Read error: Connection reset by peer]
DarkNeutrino has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
junari_ has quit []
codekipper has joined #linux-sunxi
apritzel has joined #linux-sunxi
diego71_ has joined #linux-sunxi
diego71 has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
bauen1 has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
apritzel has joined #linux-sunxi
DarkNeutrino has quit [Ping timeout: 480 seconds]
DarkNeutrino has joined #linux-sunxi
paulk has joined #linux-sunxi
paulk-ter has quit [Read error: Connection reset by peer]
bauen1 has quit [Ping timeout: 480 seconds]
paulk has quit [Quit: WeeChat 3.0]
paulk has joined #linux-sunxi
paulk has quit []
paulk has joined #linux-sunxi
DarkNeutrino has quit [Read error: Connection reset by peer]
DarkNeutrino has joined #linux-sunxi
hlauer has joined #linux-sunxi
DarkNeutrino has quit [Read error: Connection reset by peer]
hlauer has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
apritzel_ has joined #linux-sunxi
apritzel_ has quit [Ping timeout: 480 seconds]
sunshavi_ has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit []
gamiee has joined #linux-sunxi
grming has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
<apritzel>
DasChaos: I guess nobody knows anything for certain (same with the A523), but Yuzuki is typically close to the source. And the V851/V853 also seems to ship with both RISC-V and ARM cores activated.
<apritzel>
smaeul: thanks, though I am still confused: "XOR" hints at that specifying both the property and the GPIO flag would cancel each other out? So that's then active_low again? I need to test this tonight ...
codekipper has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
<gamiee>
from what I've seen, Yuzuki is employee of company, which is sub-company of Allwinner