From: guoren@kernel.org
To: marc.zyngier@arm.com, mark.rutland@arm.com, tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, jason@lakedaemon.net,
guoren@kernel.org, linux-csky@vger.kernel.org,
Guo Ren <ren_guo@c-sky.com>
Subject: [PATCH V5 0/3] irqchip/irq-csky-mpintc: Update some features
Date: Thu, 6 Jun 2019 15:37:30 +0800 [thread overview]
Message-ID: <1559806653-11249-1-git-send-email-guoren@kernel.org> (raw)
From: Guo Ren <ren_guo@c-sky.com>
Here are some patches for irq-csky-mpintc. Any feedback is welcome.
Changes for V5:
- Remove "auto irq deliver patch" in this patchset, because it has been
queued as a fix already.
- Move "remove INTCL_HPPIR define" into remove-unnecessary-loop.patch
to make patch's sequence better.
Changes for V4:
- Remove priority setting
- Add remove loop in csky_mpintc_handler in a seperate patch
- Add auto irq deliver fixup patch
- Add include file for devicetree document's example
- Add --cover-letter
Changes for V3:
- Use IRQ_TYPE_LEVEL_HIGH as default instead of IRQ_TYPE_NONE
- Remove unnecessary loop in csky_mpintc_handler
- Update commit log msg
Changes for V2:
- Fixup this_cpu_read() preempted problem
- Optimize the coding style
- Optimize #interrupt-cells to one style
Guo Ren (3):
irqchip/irq-csky-mpintc: Add triger type
dt-bindings: interrupt-controller: Update csky mpintc
irqchip/irq-csky-mpintc: Remove unnecessary loop in interrupt handler
.../bindings/interrupt-controller/csky,mpintc.txt | 20 ++++-
drivers/irqchip/irq-csky-mpintc.c | 86 ++++++++++++++++++++--
2 files changed, 95 insertions(+), 11 deletions(-)
--
2.7.4
next reply other threads:[~2019-06-06 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 7:37 guoren [this message]
2019-06-06 7:37 ` [PATCH V5 1/3] irqchip/irq-csky-mpintc: Add triger type guoren
2019-06-06 7:37 ` [PATCH V5 2/3] dt-bindings: interrupt-controller: Update csky mpintc guoren
2019-06-06 7:37 ` [PATCH V5 3/3] irqchip/irq-csky-mpintc: Remove unnecessary loop in interrupt handler guoren
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=1559806653-11249-1-git-send-email-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=ren_guo@c-sky.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).