public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Damien Le Moal" <dlemoal@kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: dwc: Reject a negative nr_irqs value in dw_pcie_edma_irq_verify()
Date: Tue, 31 Dec 2024 21:21:58 +0530	[thread overview]
Message-ID: <20241231155158.5edodo2r5zar3tfe@thinkpad> (raw)
In-Reply-To: <20241220072328.351329-2-cassel@kernel.org>

On Fri, Dec 20, 2024 at 08:23:29AM +0100, Niklas Cassel wrote:
> Platforms that do not have (one or more) dedicated IRQs for the eDMA
> need to set nr_irqs to a non-zero value in their DWC glue driver.
> 
> Platforms that do have (one or more) dedicated IRQs do not need to
> initialize nr_irqs. DWC common code will automatically set nr_irqs.
> 
> Since a glue driver can initialize nr_irqs, dw_pcie_edma_irq_verify()
> should verify that nr_irqs, if non-zero, is a valid value. Thus, add a
> check in dw_pcie_edma_irq_verify() to reject a negative nr_irqs value.
> 

Why can't we make dw_edma_chip::nr_irqs unsigned?

- Mani

> This fixes the following build warning when compiling with W=1:
> 
> drivers/pci/controller/dwc/pcie-designware.c: In function ‘dw_pcie_edma_detect’:
> drivers/pci/controller/dwc/pcie-designware.c:989:50: warning: ‘%d’ directive output may be truncated writing between 1 and 11 bytes into a region of size 3 [-Wformat-truncation=]
>   989 |                 snprintf(name, sizeof(name), "dma%d", pci->edma.nr_irqs);
>       |                                                  ^~
> 
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> ---
>  drivers/pci/controller/dwc/pcie-designware.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/pci/controller/dwc/pcie-designware.c b/drivers/pci/controller/dwc/pcie-designware.c
> index 3c683b6119c3..d7f695d5dbc4 100644
> --- a/drivers/pci/controller/dwc/pcie-designware.c
> +++ b/drivers/pci/controller/dwc/pcie-designware.c
> @@ -978,6 +978,8 @@ static int dw_pcie_edma_irq_verify(struct dw_pcie *pci)
>  		return 0;
>  	else if (pci->edma.nr_irqs > 1)
>  		return pci->edma.nr_irqs != ch_cnt ? -EINVAL : 0;
> +	else if (pci->edma.nr_irqs < 0)
> +		return -EINVAL;
>  
>  	ret = platform_get_irq_byname_optional(pdev, "dma");
>  	if (ret > 0) {
> -- 
> 2.47.1
> 

-- 
மணிவண்ணன் சதாசிவம்

  reply	other threads:[~2024-12-31 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  7:23 [PATCH] PCI: dwc: Reject a negative nr_irqs value in dw_pcie_edma_irq_verify() Niklas Cassel
2024-12-31 15:51 ` Manivannan Sadhasivam [this message]
2024-12-31 18:13   ` Niklas Cassel
2024-12-31 18:49     ` Manivannan Sadhasivam
2025-01-02 10:57       ` Niklas Cassel

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=20241231155158.5edodo2r5zar3tfe@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=robh@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