tllim has quit [Read error: Connection reset by peer]
hitech95__ has joined #linux-sunxi
reinforce has joined #linux-sunxi
gzamboni has quit [Read error: Connection reset by peer]
Andy-D has joined #linux-sunxi
paulliu has joined #linux-sunxi
reinforce1 has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
t0dd1v has joined #linux-sunxi
vagrantc has quit [Ping timeout: 260 seconds]
marble_visions has quit [Quit: bye]
reinforce1 has quit [Quit: Leaving.]
tnovotny has quit [Ping timeout: 252 seconds]
marble_visions has joined #linux-sunxi
koty0f has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
marble_visions has quit [Quit: bye]
tnovotny has joined #linux-sunxi
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
leviathanch has joined #linux-sunxi
nuuuciano has joined #linux-sunxi
The_Loko has joined #linux-sunxi
hitech95__ has quit [Ping timeout: 276 seconds]
reinforce has joined #linux-sunxi
clemens3 has quit [Read error: Connection reset by peer]
clemens3 has joined #linux-sunxi
paulliu has quit [Remote host closed the connection]
paulliu has joined #linux-sunxi
dddddd has joined #linux-sunxi
yann has joined #linux-sunxi
s_frit has quit [Ping timeout: 240 seconds]
thehan has joined #linux-sunxi
t0dd1v has quit [Quit: Connection closed for inactivity]
thehan has quit [Read error: Connection reset by peer]
IgorPec has quit [Ping timeout: 272 seconds]
chewitt has joined #linux-sunxi
<plaes>
mripard: I have a HDMI display here that seems to lack both HPD and DDC signals
<plaes>
I'm trying to "force" it on a sun7i machine with the following cmdline options: drm.edid_firmware=HDMI-A-1:edid/640x480.bin video=HDMI-A-1:640x480@30D
<plaes>
but I run into tracebacks regarding vblank
The_Loko has quit [Remote host closed the connection]
jukivili has joined #linux-sunxi
jukivili has quit [Client Quit]
leviathan has joined #linux-sunxi
DonkeyHotei has quit [Quit: This is a /quit message.]
pmpp_ is now known as pmpp
tllim has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
clemens3 has quit [Ping timeout: 246 seconds]
wasutton3_mobile has joined #linux-sunxi
tnovotny has quit [Quit: Leaving]
mavkhimenia has joined #linux-sunxi
yann has quit [Ping timeout: 252 seconds]
Gerwin_J has quit [Ping timeout: 264 seconds]
Gerwin_J has joined #linux-sunxi
scelestic has quit [Remote host closed the connection]
<quark_>
wens: about "[PATCH v4 5/7] power: supply: add AC power supply driver for AXP813" in AXP803 datasheet 010 and 011 bit fields are marked as reserved
<quark_>
that has to be typo because most probably they have mean values 110 and 111
<quark_>
AXP818 datasheet states that reg 3AH values 100, 110 and 111 all mean 4000mA.
scelestic has joined #linux-sunxi
<quark_>
but there is also typo in table 11-9 they are talking about VBUS "VBUS current limit select when VBUS Current limited mode is enabled"
<quark_>
I was thinking should code return -EINVAL or 4A for those bitfields 110/111
mavkhimenia has quit [Remote host closed the connection]
<anarsoul|2>
embed-3d: are you around?
<quark_>
anarsoul|2: just checking pinebook schematics. commit messages needs to be bit more detailed one. I just used couple of hours to change sopine change commit messages
<anarsoul|2>
quark_: what details should be added?
<quark_>
are connected via PMOS driver to SOM VBAT pins. VBAT and AXP803 TS pins are
<quark_>
routed to baseboard 3-pin battery connector.
<anarsoul|2>
ouch
<anarsoul|2>
wens: do we really need it in commit msg?
<quark_>
pinebook seems to hava over voltage and current IC WS3205D
<anarsoul|2>
I don't think that anything in driver configuration depends on it
yann has quit [Quit: Quitte]
<anarsoul|2>
quark_: is it relevant for software?
yann has joined #linux-sunxi
vagrantc has joined #linux-sunxi
RichardG867 has quit [Ping timeout: 264 seconds]
<quark_>
good question. maybe just mention that pinebook has input power jack and internal 10000mAh battery is enough
nuuuciano has quit [Ping timeout: 246 seconds]
hitech95__ is now known as hitech95
<hitech95>
anarsoul|2, were you working on the driver for asoc? the sun8i-codec.c?
<anarsoul|2>
hitech95: yes
<anarsoul|2>
well
<anarsoul|2>
sun8i-codec.c works almost out of the box on A64, with minor change
nuuuciano has joined #linux-sunxi
<hitech95>
anarsoul|2, so your working for the A64. I was tring to add more support for all the stuff on A33. (like the TDM on AIF1) I stopped some months ago due to my low spare time. I'm not a linux developer so for me takes lot of time.
<hitech95>
anarsoul|2, Anyway. Have you planned to add some quirks or stuff like that to support multiple boards?
Putti has quit [Remote host closed the connection]
<hitech95>
anarsoul|2, I was working on volume controls and L/R channel.
<anarsoul|2>
hitech95: I'm not planning to add anything else to sun8i-codec.c, it already works fine for me
<anarsoul|2>
what's TDM btw?
RichardG867 has joined #linux-sunxi
RichardG867 has joined #linux-sunxi
RichardG867 has quit [Changing host]
<anarsoul|2>
hitech95: btw volume controls probably go into sun8i-codec-analog.c
<hitech95>
anarsoul|2, Does you have a diff for me just to chekout the changes or if the patch is somewere to view it?
<anarsoul|2>
for A64 there's a separate driver - sun50i-codec-analog.c
<anarsoul|2>
hitech95: it's already in linux-next
<anarsoul|2>
dts changes will land later
<hitech95>
TDM: time division multiplexing, The AIF1 can have up to 8 channels if I remember correctly instead of the standard 4. (2 playback and 2 record)
<anarsoul|2>
oh, OK
<hitech95>
anarsoul|2, Ok thanks, I ws talking about digital volume control, not the one on the analog side of the codec.
<anarsoul|2>
I don't have any board that supports it anyway
<anarsoul|2>
I hope you'll continue working on it :)
<anarsoul|2>
hitech95: I'm working on patches for A64 boards in my spare time as well so unfortunately extending sun8i-codec is not my priority. It works just fine for me atm for both playback and capture, so I have no need in digital volume controls
iamfrankenstein has quit [Quit: iamfrankenstein]
<hitech95>
anarsoul|2, Yea. I hope to have some free time to do that. How you manage dto work on record? I have problems on that with my A33 board.
<hitech95>
The only yhing that sometimes I should have help on coding styles and suggestions form more expert peoples!
jaganteki has quit [Ping timeout: 256 seconds]
<anarsoul|2>
hitech95: what problems you have with recording?
<hitech95>
anarsoul|2, No idea. It son't work I also tried to enable the microphone playback loop but without success.
<hitech95>
but the main problem is no record devices
<anarsoul|2>
I think capture support was introduced in 4.17 or 4.18
<anarsoul|2>
and you'll need to add necessary routes to your dts
lkcl has quit [Read error: Connection reset by peer]
<quark_>
anarsoul|2: your patch does not compile for me
<anarsoul|2>
this one compiles for sure, I just tested it
<anarsoul|2>
vagrantc: so when we'll see debian with pinebook support? :)
<quark_>
yep. but now those are not in alphabetical order. there is rule that they should be
<vagrantc>
anarsoul|2: it's looking promising
<quark_>
think only way is move that include just before those power supplies
<anarsoul|2>
quark_: I have no idea how to do that considering that #include "axp803.dtsi" is in the middle of file
<vagrantc>
anarsoul|2: debian freeze cycles start in january, and get stricter every month
<anarsoul|2>
I see
<vagrantc>
anarsoul|2: if relatively simple stuff lands in mainline linux or u-boot, i can backport it to whatever version is in debian
<vagrantc>
linu will be 4.19 (due to LTS)
<anarsoul|2>
vagrantc: audio? :)
<anarsoul|2>
only 8 patches
<anarsoul|2>
well, 9 including i2s fix
<vagrantc>
anarsoul|2: in linux-next?
<anarsoul|2>
vagrantc: driver changes yes, dts changes are not there yet
* vagrantc
is also curious about support for the pinebook 11
<anarsoul|2>
vagrantc: it only requires a change to u-boot
<anarsoul|2>
a single patch
<vagrantc>
for audio?
<anarsoul|2>
vagrantc: nah, for video
<vagrantc>
ah
<anarsoul|2>
11" pinebook has 1080p screen
<vagrantc>
any way to auto-detect, or will it require separate builds?
<vagrantc>
i get the impression the .dts changes in u-boot are being pushed to 2019.01 ?
<vagrantc>
not sure if i'll use 2018.11 or 2019.01 in debian ...
<anarsoul|2>
quark_: so axp803.dtsi must be after axp803 label which is under r_rsb node
<anarsoul|2>
quark_: so I see no way how to meet requirement to have all nodes sorted alphabetically
<quark_>
yep just noticed same thing
<vagrantc>
anarsoul|2: whatever features you can get into linux 4.20 and are reasonably backportable to 4.19 i can likely get into debian buster ... maybe linux-next if it's small enough
<vagrantc>
similar story for u-boot
<Kamilion>
now that 4.19's out, what's the scoop on the H6 support?
<quark_>
anarsoul|2: checkpatch gave me some more work to do. need to document those axp803-gpio and so on compatibles
<anarsoul|2>
quark_: do you by any chance know how power button is connected to axp803 and if it's possible to wire it to regular input device?
<quark_>
have to continue tomorrow preparing this v5 patchset
<quark_>
anarsoul|2: it is connected to pwron pin in axp803
Gerwin_J has quit [Ping timeout: 264 seconds]
Gerwin_J has joined #linux-sunxi
dev1990_ has quit [Quit: Konversation terminated!]
<quark_>
so only couple of register values can be changed how long timeouts are
dev1990 has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
Gerwin_J has joined #linux-sunxi
Gerwin_J has quit [Ping timeout: 264 seconds]
IgorPec has joined #linux-sunxi
<anarsoul|2>
quark_: are you planning to add axp803 support to axp20x-pek driver?
Mr__Anderson has quit [Remote host closed the connection]
IgorPec has quit [Ping timeout: 240 seconds]
<embed-3d>
anarsoul|2: I'm here
<anarsoul|2>
embed-3d: any plans to continue working on thermal driver for sunxi?
<embed-3d>
anarsoul|2: Yes! 70-80% of the rework are done for the next iteration. I think I will submit the next version mid-end November.
<anarsoul|2>
embed-3d: cool, thanks!
<anarsoul|2>
embed-3d: do you have a tree with your changes?
t0dd1v has joined #linux-sunxi
<wens>
anarsoul|2: they are cross board connections from the SOM to the base board. other base boards may wire them differently
<anarsoul|2>
wens: OK, do we need the same verbosity for a commit that enables ac and battery nodes for pinebook?
jstein_ has joined #linux-sunxi
jstein_ is now known as jstein
<wens>
anarsoul|2: for a fixed device, just say ACIN is connected to a DC jack (as opposed to a micro-usb), and battery is what kind, what capacity
megi has quit [Quit: WeeChat 2.2]
<wens>
anarsoul|2: describing what is on the board is important, because you have some stupid designs that wire ACIN and VBUS together
<wens>
There's even one that gets it right on the SOM, but the base board wires them together
<wens>
in these cases, OTG is either non-existent or partially unusable
<anarsoul|2>
OK
<wens>
in any case, you are providing context about the changes