All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
Cc: devicetree@vger.kernel.org, alix.wu@mediatek.com,
	jason@lakedaemon.net, yj.chiang@mediatek.com, daniel@0x0f.com,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org,
	linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com,
	tglx@linutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] Add MStar interrupt controller support
Date: Sun, 13 Sep 2020 16:59:17 +0100	[thread overview]
Message-ID: <87lfhdr7l6.wl-maz@kernel.org> (raw)
In-Reply-To: <20200902063344.1852-1-mark-pk.tsai@mediatek.com>

On Wed, 02 Sep 2020 07:33:42 +0100,
Mark-PK Tsai <mark-pk.tsai@mediatek.com> wrote:
> 
> MStar contain a legacy interrupt controller that routes interrupts
> to the GIC. SigmaStar and Mediatek TV SoCs also have this interrupt
> controller IP.
> 
> Mark-PK Tsai (2):
>   irqchip: irq-mst: Add MStar interrupt controller support
>   dt-bindings: interrupt-controller: Add MStar interrupt controller

Once the binding gets approved, I'll queue this for 5.10.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
Cc: devicetree@vger.kernel.org, alix.wu@mediatek.com,
	jason@lakedaemon.net, yj.chiang@mediatek.com, daniel@0x0f.com,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org,
	linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com,
	tglx@linutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] Add MStar interrupt controller support
Date: Sun, 13 Sep 2020 16:59:17 +0100	[thread overview]
Message-ID: <87lfhdr7l6.wl-maz@kernel.org> (raw)
In-Reply-To: <20200902063344.1852-1-mark-pk.tsai@mediatek.com>

On Wed, 02 Sep 2020 07:33:42 +0100,
Mark-PK Tsai <mark-pk.tsai@mediatek.com> wrote:
> 
> MStar contain a legacy interrupt controller that routes interrupts
> to the GIC. SigmaStar and Mediatek TV SoCs also have this interrupt
> controller IP.
> 
> Mark-PK Tsai (2):
>   irqchip: irq-mst: Add MStar interrupt controller support
>   dt-bindings: interrupt-controller: Add MStar interrupt controller

Once the binding gets approved, I'll queue this for 5.10.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
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: Marc Zyngier <maz@kernel.org>
To: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
Cc: <robh+dt@kernel.org>, <alix.wu@mediatek.com>, <daniel@0x0f.com>,
	<devicetree@vger.kernel.org>, <jason@lakedaemon.net>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
	<tglx@linutronix.de>, <yj.chiang@mediatek.com>
Subject: Re: [PATCH v3 0/2] Add MStar interrupt controller support
Date: Sun, 13 Sep 2020 16:59:17 +0100	[thread overview]
Message-ID: <87lfhdr7l6.wl-maz@kernel.org> (raw)
In-Reply-To: <20200902063344.1852-1-mark-pk.tsai@mediatek.com>

On Wed, 02 Sep 2020 07:33:42 +0100,
Mark-PK Tsai <mark-pk.tsai@mediatek.com> wrote:
> 
> MStar contain a legacy interrupt controller that routes interrupts
> to the GIC. SigmaStar and Mediatek TV SoCs also have this interrupt
> controller IP.
> 
> Mark-PK Tsai (2):
>   irqchip: irq-mst: Add MStar interrupt controller support
>   dt-bindings: interrupt-controller: Add MStar interrupt controller

Once the binding gets approved, I'll queue this for 5.10.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  parent reply	other threads:[~2020-09-13 15:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  6:33 [PATCH v3 0/2] Add MStar interrupt controller support Mark-PK Tsai
2020-09-02  6:33 ` Mark-PK Tsai
2020-09-02  6:33 ` Mark-PK Tsai
2020-09-02  6:33 ` [PATCH v3 1/2] irqchip: irq-mst: " Mark-PK Tsai
2020-09-02  6:33   ` Mark-PK Tsai
2020-09-02  6:33   ` Mark-PK Tsai
2020-10-11 17:57   ` [tip: irq/core] irqchip/irq-mst: " tip-bot2 for Mark-PK Tsai
2020-09-02  6:33 ` [PATCH v3 2/2] dt-bindings: interrupt-controller: Add MStar interrupt controller Mark-PK Tsai
2020-09-02  6:33   ` Mark-PK Tsai
2020-09-02  6:33   ` Mark-PK Tsai
2020-09-02  6:52   ` [PATCH " Mark-PK Tsai
2020-09-02  6:52     ` Mark-PK Tsai
2020-09-02  6:52     ` Mark-PK Tsai
2020-09-14 20:07   ` [PATCH v3 " Rob Herring
2020-09-14 20:07     ` Rob Herring
2020-09-14 20:07     ` Rob Herring
2020-10-11 17:57   ` [tip: irq/core] " tip-bot2 for Mark-PK Tsai
2020-09-13 15:59 ` Marc Zyngier [this message]
2020-09-13 15:59   ` [PATCH v3 0/2] Add MStar interrupt controller support Marc Zyngier
2020-09-13 15:59   ` 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=87lfhdr7l6.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=alix.wu@mediatek.com \
    --cc=daniel@0x0f.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark-pk.tsai@mediatek.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yj.chiang@mediatek.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 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.