| 2018-10-10 15:16:56 |
Paolo Pisati |
description |
Impact:
During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel:
...
[ 3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517
[ 3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to init regulator, ret=-517
[ 3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to init regulator
...
or
...
[ 4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get supply 'vdd-cdc-io': -517
[ 4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get regulator supplies -517
...
this is mainly because the DRM_MSM* and the SND_QCOM_MSM* were built-in, and tries to initialize before the voltage regulators are ready, spamming the boot log with useless noise.
These patches factor out some code as modules, so when the kmods are loaded and initialized, regulators are already present and ready to attach - all these config changes shave around ~3K bytes from dmesg, making the bootlog more clear.
Fix:
Apply the attached patches and recompile
How to test:
Boot a patched kernel and check for the above noise in dmesg
Regression potential:
None, we are just turning some code into kmods, and turning off a couple of not used feature for this flavour. |
Impact:
During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel, there's some noise like:
...
[ 3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517
[ 3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to init regulator, ret=-517
[ 3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to init regulator
...
or
...
[ 4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get supply 'vdd-cdc-io': -517
[ 4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get regulator supplies -517
...
and similar.
This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in, and tries to initialize before the voltage regulators are ready to work, resulting in a noisy bootlog.
These patches factor out some code as modules, so when the kmods are loaded and initialized, regulators are already present and ready to attach - all these config changes shave around ~3K bytes from dmesg, making the bootlog easir to parse.
Fix:
Apply the attached patches and recompile
How to test:
Boot a patched kernel and check for the above noise in dmesg
Regression potential:
None, we are just turning some code into kmods, and turning off a couple of not used feature for this flavour - all the other flavours are untouched. |
|
