linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/3] ahci: Store irq number in struct ahci_host_priv
Date: Wed, 3 Jun 2015 14:39:05 +0900	[thread overview]
Message-ID: <20150603053905.GC20091@mtj.duckdns.org> (raw)
In-Reply-To: <1433073319-13796-3-git-send-email-rric@kernel.org>

On Sun, May 31, 2015 at 01:55:18PM +0200, Robert Richter wrote:
> From: Robert Richter <rrichter@cavium.com>
> 
> Currently, ahci supports only msi and intx. To also support msix the
> handling of the irq number need to be changed. The irq number for msix
> devices is taken from msi_list instead of pci_dev. Thus, the irq
> number of a device needs to be stored in struct ahci_host_priv now.
> This allows the host controller to be activated in a generic way.
> 
> This change is only intended for ahci drivers. For that reason the irq
> number is stored in struct ahci_host_priv used only by ahci drivers.
> Thus, the ABI changes only for ahci_host_activate(), but existing ata
> drivers (about 50) are unaffected and keep unchanged. All users of
> ahci_host_activate() have been updated.
> 
> While touching drivers/ata/libahci.c, doing a small code cleanup in
> ahci_port_start().
> 
> Signed-off-by: Robert Richter <rrichter@cavium.com>

Applied 1-2 to libata/for-4.2.

Thanks.

-- 
tejun

  reply	other threads:[~2015-06-03  5:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 11:55 [PATCH v4 0/3] AHCI: Add generic MSI-X interrupt support to SATA PCI driver Robert Richter
2015-05-31 11:55 ` [PATCH v4 1/3] ahci: Move interrupt enablement code to a separate function Robert Richter
2015-05-31 11:55 ` [PATCH v4 2/3] ahci: Store irq number in struct ahci_host_priv Robert Richter
2015-06-03  5:39   ` Tejun Heo [this message]
2015-05-31 11:55 ` [PATCH v4 3/3] AHCI: Add generic MSI-X interrupt support to SATA PCI driver Robert Richter
2015-06-03  5:44   ` Tejun Heo
2015-06-04  9:03     ` Robert Richter
2015-06-04 21:22       ` Tejun Heo

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=20150603053905.GC20091@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).