Nilesh_ has joined #imx6-dev
cnxsoft has joined #imx6-dev
dv_ has quit [Ping timeout: 240 seconds]
dv_ has joined #imx6-dev
eduardas_m has joined #imx6-dev
lrusak has quit [Ping timeout: 248 seconds]
lrusak has joined #imx6-dev
lrusak has quit [Changing host]
lrusak has joined #imx6-dev
antony has quit [Quit: Leaving.]
diego_r has quit [Ping timeout: 264 seconds]
diego_r has joined #imx6-dev
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft1 has joined #imx6-dev
cnxsoft1 is now known as cnxsoft
Nilesh_ has quit [Quit: Connection closed for inactivity]
<
yates>
can someone please explain to me what a "keeper" means?
<
vpeter>
Maybe "The keeper keeps the output level the same even if you turn the driver off."
<
yates>
vpeter: thanks, i guess that's all there is to it. the reference manual has a bunch of other stuff that is confusing.
<
yates>
on our variscite DART 6UL (IMX6ULL) SoM based board running their version of linux (from Yocto), ...
<
yates>
i have noticed that there are certain gpios in which i cannot set the
<
yates>
via the /sys/class/gpio/gpioXYZ.
<
yates>
i CAN configure the pin as output, but this particular one stubbornly remains 0 after i echo 1 > value
<
yates>
it remains zero at the physical pad, and it also reads back 0 when a cat value
<
yates>
s/when a/when i/
<
yates>
has any experienced this and know a fix?
cnxsoft has quit [Quit: cnxsoft]
ncgs has quit [Quit: Ex-Chat]
antony has joined #imx6-dev
caiortp has quit [Quit: Ex-Chat]
eduardas_m has quit [Quit: Konversation terminated!]
diego_r has quit [Ping timeout: 240 seconds]
yates has quit [Remote host closed the connection]