google-sargo: switch to close-to mainline kernel
There was a bit of progress on the Google Pixel 3a since the original port. This merge request contains some changes that I have been working on (and still need to clean up a little).
switch to close-to mainline kernel
Since the initial porting, I mostly tried to get mainline working. In the new close-to mainline kernel, there are 61 patches on top of v5.19.12, some of which came from the sdm845 mainlining community, others came from linux-next. USB OTG definitely does not work with it but display works.
Some things to iron out:
The kernel repo isn't in a group. Some kernels (e.g. sm6350, sm8350) link to personal repos, while others link to group repos even with only one member (e.g. sm6125). I should probably move it into a group in case someone wants write access.The extras branch isn't strictly necessary and contributes to a bad repository layout.- There is no SoC wiki page yet.
- The close-to mainline kernel contains a silly patch so that it is unnecessary to erase the devicetree overlay.
The version is still v5.19.12_beta1.
enable automatic kernel upgrade
This isn't major but is a step toward the community category in 3 kernel releases, given that someone fills in the maintainer. I should probably add myself as a maintainer.
enable A/B slot control
Since this device runs on a Qualcomm SoC, qbootctl can be used to manage A/B slots. The soc-qcom-sdm845-qbootctl package is added as a dependency to make use of its post-install and post-upgrade scripts.
I don't think this makes much sense as a dependency for a device with a different SoC. Developers on the Matrix chat have said that SDM670 is similar to SDM845~~ but the google-sargo device package doesn't even depend on soc-qcom-sdm845 itself~~. The post-install script is very generic for an SoC-specific subpackage. Perhaps this should be moved to a "feature" package (maybe called feature-qbootctl)?