<MoeIcenowy>
I can communicate with Allwinner via Pine64
<corecode>
sad, that would be good inside knowledge
<corecode>
i need to figure out how to buy allwinner chips in medium (100s) quantity
<MoeIcenowy>
aliexpress?
<MoeIcenowy>
if there is any
<corecode>
hehe yea, always a bit sketchy :/
<KotCzarny>
counterfeit allwinner chips?
<KotCzarny>
that would be quite low
<corecode>
i wonder whether i can use the FM audio input on the f1c200s as ADC
<corecode>
with good tolerances
<mru>
define good
<corecode>
1%, and stable across reboots (so that i can store calibration)
tnovotny has joined #linux-sunxi
suprothunderbolt has quit [Ping timeout: 258 seconds]
<mru>
what do you want to use it for?
<corecode>
measuring target voltage for information
<corecode>
DC voltage
<mru>
and what range is that voltage?
<corecode>
between 0V and, say 5V nominal
<mru>
what resolution do you need?
<corecode>
i think 10mV would be good enough
yann has joined #linux-sunxi
<mru>
you're probably better off using the touchscreen adc
<corecode>
why do you think?
<mru>
better suited to the type of measurement, easier to use
<corecode>
i'm thinking about using the touchscreen maybe later...
<corecode>
do you mean the keyadc?
<mru>
no
<corecode>
ok
<mru>
but I suppose you could use that too if it's good enough
<mru>
it's only 6-bit
<corecode>
what do you think will be the biggest issue with using the codec adc?
<mru>
it's a sigma-delta adc that needs to run continuously at a rather high rate
<mru>
not good for one-off sampling
<corecode>
can you explain a bit more?
<mru>
and it may well have a dc-blocking filter
<corecode>
yea at least on the h2+ (orange pi zero) the mic input does not seem to have a dc block
<corecode>
at least 0.1Hz was clearly visible
<mru>
what are you actually trying to do?
<corecode>
just sensing a remote IO voltage, to report
<mru>
how frequently?
<corecode>
like "target is at 3.01V" or "target is at 0.04V" (aka "not turned on")
<corecode>
1Hz maybe? maybe only when queried
<mru>
the tsadc is better for that
<corecode>
yea i guess so
<corecode>
but of course then i can't use a touch screen
<mru>
do you really want to use a resistive touchscreen anyway?
<corecode>
the cheap ones seem to use resistive touch
<mru>
yeah, but they suck
<mru>
now I have no idea what type of device you're building
<corecode>
yea i don't have a very good idea yet either :)
<mru>
display assemblies with capacitive touchscreen usually include an i2c-connected controller
<corecode>
yea i was surprised that the small cheap ones from buydisplay come with resistive touch
<mru>
if you want to reserve the tsadc, I think you'll be better off with an external adc for this
<mru>
lots of choices there
_whitelogger has joined #linux-sunxi
<corecode>
yea, i figured i could use a PAM1710
<mru>
typo? such a part number doesn't seem to exist
<karlp>
PAM parts are normally dacs and amps arnet they?
<corecode>
this one isn't
<karlp>
well, I'm with mru, part number doesn't exist :)
<corecode>
oh, pac1710
<karlp>
that'a s current monitor?
<mru>
looks like it is
<karlp>
I mean, if that's what you want, sure, but you were asking about voltage measurements earlier :)
<karlp>
kinda pricey too.
<corecode>
it has voltage measurement as well
<mru>
microchip MCP3021 family looks reasonable at a glance
<karlp>
one ofthe cheapest discretes at least. though at that price, you could drop a small micro with built in adc for "just" the cost of fw development :)
<mru>
and host side driver
<corecode>
yea
<corecode>
well, using the codec adc would be very simple
<mru>
not really
<mru>
it's a poor choice for your application
<corecode>
why?
<mru>
many reasons
<mru>
it's all entangled with the audio mixeer
<mru>
it's a sigma-delta adc with 8 kHz minimum output rate
<mru>
god knows what the reference voltage is
<MoeIcenowy>
corecode: btw I think F1C200s has GPADC
<MoeIcenowy>
available as muxed with resistive touch
RichardG867 has quit [Quit: Keyboard not found, press F1 to continue]
RichardG867 has joined #linux-sunxi
lkcl has joined #linux-sunxi
Guest73 has quit [Remote host closed the connection]
lkcl has quit [Read error: Connection reset by peer]
gsz has quit [Ping timeout: 258 seconds]
reinforce has quit [Quit: Leaving.]
tuxillo has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-sunxi
lkcl has quit [Read error: Connection reset by peer]
tuxd3v has quit [Ping timeout: 265 seconds]
ldevulder_ has quit [Remote host closed the connection]
ldevulder_ has joined #linux-sunxi
lkcl has joined #linux-sunxi
pmp-p has quit [Disconnected by services]
pmp-p has joined #linux-sunxi
ldevulder_ has quit [Remote host closed the connection]
ldevulder_ has joined #linux-sunxi
florian has joined #linux-sunxi
NeuroScr has joined #linux-sunxi
ldevulder_ has quit [Remote host closed the connection]
ldevulder_ has joined #linux-sunxi
ldevulder_ has quit [Remote host closed the connection]
ldevulder_ has joined #linux-sunxi
aloo_shu has joined #linux-sunxi
dev1990 has quit [Quit: Konversation terminated!]
kedder has quit [Quit: WeeChat 2.6]
<MoeIcenowy>
megi: applying OOB interrupt seems to make POWER_SAVING work
<megi>
MoeIcenowy: is it stable though?
<megi>
over say 10s of minutes
<MoeIcenowy>
associated with the same AP for 10+ minutes?
<MoeIcenowy>
I associated for a whole night just now
<megi>
the issue I had was when I was having a ssh session to the PP, it worked for a while, and then when idle for a while, it started having serious lag, like 10s of seconds
<megi>
and then the connection was lost completely, and not even ping worked after half an hour or so
<MoeIcenowy>
I seems to met this situation, but I doubt it's because of bad signal
<MoeIcenowy>
current PinePhone WiFi antennas are not well tweaked
<megi>
it was not signal for me
<megi>
I tested in a stable condition
<megi>
disabling PM fixed it
<megi>
I'll try your patches :)
<megi>
I know dev phone has not great antena for WiFi, I can't even go to the middle of the room without losing the signal :)
lurchi_ is now known as lurchi__
dev1990 has joined #linux-sunxi
florian has quit [Ping timeout: 260 seconds]
tuxd3v has joined #linux-sunxi
lkcl has quit [Ping timeout: 255 seconds]
<MoeIcenowy>
megi: I had a ssh connection idle 10min just now
<MoeIcenowy>
and after 10min it reacts in 1s
<megi>
sounds great :)
<MoeIcenowy>
megi: BTW do you know how to debug USB autosuspend?
<MoeIcenowy>
I want to lower the power of modem too
<megi>
MoeIcenowy: join #pinedev
<megi>
it was discussed there today
<MoeIcenowy>
megi: at pine server or freenode server?
<megi>
yes, join #pinedev on freenode
<megi>
I don't think there's a public log, I'll upload mine for you
<MoeIcenowy>
megi: There's log on other servers
<MoeIcenowy>
e.g. Telegram
<megi>
I don't think telegram is bridged to #pinedev
lurchi__ is now known as lurchi_
tuxillo has joined #linux-sunxi
<MoeIcenowy>
it's bridged
<megi>
ok then
<MoeIcenowy>
I saw the discuss, but I think it's about suspend, not autosuspend
<MoeIcenowy>
autosuspend is a part of runtime PM
<MoeIcenowy>
which is have the modem to sleep without sleeping the system
<megi>
is it supposed to work?
LargePrime has quit [Ping timeout: 258 seconds]
<megi>
I thought you can only send it to sleep via AT commands or gpio
<tuxd3v>
MoeIcenowy, what is the device? :)
<megi>
anyway, autosuspend just works, as long as the other device supports it, in my experience