Message ID | 20220105172618.302522-1-p.zabel@pengutronix.de |
---|---|
State | New |
Headers | show |
Series | [GIT,PULL] Reset controller updates vor v5.17 | expand |
On Wed, Jan 5, 2022 at 6:26 PM Philipp Zabel <p.zabel@pengutronix.de> wrote: > > Dear arm-soc maintainers, > > The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf: > > Linux 5.16-rc1 (2021-11-14 13:56:52 -0800) > > are available in the Git repository at: > > git://git.pengutronix.de/pza/linux.git tags/reset-for-v5.17 > > for you to fetch changes up to 89e7a6698fdd6d0cccf5bab11abc51f813944cd8: > > reset: uniphier-glue: Use devm_add_action_or_reset() (2021-12-16 09:59:55 +0100) > > ---------------------------------------------------------------- > Reset controller updates vor v5.17 > > Add an optional variant of of_reset_control_get_exclusive(), document > a deprecated hi3660-reset device tree property, check whether reset > deassertion worked in the reset-rzg2l-usbphy-ctrl driver, and simplify > the uniphier-glue driver a bit. Hi Philipp, As you probably noticed, we made a mistake here and this branch ended up not making it into v5.17-rc1, sorry about that. As far as I can tell, there are three bugfixes that we probably want in v5.17 after all, but the of_reset_control_get_optional_exclusive() interface is probably v5.18 material, as this is not a bugfix. If you like, I can cherry-pick the contents into the 5.17 fixes branch and the 5.18 drivers branch, or you can send me updated pull requests that incorporate more changes you have already queued. Please let me know how you would like to proceed. Arnd
Hi Arnd, On Tue, 2022-02-08 at 11:06 +0100, Arnd Bergmann wrote: On Wed, Jan 5, 2022 at 6:26 PM Philipp Zabel <p.zabel@pengutronix.de> wrote: > > Dear arm-soc maintainers, > > The following changes since commit > fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf: > > Linux 5.16-rc1 (2021-11-14 13:56:52 -0800) > > are available in the Git repository at: > > git://git.pengutronix.de/pza/linux.git tags/reset-for-v5.17 > > for you to fetch changes up to > 89e7a6698fdd6d0cccf5bab11abc51f813944cd8: > > reset: uniphier-glue: Use devm_add_action_or_reset() (2021-12-16 > 09:59:55 +0100) > > ---------------------------------------------------------------- > Reset controller updates vor v5.17 > > Add an optional variant of of_reset_control_get_exclusive(), > document > a deprecated hi3660-reset device tree property, check whether reset > deassertion worked in the reset-rzg2l-usbphy-ctrl driver, and > simplify > the uniphier-glue driver a bit. Hi Philipp, As you probably noticed, we made a mistake here and this branch ended up not making it into v5.17-rc1, sorry about that. Thank you for the notice. I was on vacation, blissfully unaware :) > As far as I can tell, there are three bugfixes that we probably want > in v5.17 after all, but the of_reset_control_get_optional_exclusive() > interface is probably v5.18 material, as this is not a bugfix. That one already made its way into v5.17-rc1 via timers, commit 863298738076 ("Merge branch 'reset/of-get-optional-exclusive' of git://git.pengutronix.de/pza/linux into timers/drivers/next"). There are no dependencies on it in the reset queue, so I think we can just drop it, no furter action required. > If you like, I can cherry-pick the contents into the 5.17 fixes > branch > and the 5.18 drivers branch, or you can send me updated pull > requests that incorporate more changes you have already queued. > > Please let me know how you would like to proceed. Could you pick up these two commits: 5e23c1ec4347 ("reset: renesas: Check return value of reset_control_deassert()") f90f1bbe0d70 ("dt-bindings: reset: document deprecated HiSilicon property") into v5.17 fixes? The remaining two commits: 89e7a6698fdd ("reset: uniphier-glue: Use devm_add_action_or_reset()") 9568d0259fec ("reset: uniphier-glue: Use reset_control_bulk API") are not really bugfixes, I'd just move them over into my for-v5.18 queue and send them again with the next pull request. regards Philipp
Hi Arnd, On Mi, 2022-02-16 at 17:51 +0100, Philipp Zabel wrote: > > Please let me know how you would like to proceed. > > Could you pick up these two commits: > 5e23c1ec4347 ("reset: renesas: Check return value of reset_control_deassert()") > f90f1bbe0d70 ("dt-bindings: reset: document deprecated HiSilicon property") > into v5.17 fixes? I have sent a pull request [1] containing these two now. [1] https://lore.kernel.org/all/20220406153337.1265414-1-p.zabel@pengutronix.de/ regards Philipp