public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Brian Norris <briannorris@chromium.org>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
	"Jingoo Han" <jingoohan1@gmail.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Marc Zyngier" <maz@kernel.org>
Subject: Re: [PATCH] PCI: dwc: Use level-triggered handler for MSI IRQs
Date: Sat, 4 Jan 2025 15:39:23 +0530	[thread overview]
Message-ID: <20250104100923.67tmfgiuyu2h7zzd@thinkpad> (raw)
In-Reply-To: <Z3ho7eJMWvAy3HHC@google.com>

On Fri, Jan 03, 2025 at 02:47:09PM -0800, Brian Norris wrote:

[...]

> > Oh, and it would be awesome if we can motivate this patch by mentioning
> > an actual problem it can avoid.
> > 
> > It sounds like there really *is* a problem at least in some
> > topologies, so I think we should describe that problem before
> > explaining why we haven't seen it yet.
> 
> Yeah, that's probably a good idea ... I'm still working out the nature
> of a problem I'm dealing with here, but it has to do with when (due to
> HW bugs) I have to configure the parent interrupt (GIC) as
> edge-triggered. It turns out this change alone doesn't resolve all my
> problems, but:
> 
> (a) I was hoping to get feedback on whether this change is sensible
>     regardless of the adjacent HW bug I'm dealing with (I think it is);
>     and

This patch alone (with your proposed commit message change) makes sense to me.
Since DWC MSI controller is a hierarchial interrupt controller and most of the
designs chose to use level triggered SPI to signal GIC, we never had to face an
issue. GIC would mask the interrupt first and then unmask it after handling. So
even if the DWC MSI is level/edge triggered, the behavior would mostly be the
same.

But we should model the interrupt as per the hardware design. So your patch is
doing the right thing.

> (b) I don't think I have a great publishable explanation of my HW bug(s)
>     yet.
> 

This is not a blocker for this patch IMO.

> I understand (b) is not really a great situation for public review and
> would understand if that delays/defers any action here. But I'm also not
> really an IRQ expert (though I have to dabble quite a lot) and am
> interested in (a) still.
> 
> (If it helps, I can try to summarize the above in a commit message, even
> if it's still a bit vague.)
> 

Your bug is not strictly relevant to this patch. Quoting the spec reference and
changing the commit message as per Bjorn's suggestion is enough.

- Mani

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

      reply	other threads:[~2025-01-04 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 21:12 [PATCH] PCI: dwc: Use level-triggered handler for MSI IRQs Brian Norris
2024-12-30 17:11 ` Manivannan Sadhasivam
2025-01-03  1:43   ` Brian Norris
2025-01-03 17:49     ` Bjorn Helgaas
2025-01-03 17:58       ` Bjorn Helgaas
2025-01-03 22:47         ` Brian Norris
2025-01-04 10:09           ` 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=20250104100923.67tmfgiuyu2h7zzd@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=briannorris@chromium.org \
    --cc=helgaas@kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=maz@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