Tenkawa has joined #linux-exynos
Tenkawa has joined #linux-exynos
zombah has quit [Quit: Leaving]
liquidAcid has quit [Quit: Leaving]
Tenkawa has quit [Quit: leaving]
javier__ has quit [Ping timeout: 250 seconds]
javier__ has joined #linux-exynos
amitk has joined #linux-exynos
zombah has joined #linux-exynos
gautam__ has joined #linux-exynos
Tenkawa has joined #linux-exynos
Tenkawa has joined #linux-exynos
libv has joined #linux-exynos
Tenkawa has quit [Quit: leaving]
ssvb has quit [Ping timeout: 255 seconds]
gallit has joined #linux-exynos
gallit has quit [Client Quit]
gallit has joined #linux-exynos
<javier__> afaerber: hi, I see that the downstream spring DTS has a "supports-hsicphy-reset" property to reset the HSIC hub
<javier__> that DT property doesn't exist in mainline though, is the HSIC hub enumerated for Spring in mainline?
<javier__> afaerber: I'm asking because I see that is the only difference between the donwstream spring and skate DTS so I think it make sense to add skate support too
ssvb has joined #linux-exynos
<afaerber> javier__, can't check right now... what exactly is Skate? Ajay mentioned it
<afaerber> bbiab
afaerber has quit [Quit: Verlassend]
afaerber has joined #linux-exynos
<javier__> I don't have access to that hw either but is the only exynos dts that remains in the downstream chromiumos tree so is worth to at least post it imho
<afaerber> javier__, sure, but how do I tell whether I have a Spring or Skate then? :)
<afaerber> "a slightly different BOM" is not so telling ;)
<javier__> afaerber: Board-on-Module perhaps?
<javier__> the DTS looks identical besides the hsic reset dt property that I mentioned
<javier__> so maybe skate is a spring errata?
<afaerber> javier__, bill of materials I assumed
<javier__> afaerber: right, that makes much more sense
<javier__> afaerber: if you still have the chromeos original rootfs, you may look at the compatible string in /proc/device-tree
<zombah> wiki says spring IPS lcd and skate TN lcd
<javier__> zombah: yeah, but I didn't find any difference w.r.t display in the downstream DTS
<javier__> so probably both can use the simple-panel driver
<zombah> javier__: maybe they use same panel driver, only lcd id is different
<javier__> zombah: it seems so
<javier__> afaerber: I just asked to see if that "supports-hsicphy-reset" should be upstreamed too or if it has been addressed in mainline without the need of DT info
<afaerber> javier__, "google,spring", "samsung,exynos5250"
<javier__> afaerber: and lsusb shows you the HSIC hub?
<afaerber> javier__, told you, I'm not at the device. the decompiled .dts I have on my hard drive
<javier__> afaerber: ups, sorry
<javier__> afaerber: missed that you didn't have access to the device, no worries then :)
<javier__> afaerber: I'm trying to figure out why s2r is broken btw since that used to work when samsung folks posted the patches
gallit has quit [Ping timeout: 250 seconds]
zombah has quit [Quit: Leaving]
libv has quit [Ping timeout: 264 seconds]
libv has joined #linux-exynos
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos
afaerber has quit [Quit: Verlassend]
amitk has quit [Quit: leaving]
liquidAcid has joined #linux-exynos
zombah has joined #linux-exynos
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos
liquidAcid has quit [Quit: Leaving]
zombah has quit [Quit: Leaving]
liquidAcid has joined #linux-exynos