<liquidAcid>
obbrobbrio, no, how am i supposed to know what thos fds are?
<obbrobbrio>
liquidAcid: sorry, i have little/no experience in debugging stuffs... but i don't want to waste your time
liquidAcid has quit [Quit: Leaving]
prahal has quit [Read error: Connection reset by peer]
prahal has joined #linux-exynos
<prahal>
obbrobbrio: are you stracing Xorg ?
<prahal>
nvm
<prahal>
too late I read SIGALARM when it is SIGCHLD :)
prahal has quit [Quit: prahal]
prahal has joined #linux-exynos
amitk has joined #linux-exynos
prahal has quit [Ping timeout: 255 seconds]
gautam__ has joined #linux-exynos
mkatic has quit [Ping timeout: 252 seconds]
mkatic has joined #linux-exynos
gladiac has quit [Remote host closed the connection]
gladiac has joined #linux-exynos
zombah has joined #linux-exynos
opuk has quit [Remote host closed the connection]
ssvb has quit [Ping timeout: 245 seconds]
opuk has joined #linux-exynos
ssk has joined #linux-exynos
<ssk>
i am using kernel 3.19 mainline croos compiled for exynos5420,every thing is compiled properly and connected hdmi,but it not displaying any thing,on minicom its 0k.And changed Documents/EDID and firmware
<javier__>
ssk:on which board is that?
<ssk>
arndale octa-5420
<ssk>
javier__;arndale octa-5420
<ssk>
javier__:arndale-octa-5420
<javier__>
ssk: I mentioned before that HDMI support for exynos5420-arndale-octa.dts seems to be missing
<javier__>
ssk: there isn't an HDMI dev node in the DTS
opuk has quit [Changing host]
opuk has joined #linux-exynos
<ssk>
javier__:could you tell where i have to change the code according to that.And how much work for that.
<javier__>
ssk: you have to change arch/arm/boot/dts/exynos5420-arndale-octa.dts and should be easy if you are familiar with the board
<javier__>
you can probably look at the donwstream tree for the needed information or the board schematic if you have access to
<ssk>
javier__:And according to that i have add a node in DTS also.
<javier__>
ssk: yes, HDMI is working correctly in other exynos5420 boards so is just a matter of describe the board specific information for your board
<ssk>
javier__:i am asking some silly questions on DTS.i am new to DTS support,that why if there is any thing wrong please sorry for that.
<javier__>
ssk: no worries
<ssk>
javier__:thanks,i am looking for adding adding nodes in dts and /exynos5420-arndale-octa.dts.with refence to previous exynos4 .
<javier__>
cool
<ssk>
javier__:but where i have to get hdmi @ () and reg= ;where can i get those address ex:-(hdmi@14530000 { compatible = "samsung,exynos4212-hdmi"; reg = <0x14530000 0x70000>;)
<javier__>
ssk: you don't have to define that at a board level since are already defined in the .dtsi because the HDMI is an IP of the SoC
<Wizzup>
IP = internal property here?
<javier__>
ssk: I know that exynos5420-smdk5420.dts refers in that way but that is the old way and now you should use the node labels
<javier__>
Wizzup: yes
<javier__>
ssk: look how the exynos5420-peach-pit.dts does as a better example
<ssk>
javier__:means i can get those details in TRM document.
<javier__>
ssk: no, what you can get from the TRM is already defined at the SoC level (exynos5420.dtsi) you now need to define the hw details at the board level (exynos5420-arndale-octa.dts)
<javier__>
that is what is missing
<ssk>
javier__: then i have to stop this work here itself.because i didn't have any schematic for board and datasheet for board.
<javier__>
ssk: if you have a working tree then you can probably figure it out from the board file or DTS used there
<javier__>
even if the DT bindings are different, it should describe the same hw information
<javier__>
but yeah, is harder if you don't have the board schematics
ssk has quit [Remote host closed the connection]
ssvb has joined #linux-exynos
prahal has joined #linux-exynos
prahal has left #linux-exynos [#linux-exynos]
opuk has quit [Ping timeout: 240 seconds]
opuk has joined #linux-exynos
opuk has quit [Ping timeout: 240 seconds]
opuk has joined #linux-exynos
opuk has quit [Changing host]
opuk has joined #linux-exynos
gautam__ has quit [Quit: Leaving]
opuk has quit [Ping timeout: 250 seconds]
opuk has joined #linux-exynos
opuk has quit [Changing host]
opuk has joined #linux-exynos
LanDi has joined #linux-exynos
afaerber__ has joined #linux-exynos
afaerber_ has quit [Ping timeout: 252 seconds]
zombah has quit [Quit: Leaving]
LanDi has quit [Quit: fui !]
<javier__>
afaerber__: hi, did you have time to dig deeper on the audio not working on Spring?
<javier__>
it turns out that even when defining the master clock for the codec and having the xxti crystal as default parent for the xclkout, sound is not always working on Snow so same behavior than Spring
<javier__>
afaerber__: so I could not include Snow audio support in my series and I've to look again at the downstream kernel clocks to find what is missing...