From: Jingoo Han <jg1.han@samsung.com>
To: "'Bjørn Erik Nilsen'" <ben@datarespons.no>
Cc: linux-pci@vger.kernel.org, 'Mohit KUMAR' <Mohit.KUMAR@st.com>,
'Harro Haan' <hrhaan@gmail.com>, 'Marek Vasut' <marex@denx.de>,
'Pratyush Anand' <pratyush.anand@st.com>,
'Jingoo Han' <jg1.han@samsung.com>
Subject: Re: designware/imx6: question regarding MSI
Date: Thu, 23 Jan 2014 14:52:19 +0900 [thread overview]
Message-ID: <000201cf17ff$47025bf0$d50713d0$%han@samsung.com> (raw)
In-Reply-To: <25.15.01844.D5C20E25@epmailin6.samsung.com>
On Thursday, January 23, 2014 5:39 AM, Jingoo Han wrote:
>
> Im currently playing with MSI support in pci-imx6.c using Harro Haans patch [*].
>
> Are there any technical reasons why dw_pcie_msi_init cannot be called from dw_msi_setup_irq? Or rather,
> why it should not?
No, there is no special reason.
The patch (call dw_pcie_msi_init from dw_msi_setup_irq) would be
good. Thank you for your effort.
Mohit, Pratyush,
If you have different opinions, please let us know. :-)
Best regards,
Jingoo Han
>
> Im asking because I have a hotplug scenario where this little hack (call dw_pcie_msi_init from
> dw_msi_setup_irq) fixes a problem with MSI. I therefore need to understand whether it is a sensible
> hack or just crap, and more importantly; how it can be fixed properly.
>
> Scenario:
>
> (remove endpoints)
> # echo 1 > /sys/bus/pci/devices/0000:01:00.0/remove
> # echo 1 > /sys/bus/pci/devices/0000:01:00.1/remove
>
> # take fpga in and out of reset (this will mess up the configuration space of the bridge)
>
> (reset bridge)
> # echo 1 > /sys/bus/pci/devices/0000:00:00.0/reset
>
> (rescan bus)
> # echo 1 > /sys/bus/pci/rescan
>
> At this point everything works fine except MSI. With above mention hack it works like a charm.
>
> I would be grateful if someone could shed light on this. I might have missed some important details.
>
>
> Best regards,
> Bjørn Erik Nilsen
>
> [*]
>
> From: Harro Haan <hrhaan@gmail.com>
> Date: Thu, 5 Dec 2013 14:06:37 +0100
> Subject: [PATCH 2/2] PCI: imx6: add support for MSI
next parent reply other threads:[~2014-01-23 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25.15.01844.D5C20E25@epmailin6.samsung.com>
2014-01-23 5:52 ` Jingoo Han [this message]
2014-01-23 6:51 ` designware/imx6: question regarding MSI Pratyush Anand
[not found] ` <52e1335a.8917980a.31fa.ffffd7a8SMTPIN_ADDED_MISSING@mx.google.com>
2014-01-23 17:32 ` Harro Haan
[not found] ` <6b747b65-ef6c-4f39-b61d-f534c981c98f@CH1EHSMHS003.ehs.local>
2014-01-24 8:09 ` Hong-Xing.Zhu
[not found] ` <56523137843406465091127182657491@psmtp.com>
2014-01-24 6:48 ` Pratyush Anand
[not found] ` <8E.DE.30335.83C29E25@epmailin2.samsung.com>
2014-02-03 9:28 ` Jingoo Han
2014-02-03 9:55 ` Jingoo Han
[not found] ` <C3.BD.30335.F2DBFE25@epmailin2.samsung.com>
2014-02-04 4:40 ` Jingoo Han
2014-02-05 3:13 ` Marek Vasut
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='000201cf17ff$47025bf0$d50713d0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=Mohit.KUMAR@st.com \
--cc=ben@datarespons.no \
--cc=hrhaan@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=marex@denx.de \
--cc=pratyush.anand@st.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).