clean up: move notes on components into separate files
This commit is contained in:
erebion
parent
b70cf28791
commit
fdc03a27f0
5 changed files with 80 additions and 62 deletions
83
README.md
83
README.md
|
|
@ -39,6 +39,8 @@ No status means I haven't even had a look at that component.
|
|||
|
||||
So far no work has been put in supporting the sensors (accelerometer, magnetometer, ambient light, ...).
|
||||
|
||||
Further detail on some components can be found in the `notes` folder in this repo.
|
||||
|
||||
#### Where To Help
|
||||
|
||||
- Audio/Calls <-- currently top priority, this would allow me testing the phone as a daily driver
|
||||
|
|
@ -46,19 +48,24 @@ So far no work has been put in supporting the sensors (accelerometer, magnetomet
|
|||
- Camera
|
||||
- vibration module
|
||||
- NFC
|
||||
- UFS
|
||||
- UFS <- most annoying blocker for now
|
||||
- USB-C
|
||||
- Display Port via USB-C
|
||||
|
||||
#### Kernel Work
|
||||
|
||||
I'll submit all my patches to https://github.com/sm6350-mainline/linux and then later upstream them.
|
||||
My working branch: https://salsa.debian.org/erebion/linux/-/tree/erebion/pdx213-wip
|
||||
|
||||
Current goal: Making the device usable
|
||||
Later goal: Trying to add everything else that can be added without writing new drivers and upstreaming
|
||||
The plan is to submit all my patches to https://github.com/sm6350-mainline/linux and to then upstream them to the kernel.
|
||||
|
||||
Note: I'm rebasing occasionally to make sure it does not become too chaotic, so pulling from that repo will lead to merge conflicts.
|
||||
|
||||
##### Upstreaming to the kernel
|
||||
|
||||
| no | what | link |
|
||||
| -- | ---- | ---- |
|
||||
| 0 | enables a couple components | Patch Series: https://lore.kernel.org/all/20260926-pdx213-upstream-3-v2-0-b4612e3eb536@erebion.eu/ |
|
||||
|
||||
### Issues To Solve
|
||||
|
||||
#### "AI key"
|
||||
|
|
@ -77,68 +84,20 @@ Downstream DT contains an "AI key", not sure what to do with that.
|
|||
};
|
||||
```
|
||||
|
||||
0x55 -> 0d85... perhaps gpio85?
|
||||
|
||||
#### Bluetooth
|
||||
|
||||
Works fine.
|
||||
|
||||
Note to myself: If Bluetooth does not work... Check that the kernel modules are present and load hci_uart and btqca... Yes, this breaks if I use a boot image with a rootfs that does not have the modules on it... (I'm building those separetely so I don't have to flash the microSD all the time to try out a new kernel).
|
||||
|
||||
#### Touch
|
||||
##### Workaround for missing UFS
|
||||
|
||||
```
|
||||
[ 63.964541] gpi 900000.dma-controller: Error in Transaction
|
||||
[ 63.964562] geni_i2c 988000.i2c: DMA txn failed:3
|
||||
[ 63.964594] geni_i2c 988000.i2c: GPI transfer failed: -5
|
||||
[ 63.966484] s6sy761 0-0048: failed to turn off sensing
|
||||
[ 64.599984] gpi 900000.dma-controller: Error in Transaction
|
||||
[ 64.600041] geni_i2c 988000.i2c: DMA txn failed:3
|
||||
[ 64.601254] geni_i2c 988000.i2c: GPI transfer failed: -5
|
||||
cd /dev/disk/
|
||||
mkdir by-partlabel
|
||||
ln -s /home/mobian/modemst1.img modemst1
|
||||
ln -s /home/mobian/modemst2.img modemst2
|
||||
#ln -s /home/mobian/TA.img TA
|
||||
ln -s /home/mobian/modem_a.img modem_a
|
||||
ln -s /home/mobian/modem_b.img modem_b
|
||||
systemctl restart rmtfs.service tqftpserv.service qcom-modem-setup.service # to do: find out whether all three actually have to be restarted
|
||||
```
|
||||
|
||||
When logging in, `/dev/input/event2` disappears while Phosh starts... if no finger is on the touch screen (lol), [seemingly needs this patch](https://lore.kernel.org/all/20260923-s6sy761-suspend-v1-1-6fff96e71cb0@ixit.cz/)
|
||||
|
||||
There's a patch in the kernel now: [link](https://lore.kernel.org/all/arnvS7Hk7uIKKLrZ@google.com/)
|
||||
|
||||
Have not tried it yet.
|
||||
|
||||
#### Modem
|
||||
|
||||
```
|
||||
[ 50.440514] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
|
||||
[ 50.440562] remoteproc remoteproc1: crash detected in modem: type fatal error
|
||||
[ 50.440733] remoteproc remoteproc1: handling crash #1 in modem
|
||||
[ 50.440744] remoteproc remoteproc1: recovering modem
|
||||
[ 50.473165] ath10k_snoc 18800000.wifi: firmware crashed! (guid c1e5bbb2-ee6c-4853-9f47-ba65dbda4174)
|
||||
[ 91.131777] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
|
||||
[ 91.131827] remoteproc remoteproc1: crash detected in modem: type fatal error
|
||||
[ 91.131998] remoteproc remoteproc1: handling crash #2 in modem
|
||||
[ 91.132009] remoteproc remoteproc1: recovering modem
|
||||
[ 91.179283] ath10k_snoc 18800000.wifi: firmware crashed! (guid a814647c-fc5c-4ad6-b35e-8b88eec81fef)
|
||||
```
|
||||
|
||||
Modem crashes. Reason is missing TA service. Modem works fine with TA service running.
|
||||
|
||||
Error message `[ 50.440514] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
|
||||
` seems to come from `drivers/remoteproc/qcom_q6v5.c`, see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/remoteproc/qcom_q6v5.c?h=v6.19.12#n126
|
||||
|
||||
Error message `[ 50.440562] remoteproc remoteproc1: crash detected in modem: type fatal error` seems to come from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/remoteproc/remoteproc_core.c?h=v6.19.12#n2707
|
||||
|
||||
### GPS
|
||||
|
||||
GPS likely also works via the modem. But the modem occasionally crashes:
|
||||
|
||||
```
|
||||
[ 2792.695395] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hb.c:367:Task starvation: mmgsdi_1, ping: 4, triage with owner(d.dump 0x1ecf7180)
|
||||
```
|
||||
|
||||
```
|
||||
root@mobian:~# mmcli -m any --location-enable-gps-nmea
|
||||
error: couldn't setup location gathering: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.PhoneFailure: QMI protocol error: Couldn't enable location 'gps-nmea' gathering: Couldn't start GPS engine: QMI protocol error (46): 'GeneralError''
|
||||
```
|
||||
|
||||
Needs investigation, lower priority than some other parts for now.
|
||||
With this the modem can be started for now...
|
||||
|
||||
## Unlocked Achievements
|
||||
|
||||
|
|
|
|||
5
notes/bluetooth.md
Normal file
5
notes/bluetooth.md
Normal file
|
|
@ -0,0 +1,5 @@
|
|||
#### Bluetooth
|
||||
|
||||
Works fine.
|
||||
|
||||
Note to myself: If Bluetooth does not work... Check that the kernel modules are present and load hci_uart and btqca... Yes, this breaks if I use a boot image with a rootfs that does not have the modules on it... (I'm building those separetely so I don't have to flash the microSD all the time to try out a new kernel).
|
||||
14
notes/gps.md
Normal file
14
notes/gps.md
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
### GPS
|
||||
|
||||
GPS likely also works via the modem. But the modem occasionally crashes:
|
||||
|
||||
```
|
||||
[ 2792.695395] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hb.c:367:Task starvation: mmgsdi_1, ping: 4, triage with owner(d.dump 0x1ecf7180)
|
||||
```
|
||||
|
||||
```
|
||||
root@mobian:~# mmcli -m any --location-enable-gps-nmea
|
||||
error: couldn't setup location gathering: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.PhoneFailure: QMI protocol error: Couldn't enable location 'gps-nmea' gathering: Couldn't start GPS engine: QMI protocol error (46): 'GeneralError''
|
||||
```
|
||||
|
||||
Needs investigation, lower priority than some other parts for now.
|
||||
21
notes/modem.md
Normal file
21
notes/modem.md
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
#### Modem
|
||||
|
||||
```
|
||||
[ 50.440514] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
|
||||
[ 50.440562] remoteproc remoteproc1: crash detected in modem: type fatal error
|
||||
[ 50.440733] remoteproc remoteproc1: handling crash #1 in modem
|
||||
[ 50.440744] remoteproc remoteproc1: recovering modem
|
||||
[ 50.473165] ath10k_snoc 18800000.wifi: firmware crashed! (guid c1e5bbb2-ee6c-4853-9f47-ba65dbda4174)
|
||||
[ 91.131777] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
|
||||
[ 91.131827] remoteproc remoteproc1: crash detected in modem: type fatal error
|
||||
[ 91.131998] remoteproc remoteproc1: handling crash #2 in modem
|
||||
[ 91.132009] remoteproc remoteproc1: recovering modem
|
||||
[ 91.179283] ath10k_snoc 18800000.wifi: firmware crashed! (guid a814647c-fc5c-4ad6-b35e-8b88eec81fef)
|
||||
```
|
||||
|
||||
Modem crashes. Reason is missing TA service. Modem works fine with TA service running.
|
||||
|
||||
Error message `[ 50.440514] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
|
||||
` seems to come from `drivers/remoteproc/qcom_q6v5.c`, see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/remoteproc/qcom_q6v5.c?h=v6.19.12#n126
|
||||
|
||||
Error message `[ 50.440562] remoteproc remoteproc1: crash detected in modem: type fatal error` seems to come from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/remoteproc/remoteproc_core.c?h=v6.19.12#n2707
|
||||
19
notes/touch.md
Normal file
19
notes/touch.md
Normal file
|
|
@ -0,0 +1,19 @@
|
|||
#### Touch
|
||||
|
||||
```
|
||||
[ 63.964541] gpi 900000.dma-controller: Error in Transaction
|
||||
[ 63.964562] geni_i2c 988000.i2c: DMA txn failed:3
|
||||
[ 63.964594] geni_i2c 988000.i2c: GPI transfer failed: -5
|
||||
[ 63.966484] s6sy761 0-0048: failed to turn off sensing
|
||||
[ 64.599984] gpi 900000.dma-controller: Error in Transaction
|
||||
[ 64.600041] geni_i2c 988000.i2c: DMA txn failed:3
|
||||
[ 64.601254] geni_i2c 988000.i2c: GPI transfer failed: -5
|
||||
```
|
||||
|
||||
When logging in, `/dev/input/event2` disappears while Phosh starts... if no finger is on the touch screen (lol), [seemingly needs this patch](https://lore.kernel.org/all/20260923-s6sy761-suspend-v1-1-6fff96e71cb0@ixit.cz/)
|
||||
|
||||
There's a patch in the kernel now: [link](https://lore.kernel.org/all/arnvS7Hk7uIKKLrZ@google.com/)
|
||||
|
||||
Have not tried it yet.
|
||||
|
||||
To Do: Verify the patch fixes broken touch...
|
||||
Loading…
Reference in a new issue