Add initial support for BQ Aquaris X5
cover Add initial support for BQ Aquaris X5
Aquaris X5 (Longcheer L8910) is a smartphone released by BQ in 2015.
As part of msm8916-mainline project, this series aims to bring initial mainline support for it.
Features added:
- SDHCI (internal and external storage)
- USB Device Mode
- UART
- Regulators
- WiFi/BT
- Volume buttons
- Vibrator
- Touchkeys backlight
- Accelerometer and gyroscope sensor
- Magnetometer sensor
Jonathan Albrieux (3):
arm64: dts: qcom: Add device tree for BQ Aquaris X5 (Longcheer L8910)
arm64: dts: qcom: msm8916: Add blsp_i2c3
arm64: dts: qcom: msm8916-longcheer-l8910: Add imu/magnetometer
arch/arm64/boot/dts/qcom/Makefile | 1 + .../boot/dts/qcom/msm8916-longcheer-l8910.dts | 267 ++++++++++++++++++ arch/arm64/boot/dts/qcom/msm8916-pins.dtsi | 16 ++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 15 + 4 files changed, 299 insertions(+) create mode 100644 arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts
Signature · 1 line
2.17.1
PATCH 1/3 arm64: dts: qcom: Add device tree for BQ Aquaris X5 (Longcheer L8910)
BQ Aquaris X5 (Longcheer L8910) is a smartphone using the MSM8916 SoC.
Add device tree with initial support for:
- SDHCI (internal and external storage)
- USB Device Mode
- UART
- Regulators
- WiFi/BT
- Volume buttons
- Vibrator
- Touchkeys backlight
This device tree is based on downstream device tree from BQ and from Longcheer L8915 device tree.
--- arch/arm64/boot/dts/qcom/Makefile | 1 + .../boot/dts/qcom/msm8916-longcheer-l8910.dts | 230 ++++++++++++++++++ 2 files changed, 231 insertions(+) create mode 100644 arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts
arch/arm64/boot/dts/qcom/Makefile +1 -0
@@ -6,6 +6,7 @@ dtb-$(CONFIG_ARCH_QCOM) += ipq6018-cp01-c1.dtb dtb-$(CONFIG_ARCH_QCOM) += ipq8074-hk01.dtb dtb-$(CONFIG_ARCH_QCOM) += msm8916-asus-z00l.dtb dtb-$(CONFIG_ARCH_QCOM) += msm8916-longcheer-l8150.dtb +dtb-$(CONFIG_ARCH_QCOM) += msm8916-longcheer-l8910.dtb dtb-$(CONFIG_ARCH_QCOM) += msm8916-mtp.dtb dtb-$(CONFIG_ARCH_QCOM) += msm8916-samsung-a3u-eur.dtb dtb-$(CONFIG_ARCH_QCOM) += msm8916-samsung-a5u-eur.dtb
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts new file +230 -0
230 lines not on this page · raw message
Signature · 1 line
2.17.1
Re: [PATCH 1/3] arm64: dts: qcom: Add device tree for BQ Aquaris X5 (Longcheer L8910)
The sorting on smd_rpm_regulators & msmgpio seems off.. unless it's the new thing to put it at the end?
Also, did you forget the copyright header or is that on purpose?
Otherwise, LGTM
Konrad
Re: [PATCH 1/3] arm64: dts: qcom: Add device tree for BQ Aquaris X5 (Longcheer L8910)
Quoted 2 lines · Konrad Dybcio
The sorting on
smd_rpm_regulators& msmgpio seems off.. unless it's the new thing to put it at the end?
It's consistent like this for all MSM8916 device trees at least.
Back when I converted them I thought that it's kind of annoying to have this large list of regulators and pinctrl placed right inbetween all other device definitions. And it's even worse for apq8016-sbc.dtsi which has this large list of gpio-line-names. It just makes it harder to see the actual interesting definitions (new devices etc) in my opinion.
I think I mentioned this in my patch description back then and Bjorn did not complain. :-)
But I understand this may be somewhat inconsistent with other qcom device trees at the moment, so I suppose I would be fine with a patch to order them entirely alphabetically.
(As long as it's consistent for all MSM8916 device trees...)
Thanks,
Stephan
PATCH 2/3 arm64: dts: qcom: msm8916: Add blsp_i2c3
In reply to Jonathan AlbrieuxMSM8916 has another I2C QUP controller that can be enabled on GPIO 10 and 11.
Add blsp_i2c3 to msm8916.dtsi and disable it by default.
--- arch/arm64/boot/dts/qcom/msm8916-pins.dtsi | 16 ++++++++++++++++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 15 +++++++++++++++ 2 files changed, 31 insertions(+)
arch/arm64/boot/dts/qcom/msm8916-pins.dtsi +16 -0
@@ -220,6 +220,22 @@ bias-disable; }; + i2c3_default: i2c3-default { + pins = "gpio10", "gpio11"; + function = "blsp_i2c3"; + + drive-strength = <2>; + bias-disable; + }; + + i2c3_sleep: i2c3-sleep { + pins = "gpio10", "gpio11"; + function = "gpio"; + + drive-strength = <2>; + bias-disable; + }; + i2c4_default: i2c4-default { pins = "gpio14", "gpio15"; function = "blsp_i2c4";
arch/arm64/boot/dts/qcom/msm8916.dtsi +15 -0
@@ -1528,6 +1528,21 @@ status = "disabled"; }; + blsp_i2c3: i2c@78b7000 { + compatible = "qcom,i2c-qup-v2.2.1"; + reg = <0x078b7000 0x500>; + interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&gcc GCC_BLSP1_AHB_CLK>, + <&gcc GCC_BLSP1_QUP3_I2C_APPS_CLK>; + clock-names = "iface", "core"; + pinctrl-names = "default", "sleep"; + pinctrl-0 = <&i2c3_default>; + pinctrl-1 = <&i2c3_sleep>; + #address-cells = <1>; + #size-cells = <0>; + status = "disabled"; + }; + blsp_spi3: spi@78b7000 { compatible = "qcom,spi-qup-v2.2.1"; reg = <0x078b7000 0x500>;
Signature · 1 line
2.17.1
Re: [PATCH 2/3] arm64: dts: qcom: msm8916: Add blsp_i2c3
Quoted 55 lines · Jonathan Albrieux
MSM8916 has another I2C QUP controller that can be enabled on GPIO 10 and 11.
Add
blsp_i2c3tomsm8916.dtsiand disable it by default.Signed-off-by Jonathan Albrieux <[email protected]>--- arch/arm64/boot/dts/qcom/msm8916-pins.dtsi | 16 ++++++++++++++++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 15 +++++++++++++++ 2 files changed, 31 insertions(+)arch/arm64/boot/dts/qcom/msm8916-pins.dtsi +16
-0@@ -220,6 +220,22 @@ bias-disable; }; + i2c3_default: i2c3-default { + pins = "gpio10", "gpio11"; + function = "blsp_i2c3"; + + drive-strength = <2>; + bias-disable; + }; + + i2c3_sleep: i2c3-sleep { + pins = "gpio10", "gpio11"; + function = "gpio"; + + drive-strength = <2>; + bias-disable; + }; + i2c4_default: i2c4-default { pins = "gpio14", "gpio15"; function = "blsp_i2c4";arch/arm64/boot/dts/qcom/msm8916.dtsi +8
-0@@ -1528,6 +1528,21 @@ status = "disabled"; }; + blsp_i2c3: i2c@78b7000 { + compatible = "qcom,i2c-qup-v2.2.1"; + reg = <0x078b7000 0x500>; + interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&gcc GCC_BLSP1_AHB_CLK>, + <&gcc GCC_BLSP1_QUP3_I2C_APPS_CLK>; + clock-names = "iface", "core"; + pinctrl-names = "default", "sleep";
arch/arm64/boot/dts/qcom/msm8916.dtsi line 1548
Quoted 10 lines
arch/arm64/boot/dts/qcom/msm8916.dtsi +7
-0+ pinctrl-0 = <&i2c3_default>; + pinctrl-1 = <&i2c3_sleep>; + #address-cells = <1>; + #size-cells = <0>; + status = "disabled"; + }; + blsp_spi3: spi@78b7000 { compatible = "qcom,spi-qup-v2.2.1"; reg = <0x078b7000 0x500>;
Things to consider for the future:
* DMA on I2C
* Merging in the -pins.dtsi to 8916.dtsi?
Konrad
Re: [PATCH 2/3] arm64: dts: qcom: msm8916: Add blsp_i2c3
In reply to Jonathan AlbrieuxQuoted 6 lines · Jonathan Albrieux
MSM8916 has another I2C QUP controller that can be enabled on GPIO 10 and 11.
Add
blsp_i2c3tomsm8916.dtsiand disable it by default.Signed-off-by Jonathan Albrieux <[email protected]>
Quoted 61 lines
--- arch/arm64/boot/dts/qcom/msm8916-pins.dtsi | 16 ++++++++++++++++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 15 +++++++++++++++ 2 files changed, 31 insertions(+)arch/arm64/boot/dts/qcom/msm8916-pins.dtsi +16
-0@@ -220,6 +220,22 @@ bias-disable; }; + i2c3_default: i2c3-default { + pins = "gpio10", "gpio11"; + function = "blsp_i2c3"; + + drive-strength = <2>; + bias-disable; + }; + + i2c3_sleep: i2c3-sleep { + pins = "gpio10", "gpio11"; + function = "gpio"; + + drive-strength = <2>; + bias-disable; + }; + i2c4_default: i2c4-default { pins = "gpio14", "gpio15"; function = "blsp_i2c4";arch/arm64/boot/dts/qcom/msm8916.dtsi +15
-0@@ -1528,6 +1528,21 @@ status = "disabled"; }; + blsp_i2c3: i2c@78b7000 { + compatible = "qcom,i2c-qup-v2.2.1"; + reg = <0x078b7000 0x500>; + interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&gcc GCC_BLSP1_AHB_CLK>, + <&gcc GCC_BLSP1_QUP3_I2C_APPS_CLK>; + clock-names = "iface", "core"; + pinctrl-names = "default", "sleep"; + pinctrl-0 = <&i2c3_default>; + pinctrl-1 = <&i2c3_sleep>; + #address-cells = <1>; + #size-cells = <0>; + status = "disabled"; + }; + blsp_spi3: spi@78b7000 { compatible = "qcom,spi-qup-v2.2.1"; reg = <0x078b7000 0x500>;Signature · 1 line
2.17.1
PATCH 3/3 arm64: dts: qcom: msm8916-longcheer-l8910: Add imu/magnetometer
In reply to Jonathan AlbrieuxBQ Aquaris X5 (Longcheer L8910) has:
- BMI160 accelerometer and gyroscope sensor
- AK09911 magnetometer sensor
Add them to the device tree.
This patch depends on patch "arm64: dts: qcom: msm8916: Add blsp_i2c3".
--- .../boot/dts/qcom/msm8916-longcheer-l8910.dts | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+)
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +37 -0
@@ -56,6 +56,35 @@ }; }; +&blsp_i2c3 { + status = "okay"; + + imu@68 { + compatible = "bosch,bmi160"; + reg = <0x68>; + + vdd-supply = <&pm8916_l17>; + vddio-supply = <&pm8916_l6>; + + mount-matrix = "0", "1", "0", + "-1", "0", "0", + "0", "0", "1"; + }; + + magnetometer@d { + compatible = "asahi-kasei,ak09911"; + reg = <0x0d>; + + vdd-supply = <&pm8916_l17>; + vid-supply = <&pm8916_l6>; + + reset-gpios = <&msmgpio 111 GPIO_ACTIVE_LOW>; + + pinctrl-names = "default"; + pinctrl-0 = <&mag_reset_default>; + }; +}; + &blsp1_uart2 { status = "okay"; };
@@ -220,6 +249,14 @@ bias-pull-up; }; + mag_reset_default: mag-reset-default { + pins = "gpio111"; + function = "gpio"; + + drive-strength = <2>; + bias-disable; + }; + usb_id_default: usb-id-default { pins = "gpio110"; function = "gpio";
Signature · 1 line
2.17.1
Re: [PATCH 3/3] arm64: dts: qcom: msm8916-longcheer-l8910: Add imu/magnetometer
Quoted 20 lines
+&blsp_i2c3 {
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +17
-0+ status = "okay"; + + imu@68 { + compatible = "bosch,bmi160"; + reg = <0x68>; + + vdd-supply = <&pm8916_l17>; + vddio-supply = <&pm8916_l6>; + + mount-matrix = "0", "1", "0", + "-1", "0", "0", + "0", "0", "1"; + }; + + magnetometer@d { + compatible = "asahi-kasei,ak09911"; + reg = <0x0d>;
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts line 86
Quoted 10 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +10
-0+ + vdd-supply = <&pm8916_l17>; + vid-supply = <&pm8916_l6>; + + reset-gpios = <&msmgpio 111 GPIO_ACTIVE_LOW>; + + pinctrl-names = "default"; + pinctrl-0 = <&mag_reset_default>; + }; +};
Please sort I2C devices by their address.
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts line 259
Quoted 10 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +8
-0}; + mag_reset_default: mag-reset-default { + pins = "gpio111"; + function = "gpio"; + + drive-strength = <2>; + bias-disable; + }; +
Please add this after gpio110 to keep it sorted gpio-number-wise.
Konrad
Re: [PATCH 3/3] arm64: dts: qcom: msm8916-longcheer-l8910: Add imu/magnetometer
Quoted 22 lines · Konrad Dybcio
Quoted 22 lines
+&blsp_i2c3 {
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +21
-0+ status = "okay"; + + imu@68 { + compatible = "bosch,bmi160"; + reg = <0x68>; + + vdd-supply = <&pm8916_l17>; + vddio-supply = <&pm8916_l6>; + + mount-matrix = "0", "1", "0", + "-1", "0", "0", + "0", "0", "1"; + }; + + magnetometer@d { + compatible = "asahi-kasei,ak09911"; + reg = <0x0d>; + + vdd-supply = <&pm8916_l17>; + vid-supply = <&pm8916_l6>; +
Quoted 9 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts line 86
Quoted 6 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +6
-0+ reset-gpios = <&msmgpio 111 GPIO_ACTIVE_LOW>; + + pinctrl-names = "default"; + pinctrl-0 = <&mag_reset_default>; + }; +};Please sort I2C devices by their address.
+1 :)
Quoted 14 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts line 259
Quoted 11 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +8
-0}; + mag_reset_default: mag-reset-default { + pins = "gpio111"; + function = "gpio"; + + drive-strength = <2>; + bias-disable; + }; +Please add this after gpio110 to keep it sorted gpio-number-wise.
This is ordered alphabetically. I haven't seen gpio-number order anywhere yet... :)
Thanks,
Stephan
Re: [PATCH 3/3] arm64: dts: qcom: msm8916-longcheer-l8910: Add imu/magnetometer
Quoted 33 lines · Stephan Gerhold
Quoted 22 lines · Konrad Dybcio
Quoted 22 lines
+&blsp_i2c3 {
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +21
-0+ status = "okay"; + + imu@68 { + compatible = "bosch,bmi160"; + reg = <0x68>; + + vdd-supply = <&pm8916_l17>; + vddio-supply = <&pm8916_l6>; + + mount-matrix = "0", "1", "0", + "-1", "0", "0", + "0", "0", "1"; + }; + + magnetometer@d { + compatible = "asahi-kasei,ak09911"; + reg = <0x0d>; + + vdd-supply = <&pm8916_l17>; + vid-supply = <&pm8916_l6>; +Quoted 9 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts line 86
Quoted 6 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +6
-0+ reset-gpios = <&msmgpio 111 GPIO_ACTIVE_LOW>; + + pinctrl-names = "default"; + pinctrl-0 = <&mag_reset_default>; + }; +};Please sort I2C devices by their address.
Quoted 2 lines
+1 :)
Thank you Konrad, thank you Stephan, I'll fix the order!
Quoted 15 lines
Quoted 14 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts line 259
Quoted 11 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +8
-0}; + mag_reset_default: mag-reset-default { + pins = "gpio111"; + function = "gpio"; + + drive-strength = <2>; + bias-disable; + }; +Please add this after gpio110 to keep it sorted gpio-number-wise.
Quoted 3 lines
This is ordered alphabetically. I haven't seen gpio-number order anywhere yet... :)
Let me know if this order has to be changed, meanwhile I'll prepare a v2 for the i2c device order and will prepare a v3 in case this order too has to be changed.
Again, thank you,
Jonathan
Quoted 2 lines
Thanks,
Stephan
Re: [PATCH 3/3] arm64: dts: qcom: msm8916-longcheer-l8910: Add imu/magnetometer
Quoted 53 lines · Jonathan Albrieux
Quoted 33 lines · Stephan Gerhold
Quoted 22 lines · Konrad Dybcio
Quoted 22 lines
+&blsp_i2c3 {
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +21
-0+ status = "okay"; + + imu@68 { + compatible = "bosch,bmi160"; + reg = <0x68>; + + vdd-supply = <&pm8916_l17>; + vddio-supply = <&pm8916_l6>; + + mount-matrix = "0", "1", "0", + "-1", "0", "0", + "0", "0", "1"; + }; + + magnetometer@d { + compatible = "asahi-kasei,ak09911"; + reg = <0x0d>; + + vdd-supply = <&pm8916_l17>; + vid-supply = <&pm8916_l6>; +Quoted 9 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts line 86
Quoted 6 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +6
-0+ reset-gpios = <&msmgpio 111 GPIO_ACTIVE_LOW>; + + pinctrl-names = "default"; + pinctrl-0 = <&mag_reset_default>; + }; +};Please sort I2C devices by their address.
Quoted 2 lines
+1 :)
Thank you Konrad, thank you Stephan, I'll fix the order!
Quoted 15 lines
Quoted 14 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts line 259
Quoted 11 lines
arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910.dts +8
-0}; + mag_reset_default: mag-reset-default { + pins = "gpio111"; + function = "gpio"; + + drive-strength = <2>; + bias-disable; + }; +Please add this after gpio110 to keep it sorted gpio-number-wise.
Quoted 7 lines
Quoted 3 lines
This is ordered alphabetically. I haven't seen gpio-number order anywhere yet... :)
Let me know if this order has to be changed, meanwhile I'll prepare a v2 for the i2c device order and will prepare a v3 in case this order too has to be changed.
I'm happy with having these sorted alphabetically.
Regards,
Bjorn
Hi!
Quoted 4 lines
Aquaris X5 (Longcheer L8910) is a smartphone released by BQ in 2015.
As part of msm8916-mainline project, this series aims to bring initial mainline support for it.
Good to see another phone being supported. Can I ask you to cc:
[email protected] with phone stuff?
Quoted 11 lines
Features added:
- SDHCI (internal and external storage)
- USB Device Mode
- UART
- Regulators
- WiFi/BT
- Volume buttons
- Vibrator
- Touchkeys backlight
- Accelerometer and gyroscope sensor
- Magnetometer sensor
How close are you to having useful phone calls?
Best regards,
Pavel
Signature · 1 line
http://www.livejournal.com/~pavelmachek
Hi Pavel,
Quoted 22 lines · Pavel Machek
Hi!
Quoted 4 lines
Aquaris X5 (Longcheer L8910) is a smartphone released by BQ in 2015.
As part of msm8916-mainline project, this series aims to bring initial mainline support for it.
Good to see another phone being supported. Can I ask you to cc:
[email protected] with phone stuff?Quoted 11 lines
Features added:
- SDHCI (internal and external storage)
- USB Device Mode
- UART
- Regulators
- WiFi/BT
- Volume buttons
- Vibrator
- Touchkeys backlight
- Accelerometer and gyroscope sensor
- Magnetometer sensor
Quoted 2 lines
How close are you to having useful phone calls?
You can do phone calls (with audio) and you can use mobile data, if you have the patches for that. :) I'm trying to find time to finish up the drivers needed for that, but I've been a bit short on time lately.
Actually we have come pretty far with MSM8916-based smartphones. Most functionality is (somewhat) working at this point, the primary open task is optimizing suspend/power consumption. Battery/charging and camera is also tricky but works somewhat on some of the devices.
Most of the functionality is packaged in postmarketOS [1] and you can find a list of the devices in the postmarketOS wiki [2]. Especially the ones in the "community" category are quite similar in terms of working functionality.
Stephan
[1]: https://postmarketos.org
[2]: https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_410/412_(MSM8916)
Hi!
Quoted 20 lines
Quoted 20 lines
Quoted 4 lines
Aquaris X5 (Longcheer L8910) is a smartphone released by BQ in 2015.
As part of msm8916-mainline project, this series aims to bring initial mainline support for it.
Good to see another phone being supported. Can I ask you to cc:
[email protected] with phone stuff?Quoted 11 lines
Features added:
- SDHCI (internal and external storage)
- USB Device Mode
- UART
- Regulators
- WiFi/BT
- Volume buttons
- Vibrator
- Touchkeys backlight
- Accelerometer and gyroscope sensor
- Magnetometer sensor
Quoted 5 lines
Quoted 1 line
How close are you to having useful phone calls?
You can do phone calls (with audio) and you can use mobile data, if you have the patches for that. :) I'm trying to find time to finish up the drivers needed for that, but I've been a bit short on time lately.
:-).
Quoted 4 lines
Actually we have come pretty far with MSM8916-based smartphones. Most functionality is (somewhat) working at this point, the primary open task is optimizing suspend/power consumption. Battery/charging and camera is also tricky but works somewhat on some of the devices.
Yes, power consumption is a lot of fun :-(.
Quoted 4 lines
Most of the functionality is packaged in postmarketOS [1] and you can find a list of the devices in the postmarketOS wiki [2]. Especially the ones in the "community" category are quite similar in terms of working functionality.
I know about postmarketOS (I even contributed a bit some time ago), and watch it from time to time. Currently I'm using old Nokia 6151 for phone calls, but would not mind switching. Work is ongoing in Droid 4 land -- phone calls are also "almost there". But the almost seems to be a lot of work :-(.
Best regards,
Pavel
Signature · 1 line
http://www.livejournal.com/~pavelmachek
Quoted 11 lines · Pavel Machek
Quoted 10 lines
Quoted 1 line
How close are you to having useful phone calls?
You can do phone calls (with audio) and you can use mobile data, if you have the patches for that. :) I'm trying to find time to finish up the drivers needed for that, but I've been a bit short on time lately.
Most of the functionality is packaged in postmarketOS [1] and you can find a list of the devices in the postmarketOS wiki [2]. Especially the ones in the "community" category are quite similar in terms of working functionality.
Quoted 6 lines
I know about postmarketOS (I even contributed a bit some time ago), and watch it from time to time. Currently I'm using old Nokia 6151 for phone calls, but would not mind switching. Work is ongoing in Droid 4 land -- phone calls are also "almost there". But the almost seems to be a lot of work :-(.
It's fairly simple on Qualcomm SoCs once audio DSP and modem are working (which is not that simple). I basically just tell the audio DSP to stream voice call audio to the audio ports and then it does that without involving the kernel.
It seems to work quite well, so far no one complained about quality or something like that. Not sure if anyone is actively using it already though :)
The work left is mainly making the driver more generic so it can work on other Qualcomm SoCs as well (right now I have some things hardcoded). Also, I still haven't fully figured out what is the best way to integrate it into ASoC/UCM/..., so that it can be easily activated when starting a voice call.
Stephan
Hi!
Quoted 18 lines
Quoted 11 lines
Quoted 10 lines
Quoted 1 line
How close are you to having useful phone calls?
You can do phone calls (with audio) and you can use mobile data, if you have the patches for that. :) I'm trying to find time to finish up the drivers needed for that, but I've been a bit short on time lately.
Most of the functionality is packaged in postmarketOS [1] and you can find a list of the devices in the postmarketOS wiki [2]. Especially the ones in the "community" category are quite similar in terms of working functionality.
Quoted 6 lines
I know about postmarketOS (I even contributed a bit some time ago), and watch it from time to time. Currently I'm using old Nokia 6151 for phone calls, but would not mind switching. Work is ongoing in Droid 4 land -- phone calls are also "almost there". But the almost seems to be a lot of work :-(.
Quoted 8 lines
It's fairly simple on Qualcomm SoCs once audio DSP and modem are working (which is not that simple). I basically just tell the audio DSP to stream voice call audio to the audio ports and then it does that without involving the kernel.
It seems to work quite well, so far no one complained about quality or something like that. Not sure if anyone is actively using it already though :)
Ok, thanks for info :-).
Quoted 5 lines
The work left is mainly making the driver more generic so it can work on other Qualcomm SoCs as well (right now I have some things hardcoded). Also, I still haven't fully figured out what is the best way to integrate it into ASoC/UCM/..., so that it can be easily activated when starting a voice call.
On droid 4, we use mixer settings to configure audio system for a call. Maemo Leste has some kind of component to automatically adjust mixers when call is started. We use ofonod.
Best regards,
Pavel
Signature · 1 line
http://www.livejournal.com/~pavelmachek