All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luís Mendes" <luis.p.mendes@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: Regression with commit PCI: mvebu: Convert to PCI emulated bridge config space
Date: Tue, 18 Dec 2018 15:42:34 +0000	[thread overview]
Message-ID: <CAEzXK1ryTQ5sbUSuZoq36ss=Z7ewLegaxsXtvsNOGqHyTQibmg@mail.gmail.com> (raw)
In-Reply-To: <20181218153404.45b038cf@windsurf>

Hi Thomas,

Thanks a lot for your quick reply and patch, but unfortunately the
problem remains the same with the patch applied.

How can I help to further pin down the issue?

Regards,
Luís

---
Luís Mendes, Researcher, Instituto Superior Técnico
Hardware and Software engineer
http://tecnico.ulisboa.pt/

On Tue, Dec 18, 2018 at 2:34 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello Luis,
>
> On Tue, 18 Dec 2018 14:47:02 +0100, Thomas Petazzoni wrote:
>
> > Thanks for the bug report! I have an idea of what could be causing
> > this, I've cooked a patch, I'm doing a build test. I of course won't be
> > able to test it as I don't have amdgpu hardware, but I'll share the
> > patch with you for testing.
>
> Could you try the below patch:
>
> diff --git a/drivers/pci/controller/pci-mvebu.c b/drivers/pci/controller/pci-mvebu.c
> index fa0fc46edb0c..62468415e063 100644
> --- a/drivers/pci/controller/pci-mvebu.c
> +++ b/drivers/pci/controller/pci-mvebu.c
> @@ -469,6 +469,23 @@ mvebu_pci_bridge_emul_pcie_conf_read(struct pci_bridge_emul *bridge,
>         return PCI_BRIDGE_EMUL_HANDLED;
>  }
>
> +static pci_bridge_emul_read_status_t
> +mvebu_pci_bridge_emul_base_conf_read(struct pci_bridge_emul *bridge,
> +                                    int reg, u32 *value)
> +{
> +       switch(reg) {
> +       case PCI_ROM_ADDRESS1:
> +               /* We don't support the PCI ROM mechanism */
> +               *value = 0;
> +               break;
> +
> +       default:
> +               return PCI_BRIDGE_EMUL_NOT_HANDLED;
> +       }
> +
> +       return PCI_BRIDGE_EMUL_HANDLED;
> +}
> +
>  static void
>  mvebu_pci_bridge_emul_base_conf_write(struct pci_bridge_emul *bridge,
>                                       int reg, u32 old, u32 new, u32 mask)
> @@ -555,6 +572,7 @@ mvebu_pci_bridge_emul_pcie_conf_write(struct pci_bridge_emul *bridge,
>  }
>
>  struct pci_bridge_emul_ops mvebu_pci_bridge_emul_ops = {
> +       .read_base = mvebu_pci_bridge_emul_base_conf_read,
>         .write_base = mvebu_pci_bridge_emul_base_conf_write,
>         .read_pcie = mvebu_pci_bridge_emul_pcie_conf_read,
>         .write_pcie = mvebu_pci_bridge_emul_pcie_conf_write,
>
> If that fixes the problem for you, I'll send it as a proper patch with
> a commit log that explains the issue.
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

  reply	other threads:[~2018-12-18 15:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEzXK1o9L-bVRGBpAo+a_wYqXZh6_zuebF221Bd8=b-DTL1Q9g@mail.gmail.com>
     [not found] ` <CAEzXK1po4ik1oHdwVvVMWEqh8KMdAMY7sxv9OR2bYs54qV6EyA@mail.gmail.com>
2018-12-18 13:42   ` Fwd: Regression with commit PCI: mvebu: Convert to PCI emulated bridge config space Luís Mendes
2018-12-18 13:47 ` Thomas Petazzoni
2018-12-18 14:34   ` Thomas Petazzoni
2018-12-18 15:42     ` Luís Mendes [this message]
2018-12-18 20:37       ` Thomas Petazzoni
2018-12-18 23:13         ` Luís Mendes
2019-01-08 10:48           ` Thomas Petazzoni
     [not found]             ` <CAEzXK1oQd1YNZ5pyNXA76h-3CbBRxmTke=Z-SRusyfqL=Wd8eA@mail.gmail.com>
2019-01-09  8:15               ` Thomas Petazzoni
     [not found]                 ` <CAEzXK1oHqOb3pojfX7JqrirxjOFj=UZZfi6tNNO4y6yC3u9LAA@mail.gmail.com>
2019-02-04 11:09                   ` Luís Mendes
2019-02-12 13:41                     ` Thomas Petazzoni
2019-02-13 11:34                       ` Luís Mendes
2019-02-13 12:33                         ` Thomas Petazzoni
2019-02-13 13:24                           ` Luís Mendes

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='CAEzXK1ryTQ5sbUSuZoq36ss=Z7ewLegaxsXtvsNOGqHyTQibmg@mail.gmail.com' \
    --to=luis.p.mendes@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=thomas.petazzoni@bootlin.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 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.