From: "Pali Rohár" <pali@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Andrew Murray" <amurray@thegoodpenguin.co.uk>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Marek Behún" <marek.behun@nic.cz>,
"Remi Pommarel" <repk@triplefau.lt>,
"Tomasz Maciej Nowak" <tmn505@gmail.com>,
Xogium <contact@xogium.me>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] PCI: aardvark: Don't touch PCIe registers if no card connected
Date: Tue, 14 Jul 2020 09:38:50 +0200 [thread overview]
Message-ID: <20200714073850.rvuknigpj3jt7kp4@pali> (raw)
In-Reply-To: <20200713164140.GA29307@e121166-lin.cambridge.arm.com>
On Monday 13 July 2020 17:41:40 Lorenzo Pieralisi wrote:
> On Mon, Jul 13, 2020 at 04:50:03PM +0200, Pali Rohár wrote:
> > On Monday 13 July 2020 12:23:25 Lorenzo Pieralisi wrote:
> > > I will go over the thread again but I suspect I can merge the patch even
> > > though I still believe there is work to be done to understand the issue
> > > we are facing.
> >
> > Just to note that pci-mvebu.c also checks if pcie link is up before
> > trying to access the real PCIe interface registers, similarly as in my
> > patch.
>
> I understand - that does not change my opinion though, the link check
> is just a workaround, it'd be best if we pinpoint the real issue which
> is likely to a HW one.
Lorenzo, if you have an idea how to debug this issue or if you would
like to see some test results, let me know. I can do some tests, but I
currently really do not know more then what I wrote in previous emails.
In my opinion, problem is in HW which Marvell has not documented nor
proved that it exists. Other option is that problem is in Compex card
which can be triggered only by Marvell aardvark HW.
WARNING: multiple messages have this Message-ID (diff)
From: "Pali Rohár" <pali@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "Tomasz Maciej Nowak" <tmn505@gmail.com>,
linux-pci@vger.kernel.org, Xogium <contact@xogium.me>,
linux-kernel@vger.kernel.org, "Marek Behún" <marek.behun@nic.cz>,
"Remi Pommarel" <repk@triplefau.lt>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-arm-kernel@lists.infradead.org,
"Andrew Murray" <amurray@thegoodpenguin.co.uk>
Subject: Re: [PATCH v3] PCI: aardvark: Don't touch PCIe registers if no card connected
Date: Tue, 14 Jul 2020 09:38:50 +0200 [thread overview]
Message-ID: <20200714073850.rvuknigpj3jt7kp4@pali> (raw)
In-Reply-To: <20200713164140.GA29307@e121166-lin.cambridge.arm.com>
On Monday 13 July 2020 17:41:40 Lorenzo Pieralisi wrote:
> On Mon, Jul 13, 2020 at 04:50:03PM +0200, Pali Rohár wrote:
> > On Monday 13 July 2020 12:23:25 Lorenzo Pieralisi wrote:
> > > I will go over the thread again but I suspect I can merge the patch even
> > > though I still believe there is work to be done to understand the issue
> > > we are facing.
> >
> > Just to note that pci-mvebu.c also checks if pcie link is up before
> > trying to access the real PCIe interface registers, similarly as in my
> > patch.
>
> I understand - that does not change my opinion though, the link check
> is just a workaround, it'd be best if we pinpoint the real issue which
> is likely to a HW one.
Lorenzo, if you have an idea how to debug this issue or if you would
like to see some test results, let me know. I can do some tests, but I
currently really do not know more then what I wrote in previous emails.
In my opinion, problem is in HW which Marvell has not documented nor
proved that it exists. Other option is that problem is in Compex card
which can be triggered only by Marvell aardvark HW.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-14 7:38 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 14:31 [PATCH] PCI: aardvark: Don't touch PCIe registers if no card connected Pali Rohár
2020-05-28 14:31 ` Pali Rohár
2020-05-28 16:26 ` Bjorn Helgaas
2020-05-28 16:26 ` Bjorn Helgaas
2020-05-28 16:38 ` Pali Rohár
2020-05-28 16:38 ` Pali Rohár
2020-05-28 16:49 ` Bjorn Helgaas
2020-05-28 16:49 ` Bjorn Helgaas
2020-05-29 8:30 ` Pali Rohár
2020-05-29 8:30 ` Pali Rohár
2020-06-30 12:31 ` Pali Rohár
2020-06-30 12:31 ` Pali Rohár
2020-06-30 13:51 ` Bjorn Helgaas
2020-06-30 13:51 ` Bjorn Helgaas
2020-06-30 14:04 ` Pali Rohár
2020-06-30 14:04 ` Pali Rohár
2020-06-30 14:58 ` Bjorn Helgaas
2020-06-30 14:58 ` Bjorn Helgaas
2020-07-01 8:08 ` Pali Rohár
2020-07-01 8:08 ` Pali Rohár
2020-07-01 8:20 ` [PATCH v2] " Pali Rohár
2020-07-01 8:20 ` Pali Rohár
2020-07-01 21:34 ` Bjorn Helgaas
2020-07-01 21:34 ` Bjorn Helgaas
2020-07-02 8:23 ` Pali Rohár
2020-07-02 8:23 ` Pali Rohár
2020-07-02 8:30 ` [PATCH v3] " Pali Rohár
2020-07-02 8:30 ` Pali Rohár
2020-07-09 11:35 ` Lorenzo Pieralisi
2020-07-09 11:35 ` Lorenzo Pieralisi
2020-07-09 12:22 ` Pali Rohár
2020-07-09 12:22 ` Pali Rohár
2020-07-09 14:47 ` Lorenzo Pieralisi
2020-07-09 14:47 ` Lorenzo Pieralisi
2020-07-09 15:09 ` Pali Rohár
2020-07-09 15:09 ` Pali Rohár
2020-07-10 9:18 ` Lorenzo Pieralisi
2020-07-10 9:18 ` Lorenzo Pieralisi
2020-07-10 15:44 ` Pali Rohár
2020-07-10 15:44 ` Pali Rohár
2020-07-10 16:08 ` Bjorn Helgaas
2020-07-10 16:08 ` Bjorn Helgaas
2020-07-10 19:30 ` Pali Rohár
2020-07-10 19:30 ` Pali Rohár
2020-07-10 20:08 ` Bjorn Helgaas
2020-07-10 20:08 ` Bjorn Helgaas
2020-07-13 8:27 ` Pali Rohár
2020-07-13 8:27 ` Pali Rohár
2020-07-13 11:23 ` Lorenzo Pieralisi
2020-07-13 11:23 ` Lorenzo Pieralisi
2020-07-13 14:50 ` Pali Rohár
2020-07-13 14:50 ` Pali Rohár
2020-07-13 16:41 ` Lorenzo Pieralisi
2020-07-13 16:41 ` Lorenzo Pieralisi
2020-07-14 7:38 ` Pali Rohár [this message]
2020-07-14 7:38 ` Pali Rohár
2020-07-15 12:17 ` Pali Rohár
2020-07-15 12:17 ` Pali Rohár
2020-07-15 16:21 ` Lorenzo Pieralisi
2020-07-15 16:21 ` Lorenzo Pieralisi
2020-07-21 8:57 ` Pali Rohár
2020-07-21 8:57 ` Pali Rohár
2020-07-21 10:48 ` Lorenzo Pieralisi
2020-07-21 10:48 ` Lorenzo Pieralisi
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=20200714073850.rvuknigpj3jt7kp4@pali \
--to=pali@kernel.org \
--cc=amurray@thegoodpenguin.co.uk \
--cc=bhelgaas@google.com \
--cc=contact@xogium.me \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marek.behun@nic.cz \
--cc=repk@triplefau.lt \
--cc=thomas.petazzoni@bootlin.com \
--cc=tmn505@gmail.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.