On 5/20/2019 11:27 PM, Bjorn Helgaas wrote:
On Sat, May 18, 2019 at 07:28:29AM +0530, Vidya Sagar wrote:
On 5/18/2019 12:25 AM, Bjorn Helgaas wrote:
On Fri, May 17, 2019 at 11:23:36PM +0530, Vidya Sagar wrote:
On 5/17/2019 6:54 PM, Bjorn Helgaas wrote:
Do you have "lspci -vvxxx" output for
On Sat, May 18, 2019 at 07:28:29AM +0530, Vidya Sagar wrote:
> On 5/18/2019 12:25 AM, Bjorn Helgaas wrote:
> > On Fri, May 17, 2019 at 11:23:36PM +0530, Vidya Sagar wrote:
> > > On 5/17/2019 6:54 PM, Bjorn Helgaas wrote:
> > > > Do you have "lspci -vvxxx" output for the root ports handy?
> > > >
On 5/18/2019 12:25 AM, Bjorn Helgaas wrote:
On Fri, May 17, 2019 at 11:23:36PM +0530, Vidya Sagar wrote:
On 5/17/2019 6:54 PM, Bjorn Helgaas wrote:
Do you have "lspci -vvxxx" output for the root ports handy?
If there's some clue in the standard config space that would tell us
that MSI works
On Fri, May 17, 2019 at 11:23:36PM +0530, Vidya Sagar wrote:
> On 5/17/2019 6:54 PM, Bjorn Helgaas wrote:
> > Do you have "lspci -vvxxx" output for the root ports handy?
> >
> > If there's some clue in the standard config space that would tell us
> > that MSI works for some events but not others,
On 5/17/2019 6:54 PM, Bjorn Helgaas wrote:
On Fri, May 17, 2019 at 01:49:49PM +0530, Vidya Sagar wrote:
On 5/16/2019 7:04 PM, Bjorn Helgaas wrote:
On Tue, May 14, 2019 at 09:00:19AM +0530, Vidya Sagar wrote:
On 5/13/2019 12:55 PM, Christoph Hellwig wrote:
On Mon, May 13, 2019 at 10:36:13AM
On Fri, May 17, 2019 at 01:49:49PM +0530, Vidya Sagar wrote:
> On 5/16/2019 7:04 PM, Bjorn Helgaas wrote:
> > On Tue, May 14, 2019 at 09:00:19AM +0530, Vidya Sagar wrote:
> > > On 5/13/2019 12:55 PM, Christoph Hellwig wrote:
> > > > On Mon, May 13, 2019 at 10:36:13AM +0530, Vidya Sagar wrote:
> >
On 5/16/2019 7:04 PM, Bjorn Helgaas wrote:
On Tue, May 14, 2019 at 09:00:19AM +0530, Vidya Sagar wrote:
On 5/13/2019 12:55 PM, Christoph Hellwig wrote:
On Mon, May 13, 2019 at 10:36:13AM +0530, Vidya Sagar wrote:
Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs to enable drivers
using
On Tue, May 14, 2019 at 09:00:19AM +0530, Vidya Sagar wrote:
> On 5/13/2019 12:55 PM, Christoph Hellwig wrote:
> > On Mon, May 13, 2019 at 10:36:13AM +0530, Vidya Sagar wrote:
> > > Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs to enable drivers
> > > using these APIs be able to build as
On Mon, May 13, 2019 at 10:36:13AM +0530, Vidya Sagar wrote:
> Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs to enable drivers
> using these APIs be able to build as loadable modules.
>
> Signed-off-by: Vidya Sagar
Nak, as-is.
1) The argument for why this is needed is unconvincing.
On Tue, May 14, 2019 at 09:00:19AM +0530, Vidya Sagar wrote:
> There is nothing broken in Tegra194 root port as such, rather, this is more
> of software configuration choice and we are going with legacy interrupts than
> MSI interrupts (as Tegra194 doesn't support raising PME interrupts through
On 5/13/2019 12:55 PM, Christoph Hellwig wrote:
On Mon, May 13, 2019 at 10:36:13AM +0530, Vidya Sagar wrote:
Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs to enable drivers
using these APIs be able to build as loadable modules.
But this is a global setting. If you root port is
On Mon, May 13, 2019 at 10:36:13AM +0530, Vidya Sagar wrote:
> Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs to enable drivers
> using these APIs be able to build as loadable modules.
But this is a global setting. If you root port is broken you need
a per-rootport quirk instead.
Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs to enable drivers
using these APIs be able to build as loadable modules.
Signed-off-by: Vidya Sagar
---
Changes since [v5]:
* Corrected inline implementation of pcie_pme_no_msi() API
Changes since [v4]:
* None
Changes since [v3]:
* None
13 matches
Mail list logo
