<mirko>
is audio via spdif/coax supported on h6? briefly scrolling through the dts(i) files i see definitions in arch/arm/boot/dts/sunxi-h3-h5.dtsi - but but that's it
<mirko>
ah, in the megous branch there's also spdif defined for h6
akaWolf has quit [Ping timeout: 256 seconds]
gaston1980 has quit [Quit: Konversation terminated!]
sunshavi has quit [Ping timeout: 240 seconds]
_whitelogger has joined #linux-sunxi
lkcl_ has joined #linux-sunxi
lkcl has quit [Ping timeout: 240 seconds]
_whitelogger has joined #linux-sunxi
[7] has quit [Disconnected by services]
TheSeven has joined #linux-sunxi
camh has quit [Ping timeout: 260 seconds]
camh has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
abelvesa has quit [Quit: Lost terminal]
abelvesa has joined #linux-sunxi
cmeerw has joined #linux-sunxi
sunshavi has joined #linux-sunxi
AneoX has joined #linux-sunxi
netlynx has joined #linux-sunxi
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
_whitelogger has joined #linux-sunxi
<jernej>
MoeIcenowy: Do you know what happen to V3s analog codec? it seems that there is V3s specific code in the driver but nothing in DT
nashpa has quit [Ping timeout: 246 seconds]
nashpa has joined #linux-sunxi
[Emrald] is now known as [Octopus]
<mirko>
hm, anybody an idea where PH7 is located on the orangepi3? doesn't appear to be part of the exposed pin header. it's supposed to be s/pdif. or can i even map s/pdif to any arbitrary gpio?
cnxsoft has quit [Ping timeout: 256 seconds]
<jernej>
mirko: According to OPi3 schematic, SPDIF is not exposed at all
<jernej>
and no, you can't remap it to arbitrary pin
<jernej>
in fact, spdif can be only routed through PH7 on H6
<mirko>
jernej: pity, thanks
<mirko>
jernej: did you check the pin header(s) or it's not accessiable from anywhere on the pcb?
<jernej>
download OPi3 schematic and search for PH7
<jernej>
you'll see that it's not connected anywhere
<mirko>
i see - and it looks like being the only single pin not being connected to anywhere..
<mirko>
ah, well, PL6, too - shame
<mirko>
not doubting, just out of curiousity: how do you know PH7 is the only pin spdif can be routed through? is that part of the h6 datasheet?
<mirko>
ok, i can see the user manual mentioning swa_out only together with ph7
cnxsoft has joined #linux-sunxi
[Octopus] has quit [Quit: octo-accuracy.]
<jernej>
it can be confusing, spdif is referenced as One Wire Audio in datasheet
<jernej>
s/referenced/referred/
<jernej>
another good source of such information is pinctrl driver
<mirko>
figured that out by now - hence mentioning swa_out
<mirko>
ok, will take a look, thanks
<mirko>
but re SWA - what actually confusing me: it's described as One Wire Audio (as you said) - however it actually has 3 lines (OUT, IN, CLK) - how is that one-wire?
<mirko>
i mean, i know spdif is, but swa only mentions being spdif compatible (via swa_out) - still having 3 wires..
<jernej>
I don't know enough about this peripheral to answer that
<jernej>
maybe it's similar to I2S controller which actually supports I2S, PCM and TDM modes
<jernej>
e.g. similar enough to be supported with one peripheral
<mirko>
i see..
<mirko>
interesting, the term OWA seems to be used (created?) by allwinner only
jbrown has joined #linux-sunxi
qschulz has quit [Read error: Connection reset by peer]
TheSeven has quit [Remote host closed the connection]
TheSeven has joined #linux-sunxi
pmp-p has quit [Ping timeout: 256 seconds]
pmp-p has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
\\Mr_C\\ has joined #linux-sunxi
jbrown has quit [Ping timeout: 272 seconds]
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Read error: Connection reset by peer]
jbrown has joined #linux-sunxi
pgreco has quit [Ping timeout: 265 seconds]
<mirko>
mru: was thinking the same (trademark), however i never heard of s/pdif having a(n optional) clock line - so i figured that's owa specific
<mru>
s/pdif is just the one signal
<mru>
that's the point
<mirko>
ok, but then i'm even more curious about what's the clk line in OWA is supposed to do
<mru>
what clk line?
<mirko>
mru: OWA - according to Allwinner datasheets - consists of 3 wires: OWA_OUT, OWA_IN and OWA_CLK
<mirko>
OWA_OUT is s/pdif (compatible) obviously
<mru>
oh, that's probably just an input for an external clock reference
<mru>
not part of the interface
AneoX has quit [Read error: Connection reset by peer]
<mirko>
hm - not sure how that would/could work when owa_out already has everything on its line (incl. clk/sync), but it's described as "One Wire Audio Master Clock".. *shrug*
AneoX has joined #linux-sunxi
<mru>
oh wait, it's just an ancillary output
<mru>
if I'm reading between the lines correctly
<mirko>
datasheet says it's an output indeed
<mru>
there's an "mclk output enable" control bit
<mru>
it's probably intended for synchronising other circuitry
<mru>
you might use it to clock an adc, for instance
<mru>
whatever you connect the spdif signal to obviously doesn't need it
<mirko>
was wondering about that :) - anyway, i was just curious.
<mirko>
there's even a "MCLK Clock Divide Ratio"
cnxsoft1 has quit [Quit: cnxsoft1]
AneoX_ has joined #linux-sunxi
AneoX has quit [Ping timeout: 264 seconds]
AneoX_ has quit [Read error: Connection reset by peer]
AneoX has joined #linux-sunxi
pgreco has joined #linux-sunxi
AneoX has quit [Ping timeout: 256 seconds]
AneoX has joined #linux-sunxi
[Smarties] has joined #linux-sunxi
AneoX_ has joined #linux-sunxi
AneoX has quit [Ping timeout: 256 seconds]
Ixnus has joined #linux-sunxi
<Ixnus>
jernej: do you have v3s board - which one?
<jernej>
Ixnus: I don't have any v3s, I'm just looking into R40 analog codec and I noticed that V3s analog codec is most similar
<Ixnus>
Do you have BPI-M2 Berry or BPI-M2 Ultra ?
<wens>
karlp: did you assign the MCLK (macro is CCU_CSI0_MCLK or something) output as the ov5640's xclk ? also muxed the MCLK pin?
Ixnus has quit [Remote host closed the connection]
<Ashleee>
btw the Tanix that I accidentaly shorted is fixed. Only after repairing the trace I found out it was straight from the power barrel jack so I could have used much larger pads to solder to :)
<wens>
if you set everything on by hand (pinmux, clk, gpios), can you at least see it using i2c-detect?
psydread has left #linux-sunxi [#linux-sunxi]
<karlp>
no. but I'ðve heard conflicting reports on whether i2cddetect sees it anyway
<karlp>
I don't know how to seup the clock by hand anyway, but I'd be more than happy to try
<karlp>
I get some results from i23cdetect, but nothign at 0x3c where it should be, and manually trying i2cset 2 0x3c 0x03 0x0a, and i2cget 2 doesn't give me anything either, which is theoretically attempting to read the id register
<karlp>
I could manually set the gpios to get the regualtors working, that's ok.
<karlp>
I can maybe try manually doing the enable/standby pins too, but I'm concerned abotu the clock, a few reports say you won't get any response until it's clocked.
jbrown has joined #linux-sunxi
<wens>
karlp: poke the pio and ccu registers by hand using devmem to mux and enable the mclk
<wens>
correct, it won't respond until it's clocked
<karlp>
got a link to the register map for that?
<karlp>
ok, think I found them in the h3 data sheet rev 1.2 from sunxi
<karlp>
csi is at right, devmem says csi_clock register is all zero
<karlp>
devmem2 readback after writing fails though, which is not convincing
<karlp>
nope, reading the wrong offsets.
<karlp>
ahha, ccu wasn't enabled for csi mclkc out
<karlp>
hrm, modprobe clears it agian though
pgreco has joined #linux-sunxi
<karlp>
so that's the ccu-> csi clokc register at 0x1c20134, just bit 15 shoudl eb enough, ov56450 can take 6--27Mhz,
<karlp>
PE Configure Register 0 already has 0x2 for "CSI" correctly though, so I guess that bits ok.
gaston1980 has joined #linux-sunxi
<karlp>
so, yes, CCU CSI mclkc gate is not correct, but i2cdetect still fails after that, (gives rotating mixed replies) and modprobe ov5640 after manually setting it clears CCU again, and still fails to read the i2c chjip id
<karlp>
csi-mclk-pin on PE1 appears to be correctly muxed to CSI though
<karlp>
I unfortunately have to go soon though but will read any scrollback. any more tips very much appreciated
[Smarties] is now known as [NutShell]
jstein has joined #linux-sunxi
<wens>
the ov5640 driver seems to disable the clock if it the camera is not active, or if the probe failed
<wens>
rotating mixed replies sounds fishy though. are you probing the correct bus?
<wens>
also, since you are not getting anywhere, might be worth checking the connector and cable?