linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
To: Shawn Lin <shawn.lin@rock-chips.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	Gustavo Pimentel <gustavo.pimentel@synopsys.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [RFC PATCH] PCI: designware: Skip allocating own MSI domain if using external MSI domain
Date: Tue, 13 Nov 2018 05:45:35 +0000	[thread overview]
Message-ID: <9a724bae-e886-8c11-4b02-e67009cc387c@synopsys.com> (raw)
In-Reply-To: <1540435647-134674-1-git-send-email-shawn.lin@rock-chips.com>

Hi Shawn,

I'd suggest to change the designware by dwc on the patch title.

On 25/10/2018 03:47, Shawn Lin wrote:
> On some platform, external MSI domain is using instead of the one
> created by designware driver. For instance, if using GIC-V3-ITS
> as a MSI domain, we only need set msi-map in the devicetree but
> never need any bit in the designware driver to handle MSI stuff.
> So skip allocating its own MSI domain for that case.
> 
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
> 
> ---
> 
>  drivers/pci/controller/dwc/pcie-designware-host.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
> index 29a0575..39254b1 100644
> --- a/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ b/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -278,6 +278,10 @@ int dw_pcie_allocate_domains(struct pcie_port *pp)
>  		return -ENOMEM;
>  	}
>  
> +	/* Rely on the external MSI domain */
> +	if (device_property_read_bool(dev, "msi-map"))
> +		return 0;
> +

I would suggest to read this property only in the init of the host and
configuring it in a Boolean variable to be created in the pp structure and use
it to verify the feature presence or not.

>  	pp->msi_domain = pci_msi_create_irq_domain(fwnode,
>  						   &dw_pcie_msi_domain_info,
>  						   pp->irq_domain);
> @@ -433,7 +437,8 @@ int dw_pcie_host_init(struct pcie_port *pp)
>  	if (ret)
>  		pci->num_viewport = 2;
>  
> -	if (IS_ENABLED(CONFIG_PCI_MSI)) {
> +	if (IS_ENABLED(CONFIG_PCI_MSI) &&
> +	    !device_property_read_bool(dev, "msi-map")) {

You could use the previous boolean variable here also.

>  		/*
>  		 * If a specific SoC driver needs to change the
>  		 * default number of vectors, it needs to implement
> 

You should protect the dw_pcie_free_msi(), since it uses the pp->msi_domain and
pp->msi_irq also, maybe using the boolean variable also.

Regards,
Gustavo

  reply	other threads:[~2018-11-13  5:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  2:47 [RFC PATCH] PCI: designware: Skip allocating own MSI domain if using external MSI domain Shawn Lin
2018-11-13  5:45 ` Gustavo Pimentel [this message]
2018-11-13  6:21   ` Shawn Lin

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=9a724bae-e886-8c11-4b02-e67009cc387c@synopsys.com \
    --to=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marc.zyngier@arm.com \
    --cc=shawn.lin@rock-chips.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).