<jonasschwoebel[m>
it's a `Integrated Device Technology V103`
<jenneron[m]>
if driver does some workarounds for thine then it's better to use lvds-encoder compatible
<jenneron[m]>
or "idt,v103", "lvds-encoder", but "idt,v103" doesn't exist and most likely won't, it will always fall back to "lvds-encoder", so i assumed using "lvds-encoder" itself is okay
oldgalileo has quit [Remote host closed the connection]
oldgalileo has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
sikhye has quit [Read error: Connection reset by peer]
sikhye has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
<digetx>
DavidHeidelberg: adding "power-supplies: true" to yaml should fix it, but I don't know whether the referenced power-supply.yaml should work
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
oldgalileo has quit [Remote host closed the connection]
oldgalileo has joined #tegra
torez has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
oldgalileo has quit [Remote host closed the connection]
oldgalileo has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
quarkyalice__ has joined #tegra
quarkyalice__ has quit [Read error: Connection reset by peer]
gouchi has joined #tegra
oldgalileo has quit [Remote host closed the connection]
oldgalileo has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
torez has quit [Ping timeout: 246 seconds]
torez has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
<DavidHeidelberg>
digetx thanks for CCing me, but my CI inside me is disappointed by just adding few lines to the .txt definition :D
<DavidHeidelberg>
(or maybe I missed the switch to the yaml)
<DavidHeidelberg>
but vde .txt -> yaml made me happy enough :D
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
<digetx>
ideally there should be more yaml conversions or more lines added to txt, but I'll let you do that :)
<leanderglanda[m]>
If the firmware only supplies one GOP handle, then this will fail, because i < num_handles isn't true anymore. So it just skips checking the only valid GOP handle.
<jenneron[m]>
ok, then i need to detect firmware, thanks
<leanderglanda[m]>
you are welcome. if you have any other questions about EFI stuff feel free to ask them.
digetx has quit [Ping timeout: 264 seconds]
digetx has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
gouchi has quit [Remote host closed the connection]
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
digetx has quit [Ping timeout: 265 seconds]
digetx has joined #tegra
<DavidHeidelberg>
jenneron in that case it should be "idt,v103", "thine,thc63lvd103", "lvds-encoder";
<jenneron[m]>
still thine will be used
<DavidHeidelberg>
if idt is not found
<jenneron[m]>
it will not be found and idt compatible will probably never exist
<DavidHeidelberg>
if we decide to add idt compatible, it has to be entered into Documentation
<DavidHeidelberg>
trick is it's pin compatible with thine, so thine is logical compatible
<jenneron[m]>
hm can't we just document "lvds-encoder" compatible?
<DavidHeidelberg>
please elaborate more, not sure if I understand
<jenneron[m]>
and.. i don't really understand what is wrong with "lvds-encoder" compatible, as for me the best ways are just to use this one or add idt compatible to the driver
<DavidHeidelberg>
it doesn't describe the HW. In case when there will be discovered some specific quirk for thc63... or idt, the driver will not know it's needed, since it gets lvds-encoder
<DavidHeidelberg>
*gets only lvds-encoder compatible
<DavidHeidelberg>
(of course driver could try to autodetect it, but why when we have `compatible` string)
<jenneron[m]>
DavidHeidelberg: in this case we should add idt compatible and not use thine
<DavidHeidelberg>
well, imho we should do idt, lvds-encoder or idt, thc63, lvds-
<DavidHeidelberg>
maybe digetx will have reasonable idea what would be optional?
<DavidHeidelberg>
but since idt is pin compatible with thc63, I think it could be reasonable mention thc63 in compatible string
<jenneron[m]>
pin compatible just means that you can place IC instead of another one on board, it doesn't mean they have same logic and registers
<jenneron[m]>
it's in general
<jenneron[m]>
but speaking of lvds encoders you're right, they're probably compatible at least for driver side
<DavidHeidelberg>
yeah, but the description of thc63 is closed to the HW than lvds-encoder
<DavidHeidelberg>
ofc "match, generic" could most likely make sense too
<jenneron[m]>
it doesn't sound good for me when IC works fine with generic compatible and if match compatible will never be added to the driver, but you may know better
<DavidHeidelberg>
well, DT isn't about driver, it's description of the HW
<DavidHeidelberg>
you describe HW and driver can use it or just ignore it
<DavidHeidelberg>
but when driver will need to use it (distinguish between generic lvds-encoder), then you can just patch the kernel without touching DT and it'll work
<jenneron[m]>
ok, then `"idt,v103", "lvds,encoder"` may be reasonable
sikhye has quit [Remote host closed the connection]
<DavidHeidelberg>
yeah. Also one reason why there should be two entries is that lvds yaml definition doesn't allow using "only" generic compatible and I assume it's for the reason of being able to implement specific features for different compatible
sikhye has joined #tegra
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
torez has quit [Quit: torez]
sikhye has quit [Remote host closed the connection]
sikhye has joined #tegra
oldgalileo has quit [Remote host closed the connection]