All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Palmer <daniel@0x0f.com>
To: linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, arnd@arndb.de, maz@kernel.org,
	Daniel Palmer <daniel@0x0f.com>,
	linux-kernel@vger.kernel.org, mark-pk.tsai@mediatek.com
Subject: [PATCH 0/3] ARM: mstar: wire up interrupt controllers
Date: Fri, 18 Sep 2020 19:49:46 +0900	[thread overview]
Message-ID: <20200918104949.3260823-1-daniel@0x0f.com> (raw)

Mark-PK Tsai's driver for the MStar interrupt
controller should be going into 5.10[0].

This small series selects the driver when building
support for MStar/SigmaStar Arm v7 SoCs, adds the
instances of it to the base dtsi and wires up the
interrupt for pm_uart.

0 - https://lore.kernel.org/linux-arm-kernel/87lfhdr7l6.wl-maz@kernel.org/

Daniel Palmer (3):
  ARM: mstar: Select MStar intc
  ARM: mstar: Add interrupt controller to base dtsi
  ARM: mstar: Add interrupt to pm_uart

 arch/arm/boot/dts/mstar-v7.dtsi | 20 ++++++++++++++++++++
 arch/arm/mach-mstar/Kconfig     |  1 +
 2 files changed, 21 insertions(+)

-- 
2.27.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Palmer <daniel@0x0f.com>
To: linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, mark-pk.tsai@mediatek.com,
	arnd@arndb.de, maz@kernel.org, linux-kernel@vger.kernel.org,
	Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH 0/3] ARM: mstar: wire up interrupt controllers
Date: Fri, 18 Sep 2020 19:49:46 +0900	[thread overview]
Message-ID: <20200918104949.3260823-1-daniel@0x0f.com> (raw)

Mark-PK Tsai's driver for the MStar interrupt
controller should be going into 5.10[0].

This small series selects the driver when building
support for MStar/SigmaStar Arm v7 SoCs, adds the
instances of it to the base dtsi and wires up the
interrupt for pm_uart.

0 - https://lore.kernel.org/linux-arm-kernel/87lfhdr7l6.wl-maz@kernel.org/

Daniel Palmer (3):
  ARM: mstar: Select MStar intc
  ARM: mstar: Add interrupt controller to base dtsi
  ARM: mstar: Add interrupt to pm_uart

 arch/arm/boot/dts/mstar-v7.dtsi | 20 ++++++++++++++++++++
 arch/arm/mach-mstar/Kconfig     |  1 +
 2 files changed, 21 insertions(+)

-- 
2.27.0


             reply	other threads:[~2020-09-18 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 10:49 Daniel Palmer [this message]
2020-09-18 10:49 ` [PATCH 0/3] ARM: mstar: wire up interrupt controllers Daniel Palmer
2020-09-18 10:49 ` [PATCH 1/3] ARM: mstar: Select MStar intc Daniel Palmer
2020-09-18 10:49   ` Daniel Palmer
2020-09-18 10:49 ` [PATCH 2/3] ARM: mstar: Add interrupt controller to base dtsi Daniel Palmer
2020-09-18 10:49   ` Daniel Palmer
2020-09-18 10:49 ` [PATCH 3/3] ARM: mstar: Add interrupt to pm_uart Daniel Palmer
2020-09-18 10:49   ` Daniel Palmer
2020-09-18 11:34 ` [PATCH 0/3] ARM: mstar: wire up interrupt controllers Arnd Bergmann
2020-09-18 11:34   ` Arnd Bergmann
2020-09-18 11:43   ` Daniel Palmer
2020-09-18 11:43     ` Daniel Palmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200918104949.3260823-1-daniel@0x0f.com \
    --to=daniel@0x0f.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark-pk.tsai@mediatek.com \
    --cc=maz@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.