mbox series

[GIT,PULL] Allwinner Fixes for 5.4, take 3

Message ID 45023fa6-b2bc-4934-b85c-3e7841dde0b1.lettre@localhost (mailing list archive)
State Mainlined
Commit f129230b8c1f12e308dae89209c8b0d28136e81d
Headers show
Series [GIT,PULL] Allwinner Fixes for 5.4, take 3 | expand

Pull-request

https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-fixes-for-5.4-3

Message

Maxime Ripard Nov. 6, 2019, 12:14 p.m. UTC
Hi,

Please pull the following changes for the current release. While this
is a patch that adds a node (and thus a feature), that node was
removed in a previous fixes PR since no interrupts were working on the
PMU. This has been figured out now, so the net outcome of those two
patches are making a device that wasn't functional functional, hence
why it's in a fixes PR.

Thanks!
Maxime

The following changes since commit e690053e97e7a9c968df9a97cef9089dfa8e6a44:

  ARM: sunxi: Fix CPU powerdown on A83T (2019-10-29 09:09:56 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-fixes-for-5.4-3

for you to fetch changes up to 6b832a148717f1718f57805a9a4aa7f092582d15:

  arm64: dts: allwinner: a64: Re-add PMU node (2019-11-06 13:07:30 +0100)

----------------------------------------------------------------
One patch to add back the PMU node that was removed because the
interrupts were improper in a previous fixes PR.
----------------------------------------------------------------
Andre Przywara (1):
      arm64: dts: allwinner: a64: Re-add PMU node


 arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi |  9 +++++++++
 1 file changed, 9 insertions(+)

Comments

Olof Johansson Nov. 6, 2019, 3:41 p.m. UTC | #1
On Wed, Nov 06, 2019 at 01:14:23PM +0100, Maxime Ripard wrote:
> Hi,
> 
> Please pull the following changes for the current release. While this
> is a patch that adds a node (and thus a feature), that node was
> removed in a previous fixes PR since no interrupts were working on the
> PMU. This has been figured out now, so the net outcome of those two
> patches are making a device that wasn't functional functional, hence
> why it's in a fixes PR.

Hi,

This doesn't fix a regression, so I've queued it up for 5.5.


Thanks,

-Olof