ChanServ changed the topic of #linux-msm to:
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
pevik_ has joined #linux-msm
Caterpillar has joined #linux-msm
pespin has joined #linux-msm
<aka_[m]> Marijn: have you noticed minecrell[m] reply about 28nm phy?
<Marijn[m]> aka_: no I don't have email, how am I supposed to receive replies?
<Marijn[m]> aka_: what about it?
pevik_ has quit [Ping timeout: 480 seconds]
<Marijn[m]> aka_: yes, again, what about it?
<aka_[m]> what do you think of dropping usage of 28nm femto driver and using 8916 one
<aka_[m]> just like recommended by Stephan
<Marijn[m]> Correct, that's what he's proposing
<Marijn[m]> Anything you want to add to that?
<aka_[m]> nothing, just asking if this is possibility
<Marijn[m]> I had a similar chat with Mis012 about that just yesterday, and told him I'd test that, so yes.
<aka_[m]> well
<aka_[m]> guess where it started
<Marijn[m]> Since minecrell[m] suggested the same thing, might as well
<aka_[m]> me trying to do things proper way with overriding that register and having Mis012 to do upgrades to driver
<aka_[m]> then we noticed its wrong
<aka_[m]> and had some chat with minecrell, somehow Mis012 failed to deliver and i see he had chat with you
<aka_[m]> so thats quick recap on why i ask
<aka_[m]> i have device with 8976 you know and im also interested in sending dts for 6.3
<aka_[m]> Mis012: oh hi
<Marijn[m]> I also noticed that while porting 8976, but never got to reverting this patch and sending it until now, and never bothered to test the existing nor omitted writes as it "just works"
<Marijn[m]> Maybe otg might not or something else?
<Marijn[m]> aka_[m]: Yes please send your DTS, we'll try to send mdp5 soon but ehh iommu..
<aka_[m]> my only pain was usb was not really getting kicked in if i rebooted phone and then launching linux without replugging usb
<Marijn[m]> At least all the driver support sent by Angelo and me landed years ago 😅
<aka_[m]> not sure if related to phy or tusb somehow does not get reset
<Mis012[m]> 8916 isn't femtophy, it's picophy iirc?
<aka_[m]> was pico
pespin has quit [Remote host closed the connection]
<Mis012[m]> picophy is a different IP block...
<aka_[m]> it appears "API" is same
<Mis012[m]> pretty sure I checked that and it wasn't
<aka_[m]> and wasnt qusb also some kind of their IP?
<Marijn[m]> aka_[m]: By the way don't bother with Linux versions, just use -next and send things as soon as they are ready
<minecrell> Mis012[m]: the PHY driver used for msm8916 isn't specific to one particular "IP", it's a fairly generic ULPI PHY driver
<minecrell> it doesn't have pico specific code atm
<Mis012[m]> oh, you mean the ULPI part
<Marijn[m]> Things will get reviewed by maintainers and external contributors whenever there's time, and picked up whenever it's acceptable/accepted. No point aiming for kernel versions or you might get disappointed
<aka_[m]> ulpi is somehow written via host controller to phy or what exactly
<Mis012[m]> the femtophy driver is specifically for femtophy
<Mis012[m]> resp. for qcom's register interface to femtophy
<Marijn[m]> So if you have a minimal boots-to-uart dts ready, send it sooner rather than later ;)
<Mis012[m]> since femtophy doesn't contain registers
<Mis012[m]> but qcom connected a lot of it's wires to registers
<aka_[m]> Marijn[m]: well i would love to be able to send dts with mdp set up already but no iommu so yea
<Marijn[m]> For that mdp first needs to land in soc dts.... Don't depend on it
<aka_[m]> why not send mdp iommu-less first
<Mis012[m]> for the femtophy part, 8976 basically needs no quirks while 404 needs quite some quirks
<aka_[m]> then assign it once context banks can be defined
<Marijn[m]> aka_[m]: Theoretically that shouldn't work, neither the dma nor vig pipes?
<Marijn[m]> We were thinking of sending it with a "depends on link to iommu patches" regardless
<aka_[m]> hmm, iommu patches arent they required mostly for gpu one due to asid=0?
<aka_[m]> 8953 have already apps landed
<Mis012[m]> for example 404 POR for some reason sets it to the wrong ULPI bridge vs plain UTMI mode, since it's connected to dwc3 on 404 which uses UTMI iirc? while 8976 is connected to something that uses ULPI, was that qusb maybe
<aka_[m]> Mis012[m]: ci-hdcr(?) as host
<Mis012[m]> so the driver needs to set the right values since POR values are broken
<Mis012[m]> aka_: right, chipidea
<Mis012[m]> that's the one
<Marijn[m]> aka_[m]: Not probe the driver and leave bootloader context banks?
narmstrong_ has joined #linux-msm
hfink_ has joined #linux-msm
flto_ has joined #linux-msm
krzk4 has joined #linux-msm
hfink has quit [Ping timeout: 480 seconds]
krzk has quit []
flto has quit []
narmstrong has quit []
bhsharma has quit []
vkoul has quit []
sumits has quit []
krzk4 is now known as krzk
krzk is now known as Guest2402
vkoul has joined #linux-msm
sumits has joined #linux-msm
krzk has joined #linux-msm
bhsharma has joined #linux-msm
flto has joined #linux-msm
vkoul has quit [Ping timeout: 482 seconds]
sumits has quit [Ping timeout: 482 seconds]
krzk has quit [Ping timeout: 482 seconds]
flto has quit [Ping timeout: 482 seconds]
bhsharma has quit [Ping timeout: 482 seconds]
flto_ has quit []
flto has joined #linux-msm
sumits has joined #linux-msm
vkoul has joined #linux-msm
bhsharma has joined #linux-msm