jacobk has quit [Remote host closed the connection]
jacobk has joined #linux-msm
jacobk has quit [Remote host closed the connection]
jacobk has joined #linux-msm
jacobk has quit [Remote host closed the connection]
jacobk has joined #linux-msm
jacobk has quit []
gnuiyl_ has joined #linux-msm
jacobk has joined #linux-msm
gnuiyl has quit [Ping timeout: 480 seconds]
jacobk has quit [Remote host closed the connection]
jacobk has joined #linux-msm
jacobk has quit []
jacobk has joined #linux-msm
jacobk has quit [Remote host closed the connection]
jacobk has joined #linux-msm
jacobk_ has joined #linux-msm
jacobk is now known as Guest9497
jacobk_ is now known as jacobk
Guest9497 has quit [Ping timeout: 480 seconds]
jacobk has quit [Remote host closed the connection]
jacobk has joined #linux-msm
jacobk_ has joined #linux-msm
jacobk is now known as Guest9498
jacobk_ is now known as jacobk
Guest9498 has quit [Ping timeout: 480 seconds]
<logicalerzor[m]>
hello all i have two questions: 1) if i want to submit someone else's commit into upstream Linux, what's the best process to do that?
<logicalerzor[m]>
however the driver seems to bail at "Could not detect nfc_en polarity, fallback to active high" and im not sure what im doing wrong in the dts that could do that (as far as im aware it matches the board file). any help on this would be great, thanks
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
ungeskriptet_ has joined #linux-msm
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet_ is now known as ungeskriptet
niej_ has joined #linux-msm
jhovold has joined #linux-msm
<krzk>
logicalerzor[m]: submitting patches covers this exactly
<krzk>
logicalerzor[m]: 2. read the driver code - what piece leads to such error?
<logicalerzor[m]>
krzk: ah thanks! sorry i had just skimmed that document. will read this in its entirety then
<logicalerzor[m]>
<krzk> "logicalerzor: 2. read the driver..." <- also thanks! it seems downstream driver also configures some pins in addition to the board file. It seems like im getting a new error now with "SE discovery failed\n" but ill try to figure this out until i ask for help here
zstas has joined #linux-msm
zstas_ has joined #linux-msm
zstas has quit [Ping timeout: 480 seconds]
jacobk_ has joined #linux-msm
jacobk is now known as Guest9513
jacobk_ is now known as jacobk
Guest9513 has quit [Ping timeout: 480 seconds]
srinik has joined #linux-msm
pespin has joined #linux-msm
srinik has quit [Ping timeout: 480 seconds]
srinik has joined #linux-msm
jacobk has quit [Ping timeout: 480 seconds]
niej_ has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
fossdd has quit [Ping timeout: 480 seconds]
pespin has quit []
zstas_ has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
fossdd has joined #linux-msm
Tyalie7098[m] has joined #linux-msm
tyalie has joined #linux-msm
Tyalie7098[m] is now known as Tyalie[m]
Tyalie[m] has left #linux-msm [#linux-msm]
<tyalie>
hi. I'm rn trying to get PCIe running on an Qualcomm SM8475 device with mainline. Looking into the downstream kernel by Qualcomm the SM8475 and SM8450 pcie initialization sequences are quite different. As the SM8450 is already supported I've been trying to understand the downstream init sequence (only bytes) using the info contained in
<tyalie>
drivers/phy/qualcomm/phy-qcom-qmp-pcie.c in hope that I can use that knowledge to get the SM8475 running. But I noticed that a lot of registers in QCs phy init sequence for the SM8450 do not have a corresponding mention in the mainline headers (even considering the offsets). e.g. I was unable to find the register associated to `0x0240` or `0x11a4`.