mbox series

[v2,0/6] phy: qcom-qmp-combo: preparatory fixes (set 1/3)

Message ID 20221114081346.5116-1-johan+linaro@kernel.org
Headers show
Series phy: qcom-qmp-combo: preparatory fixes (set 1/3) | expand

Message

Johan Hovold Nov. 14, 2022, 8:13 a.m. UTC 
Here's a set of fixes for bugs founds while fixing the devicetree
binding and adding (proper) support for SC8280XP to the combo driver.

The full series is over forty patches and I'll be posting these in three
parts of which this is the first. In an effort to get all of these into
6.2, I'll also be submitting all three series before waiting for the
previous ones to be applied.

The first fix below could possibly be considered 6.1-rc material, but I
believe it's be fine to take all of these for 6.2.

Note that the next part of the series will do away with some of problems
with this driver that led to the issues being fixed here (e.g. the split
driver data and configuration).

Johan


Changes in v2
 - fix SW_PWRDN typo in commit message (Dmitry)
 - use the right commit for the runtime PM Fixes tag (Dmitry)


Johan Hovold (6):
  phy: qcom-qmp-combo: fix out-of-bounds clock access
  phy: qcom-qmp-combo: fix sdm845 reset
  phy: qcom-qmp-combo: fix sc8180x reset
  phy: qcom-qmp-combo: fix broken power on
  phy: qcom-qmp-combo: fix runtime suspend
  phy: qcom-qmp-combo: clean up common initialisation

 drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 91 +++++++++++------------
 1 file changed, 44 insertions(+), 47 deletions(-)

Comments

Vinod Koul Nov. 24, 2022, 3:33 p.m. UTC | #1 
On 14-11-22, 09:13, Johan Hovold wrote:
> Here's a set of fixes for bugs founds while fixing the devicetree
> binding and adding (proper) support for SC8280XP to the combo driver.
> 
> The full series is over forty patches and I'll be posting these in three
> parts of which this is the first. In an effort to get all of these into
> 6.2, I'll also be submitting all three series before waiting for the
> previous ones to be applied.
> 
> The first fix below could possibly be considered 6.1-rc material, but I
> believe it's be fine to take all of these for 6.2.
> 
> Note that the next part of the series will do away with some of problems
> with this driver that led to the issues being fixed here (e.g. the split
> driver data and configuration).

Applied, thanks