All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Jingoo Han <jingoohan1@gmail.com>,
	Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Stanimir Varbanov <svarbanov@mm-sol.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Vinod Koul <vkoul@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v11 3/7] PCI: dwc: Handle MSIs routed to multiple GIC interrupts
Date: Mon, 23 May 2022 18:36:34 +0300	[thread overview]
Message-ID: <363d3be3-575d-260f-ece1-0b56b3c134ba@linaro.org> (raw)
In-Reply-To: <YoupEr0TkgEa1S+/@hovoldconsulting.com>

On 23/05/2022 18:32, Johan Hovold wrote:
> On Mon, May 23, 2022 at 06:17:19PM +0300, Dmitry Baryshkov wrote:
>> On 23/05/2022 17:02, Johan Hovold wrote:
>>> On Mon, May 23, 2022 at 04:39:56PM +0300, Dmitry Baryshkov wrote:
>>>> On 23/05/2022 10:53, Johan Hovold wrote:
>>>>> On Fri, May 20, 2022 at 09:31:10PM +0300, Dmitry Baryshkov wrote:
>>>
>>>>>> +static int dw_pcie_parse_split_msi_irq(struct pcie_port *pp)
>>>>>> +{
>>>>>> +	struct dw_pcie *pci = to_dw_pcie_from_pp(pp);
>>>>>> +	struct device *dev = pci->dev;
>>>>>> +	struct platform_device *pdev = to_platform_device(dev);
>>>>>> +	int irq;
>>>>>> +	u32 ctrl;
>>>>>> +
>>>>>> +	irq = platform_get_irq_byname_optional(pdev, split_msi_names[0]);
>>>>>> +	if (irq == -ENXIO)
>>>>>> +		return -ENXIO;
>>>>>
>>>>> You still need to check for other errors and -EPROBE_DEFER here.
>>>>
>>>> I think even the if (irq < 0) return irq; will work here.
>>>
>>> No need to print errors unless -EPROBEDEFER as you do below?
>>
>> There is no separate print for the dw_pcie_parse_split_msi_irq() errors.
> 
> I don't understand what you're referring to here.
> 
> My question is: Why would you not be printing error messages for msi0 as
> you are for msi1..msi7 in the loop below.

Yeah, this seems like a correct idea. Thank you!

> 
>>>>>> +
>>>>>> +	pp->msi_irq[0] = irq;
>>>>>> +
>>>>>> +	/* Parse as many IRQs as described in the DTS. */
>>>>>
>>>>> s/DTS/devicetree/
>>>>>
>>>>>> +	for (ctrl = 1; ctrl < MAX_MSI_CTRLS; ctrl++) {
>>>>>> +		irq = platform_get_irq_byname_optional(pdev, split_msi_names[ctrl]);
>>>>>> +		if (irq == -ENXIO)
>>>>>> +			break;
>>>>>> +		if (irq < 0)
>>>>>> +			return dev_err_probe(dev, irq,
>>>>>> +					     "Failed to parse MSI IRQ '%s'\n",
>>>>>> +					     split_msi_names[ctrl]);
>>>>>> +
>>>>>> +		pp->msi_irq[ctrl] = irq;
>>>>>> +	}
>>>>>> +
>>>>>> +	pp->num_vectors = ctrl * MAX_MSI_IRQS_PER_CTRL;
>>>>>> +
>>>>>> +	return 0;
>>>>>> +}
> 
> Johan


-- 
With best wishes
Dmitry

  reply	other threads:[~2022-05-23 15:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 18:31 [PATCH v11 0/7] PCI: qcom: Fix higher MSI vectors handling Dmitry Baryshkov
2022-05-20 18:31 ` [PATCH v11 1/7] PCI: dwc: Convert msi_irq to the array Dmitry Baryshkov
2022-05-20 18:31 ` [PATCH v11 2/7] PCI: dwc: split MSI IRQ parsing/allocation to a separate function Dmitry Baryshkov
2022-05-20 18:31 ` [PATCH v11 3/7] PCI: dwc: Handle MSIs routed to multiple GIC interrupts Dmitry Baryshkov
2022-05-23  7:53   ` Johan Hovold
2022-05-23 13:39     ` Dmitry Baryshkov
2022-05-23 14:02       ` Johan Hovold
2022-05-23 15:17         ` Dmitry Baryshkov
2022-05-23 15:32           ` Johan Hovold
2022-05-23 15:36             ` Dmitry Baryshkov [this message]
2022-05-20 18:31 ` [PATCH v11 4/7] PCI: dwc: Implement special ISR handler for split MSI IRQ setup Dmitry Baryshkov
2022-05-20 18:31 ` [PATCH v11 5/7] dt-bindings: PCI: qcom: Support additional MSI interrupts Dmitry Baryshkov
2022-05-20 18:31 ` [PATCH v11 6/7] arm64: dts: qcom: sm8250: provide " Dmitry Baryshkov
2022-05-20 18:31 ` [PATCH v11 7/7] dt-bindings: mfd: qcom,qca639x: add binding for QCA639x defvice Dmitry Baryshkov
2022-05-23  7:42 ` [PATCH v11 0/7] PCI: qcom: Fix higher MSI vectors handling Johan Hovold
2022-05-23 13:03   ` Dmitry Baryshkov

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=363d3be3-575d-260f-ece1-0b56b3c134ba@linaro.org \
    --to=dmitry.baryshkov@linaro.org \
    --cc=agross@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=johan@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=svarbanov@mm-sol.com \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.