Samsung Galaxy Book2 Go support#31
Conversation
Signed-off-by: Jasper Korten <jja2000@gmail.com>
supposedly......... Signed-off-by: Jasper Korten <jja2000@gmail.com>
Signed-off-by: Jasper Korten <jja2000@gmail.com>
Signed-off-by: Jasper Korten <jja2000@gmail.com>
Signed-off-by: Jasper Korten <jja2000@gmail.com>
Signed-off-by: Jasper Korten <jja2000@gmail.com>
Signed-off-by: Jasper Korten <jja2000@gmail.com>
Signed-off-by: Jasper Korten <jja2000@gmail.com>
Signed-off-by: Federico Amedeo Izzo <federico@izzo.pro>
Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
|
This kernel booted as is on a postmarketOS edge installation with "console" UI booted using the following cmdline, results in a blinking framebuffer that stays black after a few seconds. It completed the boot on Linux 6.16 By replacing the current usb nodes in the dts with these nodes taken from Edit: it was a problem with my WIP pmOS device package: Adding dtbloader to the depends of APKBUILD makes the system boot. usb dts nodes
&usb_1 {
dr_mode = "host";
status = "okay";
};
&usb_1_hsphy {
status = "okay";
vdda-pll-supply = <&vreg_l10c_0p8>;
vdda33-supply = <&vreg_l2b_3p0>;
vdda18-supply = <&vreg_l1c_1p8>;
qcom,hs-rise-fall-time-bp = <0>;
qcom,squelch-detector-bp = <(-2090)>;
qcom,hs-disconnect-bp = <1743>;
qcom,hs-amplitude-bp = <1780>;
qcom,hs-crossover-voltage-microvolt = <(-31000)>;
qcom,hs-output-impedance-micro-ohms = <2600000>;
};
&usb_1_qmpphy {
status = "okay";
vdda-phy-supply = <&vreg_l6b_1p2>;
vdda-pll-supply = <&vreg_l1b_0p8>;
}; |
|
I was able to make WiFi work by enabling the remoteproc nodes, replacing the Here are two patches to fix USB and display (were broken on 7.0) and to enable WiFi (needs firmware packages and firmware files from the Windows installation) |
|
I propose we rename all references to |
|
The display panel works as-is, as long as the following Kconfig options are enabled:
They are not on sc7280_defconfig from linux-postmarketos-qcom-sc7280 |
|
|
||
| &mdss_edp_out { | ||
| data-lanes = <0 1 2 3>; | ||
| link-frequencies = /bits/ 64 <1620000000 2700000000 5400000000 8100000000>; |
There was a problem hiding this comment.
data-lanes and link-frequencies are not needed, I tested it and panel works fine without them.
|
Enabling the GPU only requires enabling the dts node and copying the |
|
We need to decide whether to keep the android-style firmware names to make them easily recognizable (e.g. adsp.mbn, cdsp.mbn) or switch to the windows-style firmware names to avoid renaming them (qcadsp7280.mbn, qcdxkmsuc7280.mbn). |
…or 7.0 kernel Signed-off-by: Federico Amedeo Izzo <federico@izzo.pro>
…moteprocs and wifi Signed-off-by: Federico Amedeo Izzo <federico@izzo.pro>
Signed-off-by: Federico Amedeo Izzo <federico@izzo.pro>
Signed-off-by: Luca Weiss <luca@lucaweiss.eu>
Signed-off-by: Luca Weiss <luca@lucaweiss.eu>
Signed-off-by: Luca Weiss <luca@lucaweiss.eu>
|
In a comment, since it got nuked in the usb fixup commit for USB, I've mapped out how the usb lanes are divided over the ports. Results are based on the output given by HWiNFO. Expect windows'isms.
As far as capabilities per-port go, ACPI might be poorly written or muxing is working incorrectly. All are declared as USB3-compatible ports "with a switch" implying muxing, but when connecting actual devices, only the above configuration is possible. For video, only the right USB Type-C connector seems to support DisplayPort out, left USB Type-C connector will throw up an error by the Samsung app that I should use the right side. Disabling the screen does not help in case the internal display is muxed. |
seems our adsp firmware has audioreach and not elite. At least with elite probe nothing appears and audioreach we seem to get something. Let's see.
based on the DSDT
jja2000
left a comment
There was a problem hiding this comment.
In addition to the other comments w.r.t. the i2c addresses for the EMEC device (SAM0604), the following interrupts are also in that device node:
GpioInt (Level, ActiveLow, ExclusiveAndWake, PullUp, 0x0000,
"\\_SB.GIO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0300 // PDC, should be TLMM 101
}
GpioInt (Edge, ActiveLow, ExclusiveAndWake, PullDefault, 0x0000,
"\\_SB.GIO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0280 // PDC, should be TLMM 20
}
GpioInt (Level, ActiveLow, ExclusiveAndWake, PullUp, 0x0000,
"\\_SB.GIO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0340 // PDC, should be TLMM 103
}
GpioInt (Edge, ActiveLow, ExclusiveAndWake, PullDefault, 0x0000,
"\\_SB.GIO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x02C0 // PDC, should be TLMM 21
}
Not sure what device they belong to specifically though...
| &i2c1 { | ||
| status = "okay"; | ||
|
|
||
| // i2cdetect shows 0x31, 0x32, 0x33, 0x34, 0x49 |
There was a problem hiding this comment.
ACPI says EMEC device (SAM0604) should be connected to i2c1 at address 0x14 and 0x33
| &i2c10 { | ||
| status = "okay"; | ||
|
|
||
| // i2cdetect shows 0x09, 0x0b |
There was a problem hiding this comment.
Both of these belong to the EMEC device (SAM0604)
|
|
||
| // i2cdetect shows 0x20, 0x21 | ||
| }; | ||
|
|
There was a problem hiding this comment.
ACPI says EMEC (SAM0604) is connected to i2c3 on address 0x14 and 0x33
|
|
||
| // i2cdetect shows 0x1d | ||
| }; | ||
|
|
There was a problem hiding this comment.
ACPI says EMEC (SAM0604) is connected to i2c8 on address 0x10
|
|
||
| // i2cdetect shows 0x0d | ||
| }; | ||
|
|
There was a problem hiding this comment.
ACPI says EMEC (SAM0604) is connected to i2c13 on address 0x2C
| }; | ||
|
|
||
| // \\_SB.I2C3 -- has SAMM0210 at 0x20 (SAR2) & 0x21 (SAR3) with interrupt | ||
| // https://treexy.com/products/driver-fusion/database/sensors/samsung/a96t396-proximity/ |
There was a problem hiding this comment.
Grip sensor has no driver upstream, but there are Samsung phones with downstream drivers that have it, like the A25 5G.
Will update the comment with the right interrupt pin.
| }; | ||
|
|
||
| // \\_SB.I2C5 -- has SAMM0214 / ACC1 at 0x1d with interrupt | ||
| // https://treexy.com/products/driver-fusion/database/sensors/samsung/lis2dlc12-accelerometer-device/ |
There was a problem hiding this comment.
Probably compatible with st-accel, not sure what compatible exactly.
Matrix seems to be defined in the DSDT.
Will update comment with the right interrupt pin.
There was a problem hiding this comment.
I agree it should be compatible with the driver, at least after some lis2dlc12-specific addition. Haven't looked around too much yet, but I can't find the sensor on the ST website but there's more mentions of this part number than just related to this laptop. No datasheet found of course.
No description provided.