From: Kishon Vijay Abraham I <kishon@ti.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Jingoo Han <jingoohan1@gmail.com>,
Joao Pinto <Joao.Pinto@synopsys.com>,
Bjorn Helgaas <bhelgaas@google.com>, <nsekhar@ti.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Xiaowei Bao <xiaowei.bao@nxp.com>,
Niklas Cassel <niklas.cassel@axis.com>
Subject: Re: [PATCH] PCI: designware-ep: Fix ->get_msi() to check MSI_EN bit
Date: Wed, 22 Nov 2017 17:24:21 +0530 [thread overview]
Message-ID: <1c958730-e50e-06ea-84b5-592e63ddeb87@ti.com> (raw)
In-Reply-To: <20171122113749.GA26278@red-moon>
Hi Lorenzo,
On Wednesday 22 November 2017 05:07 PM, Lorenzo Pieralisi wrote:
> On Wed, Nov 22, 2017 at 02:34:27PM +0530, Kishon Vijay Abraham I wrote:
>> ->get_msi() now checks MSI_EN bit in the MSI CAPABILITY register to
>> find whether the host supports MSI instead of using the
>> MSI ADDRESS in the MSI CAPABILITY register.
>
> I think that's a sensible thing to do regardless, given that I do not
> understand why 0x0 can't be a valid MSI address in the first place.
>
>> This fixes the issue with the following sequence
>> 'modprobe pci_endpoint_test' enables MSI
>> 'rmmod pci_endpoint_test' disables MSI but MSI address has a valid value
>> 'modprobe pci_endpoint_test no_msi=1' - Since MSI address has a valid
>> value (set during the previous insertion of the module), EP
MSI address is written in the MSI capabiltiy register by the host.
>
> Where is the address set ?
>
>> thinks host supports MSI.
>
> Add a Fixes: tag please.
sure.
>
>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>> ---
>> drivers/pci/dwc/pcie-designware-ep.c | 12 +++---------
>> drivers/pci/dwc/pcie-designware.h | 1 +
>> 2 files changed, 4 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/pci/dwc/pcie-designware-ep.c b/drivers/pci/dwc/pcie-designware-ep.c
>> index d53d5f168363..7c621877a939 100644
>> --- a/drivers/pci/dwc/pcie-designware-ep.c
>> +++ b/drivers/pci/dwc/pcie-designware-ep.c
>> @@ -197,20 +197,14 @@ static int dw_pcie_ep_map_addr(struct pci_epc *epc, phys_addr_t addr,
>> static int dw_pcie_ep_get_msi(struct pci_epc *epc)
>> {
>> int val;
>> - u32 lower_addr;
>> - u32 upper_addr;
>> struct dw_pcie_ep *ep = epc_get_drvdata(epc);
>> struct dw_pcie *pci = to_dw_pcie_from_ep(ep);
>>
>> - val = dw_pcie_readb_dbi(pci, MSI_MESSAGE_CONTROL);
>> - val = (val & MSI_CAP_MME_MASK) >> MSI_CAP_MME_SHIFT;
>> -
>> - lower_addr = dw_pcie_readl_dbi(pci, MSI_MESSAGE_ADDR_L32);
>> - upper_addr = dw_pcie_readl_dbi(pci, MSI_MESSAGE_ADDR_U32);
>
> I can't find code that writes these registers, see above for my
> question.
IIUC the host will write to these registers in __pci_write_msi_msg using the
configuration writes.
>
> On top of that I think that what's done the EPF test function driver in
> struct pci_epf.bind() should be undone in struct pci_epf.unbind() and I
> do not think that's happening for MSIs.
>
>> -
>> - if (!(lower_addr || upper_addr))
>> + val = dw_pcie_readw_dbi(pci, MSI_MESSAGE_CONTROL);
>
> MSI_MESSAGE_CONTROL is written in dw_pcie_ep_set_msi(), I assume a write
> to bit[0] (ie MSI_CAP_MSI_EN_MASK) is ignored - it would be good if you
> can clarify that as well please.
Do you mean dw_pcie_ep_set_msi can overwrite MSI_CAP_MSI_EN and we should avoid
that?
Thanks
Kishon
next prev parent reply other threads:[~2017-11-22 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 9:04 Kishon Vijay Abraham I
2017-11-22 11:37 ` Lorenzo Pieralisi
2017-11-22 11:54 ` Kishon Vijay Abraham I [this message]
2017-11-22 14:58 ` Lorenzo Pieralisi
2017-11-27 13:01 ` Kishon Vijay Abraham I
2017-11-27 15:32 ` Lorenzo Pieralisi
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=1c958730-e50e-06ea-84b5-592e63ddeb87@ti.com \
--to=kishon@ti.com \
--cc=Joao.Pinto@synopsys.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=niklas.cassel@axis.com \
--cc=nsekhar@ti.com \
--cc=xiaowei.bao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome