Skip to contentSkip to conversation

RaspberryPi SoC (mach) changes due for v4.2

DISCUSSION Lee Jones 3 participants 3 messages May 14, 2015 – May 15, 2015

lore
Share & tools
lore

Lee Jones

author
#0 lore raw

ARM-SoC Chaps,

The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:

Linux 4.1-rc1 (2015-04-26 17:59:10 -0700)

are available in the git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/rpi/linux-rpi.git tags/rpi-soc-for-armsoc-v4.2

for you to fetch changes up to 33a9f5bc1547b563b072b8ac1c453d861aeef0b8:

ARM: bcm2835: Move the restart/power_off handling to the WDT driver (2015-05-14 10:04:19 +0100)

----------------------------------------------------------------
RaspberryPi SoC (mach) changes due for v4.2

----------------------------------------------------------------
Eric Anholt (3):
ARM: bcm2835: Skip doing our own iotable_init() initialization
ARM: bcm2835: Drop the init_irq() hook
ARM: bcm2835: Move the restart/power_off handling to the WDT driver

 arch/arm/mach-bcm/board_bcm2835.c | 91 ---------------------------------------
 drivers/watchdog/bcm2835_wdt.c    | 62 ++++++++++++++++++++++++++
 2 files changed, 62 insertions(+), 91 deletions(-)
#1 lore raw
Quoted 6 lines · On Thursday 14 May 2015 10:25:43 Lee Jones wrote:

Eric Anholt (3):
ARM: bcm2835: Skip doing our own iotable_init() initialization
ARM: bcm2835: Drop the init_irq() hook
ARM: bcm2835: Move the restart/power_off handling to the WDT driver

Very nice!

Do you already know if the bcm2836 support will be ready in time for 4.2?

Arnd

#2 lore raw
Quoted 11 lines · Arnd Bergmann
Quoted 6 lines · On Thursday 14 May 2015 10:25:43 Lee Jones wrote:

Eric Anholt (3):
ARM: bcm2835: Skip doing our own iotable_init() initialization
ARM: bcm2835: Drop the init_irq() hook
ARM: bcm2835: Move the restart/power_off handling to the WDT driver

Very nice!

Do you already know if the bcm2836 support will be ready in time for 4.2?

For 2836 we need the firmware driver, dt-clocks driver, and extension of
the interrupt controller. I also need to rebase the 2836 series to
handle the dtsi sharing better. Unless getting review and acceptance
speeds up massively, I'd be skeptical of it even for 4.3 -- just mbox
took 2 months to land, and firmware, dt-clocks, bcm2836 intc, and
bcm2836 dtsi are each of similar scale.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150515/193a36ce/attachment-0001.sig>