From: Marek Vasut <marek.vasut@gmail.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH V4] PCI: rcar: Add L1 link state fix into data abort hook
Date: Tue, 8 Dec 2020 18:45:34 +0100 [thread overview]
Message-ID: <529ff24a-dcb5-6c9e-2825-b2fbd0fbcd70@gmail.com> (raw)
In-Reply-To: <20201208101823.GA30579@e121166-lin.cambridge.arm.com>
On 12/8/20 11:18 AM, Lorenzo Pieralisi wrote:
[...]
>>> I suppose a fault on multiple cores can happen simultaneously, if it
>>> does this may not work well either - I assume all config/io/mem would
>>> trigger a fault.
>>>
>>> As I mentioned in my reply to v1, is there a chance we can move
>>> this quirk into config accessors (if the PM_ENTER_L1_DLLP is
>>> subsequent to a write into PMCSR to programme a D state) ?
>>
>> I don't think we can, since the userspace can do such a config space write
>> with e.g. setpci and then this fixup is still needed.
>
>
> Userspace goes via the kernel config accessors anyway, right ?
As far as I can tell, you can just write the register with devmem, so
no. You cannot assume everything will go through the accessors. I don't
think setpci does either.
> I would like to avoid having arch specific hooks in PCI drivers so
> if we can work around it somehow it is much better.
I think we had this discussion before, which ultimately led to hiding
the workaround in ATF on Gen3. On Gen2, there is no ATF, so the work
around must be in Linux.
> I can still merge this patch this week but I would like to explore
> alternatives before committing it.
Please merge it as-is.
next prev parent reply other threads:[~2020-12-08 17:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 12:04 [PATCH V4] PCI: rcar: Add L1 link state fix into data abort hook marek.vasut
2020-10-17 14:03 ` Geert Uytterhoeven
2020-11-19 17:35 ` Lorenzo Pieralisi
2020-11-29 13:05 ` Marek Vasut
2020-12-08 10:18 ` Lorenzo Pieralisi
2020-12-08 17:45 ` Marek Vasut [this message]
2020-12-08 17:52 ` Geert Uytterhoeven
2020-12-08 16:40 ` Bjorn Helgaas
2020-12-08 18:05 ` Marek Vasut
2020-12-08 18:46 ` Bjorn Helgaas
2020-12-10 12:12 ` Lorenzo Pieralisi
2020-12-12 19:12 ` Marek Vasut
2020-12-14 17:13 ` Lorenzo Pieralisi
2020-12-16 17:52 ` Marek Vasut
2020-12-12 19:10 ` Marek Vasut
2020-12-14 20:38 ` Bjorn Helgaas
2020-12-16 17:56 ` Marek Vasut
2020-12-16 18:20 ` Bjorn Helgaas
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=529ff24a-dcb5-6c9e-2825-b2fbd0fbcd70@gmail.com \
--to=marek.vasut@gmail.com \
--cc=bhelgaas@google.com \
--cc=geert+renesas@glider.be \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=wsa@the-dreams.de \
--cc=yoshihiro.shimoda.uh@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).