From: Pratyush Anand <pratyush.anand@st.com>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King <linux@arm.linux.org.uk>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Richard Zhu <r65037@freescale.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Marek Vasut <marex@denx.de>, Arnd Bergmann <arnd@arndb.de>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v5 2/5] PCI: designware: refactor MSI code to work with v3.65 dw hardware
Date: Thu, 17 Jul 2014 09:01:32 +0530 [thread overview]
Message-ID: <20140717033132.GH12278@pratyush-vbox> (raw)
In-Reply-To: <1405528686-16539-3-git-send-email-m-karicheri2@ti.com>
On Thu, Jul 17, 2014 at 12:38:03AM +0800, Murali Karicheri wrote:
> Keystone PCI controller is based on v3.65 version of the DW
> PCI h/w that implements MSI controller registers in application
> space compared to the newer version. This requires updates to
> the DW core API to support the PCI controller driver based on
> this old DW hardware. Add msi_irq_set()/clear() API functions to
> allow Set/Clear MSI IRQ enable bit in the application register.
> Also the old h/w uses MSI_IRQ register in application register
> space to raise MSI IRQ to the RC from EP. Current code uses the
> standard mechanism as per PCI spec. So add another API get_msi_data()
> to get the address of this register so that common code can be
> re-used on old h/w.
>
> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
> Acked-by: Mohit Kumar <mohit.kumar@st.com>
> Acked-by: Jingoo Han <jg1.han@samsung.com>
> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>
Reviewed-by: Pratyush Anand <pratyush.anand@st.com>
next prev parent reply other threads:[~2014-07-17 3:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 16:38 [PATCH v5 0/5] Add Keystone PCIe controller driver Murali Karicheri
2014-07-16 16:38 ` [PATCH v5 1/5] PCI: designware: add rd[wr]_other_conf API Murali Karicheri
2014-07-17 3:30 ` Pratyush Anand
2014-07-16 16:38 ` [PATCH v5 2/5] PCI: designware: refactor MSI code to work with v3.65 dw hardware Murali Karicheri
2014-07-17 3:31 ` Pratyush Anand [this message]
2014-07-16 16:38 ` [PATCH v5 3/5] PCI: designware: enhance dw_pcie_host_init() to support v3.65 DW hardware Murali Karicheri
2014-07-17 3:36 ` Pratyush Anand
2014-07-17 4:18 ` Mohit KUMAR DCG
2014-07-17 15:11 ` Murali Karicheri
2014-07-17 15:04 ` Murali Karicheri
2014-07-16 16:38 ` [PATCH v5 4/5] PCI: add PCI controller for keystone PCIe h/w Murali Karicheri
2014-07-17 15:35 ` Murali Karicheri
2014-07-16 16:38 ` [PATCH v5 5/5] PCI: keystone: Update maintainer information Murali Karicheri
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=20140717033132.GH12278@pratyush-vbox \
--to=pratyush.anand@st.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m-karicheri2@ti.com \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=r65037@freescale.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.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).