| Message ID | CAK8P3a1vFJ+uUGPGifZGhECXvxA=2u745WrGNZb08s1nHkZQ9g@mail.gmail.com |
|---|---|
| Headers | show |
| Series | ARM: SoC: changes for v5.9 | expand |
Hi! > 2. In the past few merge windows we have seen an increase in (usually > older) Android phones and tablets gaining mainline kernel support. > This time we get a total of eight Snapdragon phones and two Tegra > tablets. To me this indicates that we finally have sufficient driver > support, in particular on the GPU side, to make this workable. > It also shows the impact that a single hobbyist developer can have, > as most of the new support was submitted by Konrad Dybcio who only > started contributing kernel patches to mainline Linux for postmarketos > earlier this year. I'm happy to see that. So far, Nokia N900 is reaonably supported (basically everything but Bluetooth works, voicecalls miss userland daemon for audio), and Motorola Droid 4 (modem needs some more in kernel, camera will be hard). Is there anything with similar support coming in, or is it usual "it boots, serial console works"? Should we have some kind of linux-phones mailing list? There is quite a lot of stuff common in phones. Best regards, Pavel
On Wed, Aug 5, 2020 at 7:27 PM Pavel Machek <pavel@ucw.cz> wrote: > > 2. In the past few merge windows we have seen an increase in (usually > > older) Android phones and tablets gaining mainline kernel support. > > This time we get a total of eight Snapdragon phones and two Tegra > > tablets. To me this indicates that we finally have sufficient driver > > support, in particular on the GPU side, to make this workable. > > It also shows the impact that a single hobbyist developer can have, > > as most of the new support was submitted by Konrad Dybcio who only > > started contributing kernel patches to mainline Linux for postmarketos > > earlier this year. > > I'm happy to see that. So far, Nokia N900 is reaonably supported (basically everything > but Bluetooth works, voicecalls miss userland daemon for audio), and Motorola > Droid 4 (modem needs some more in kernel, camera will be hard). > > Is there anything with similar support coming in, or is it usual "it boots, > serial console works"? My impression is that the newly added phones are still fairly rudimentary, but some others that were added in the past releases have gotten further. I don't know any details, but I've added Konrad to Cc, he can comment on his work. One of the missing pieces with the OMAP based phones has always been the GPU, and on that front I think by now almost every other GPU is ahead. > Should we have some kind of linux-phones mailing list? There is quite a lot of > stuff common in phones. PostmarketOS is probably the right place to look for this. Arnd
Thanks for all the kind words, I really appreciate it. >My impression is that the newly added phones are still fairly rudimentary, >but some others that were added in the past releases have gotten >further. I don't know any details, but I've added Konrad to Cc, he can >comment on his work. Thanks for adding me. The Sony sdm630/6 phones are shaping up really well, but most of the work is not upstreamed yet mainly due to SMMU maintainers not liking Qualcomm code and looking for cleaner solutions. As time progresses, more things will see the light of the upstream. The current-ish progress can be seen on my github [1]. And much more is yet to come. Regarding msm8992/4, there is a need for the 20nm DSI PHY driver. It exists for every other gen of qcom SoCs since 2013, but due to low interest in these platforms, this specific one never got there. I tried emailing the person who wrote most of the present ones, but gmail told me the mail didn't exist :shrug:. >> Should we have some kind of linux-phones mailing list? There is quite a lot of >> stuff common in phones. >PostmarketOS is probably the right place to look for this. First of all: postmarketOS, not PostmarketOS :P I would actually say that's incorrect. With the release of the PinePhone and the Librem 5, the Linux mobile community has entered its heyday and plenty mobile-oriented distributions have arisen (for example Mobian, Manjaro ARM, Pure OS-ARM etc.) and some have gotten more attention than before (think Ubuntu Touch, Maemo Leste). pmOS is only one of many. The current thing to do is every distro maintains their own kernel (or over 100 like in pmOS, which is terrible for the poor CI :/) and only a small percentage of patches end up being upstreamed for various reasons (clean-ness of the code, will of the maintainers, time constraints..). As time goes, we're gonna see more stuff being added. [1] https://github.com/konradybcio/linux/commits/58ninges_labs Konrad
On Wed 2020-08-05 21:06:45, Arnd Bergmann wrote: > On Wed, Aug 5, 2020 at 7:27 PM Pavel Machek <pavel@ucw.cz> wrote: > > > 2. In the past few merge windows we have seen an increase in (usually > > > older) Android phones and tablets gaining mainline kernel support. > > > This time we get a total of eight Snapdragon phones and two Tegra > > > tablets. To me this indicates that we finally have sufficient driver > > > support, in particular on the GPU side, to make this workable. > > > It also shows the impact that a single hobbyist developer can have, > > > as most of the new support was submitted by Konrad Dybcio who only > > > started contributing kernel patches to mainline Linux for postmarketos > > > earlier this year. > > > > I'm happy to see that. So far, Nokia N900 is reaonably supported (basically everything > > but Bluetooth works, voicecalls miss userland daemon for audio), and Motorola > > Droid 4 (modem needs some more in kernel, camera will be hard). > > > > Is there anything with similar support coming in, or is it usual "it boots, > > serial console works"? > > My impression is that the newly added phones are still fairly rudimentary, > but some others that were added in the past releases have gotten > further. I don't know any details, but I've added Konrad to Cc, he can > comment on his work. > > One of the missing pieces with the OMAP based phones has always > been the GPU, and on that front I think by now almost every other GPU > is ahead. I have working 3D on Droid 4 with Maemo Leste... but I'm not sure what kind of hacks are involved. (And not sure I want to know). > > Should we have some kind of linux-phones mailing list? There is quite a lot of > > stuff common in phones. > > PostmarketOS is probably the right place to look for this. Yes, I monitor postmarketOS a bit. But I believe we should have something cross-distro. I'm more involved with Maemo Leste, but there are other players -- at least Librem and Jolla. Best regards, Pavel
Hi! > Thanks for all the kind words, I really appreciate it. Thanks for good work :-). > >My impression is that the newly added phones are still fairly rudimentary, > >but some others that were added in the past releases have gotten > >further. I don't know any details, but I've added Konrad to Cc, he can > >comment on his work. > > Thanks for adding me. The Sony sdm630/6 phones are shaping up really > well, but most of the work is not upstreamed yet mainly due to SMMU > maintainers not liking Qualcomm code and looking for cleaner > solutions. As time progresses, more things will see the light of the > upstream. The current-ish progress can be seen on my github [1]. And > much more is yet to come. > > Regarding msm8992/4, there is a need for the 20nm DSI PHY driver. It > exists for every other gen of qcom SoCs since 2013, but due to low > interest in these platforms, this specific one never got there. I > tried emailing the person who wrote most of the present ones, but > gmail told me the mail didn't exist :shrug:. I won't pretend to understand all this. Do you normally have modems working? > >> Should we have some kind of linux-phones mailing list? There is quite a lot of > >> stuff common in phones. > > >PostmarketOS is probably the right place to look for this. > > First of all: postmarketOS, not PostmarketOS :P > > I would actually say that's incorrect. With the release of the > PinePhone and the Librem 5, the Linux mobile community has entered its > heyday and plenty mobile-oriented distributions have arisen (for > example Mobian, Manjaro ARM, Pure OS-ARM etc.) and some have gotten > more attention than before (think Ubuntu Touch, Maemo Leste). pmOS is > only one of many. > > The current thing to do is every distro maintains their own kernel (or > over 100 like in pmOS, which is terrible for the poor CI :/) and only > a small percentage of patches end up being upstreamed for various > reasons (clean-ness of the code, will of the maintainers, time > constraints..). As time goes, we're gonna see more stuff being > added. I did not know how popular PinePhone is. Does it currently have useful battery life? Would something like phone@vger.kernel.org be useful for low-level stuff? Best regards, Pavel
> I did not know how popular PinePhone is. Does it currently have useful > battery life? It basically sells out in a few days after a new batch is up :D You might want to join some pine64 irc/matrix/telegram channels. Currently, as far as I'm aware (I haven't got one), it can survive a full day but enhancements are still coming. > Would something like phone@vger.kernel.org be useful for low-level > stuff? It would certainly make for less spam (yes, I once got (jokingly) called out for "spamming" linux-arm-msm :D) on the general arm lists. Many commits just tackle DTS or some bizarre only-found-on-phones hardware. Considering Xiaomi releases 1 phone a week on average, expect to be flooded when mainlining gets popular on sites like XDA-Developers forums where many Android devs currently are. Also it would be easier for people to find other phone/mobile developers. Also, you guys might want to consider arch/arm64/boot/dts/qcom/vendor in the future to prevent it from becoming a mess of a directory that arch/arm/boot/dts is (though that will obviously take some time) :P Konrad
>Regarding msm8992/4, there is a need for the 20nm DSI PHY driver.
Well... Of course I meant DSI PLL there. It's so easy to mistake
three-letter acronyms..
Konrad
There is much of the usual this time, but there are also three parts I find worth pointing out in particular: 1. We tend to add support for new SoCs every merge window, but usually these are all variations of those we already support. This time there are three newly added families of Arm SoCs: - Intel/Movidius Keem Bay - Microchip SparX5 - Mediatek (Mstar) Infinity3/Mercury5 There is a separate pull request for these three that has additional details. 2. In the past few merge windows we have seen an increase in (usually older) Android phones and tablets gaining mainline kernel support. This time we get a total of eight Snapdragon phones and two Tegra tablets. To me this indicates that we finally have sufficient driver support, in particular on the GPU side, to make this workable. It also shows the impact that a single hobbyist developer can have, as most of the new support was submitted by Konrad Dybcio who only started contributing kernel patches to mainline Linux for postmarketos earlier this year. 3. The memory controller subsystem in drivers/memory used to be handled mostly by having patches through the soc tree, but without proper review from someone who understands the details of memory controllers. Krzysztof Kozlowski has now taken over maintainership and sent a good set of drivers cleanups that are part of the soc drivers branch. Overall we have a total of 864 non-merge changesets from 164 authors, with most changes coming from these developers: 90 Thierry Reding (Tegra) 58 Krzysztof Kozlowski (drivers/memory, Samsung Exynos) 39 Lad Prabhakar (Renesas) 33 Konrad Dybcio (Snapdragon based phones) 25 Daniel Palmer (Mstar SoC) 22 Marian-Cristian Rotariu (Renesas) 18 Benjamin Gaignard (STM32) 15 Suman Anna (TI OMAP) 15 Sudeep Holla (SCMI, soc-device) 15 Peng Fan (i.MX8) 14 Maxime Ripard (sunxi) 14 Geert Uytterhoeven (Renesas) 14 Anson Huang (i.MX) 13 Lubomir Rintel (MMP2/3) 13 Cristian Marussi (SCMI) 12 Rajendra Nayak (Snapdragon) 12 Bjorn Andersson (Snapdragon) 11 Martin Blumenstingl (Meson) 11 Jagan Teki (Rockchip) 10 Grygorii Strashko (TI K3) 10 Erwan Le Ray (STM32) 10 Douglas Anderson (Snapdragon) 10 Alexander A. Klimov (sed -i 's/http/https/g') The overall dirstat shows most of the changes as usual being for devicetree files, again split roughly 50:50 between 32-bit and 64-bit. Other changes are a Tegra driver update from Thierry, and some owrk on the scmi firmware code. 0.5% Documentation/devicetree/bindings/arm/ 0.4% Documentation/devicetree/bindings/reset/ 0.2% Documentation/devicetree/bindings/soc/qcom/ 0.3% Documentation/devicetree/bindings/soc/ti/ 0.3% Documentation/devicetree/bindings/ 36.1% arch/arm/boot/dts/ 0.2% arch/arm/mach-mstar/ 1.2% arch/arm/mach-omap2/ 0.4% arch/arm/mach-s3c24xx/ 1.2% arch/arm/ 0.4% arch/arm64/boot/dts/allwinner/ 0.6% arch/arm64/boot/dts/amazon/ 1.1% arch/arm64/boot/dts/amlogic/ 0.3% arch/arm64/boot/dts/exynos/ 1.0% arch/arm64/boot/dts/freescale/ 0.8% arch/arm64/boot/dts/hisilicon/ 0.3% arch/arm64/boot/dts/intel/ 1.5% arch/arm64/boot/dts/mediatek/ 0.8% arch/arm64/boot/dts/microchip/ 6.1% arch/arm64/boot/dts/nvidia/ 13.8% arch/arm64/boot/dts/qcom/ 6.0% arch/arm64/boot/dts/renesas/ 0.8% arch/arm64/boot/dts/rockchip/ 1.0% arch/arm64/boot/dts/ti/ 0.2% arch/arm64/ 4.2% drivers/firmware/arm_scmi/ 0.2% drivers/firmware/imx/ 0.2% drivers/firmware/smccc/ 0.5% drivers/firmware/tegra/ 0.2% drivers/firmware/ 10.4% drivers/memory/tegra/ 0.8% drivers/memory/ 0.4% drivers/soc/qcom/ 0.3% drivers/soc/samsung/ 0.3% drivers/soc/ti/ 0.2% drivers/soc/versatile/ 0.3% drivers/soc/ 0.5% drivers/spi/ 0.4% drivers/tty/serial/ 0.7% drivers/ 0.3% include/dt-bindings/ 0.5% include/linux/ 1.5% include/soc/tegra/ 918 files changed, 50867 insertions(+), 9369 deletions(-) Arnd