From: Florian Fainelli <f.fainelli@gmail•com>
To: linux-kernel@vger•kernel.org
Cc: Mark Rutland <mark.rutland@arm•com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger•kernel.org>,
Florian Fainelli <f.fainelli@gmail•com>,
Jason Cooper <jason@lakedaemon•net>,
Marc Zyngier <maz@kernel•org>, Rob Herring <robh+dt@kernel•org>,
"maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE..."
<bcm-kernel-feedback-list@broadcom•com>,
Thomas Gleixner <tglx@linutronix•de>,
"moderated list:BROADCOM BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists•infradead.org>
Subject: [PATCH v3 0/5] irqchip/irq-bcm7038-l1 updates
Date: Thu, 24 Oct 2019 13:14:10 -0700 [thread overview]
Message-ID: <20191024201415.23454-1-f.fainelli@gmail.com> (raw)
Hi Marc, Jason, Thomas,
This patch series contains some updates from our internal tree to
support power management and allow configuring specific instances of the
brcm,bcm7038-l1-intc to leave some interrupts untouched and how the
firmware might have configured them.
Changes in v3:
- added Rob's Acked-by to dt-bindings patches
- avoid registering syscore_ops() unconditionally, do this the first we
register a controller instance
- added locking around the list handling of the controller
- ensure that irq_fwd_mask gets writtent properly to the hardware during
initial configuration and suspend/resume
- simplified logic around use of irq_fwd_mask
- added check to refuse mapping of interrupts assigned to firmware
Changes in v2:
- dropped the accidental fixup patch that made it to the list and squash
it with patch #1 as it should have
Florian Fainelli (4):
dt-bindings: Document brcm,irq-can-wake for brcm,bcm7038-l1-intc.txt
irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary
dt-bindings: Document brcm,int-fwd-mask property for bcm7038-l1-intc
irqchip/irq-bcm7038-l1: Support brcm,int-fwd-mask
Justin Chen (1):
irqchip/irq-bcm7038-l1: Add PM support
.../brcm,bcm7038-l1-intc.txt | 11 ++
drivers/irqchip/irq-bcm7038-l1.c | 119 +++++++++++++++++-
2 files changed, 128 insertions(+), 2 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-10-24 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 20:14 Florian Fainelli [this message]
2019-10-24 20:14 ` [PATCH v3 1/5] irqchip/irq-bcm7038-l1: Add PM support Florian Fainelli
2019-10-24 20:14 ` [PATCH v3 2/5] dt-bindings: Document brcm, irq-can-wake for brcm, bcm7038-l1-intc.txt Florian Fainelli
2019-10-24 20:14 ` [PATCH v3 3/5] irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary Florian Fainelli
2019-10-24 20:14 ` [PATCH v3 4/5] dt-bindings: Document brcm, int-fwd-mask property for bcm7038-l1-intc Florian Fainelli
2019-10-24 20:14 ` [PATCH v3 5/5] irqchip/irq-bcm7038-l1: Support brcm,int-fwd-mask Florian Fainelli
2019-11-11 10:52 ` [PATCH v3 0/5] irqchip/irq-bcm7038-l1 updates Marc Zyngier
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=20191024201415.23454-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail$(echo .)com \
--cc=bcm-kernel-feedback-list@broadcom$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=jason@lakedaemon$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=maz@kernel$(echo .)org \
--cc=robh+dt@kernel$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox