linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: [RFC PATCH 0/2] irqchip/ti-sci-intr: Add support for INTR connecting to INTR
Date: Mon, 23 Sep 2019 09:54:03 +0530	[thread overview]
Message-ID: <20190923042405.26064-1-lokeshvutla@ti.com> (raw)

This series updates the driver and dt-bindings to accept INTR being a
parent to INTR and drop all the firmware related bindings.

Lokesh Vutla (2):
  dt-bindings: irqchip: Update bindings to drop the usage of gic as
    parent
  irqchip/ti-sci-intr: Add support for INTR being a parent to INTR

 .../interrupt-controller/ti,sci-intr.txt      |  28 ++--
 drivers/irqchip/irq-ti-sci-intr.c             | 137 +++++++++++-------
 2 files changed, 95 insertions(+), 70 deletions(-)

-- 
2.22.0


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

             reply	other threads:[~2019-09-23  4:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23  4:24 Lokesh Vutla [this message]
2019-09-23  4:24 ` [RFC PATCH 1/2] dt-bindings: irqchip: Update bindings to drop the usage of gic as parent Lokesh Vutla
2019-10-02 12:57   ` Marc Zyngier
2019-10-03 13:15     ` Lokesh Vutla
2019-10-09  5:00       ` Lokesh Vutla
2019-10-24 10:22         ` Lokesh Vutla
2019-10-25 10:46           ` Marc Zyngier
2019-10-25 16:07   ` Peter Ujfalusi
2019-10-29  6:20     ` Lokesh Vutla
2019-09-23  4:24 ` [RFC PATCH 2/2] irqchip/ti-sci-intr: Add support for INTR being a parent to INTR Lokesh Vutla
2019-10-02 13:12   ` Marc Zyngier
2019-10-04  3:37     ` Lokesh Vutla

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=20190923042405.26064-1-lokeshvutla@ti.com \
    --to=lokeshvutla@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=nm@ti.com \
    /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).