From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
kw@linux.com, kishon@kernel.org, bhelgaas@google.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 7/7] PCI: endpoint: Add PCI Endpoint function driver for MHI bus
Date: Tue, 30 May 2023 16:48:53 +0530 [thread overview]
Message-ID: <20230530111853.GH6379@thinkpad> (raw)
In-Reply-To: <dd4b1867-204d-8ee0-fcfc-29c52abddb48@kernel.org>
On Tue, May 30, 2023 at 08:37:07AM +0900, Damien Le Moal wrote:
> On 5/30/23 02:38, Manivannan Sadhasivam wrote:
> [...]
> >>> +static void pci_epf_mhi_unmap_free(struct mhi_ep_cntrl *mhi_cntrl, u64 pci_addr,
> >>> + phys_addr_t phys_addr, void __iomem *virt_addr, size_t size)
> >>> +{
> >>> + struct pci_epf_mhi *epf_mhi = container_of(mhi_cntrl, struct pci_epf_mhi, mhi_cntrl);
> >>> + struct pci_epf *epf = epf_mhi->epf;
> >>> + struct pci_epc *epc = epf->epc;
> >>> + size_t offset = pci_addr & (epc->mem->window.page_size - 1);
> >>> +
> >>> + pci_epc_unmap_addr(epc, epf->func_no, epf->vfunc_no, phys_addr - offset);
> >>> + pci_epc_mem_free_addr(epc, phys_addr - offset, virt_addr - offset, size + offset);
> >>> +}
> >>> +
> >>> +static void pci_epf_mhi_raise_irq(struct mhi_ep_cntrl *mhi_cntrl, u32 vector)
> >>> +{
> >>> + struct pci_epf_mhi *epf_mhi = container_of(mhi_cntrl, struct pci_epf_mhi, mhi_cntrl);
> >>> + struct pci_epf *epf = epf_mhi->epf;
> >>> + struct pci_epc *epc = epf->epc;
> >>> +
> >>> + /*
> >>> + * Vector is incremented by 1 here as the DWC core will decrement it before
> >>> + * writing to iATU.
> >>
> >> This isn't OK. It is an API, you can't write code explicitly relying on
> >> the underlying implementation. I assume the API is not well specified,
> >> that's why we need these tricks ?
> >>
> >
> > Well, this is not an API issue but rather an implementation detail of the DWC EP
> > core driver. The DWC driver expects the interrupt vectors to be 1 based, so it
> > decrements it before writing to the MSI address:
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/controller/dwc/pcie-designware-ep.c#n537
>
> Then the driver should be fixed so that this peculiarity is not visible at the
> user API level, resulting in a uniform usage of the API for all functions
> regardless of the controller being used.
>
Just checked with Kishon offline and confirmed that this is an API behavior.
I also checked other drivers and they all doing the same.
But unfortunately, this behavior is not documented in the API. Will add a patch
for that.
- Mani
> --
> Damien Le Moal
> Western Digital Research
>
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2023-05-30 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 14:42 [PATCH v4 0/7] Add support for MHI Endpoint function driver Manivannan Sadhasivam
2023-05-19 14:42 ` [PATCH v4 1/7] PCI: endpoint: Pass EPF device ID to the probe function Manivannan Sadhasivam
2023-05-19 18:11 ` [EXT] " Frank Li
2023-05-29 9:36 ` Lorenzo Pieralisi
2023-05-29 17:10 ` Manivannan Sadhasivam
2023-05-19 14:42 ` [PATCH v4 2/7] PCI: endpoint: Warn and return if EPC is started/stopped multiple times Manivannan Sadhasivam
2023-05-19 14:42 ` [PATCH v4 3/7] PCI: endpoint: Add linkdown notifier support Manivannan Sadhasivam
2023-05-19 14:42 ` [PATCH v4 4/7] PCI: endpoint: Add BME " Manivannan Sadhasivam
2023-05-19 18:19 ` [EXT] " Frank Li
2023-05-27 2:21 ` Manivannan Sadhasivam
2023-05-27 3:34 ` Frank Li
2023-05-19 14:42 ` [PATCH v4 5/7] PCI: qcom-ep: Add support for Link down notification Manivannan Sadhasivam
2023-05-19 14:42 ` [PATCH v4 6/7] PCI: qcom-ep: Add support for BME notification Manivannan Sadhasivam
2023-05-19 14:42 ` [PATCH v4 7/7] PCI: endpoint: Add PCI Endpoint function driver for MHI bus Manivannan Sadhasivam
2023-05-29 13:11 ` Lorenzo Pieralisi
2023-05-29 17:38 ` Manivannan Sadhasivam
2023-05-29 23:37 ` Damien Le Moal
2023-05-30 11:18 ` Manivannan Sadhasivam [this message]
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=20230530111853.GH6379@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bhelgaas@google.com \
--cc=dlemoal@kernel.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@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