All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: shawnguo@kernel.org, linux@rasmusvillemoes.dk,
	leoyang.li@nxp.com, mark.rutland@arm.com, zhiqiang.hou@nxp.com,
	Biwen Li <biwen.li@oss.nxp.com>,
	robh+dt@kernel.org, tglx@linutronix.de, lenb@kernel.org,
	John Garry <john.garry@huawei.com>,
	martin.petersen@oracle.com, jejb@linux.ibm.com,
	rjw@rjwysocki.net, gregkh@linuxfoundation.org
Cc: xiaobo.xie@nxp.com, Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Biwen Li <biwen.li@nxp.com>,
	linux-kernel@vger.kernel.org, jiafei.pan@nxp.com,
	linuxarm@huawei.com, linux-scsi@vger.kernel.org, dwagner@suse.de,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v5 0/5] Support managed interrupts for platform devices
Date: Fri, 11 Dec 2020 15:01:36 +0000	[thread overview]
Message-ID: <160769813659.482133.15424390769079423897.b4-ty@kernel.org> (raw)
In-Reply-To: <1606905417-183214-1-git-send-email-john.garry@huawei.com>

On Wed, 2 Dec 2020 18:36:52 +0800, John Garry wrote:
> So far, managed interrupts are only used for PCI MSIs. This series adds
> platform device support for managed interrupts. Initially this topic was
> discussed at [0].
> 
> The method to enable managed interrupts is to allocate a group of IRQs for
> the device, and then switch the interrupts to managed - this is done
> through new function irq_update_affinity_desc().
> 
> [...]

Applied to irq/irqchip-next, thanks!

[1/5] genirq/affinity: Add irq_update_affinity_desc()
      commit: 1d3aec89286254487df7641c30f1b14ad1d127a5
[2/5] resource: Add irqresource_disabled()
      commit: 9806731db684a475ade1e95d166089b9edbd9da3
[3/5] ACPI: Drop acpi_dev_irqresource_disabled()
      commit: 1c3f69b4543af0aad514c127298e5ea40392575d
[4/5] Driver core: platform: Add devm_platform_get_irqs_affinity()
      commit: e15f2fa959f2cce8a05e8e3a596e75d068cd42c5

Please route patch 5 via the SCSI tree when possible.

Cheers,

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



WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: shawnguo@kernel.org, linux@rasmusvillemoes.dk,
	leoyang.li@nxp.com, mark.rutland@arm.com, zhiqiang.hou@nxp.com,
	Biwen Li <biwen.li@oss.nxp.com>,
	robh+dt@kernel.org, tglx@linutronix.de, lenb@kernel.org,
	John Garry <john.garry@huawei.com>,
	martin.petersen@oracle.com, jejb@linux.ibm.com,
	rjw@rjwysocki.net, gregkh@linuxfoundation.org
Cc: devicetree@vger.kernel.org, dwagner@suse.de,
	linux-scsi@vger.kernel.org, Biwen Li <biwen.li@nxp.com>,
	Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
	linuxarm@huawei.com, linux-kernel@vger.kernel.org,
	xiaobo.xie@nxp.com, linux-acpi@vger.kernel.org,
	jiafei.pan@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/5] Support managed interrupts for platform devices
Date: Fri, 11 Dec 2020 15:01:36 +0000	[thread overview]
Message-ID: <160769813659.482133.15424390769079423897.b4-ty@kernel.org> (raw)
In-Reply-To: <1606905417-183214-1-git-send-email-john.garry@huawei.com>

On Wed, 2 Dec 2020 18:36:52 +0800, John Garry wrote:
> So far, managed interrupts are only used for PCI MSIs. This series adds
> platform device support for managed interrupts. Initially this topic was
> discussed at [0].
> 
> The method to enable managed interrupts is to allocate a group of IRQs for
> the device, and then switch the interrupts to managed - this is done
> through new function irq_update_affinity_desc().
> 
> [...]

Applied to irq/irqchip-next, thanks!

[1/5] genirq/affinity: Add irq_update_affinity_desc()
      commit: 1d3aec89286254487df7641c30f1b14ad1d127a5
[2/5] resource: Add irqresource_disabled()
      commit: 9806731db684a475ade1e95d166089b9edbd9da3
[3/5] ACPI: Drop acpi_dev_irqresource_disabled()
      commit: 1c3f69b4543af0aad514c127298e5ea40392575d
[4/5] Driver core: platform: Add devm_platform_get_irqs_affinity()
      commit: e15f2fa959f2cce8a05e8e3a596e75d068cd42c5

Please route patch 5 via the SCSI tree when possible.

Cheers,

	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

  parent reply	other threads:[~2020-12-11 15:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 10:36 [PATCH v5 0/5] Support managed interrupts for platform devices John Garry
2020-12-02 10:36 ` [PATCH v5 1/5] genirq/affinity: Add irq_update_affinity_desc() John Garry
2020-12-11 14:58   ` [irqchip: irq/irqchip-next] " irqchip-bot for John Garry
2020-12-02 10:36 ` [PATCH v5 2/5] resource: Add irqresource_disabled() John Garry
2020-12-11 14:58   ` [irqchip: irq/irqchip-next] " irqchip-bot for John Garry
2020-12-02 10:36 ` [PATCH v5 3/5] ACPI: Drop acpi_dev_irqresource_disabled() John Garry
2020-12-11 14:58   ` [irqchip: irq/irqchip-next] " irqchip-bot for John Garry
2020-12-02 10:36 ` [PATCH v5 4/5] Driver core: platform: Add devm_platform_get_irqs_affinity() John Garry
2020-12-09 18:32   ` Greg KH
2020-12-09 19:04     ` John Garry
2020-12-09 19:13       ` Greg KH
2020-12-09 19:36         ` John Garry
2020-12-09 19:39         ` Marc Zyngier
2020-12-10 10:10           ` John Garry
2020-12-10 15:29           ` Greg KH
2020-12-10 16:37             ` John Garry
2020-12-11 14:58   ` [irqchip: irq/irqchip-next] driver " irqchip-bot for John Garry
2020-12-02 10:36 ` [PATCH v5 5/5] scsi: hisi_sas: Expose HW queues for v2 hw John Garry
2020-12-11 16:56   ` John Garry
2020-12-11 17:20     ` Martin K. Petersen
2020-12-11 17:33       ` John Garry
2020-12-11 15:01 ` Marc Zyngier [this message]
2020-12-11 15:01   ` [PATCH v5 0/5] Support managed interrupts for platform devices 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=160769813659.482133.15424390769079423897.b4-ty@kernel.org \
    --to=maz@kernel.org \
    --cc=biwen.li@nxp.com \
    --cc=biwen.li@oss.nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwagner@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jejb@linux.ibm.com \
    --cc=jiafei.pan@nxp.com \
    --cc=john.garry@huawei.com \
    --cc=lenb@kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=martin.petersen@oracle.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=xiaobo.xie@nxp.com \
    --cc=zhiqiang.hou@nxp.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.